- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
The paper relies on key observations: Models like Self Forcing are trained only on short clips, so during long rollouts their cache becomes increasingly out-of-distribution and causes color drift, structure collapse, identity changes, and fading motion. Rolling Sink addresses this by managing the cache in three ways: it reuses low-drift chunks from the initial training horizon as sink chunks, re-indexes their temporal positions so they appear recent, and uses a forward-reverse Rolling Semantics schedule so the sink content changes over time instead of remaining static. One recent chunk is always retained to preserve current local motion.
Critical strengths
I liked the honesty in the paper, which clearly separates the main contributions.
Experiments are well designed, followed the general protocol in the long video generation field. Also experiments clearly demonstrate the effect of the proposed method in preserving the details. Competitive results in 1-minute and 5-minute generations.
Critical weaknesses
There is a fundamental ambiguity in the Rolling Semantics, and I kindly ask authors to clarify the situation clearly:
Let's consider the following cache transition.
{} {}
Assume:
{}
{}
Then transitioned cache becomes:
{} = {}
I can understand the motivation behind this sink schedule. The sink becomes dynamic rather than static + there is no large jump when the traversal reaches the end of the sink bank, since the latent frames are reversed and the trajectory smoothly changes direction.
However, I kindly argue that the proposed reversed sink schedule is not working as intended in the pixel space.
The reason is that each latent frame in the Wan VAE corresponds to a 4 pixel-space frames. Importantly, the pixel frames represented by each individual latent are still ordered forward in time. Therefore, although {} looks like a temporally reversed sequence with no jump in latent space, it does not necessarily correspond to a truly reversed video in pixel space.
Example:
Suppose {} latent frames corresponds to following pixel frames.
{ }
{ }
{ }
Then {} in the cache corresponds to following structure in pixel space
{ }
which eventually creates temporal jumps entire paper attempted to avoid.
Questions for authors
The most significant issue, which is against of the main claim of the paper, is shared in Critical Weaknesses section. Unfortunately, the paper is very limited regarding the ablations of the Rolling order schedule, so we can't quite see the direct advantage of reversed rolling sink.
Apart from that, can the authors explain what causes the performance differences across different sink orders in the cache? From an information-theoretic perspective, the cache contains the same amount of information, and only the temporal ordering or recency of that information changes.
3 comments
Authors' Kind Reminder to Reviewer v5wP
Dear Reviewer v5wP,
Thank you for taking the time to review our paper and provide your valuable feedback. We have submitted detailed responses to your comments and suggestions, addressing the key points raised. As the discussion is scheduled to end on 2026-11-18, we would greatly appreciate it if you could review our responses and provide any further clarifications at your earliest convenience. Your feedback is extremely important to us.
Thank you again for your time and effort.
Best,
Authors of Submission 837
Authors' Second Kind Reminder to Reviewer v5wP (Only 1 Day Left)
Dear Reviewer v5wP,
We sincerely thank you for your time and effort for reviewing our submission, and writing your responses.
However, as the discussion deadline approaches in less than 1 day, we would greatly appreciate it if you could carefully review our latest responses and provide further clarifications at your earliest convenience. We highly value any opportunities to address any potential remaining issues, which we believe will be helpful for a higher rating. Your timely feedback is extremely important to us!
Thanks so much again for your time and effort, we deeply appearciate it!
Best,
Authors of Submission 837
Response to Reviewer v5wP
Thank you for pointing out the distinction between latent and pixel reversal. This prompted us to propose a broader version of Rolling Sink with three levels: Chunk-Level, Latent-Level (submitted version), and Pixel-Level. Please check App. J. We agree that this does not imply a reversed RGB sequence under temporal VAE compression.
We now distinguish:
The key is the train–test gap in cache behavior. During training, cached chunks and the current chunk occupy consecutive temporal positions that advance as a sliding window. Keeping early sink chunks at their original indices breaks this pattern as AR generation proceeds. Temporal re-indexing restores this positional relationship, bringing the test cache closer to its training behavior and improving performance. The Temporal Re-index ablation is in the submission's App. C, Tabs. S2-S3, and Fig. 5. The ablations in Tabs. 1-2 of the General Response keep temporal re-indexing fixed while comparing forward-only, random, fixed/random, and forward–reverse policies.
Changing sink order changes the content–position assignments. RoPE makes attention depend on these relative positions: placing chunk A closer to the current chunk than chunk B gives different conditioning from placing B closer to the current chunk than A. Advancing every index by the same offset preserves relative positions.