- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This work studies how to make long videos follow a specified schedule of events. Building on existing TIE and RoTE, the author introduces Rolling Timeline Conditioning (RTC). RTC keeps scene and character descriptions available throughout generation, assigns them to the current local time window, and includes nearby actions while preserving their original start and end times.
Critical strengths
RTC addresses the problem in extending temporal conditioning to longer videos. It keeps scene and character descriptions available without making their assigned duration grow with the full video. Actions retain their original intervals, including those that continue across generation blocks. The complete system shows good long video results. The examples and the small human study favor OnTime in visual quality and continuity. Producing these longer sequences from short-sequence training is useful.
Critical weaknesses
The contribution is somewhat incremental, and RTC’s effect has not been isolated. TIE and its RoTE encoding come from prior work, with RTC as the main addition. The experiments compare complete systems, making it hard to tell how much RTC contributes. A comparison within the same model would help show what RTC itself adds. The evidence for improved action timing is mixed. The human study favors OnTime on a small, selected set of videos, while the broader timeline-following evaluation favors LongLive. The event-clip results do not settle this issue. For example, watering could look correct between 10 and 20 seconds even if it starts early or continues too long.
Questions for authors
Could the authors clarify how much RTC contributes to the reported improvements, given that much of the framework comes from prior work? It would also help to explain the mixed timing results and provide stronger evidence that OnTime follows the requested schedule more accurately. Please see the weaknesses for the specific concerns.
2 comments
Final Remarks
Dear Reviewer jDyJ,
Before the discussion period ends, we wanted to check whether our new within-model RTC ablation and full-video action-boundary metrics (AP, Time mIoU, Loc. mIoU) have addressed your questions on isolating RTC and action timing. Please let us know if anything remains unclear.
We thank Reviewer jDyJ for the constructive comments on isolating RTC and evaluating action boundaries.
Isolating RTC within the same model. We evaluate the same trained OnTime model on all 128 60-second timelines with and without RTC (where w/o RTC disables rolling conditioning and uses full-video persistent intervals), reporting all Table 1 metrics alongside our full-video temporal localization metrics:
RTC improves visual quality, motion, and timeline adherence (+0.8869 VideoReward Overall, +0.0677 TFS, +15.41% AP, +0.0988 Time mIoU). Without RTC, all action tokens remain active across the video and leak beyond their target intervals, keeping cropped-clip InternVideo2 slightly higher (-0.0047) while degrading temporal localization (Time mIoU 0.1466 vs. 0.2454).
Action-boundary accuracy and mixed timing results. Cropped-clip metrics do not penalize actions that start early or continue too long, whereas full-video TFS (Eq. 8) assigns 60% weight to frame, global, and consistency terms (F,G,C). Static LongLive obtains a higher TFS (0.4165) by generating largely static videos (MQ = 0.1297 vs. OnTime's 0.5376), avoiding drift at the cost of missing scheduled transitions (LongLive Interactive, which switches prompts, scores 0.3310 vs. OnTime's 0.3714).
To directly test start/end boundary accuracy over the full 60s video, we evaluate Action Presence (AP), Time mIoU (temporal IoU between predicted and requested action intervals, scoring missing actions as 0), and Loc. mIoU (temporal IoU over localized actions), which penalize both early onsets and late endings:
OnTime leads all baselines in both action presence (78.85%) and interval overlap (0.2454 Time mIoU, 0.3529 Loc. mIoU), more than doubling static LongLive's Time mIoU (0.0969) and aligning with the human timing evaluation in Table 2.