- Rating
- 2(+1)
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
This paper proposed OmniShowcase, a system that generates an orbiting video of an object from the object's multi-view renderings and a text description. To train such a model, the author proposed to synthesize data by inpaint the object and use pretrained VACE to generate the orbiting video. Then the model is trained using both reference images and rendered geometry (depth and surface normal) information. Results show improvement upon existing methods.
Critical strengths
None
Critical weaknesses
-
The need for generative video synthesis is insufficiently justified. The paper only considers static subjects under orbiting camera motion and already reconstructs a 3D representation from the input views. A natural alternative is to render that reconstruction within a 3D scene, which offers explicit camera control and geometric consistency. Obtaining such 3D scene is very simple, e.g., either by download or purchase from Internet sources or use any existing scene generation systems to create them. The paper does not prove that the proposed generative approach is a good trade-off. Thus, the central design choice insufficiently motivated. Moreover, the experiments do not resolve this design question. Comparisons with other subject-to-video methods demonstrate improvements within the chosen approach, but omit reconstruction-and-rendering alternatives using the same four reference images.
-
Following the first point, the proposed data pipeline introduces uncertainty into the scene consistency it aims to promote. Rendering the subject from a fixed mesh provides a sound basis for consistency. However, generating the surrounding scene with video inpainting does not enforce a consistent background, especially when the base model is poor, and the authors acknowledge related limitations in Appendix. As a result, the training data might be 3D-inconsistent and harm the overall performance.
-
The methodological novelty appears incremental. The method adapts a pretrained video DiT through LoRA and conditions it on reference-image and reconstructed-normal latents concatenated along the temporal axis. This is a very standard design. Given that the dataset part is also not well-motivated, I do not find this paper delivering meaning contribution to the community.
-
Minor issues
- Section 4.1 characterizes the four-view baseline extensions as stronger on almost every metric, whereas Tables 6–7 show worse GT-CD for both Phantom and MAGREF on both datasets; on NAVI, MAGREF also worsens on MEt3R and RotCoverage.
- Table 8’s caption does not correctly distinguish the four orbit variants from the other motions, while Table 9 states that arc motions take no suffix despite the framing suffixes specified in Section G.2 and Table 10.
- The discussion of Table 3 introduces the undefined labels “RGB DC” and “Sparse DC,” rather than using the table’s terminology.
Questions for authors
Please address my concerns mentioned in the weakness section.
7 comments
First Rebuttal for Reviewer kFNm (2/3) - W1b, minor issues
Reviewer kFNm - W1b: Obtaining a 3D scene
"Obtaining such 3D scene is very simple" (W1)
We agree that obtaining 3D scenes itself is relatively easy. However, scenes that match each prompt exactly are very hard to obtain off the shelf, because our prompts describe eighty-five distinct environments (50 for ShowcaseBench and 35 for NAVI) that no asset library covers. We therefore took the other route you suggested, an existing scene generation system, and generated each scene with Marble from World Labs, a commercial text-to-world system, on a pay-as-you-go basis at $1.26 per scene. Marble is prompted with a scene description taken from the same prompt our model receives, by dropping the camera-trajectory clause and the subject description and keeping the remaining scene as a noun phrase. Since R&R's identity and 3D scores are measured on the subject rendered alone, the scene does not lower them. The hard part turned out to be composing the subject into the scene, not obtaining it.
To implement R&R faithfully at benchmark scale, we fit a composition instruction rather than placing each subject by hand (Appendix G.1, Figure 12). For a small set of representative failure modes we prepared handcrafted targets, and an LLM agent (Claude Opus 5.5) revised a shared instruction through a render-and-review loop until its compositions matched them. The fitted instruction was then applied to all 85 samples. Per sample, reconstructing the subject takes 2.6 minutes, generating the scene about five, the automated render-and-review loop about one, and our own inspection and corrections about five, so a sample costs on the order of fifteen minutes end to end. This is somewhat longer than the 11.8 minutes OmniShowcase needs per video (Appendix H.4), and part of that time is human effort that does not go away with more compute. Building it this way showed two problems.
- The scene is fixed once it is generated. Running the commanded orbit at a scale where the background is legible drives the camera through a wall or a piece of furniture. Tightening the orbit clears the geometry but exposes the scene's finite resolution and leaves almost no background in frame, and enlarging the scene pushes the elements described in the prompt out of readable range. The composition finally used is a compromise rather than a solution.
- Placement is per sample. The fitted instruction carries the strategy but not the surface, scale and heading each scene calls for, and for a few samples the camera path itself had to be adjusted slightly.
R&R keeps explicit camera control and a rigid subject. OmniShowcase produces the commanded orbit from a text description alone, without per-sample scene acquisition, placement or relighting, and on the same subjects it gives better identity and visual quality (Table 2).
Reviewer kFNm - Minor issues
We are glad that you point them out. All three are correct and now they are fixed. In the revision, Tables 6 to 10 of the submission are now Tables 7, 8, 12, 13 and 14, and Section G.2 is now Section I.2.
- Section 4.1 now states that the four-view extension improves identity for both baselines but degrades GT-CD in every case, and on NAVI also MAGREF-MV's MEt3R and RotCoverage, that we report the four-view numbers because they use the same four reference images as our method, and that OmniShowcase outperforms both settings on every metric of Tables 7 and 8.
- The Table 12 caption now distinguishes the four orbit variants from the other motions, and the Table 13 statement now matches the framing suffixes in Section I.2 and Table 14.
- The Table 3 discussion now uses the table terminology, Textured and Sparse, in place of RGB DC and Sparse DC.
We continue our rebuttal in the next comment.
First Rebuttal for Reviewer kFNm (3/3) - W2, W3
Reviewer kFNm - W2: Background consistency of the training data
"the training data might be 3D-inconsistent" (W2)
We are grateful that you raised it, which has led to clarification of the scope of OmniShowcase. Our work targets subject-level 3D consistency, meaning that the subject's shape and appearance should stay coherent as the camera moves around it. Background consistency was not among the goals we set for the method, and the evaluation reflects this, since every identity and 3D metric is computed on the masked subject (Section 4.1). We recognize, however, that the submission does not state this scope where it matters most. Section 3.2 was titled Automated 3D-Consistent Data Synthesis without a qualifier, and the compositing paragraph described the inpainted background as coherent, so it is natural to read the claim as covering the whole scene.
We have retitled the subsection to Automated Data Synthesis with 3D-Consistent Subjects to make this scope explicit, and the compositing paragraph now describes a realistic background that follows the scene prompt rather than a coherent one.
During curation, gate G2 rejects composited clips whose background does not behave like one rigid 3D place (Appendices I.1 and K). We have also measured the background directly. Appendix H.2 (Table 10) compares Showcase-4K clips with clips that Uni3C, a camera-controllable image-to-video model, generates for the same subjects along the same camera paths. With a similar amount of background motion, Showcase-4K is more consistent on both background MEt3R (0.138 versus 0.186) and VBench background consistency (0.903 versus 0.889). So the inpainting step leaves the training background more consistent than generating the whole clip would. In the generated videos, our background MEt3R matches that of the ground-truth render (0.182 for both) at a similar camera rotation, and the model trained on these clips leads every method on DINO, CLIP, MEt3R and GT-CD (Table 2).
Reviewer kFNm - W3: Methodological novelty
"This is a very standard design." (W3)
We agree that LoRA adaptation and temporal-axis concatenation are established components, and we do not claim them as contributions. The design is deliberately simple, and each of its choices comes from the analyses in the paper. Our key observation is that, when the camera reveals sides that no reference shows, the difficulty is geometric rather than purely photometric (Section 1). Therefore, the model needs training data with exact subject geometry and explicit dense geometry at inference.
Our data synthesis pipeline provides the first. It renders the subject from its 3D asset and inpaints only the background, so the subject and its 3D consistency come from the asset itself. Vision-language gates with fixed rubrics replace human review, so the corpus scales with compute rather than annotator time (Appendix I.1). Against clips of the same subjects and camera paths generated by Uni3C, a camera-controllable image-to-video model, Showcase-4K clips score better on DINO (0.8030 versus 0.7167) and MEt3R (0.1871 versus 0.3052) (Appendix E).
The normal turntable provides the second, and the ablations show that it is essential to our model. Without it, held-out GT-CD rises from 0.0824 to 0.2092 and NAVI GT-CD from 0.0975 to 0.1987. A textured turntable of the same geometry gives 0.1698 and a sparser one 0.1777, and even a turntable from a single view helps (Appendix H.1). Since it needs no frame-by-frame alignment to the target, a single render of the reconstruction serves multiple camera motions.
With these two parts, our model requires neither large-scale training data nor per-subject optimization (Table 1). On ShowcaseBench held-out DINO, the best generative baseline scores 0.707 and R&R 0.714, our model without geometry conditioning 0.752, and the full model 0.799, and NAVI shows the same pattern (Tables 2 and 3). The R&R alternative, which we newly added to address W1, also falls behind this simple design on DINO and MEt3R on both benchmarks (Table 2). Showcase-4K and ShowcaseBench will be released with their source meshes and ground-truth cameras, and we hope they will support future research on this task.
Thank you again for the close reading, which has made the paper more accurate and its claims more carefully scoped. We hope our rebuttal addresses the reviewer's concerns and would appreciate it if the reviewer could reconsider the assessment, taking our rebuttal into consideration. We are happy to answer any further questions.
Best Regards,
The Authors
First Rebuttal for Reviewer kFNm (1/3) - W1a
Thank you for checking the appendix tables against the main text closely enough to find a factual error in Section 4.1 and two caption errors, and for pointing out the comparison we had left out, reconstruct-and-render from the same four references. The revision now includes that comparison and all three corrections. We answer the first part of W1 here, and the remaining points in parts (2/3) and (3/3).
Our description of the setup was compact, so we restate three details in brief to avoid any misunderstanding. (1) The NAVI references are real photographs of real-world subjects. (2) Each training clip renders the subject from its 3D asset and generates only the background around it (Section 3.2). (3) The geometry condition is surface normals only, which are converted from rendered depth maps (Section 3.2).
Reviewer kFNm - W1a: Comparison with reconstruct-and-render
We implement this as a new baseline to complete the comparison and evaluation. The revision adds it to the main comparison (Table 2), with implementation details in Appendix G.1.
Reconstruct-and-Render (R&R). The subject is reconstructed from the same four reference images with MV-SAM3D, the same reconstruction our pipeline runs, placed into a 3D scene that Marble generates from a scene description taken from the prompt the generative methods receive, and rendered along the commanded trajectory. R&R is provided with the ground-truth camera path of each sample and with colors matched to the ground truth, while OmniShowcase receives neither and is given only the trajectory sentence in its prompt. Its identity and 3D metrics are computed on the subject rendered alone, so they judge the reconstruction rather than the scene around it, while the video quality and prompt alignment metrics use the whole video.
Table 2 (partially excerpted from the updated PDF). Reconstruct-and-render against OmniShowcase.
Analysis. Because it follows the ground-truth path, R&R leads every generative baseline on GT-CD and RotCov. OmniShowcase, given only the trajectory sentence, is still ahead of it on DINO and MEt3R on both benchmarks and on held-out GT-CD (0.0824 versus 0.1015), and matches it on NAVI GT-CD (0.0975 versus 0.0988) without the ground-truth path. R&R also records the lowest ViCLIP, imaging and aesthetic scores in Table 2. R&R keeps a small edge in RotCov on NAVI (1.013 versus 1.074), which follows from executing the path directly. The identity gap is visible in Figure 5, where R&R is shown at the upper bound of our implementation, with the ground-truth camera path and colors matched to the ground truth. The fine print on a label is still blurred in four-view reconstruction by MV-SAM3D, and careful composition of the scene cannot fix it. OmniShowcase uses the same reconstruction only for its geometry, as a normal turntable, and takes the appearance from the reference images, so this limit does not apply to it.
This is the trade-off the Reviewer kFNm asked us to demonstrate. R&R gives explicit camera control by construction, but it can only render the subject as reconstructed inside a scene that was fixed when it was generated, and the two have to be fitted together sample by sample. This fitting has to meet three requirements that work against each other, following the commanded trajectory, keeping the scene elements described in the prompt readable, and keeping the camera out of the scene geometry, as detailed in part (2/3) and Appendix G.1. OmniShowcase instead leaves scene creation to the generative prior and draws the scene that the prompt describes around the subject in a single video. It adds only the part the prior lacks, keeping the subject's identity and 3D structure consistent along the commanded trajectory, without per-sample human intervention. Measured on the same subjects with the same protocol, OmniShowcase yields better identity and MEt3R, lower GT-CD on the held-out set and comparable GT-CD on NAVI, and higher imaging and aesthetic scores with high visual quality.
We continue our rebuttal in the next comment.