- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
Hybrid Forcing combines a persistent linear history state with sparse sliding-window attention for streaming video generation. A staged distillation procedure, bounded relative temporal RoPE, and teacher-guided regularization support stable generation. The method reports improved quality and throughput on short and 30-second video benchmarks.
Critical strengths
-
The architecture directly addresses the complementary requirements of efficient local processing and retention of evicted history.
-
Automatic evaluation is supplemented by a human preference study and qualitative longer-duration examples.
Critical weaknesses
- The strongest long-horizon claims exceed the quantitative evidence. The primary quantitative evaluation covers 30-second videos, whereas ten-minute stability is supported mainly by examples. Fixed-suite evaluations of segment-wise quality, identity retention, repetition, and failure frequency would better substantiate the broader claim.
- History-state usefulness does not fully establish detailed long-term recall. The interventions show that historical information affects generation, but do not determine whether the state preserves specific earlier events or mainly stabilizes aggregate appearance and motion. Controlled object-reappearance or delayed-attribute-recall tasks would be informative.
- The user-study statistics contain an inconsistency. The appendix describes complete rankings of seven methods. Under the standard 1–7 ranking convention, the seven average ranks must sum to 28. However, Table 5 sums to 29.00, which cannot be explained by rounding. The ranking convention and aggregation procedure should be clarified, or the table corrected.
- The throughput measurement boundary needs clarification. It should be explicit whether the reported 29.5 FPS includes VAE decoding, text encoding, and cache reconstruction. First-chunk latency should also be reported separately from sustained throughput.
Questions for authors
-
Responses to the weaknesses.
-
And also:
- Can the authors provide anonymized ranking data and explain the average-rank inconsistency?
- How do quality and consistency evolve beyond 30 seconds on a fixed evaluation suite?
- What are the complete measurement boundaries and first-chunk latency for the throughput result?
2 comments
Thank you for recognizing our substantive responses and our candid discussion of long-term recall. We have narrowed the conclusions about long videos and DiT generation throughput on an H100. The revised text specifies that the reported 29.5 FPS includes clean KV recaching and excludes text encoding, VAE decoding, and video encoding/writing. Thank you for helping us make the scope of these conclusions more precise. We have also explicitly acknowledged this limitation in the Limitations section, noting the constraints of the base model’s capabilities and the potential need for fine-tuning on high-quality exploration-and-return data.
Given the limited time remaining and the visual similarity of some generated videos, we cannot conduct a complete new user study during the rebuttal period. We have clarified in the manuscript that some visually similar outputs received tied ranks, which our original description of complete rankings did not make explicit. And we will conduct a more comprehensive user study with an explicit protocol for handling tied rankings and report the updated results in the final version.
Responses to rebuttal
Thank the authors for the rebuttal.
There are substantive responsies and candidaly acknowledge the limiations of the long-term recall.
However, the statistical issues in user study remain unresolved, and the conclusion regarding long videos and real-time performance also need to be narrowed down.
Based on the rebuttal, the reviewer tend to keep weak accept atm.