- Rating
- 3
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
OpenLongTail proposes a generative pipeline that converts monocular driving videos into synchronized multi-view training data. It combines ego-pose recovery, geometry-guided view synthesis, and joint rear-view generation with road-surface conditioning. Experiments demonstrate improved generation quality and show that the synthesized data benefits downstream closed-loop driving performance.
Critical strengths
-
Practical significance. The paper addresses an important limitation in autonomous driving data collection. Converting abundant monocular long-tail videos into multi-view training data offers a promising way to improve data coverage.
-
Meaningful downstream validation. The authors evaluate the generated data through closed-loop driving experiments. The results show clear improvements over nominal-data fine-tuning and approach the performance achieved with real multi-view data. This supports the practical value of the proposed pipeline.
Critical weaknesses
-
Multi-view consistency and missing comparisons. The rear-tele view in the demos appears to exhibit substantially different motion speeds from the other rear views. This raises concerns about multi-view consistency, which has received considerable attention in recent driving generation research, including the WorldLens benchmark (Liang et al., CVPR 2026). The paper also lacks comparisons with closely related methods such as NeoVerse and Sensor2Sensor. More quantitative evaluations and explanations are needed.
-
Unclear advantage over direct multi-view generation. Existing driving world models, such as opendwm and magicdrive-v2, can directly generate multi-view videos with explicit control over road layouts and foreground objects. What advantages does converting real front-view videos into surround-view data offer over direct multi-view synthesis for long-tail data augmentation? A comparison of downstream policy improvements would help establish the value of this approach.
Questions for authors
Fig.2 jointly generates three rear views but does not explicitly connect the front-left and rear-left views, or the front-right and rear-right views. Why are these potentially related views generated separately? Could this design limit spatial and temporal consistency across the full camera rig?
3 comments
Response to Vkr9 (2/2)
Q1. Separate generation of side and rear views
Thanks for this question. The split follows where same-time evidence exists: CL and CR overlap the front camera and are generated from its reprojection, while the rear cameras have no same-time overlap with the front camera and are generated jointly from each other and from road priors (Sec. 3.2–3.3). In the PAV rig, CL and RL (CR and RR) do not overlap at all: 0% of RL pixels fall inside the CL view and 0% of RR pixels inside the CR view, at any depth from 5 m to infinity, with a gap of about 8° between the two fields of view. A direct link would therefore attend only to unmatched tokens, and adding CL and CR to the joint rear sequence would add two video streams to a branch that already takes 486 s per clip (Appendix F.2). Both branches share the same front-view conditioning and recovered ego trajectory, which keeps the motion of the side and rear views consistent. In conclusion, the split follows the overlap structure of the rig at a practical cost.
Dear Reviewer Vkr9,
Thank you for your constructive feedback and recognition of our work's practical significance and downstream value. We truly appreciate your support.
Following your suggestions, we added a NeoVerse comparison, WorldLens consistency evaluation, and optical-flow analysis confirming that rear-view motion differences match ground truth, along with further clarifications.
As the discussion period comes to a close, we hope you may review our responses. We aim to make the paper as solid as possible and welcome any further feedback.
Thank you once again for your encouragement, time, and consideration!
Response to Vkr9 (1/2)
We thank the reviewer for the constructive feedback. Your review raises two main concerns and one question:
We address these points below with additional experiments and clarifications.
W1. Multi-view consistency and missing comparisons
We clarify that the apparent motion differences across rear views are expected consequences of their distinct camera geometries. The rear-tele camera (30° FoV) looks directly backward, while the rear-left and rear-right cameras (70° FoV) capture stronger lateral parallax from roadside structures. These different camera configurations naturally produce distinct apparent-motion patterns. OpenLongTail faithfully reproduces these camera-dependent motion differences, closely matching the corresponding GT values. In contrast, GEN3C substantially overestimates rear-view motion. This result confirms that the slower rear-tele motion reflects real camera-dependent motion patterns rather than generation artifacts.
Table 1. Mean optical-flow magnitude (px/frame) across five target views on 80 held-out clips.
Besides, we include NeoVerse [1] in an additional comparison under the original evaluation protocol (Main Table 1, Sec. 4.2), reported in Table 2. All methods are evaluated on the same 80 held-out long-tail clips, with results aggregated across five target views. Sensor2Sensor [2] is excluded because its code and checkpoints are not publicly available for comparison.
Table 2. Extrapolative view evaluation on held-out long-tail clips.
Additionally, we evaluate generation quality using seven metrics from the WorldLens [3] evaluation framework on our 80 held-out NVIDIA PAV long-tail clips. All methods are evaluated on the same clips under identical preprocessing and metric protocols, enabling a controlled comparison of object fidelity, temporal consistency, semantic stability, and cross-view coherence. Therefore, OpenLongTail still outperforms the baselines on generation quality.
Table 3. WorldLens generation evaluation on held-out long-tail clips.
W2. Advantage over direct multi-view generation
Thanks. Layout-conditioned generators such as MagicDrive-V2 [4] and OpenDWM [5] synthesize all views from BEV maps, 3D boxes, and text, which monocular long-tail videos from heterogeneous sources do not provide, whereas OpenLongTail keeps the recorded front video with its real event and generates only the missing views. The front view and its front-tele crop therefore remain real observations, covering two of the four Alpamayo-R1 inputs. Under matched fine-tuning budgets, these assets improve AS from 0.717 to 0.748, approaching 0.764 with the corresponding recorded multi-view data (Main Table 2). We agree that a downstream comparison with layout-conditioned generation would be informative, and it needs BEV maps and 3D boxes for the same long-tail events, which our monocular sources lack. In summary, layout-conditioned generators create new scenes from annotations, and OpenLongTail converts recorded events into multi-camera training data.
References
[1] Yuxue Yang et al. NeoVerse: Enhancing 4D World Model with in-the-wild Monocular Videos. CVPR, 2026.
[2] Jiahao Wang et al. Sensor2Sensor: Cross-Embodiment Sensor Conversion for Autonomous Driving. CVPR, 2026.
[3] Ao Liang et al. WorldLens: Full-Spectrum Evaluations of Driving World Models in Real World. CVPR, 2026.
[4] Ruiyuan Gao et al. MagicDrive-V2: High-Resolution Long Video Generation for Autonomous Driving with Adaptive Control. ICCV, 2025.
[5] OpenDWM: Open Driving World Models https://github.com/SenseTime-FVG/OpenDWM. Software repository, 2025.