A timeline connects beats and moves.
DuckEMW represents tempo, the first beat, the duration and a sequence of movement segments. Playback turns those values into commands for a compatible dance policy.
Concept arrangement, not an executed performance.
Keep the policy and timeline together.
The moves and their encoding depend on the policy version. A timeline using an unsupported move is not a compatible playback input.
What can you prepare before training?
- Sketch the beat positions and movement transitions.
- Record the target policy and source revision.
- Explain the expected result for each segment.
A visual timeline editor is planned as a later site tool. This guide explains the arrangement only.
What would you like to understand next?
Keep the source, your environment and your observations together.
Before you continue
Does a dance timeline include a working policy?
No. Timing and movement planning are separate from obtaining a compatible policy and checking playback in the target environment.
Applies to: DuckEMW · emwstudio. Keep the model, image, software and driver versions together. The dated sections below retain their original verification limits.
Source checked:
Next useful guides
DuckEMW: MicroDuck Sprint & Dance Simulation Project
Explore emwstudio’s DuckEMW sprint and dance simulation project, with pinned source revisions, measurement notes and clearly stated verification limits.
DuckEMW Sprint Speed: Average vs Peak Measurements
Interpret DuckEMW simulation speed results, including reported average and upright-gated peak speed, with source revisions and measurement limits.
MicroDuck Simulator: First Walk and Public Move Loading
Walk in the official MicroDuck browser simulator, load a public policy by URL, check manifest compatibility and restore the built-in move.