- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes DRUM, a real-time humanoid dance generation framework that replaces fixed-sequence generation with streaming synthesis. Short dance segments are generated conditioned on incoming music and recently executed robot motion. The generator is further adapted with execution-feedback training (EFT), which alternates tracker-reward optimization with rehearsal on generated and executed motion histories. Experiments on FineDance and AIST++ and deployment on a real X2 humanoid demonstrate competitive dance-generation quality, real-time generation efficiency, and improved execution stability after EFT.
Critical strengths
-
The paper is well motivated. The mismatch between offline generated references and the states actually reached by a physical humanoid is an important problem for continuous robot dancing.
-
Conditioning future generation on executed motion and incorporating executed histories during post-training are well suited to the streaming deployment setting.
-
The evaluation is relatively comprehensive, including generation benchmarks, three frozen trackers, real-robot experiments, ablations, and a user study.
Critical weaknesses
Weakness
-
The real contribution over existing work is not sufficiently clear. DRUM combines streaming music-conditioned generation, tracker-based execution feedback, and executed-history rehearsal, but several of these ingredients are closely related to prior work such as DiscoForcing, RLPF, and closed-loop motion generation methods. Although the paper discusses these differences, it remains unclear how much methodological novelty lies in the specific combination and alternating optimization strategy, and which interactions between components are essential to the reported gains.
-
EFT introduces a substantial trade-off between executability and standard generation quality. In Table 1, the model before EFT consistently achieves better FID, diversity, and music-alignment metrics than the final model, particularly on AIST++. The paper acknowledges this trade-off, but it remains unclear how much degradation is necessary to achieve the reported execution gains. An analysis of intermediate training checkpoints or different EFT strengths would help clarify whether a better balance between generation quality and execution robustness is possible.
Minor Weaknesses
- The supplementary demonstrations do not provide robot-execution videos for the main competing dance-generation baselines. Since an important claim is that conventional generators produce references that are less suitable for real humanoid execution, side-by-side robot videos using the same tracker would substantially improve the visual evidence for this claim. Besides, the resolution is relatively low, which makes it difficult to inspect motion smoothness, foot contacts, and small tracking artifacts. Providing higher-resolution videos would improve the qualitative evaluation.
Questions for authors
-
What is the key contribution of DRUM beyond existing streaming generation, tracker-feedback optimization, and closed-loop motion generation methods? In particular, which component or interaction between components is essential to DRUM?
-
Table 1 shows that EFT consistently worsens several conventional generation metrics, especially FID and BAS on AIST++. How do the authors interpret this trade-off? Is this degradation intrinsic to optimizing tracker executability, or could the strength of EFT be adjusted to obtain a better Pareto trade-off between generation fidelity/music alignment and execution robustness?
-
In Table 3, reward-only training obtains lower joint error than the full model, whereas adding rehearsal improves motion quality and other execution characteristics. The paper attributes the reward-only behavior to reduced motion amplitude. How sensitive is the balance between execution accuracy and dance expressiveness to the relative weighting of reward optimization and rehearsal?
-
Since the paper reports quantitative real-robot results for EDGE and FlowerDance, could the authors provide side-by-side real-robot videos of DRUM and the main baselines under the same frozen tracker and matched music?
-
The reported 680 FPS measures generator throughput while excluding the tracker. Could the authors report the end-to-end latency of one online generation-execution-feedback cycle, including motion generation, communication, tracker inference, and the feedback update, and clarify the hardware used for the real-time deployment?