- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes a two-stage framework for camera-controlled 360-degree video generation from incomplete initial observations. Stage 1 learns a panoramic prior from complete general-domain ERP videos. Stage 2 adapts this model to driving using calibrated perspective multi-view videos projected into partial ERP targets. During evaluation, the model generates complete ERP videos from partial observation, a text prompt, and target trajectory. Experiments evaluate held-out self-driving sequences, cross-dataset transfer to nuScenes, and driving sequences from 360-1M.
Critical strengths
-
The adaptation mechanism addresses a useful practical setting: exploiting existing calibrated multi-view recordings without requiring complete target-domain panoramic ground truth. Masking unreliable supervision, including its spatial and temporal propagation into VAE latents, is a sensible way to avoid learning camera-boundary artifacts and treating missing regions as valid targets.
-
The paper is well-presented and easy to follow.
-
I love the website that contains abundant interactive visualizations .
Critical weaknesses
- The paper's claimed scope
The paper framed itself as general-propose panoramic video generation, but Stage 2 and the main adaptation experiments focus on driving videos. It is unclear whether driving is simply one example target domain for a general adaptation recipe, the intended scope of the contribution, or a source of training data expected to improve general panoramic generation. Besides, Stage I uses complete ERP videos, so the "panorama without panoramas" claim needs to remain explicitly limited to target-domain adaptation and inference requirements.
- Regarding Data
The reviewer does not fully agree with the authors' claim. The introduction reports approximately 150 suitable driving panoramas after filtering 360-1M, but does not disclose how this number is computed. As far as the reviewer know, Argus releases approximately 112k high-quality 10-second clip lists derived from 360-1M, while CubeComposer further curates this data source into 4K360Vid with 12k high-resolution clips and uses it for training. Although these are general-domain videos and do not directly contradict the "150 driving-only video" claim, the ratio between 150 and tens/hundreds thousand video is large, and the author should explicitly explain this.
Synthetic panoramas are another relevant alternative: game engines can render complete 360-degree sequences with known camera trajectories for driving and other scenes. Many existing papers (e.g., GenEx) used game engines such as Unreal Engine and Unity to synthesize high-quality 360 panoramic videos, either for self-driving or general propose domain. The paper neither adequately explain why such data are unsuitable, nor compared with baselines that make use of these synthesized data. A real-to-synthetic domain gap may matter, but it should be discussed and supported rather than assumed.
- Insufficient Experiments and Unclear Setting
Table 1 reports PwP (multiview) against baselines, while Figure 4 explicitly states that the baselines use single-view inputs and PwP uses multiview observations plus geometric control. This comparison mixes model differences with differences in visual coverage and conditioning. Section 5.1 claims a single-view PwP comparison, but Table 1 does not show the corresponding row. Moreover, "single-view" does not establish equivalent temporal information: these baselines are described as video-to-video methods, whereas PwP's single-view RGB condition is the first frame. The authors need to specify exactly which frames, views, camera information, and geometric inputs each method receives, and report a comparison with matched available information. The comparison also omits CubeComposer, a directly relevant recent perspective-to-360-degree video method with public inference code and checkpoints.
- Minor issues
- Some bib entires contains page/volume information while others do not. It would be better to make the citation format consistent.
- Figure 7 is not very easy to view in pdf.
Questions for authors
-
Is driving intended as an example target domain or the principal application? Is the claim that Stage 2 improves driving generation while preserving the panoramic prior, or that it improves general panoramic generation? What evidence supports the latter, if intended?
-
How was the approximately 150-video driving subset obtained? Please provide counts after each filtering step, distinguish source videos from clips, and explain its relationship to the public Argus/4K360Vid data. Why are existing driving-relevant panoramic clips and game-engine-rendered panoramic sequences insufficient or unsuitable alternatives?
-
For every baseline and PwP variant in Table 1, what exact RGB frames and views are provided? Do the baselines receive a real perspective video or only an initial image? What data are used to reconstruct the point cloud and render the control sequence, and do they include future frames or additional views in the single-view setting? Please provide the missing single-view PwP results with matched conditioning.
-
Can the authors add a comparison with CubeComposer or 360Anything (if they release code)?