- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper argues that target error alone conflates genuine controller contribution with motion the causal video generator would have produced anyway, and introduces TrajectoryBench, an 80-item paired protocol that compares each guided rollout with an unguided rollout under matched prompt, seed, and initial noise, reporting both error reduction and prior transmission, the slope between guided and matched unguided displacement along the requested axis. Across ten CausVid seeds the slope is about 0.52, survives seed-by-direction fixed effects, a wrong-seed derangement control, and a tracker swap, and reappears on Causal Forcing. The authors then propose Warp Forcing, a training-free blockwise controller that warps the clean estimate inside a tracked mask, rebuilds the KV cache from corrected frames, and replans each block; subtracting drift estimated from the matched unguided preview reduces mean path error by 25 percent on CausVid and 38 percent on CF, and a preview-free online estimator matches the gain on CF while recovering about one third of it on CausVid on a single seed.
Critical strengths
- Seed-matched paired evaluation is a simple and sound way to separate control contribution from motion the model would produce anyway.
- The transmission analysis is statistically careful, with object and seed clustering, wrong-seed derangement, seed-by-direction fixed effects, and an independent tracker check.
- The measurement directly motivates the correction, and the derangement control shows that item-specific drift, not only generic drift rejection, drives part of the gain.
- Ablations on cache reconstruction, replanning, and injection step give a coherent picture of which components matter.
Critical weaknesses
- The controller is not practically competitive, as native bidirectional baselines reach 23 to 29px path error while corrected WF-r still sits near 91 to 93px on CF and 35.7px on CausVid.
- Absolute adherence on CF remains poor, with a large fraction of leftward items still moving opposite the request after correction. Drift compensation is standard feedforward disturbance rejection and the paired unguided baseline is an obvious control, so conceptual novelty is limited relative to the empirical effort.
- Evaluation is narrow, covering template prompts, centroid-only rigid translation, mostly cardinal 150px moves, no user study, and quality judged mainly by global DOVER and sharpness.
- Prior transmission is explicitly a predictive statistic rather than a causal quantity, so its value as a benchmark metric is interpretive rather than diagnostic.
- Matched-preview correction measurably degrades CF background fidelity, with background LPIPS rising from 0.258 to 0.308 and PSNR dropping from 17.98 to 16.87dB.
- The preview-free estimator comparison rests on a single seed, so the practical claim that online estimation matches matched-preview correction on CF is not established at the same evidence level as the main result.
- The paper is hard to follow because results are spread over many campaigns with different splits, seeds, and item counts, and key claims require cross-referencing multiple appendix tables.
Questions for authors
- Can the online estimator comparison be repeated over the full three seeds on both backbones, with object-clustered intervals against matched preview.
- Why does WF-r on CF still perform worse than a stationary object on many leftward items, and would forward-predicting the mask support with the estimated drift address this.
- Since the matched preview and the evaluation both use CoTracker3 on the same base clip, have you computed the preview drift with a different tracker to rule out tracker-specific shared bias.
- Can you show a case where prior transmission changes a design decision or controller ranking that path error and error reduction alone would not.
- How sensitive are the slope and the correction gain to prompt richness, given that the template prompt deliberately leaves motion underspecified.
- Can you report CF results separately by direction, since the rightward bias appears to dominate the aggregate numbers and may mask per-direction behavior.