- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
The paper proposes Time Interval Encoding (TIE) for video generation with concurrent and overlapping events. Its uniform-kernel instance, RoTE, integrates rotary features over event intervals and applies self-overlap calibration, yielding a closed-form sinc-modulated encoding. The authors evaluate temporal controllability and visual quality on OmniEvents, with additional benchmark comparisons and ablations.
Critical strengths
-
The method is well-motivated and compact. The point-to-interval formulation explicitly incorporates event duration while preserving the standard attention interface. Its closed form and reduction to RoPE in the point-wise limit make the design technically coherent and potentially reusable.
-
The empirical improvements are meaningful. In Table 2, RoTE improves StoryEval over finetuning from 39.3% to 49.4% at 5 seconds and from 38.8% to 52.3% at 10 seconds. Appendix F also provides useful comparisons with alternative interval encodings, kernels, and normalization schemes.
Critical weaknesses
-
The human temporal metrics require clearer interpretation. Table A10 reports identical occurrence and TCSR scores of 96.03%, alongside lower order and overlap accuracy. Since TCSR includes relation constraints, the exact constraint sets and aggregation across videos and annotators are needed to reconcile these figures; the reported numbers alone do not establish an error. Moreover, missing-event penalties make it difficult to separate improved event coverage from more accurate temporal localization.
-
The advantage over strong interval alternatives needs uncertainty analysis. Endpoint averaging nearly matches RoTE on nDTW (0.2782 versus 0.2805), although RoTE achieves better FVD (Table A7). Without run-to-run variability estimates or matched human temporal evaluations of these alternatives, the reliability and practical significance of the smaller gains remain unclear.
-
Comparative noise robustness is insufficiently tested. Figure 7 compares perturbed RoTE with a clean-timestamp finetuned baseline. This demonstrates useful performance under noise, but does not establish lower noise sensitivity than competing encodings. Matched perturbations are needed to compare each method’s degradation from its own clean baseline.
Questions for authors
-
Could the authors provide per-type TCSR constraint counts and clarify aggregation across videos and annotators? Are absolute boundary errors computed before or after averaging signed annotations?
-
Can the authors report uncertainty and matched human temporal evaluations for RoTE versus center–length or endpoint averaging, including boundary errors on events generated by both methods?
-
Are timestamp perturbations applied during training, inference, or both? How do the competing methods degrade under the same perturbations?
Q1. Constraint counts and aggregation. For a start-time constraint, we assign a score of one if the event occurs and its absolute start-time error is at most 0.25 seconds, and zero otherwise. We score the end time separately. The human evaluation results are mainly performed on GamesEvents dataset, its event types are clear and fixed. However, the actual timestamp annotation may be hard to determine. Annotators can clearly distinguish whether an event actually occurred or if the sequence is incorrect, and they can flag instances where there is a visible temporal misalignment; however, they may be less sensitive to minor temporal discrepancies. The aggregation is the arithmetic mean of each annotators' scores. Missing-event penalties takes about 79% of the temporal error gain of TIE against Finetuned. Event Occurrence and TCSR score are identical here since all flagged temporal misalignment is less than 0.25s. However, this may involve issues such as annotator fatigue, insensitivity to the video timing, and the influence of default options.
Q2. Coverage, localization and uncertainty.
DoTE human evaluation results:
Q3. Matched noise robustness. The noise experiment perturbs timestamps at inference. Each method is trained on the original annotations. For each validation prompt, we apply the same perturbation to internal event boundaries across methods, preserve event order, hold clip endpoints fixed, and use the same generation seed.