- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
The authors propose Warp-as-History, a method that converts camera-induced warps into camera-warped pseudo-history with target-frame positional alignment and visible-token selection to route camera control through a model's native visual-history pathway. This simple interface reveals a non-trivial zero-shot capability in frozen video generation models to follow prescribed camera trajectories without requiring architectural changes or test-time optimization. Applying lightweight offline LoRA finetuning on just a single separate video further stabilizes this camera-following behavior and allows it to generalize effectively to unseen videos.
Critical strengths
- Unlike existing methods that require large-scale datasets, the proposed approach achieves competitive performance using only a single training video and lightweight offline LoRA finetuning.
- By routing camera-warped pseudo-history through the model's native visual-history pathway with PE adjustment, the method unlocks a zero-shot camera-control capability in the frozen Helios model.
Critical weaknesses
- Overall, the manuscript suffers from significant writing and organizational issues. The logical flow is difficult to follow, paragraph transitions are weak, and intra-paragraph cohesion needs substantial improvement. In particular, the Introduction section requires a major overhaul to clearly set up the work.
- There is an apparent contradiction in the core pitch: the introduction claims that Warp-as-History achieves generalizable camera control without any training or inference-time optimization methods, yet the methodology later states that offline LoRA fine-tuning is performed on a single camera-annotated video. This conceptual inconsistency needs to be reconciled.
- Please specify which individual video is used for the offline LoRA fine-tuning. Furthermore, what is the underlying mechanism or justification that enables a model fine-tuned on just a single video to achieve universal generalizability?
- Regarding Table 3, evaluating video generation metrics against baselines that do not share the same backbone offers limited utility. These metrics should instead be compared against the distilled Helios model without any fine-tuning applied to provide a fair and meaningful baseline.
Questions for authors
- Line 458 states: 'The fixed car-roundabout source was chosen before the retrospective sweep.' Please clarify the meaning of this sentence and provide sufficient context to explain its relevance to the discussion."
- Is the DAVIS dataset considered an appropriate or standard benchmark for evaluating camera-controllable video generation methods, given the specific domain?
5 comments
Reply by Reviewer iRYX
The rebuttal addresses my concerns partly. Specifically, I now understand the generalization claim / backbone-dependent comparison / evalset points after reading the author's rebuttal. None of updates are applied in the manuscript. Similarly, authors agree significant modification of writing and organization is needed. However, I do not see any modifications applied on the draft. Authors can correct me if I am wrong. Thus, my most concerning point is not addressed at all. Moreover, similar to what Reviewer sxPw pointed out, statements on latency is quite misleading on the manuscript even though the authors answered clearly on the rebuttal. I strongly believe that the manuscript be updated to address reviewers' concerns.
Response to Reviewer iRYX
Thank you for pointing this out. You are correct: our previous rebuttal described the intended revisions, but we did not upload an updated manuscript. That was our oversight, and we apologize for the discrepancy between our response and the PDF.
We have now uploaded a revised manuscript, with the changes highlighted in blue. Specifically, we have (1) substantially reorganized and rewritten the Introduction to clarify the zero-shot observation versus the final one-video LoRA model; (2) added matched Helios-Distilled comparisons to Tables 2 and 3 and explicitly discussed the resulting quality trade-offs; (3) revised the camera-accuracy and generalization claims; (4) clarified the source-selection timeline and the complementary role of DAVIS; and (5) corrected the latency statements by distinguishing the standard A800 measurements from the separately optimized H200 configuration.
Thank you again for encouraging us to address these concerns directly in the manuscript.
Response to Reviewer iRYX
Thank you for the detailed comments. We agree that our organization and presentation did not make several important distinctions sufficiently visible, and we address each concern below.
Writing and organization. We accept this criticism and will substantially rewrite the Introduction. It will follow a clearer sequence: (1) limitations of existing camera-conditioning approaches; (2) our observation that pretrained history-conditioned models contain latent camera-following behavior; (3) zero-shot Warp-as-History as a diagnostic of this behavior; and (4) the final one-video offline LoRA model, with fixed weights at test time. We will also use zero-shot, one-shot, offline finetuning, and test-time optimization consistently throughout.
The training claim. We would like to clarify that the paper does not claim that the final one-shot model requires no training. “Without any training” refers only to the zero-shot observation on the frozen model. The Introduction explicitly states: “Although this zero-shot effect is not robust enough to serve as a final method on its own,” followed by, “We further enhance this capability with lightweight offline LoRA finetuning on only one single camera-annotated video.” Thus, zero-shot is diagnostic evidence of a latent capability; the final model uses offline LoRA on one separate video, with no test-time optimization, per-video fitting, or target-video adaptation. We apologize that our presentation did not make this separation sufficiently prominent.
Source video and generalization mechanism. The sole source is DAVIS car-roundabout, as stated in Section 4.1, and it is disjoint from the evaluation videos. Our claim is not that one video teaches universal video generation or camera control from scratch. The pretrained base model already acquires rich appearance, motion, and viewpoint generation capabilities. Warp-as-History reuses its native history-conditioning interface to supply geometric evidence; one-video LoRA then learns to interpret and stabilize this evidence, balancing it against the generative prior. The zero-shot behavior supports this activation interpretation. We will avoid “universal generalizability” and restrict our claims to the unseen videos, trajectories, and backbones actually evaluated.
Same-backbone comparison. We agree that cross-backbone metrics alone cannot isolate our contribution. Importantly, the requested comparison already appears in Appendix Table 12: Text-only Base, Zero-shot Full, and One-shot Full all use Helios-Distilled and include FID, FVD, DOVER, and VBench metrics. Table 1 provides a similar text-only comparison on WorldScore. On DAVIS, Text-only Base→One-shot Full improves PSNR (14.38→15.21), LPIPS (0.4199→0.3794), FID (71.55→68.18), and FVD (80.87→57.95), while Dynamic Degree increases from 0.091 to 0.714. However, DOVER (0.463→0.448), Imaging Quality (65.21→62.20), and some consistency metrics decrease. We therefore do not claim lossless improvement on every quality axis; the results show a control–quality trade-off. We regret not foregrounding these controls and will move them into the main comparison, treating external cross-backbone results only as system-level references.
“Chosen before the retrospective sweep.” This means that car-roundabout was fixed for the main experiments before we conducted the multi-source sensitivity sweep in Tables 9–11. We did not replace it afterward with a better-performing source based on downstream results. The statement was intended to rule out post-hoc selection of the best source, not to claim that car-roundabout was optimal. We will state this timeline and selection process directly.
DAVIS. We agree that DAVIS is a widely used video-object-segmentation dataset, not a standard camera-control benchmark. Since existing camera-control evaluations predominantly emphasize static scenes, we use DAVIS as a complementary dynamic-foreground stress test, not as a replacement for WorldScore or RE10K. Its estimated camera trajectories also introduce pseudo-ground-truth noise and monocular geometry errors. We apologize for insufficiently explaining this motivation and will clearly state both DAVIS’s complementary role and its limitations.