Summary
The paper introduces a large-scale, real-world, multiview, 360-degree outward dataset designed for static novel view synthesis and 3D reconstruction. To capture these data, the study develops a pipeline capable of identifying corresponding multiview frames from 360-degree outward videos with a fixed camera trajectory. To demonstrate the dataset's contribution and impact, the work proposes a diffusion-based model that achieves state-of-the-art performance using this dataset.
Strengths
Strength
- The work introduces a real-world, multiview, 360-degree outward dataset that is significantly larger and more diverse than existing datasets for static novel view synthesis. This dataset is crucial for modern data-driven methods.
- The work presents a novel and efficient pipeline that utilizes Dust3R to find corresponding frames and graphs to maintain long-range correspondence for data collection. This innovative pipeline makes the data collection process scalable.
- The work proposes a diffusion-based model, ODIN, that leverages the video dataset for static novel view synthesis by incorporating motion masking and viewpoint conditions to achieve state-of-the-art performance. Additionally, the model can generate long-range novel views, further validating the dataset's positive impact.
Weaknesses
Dateset
- The dataset is collected from 360 YouTube videos, captured beforehand by the camera operator. The camera trajectory (x, y, z) is controlled by the camera operator, thereby limiting the flexibility to select diverse viewpoints from different positions.
- The quality of the data is unknown and can be unstable across different data points because the author cannot investigate each video one by one or frame by frame. This represents a tradeoff between capturing one's own data and crawling data from the Internet. For instance, the author acknowledges in lines 178-179 that it is infeasible to guarantee the uniqueness of video content.
- Although the work claims that 1 fps is sufficient in lines 126-128, this claim lacks experimental support. The author should consider trying different fps rates and show the performance gap and computational time between them.
- Larger dataset may need more training time and computational resource.
Method
- One of the most challenging aspects that prevent people from using video for static scene tasks is the impact of motion over time (multiview inconsistency). The work proposes a motion mask method to mitigate this impact. However, this aspect lacks analysis and discussion. For instance, the importance of the hyperparameter in Eq. 3 is unknown.
- In Fig. 3, in the second row, the method is shown to synthesize humans as well. However, I wonder whether the motion masking has a negative impact on synthesizing dynamic objects when they are static.
Writing
- In lines 5-6, the claim may be too arbitrary. As mentioned in lines 87-90, there are some large-scale real-world datasets, such as CO3D, albeit with limited diversity. A related work, OmniObject3D, should also be mentioned.
- In lines 8-12, the phrase "...diverse views" may be too broad and should be softened. The proposed dataset is collected from pre-captured 360 YouTube videos. The camera trajectory is decided by the camera operator beforehand, and only the camera orientation can be controlled after that. Hence, compared to general multiview datasets, which can have multiple viewpoints from different locations at the same timestamp, the views of the proposed dataset are limited.
- Eq. 2 does not match the equation in Sec. 5.1. The equation in Sec. 5.1 contains an undefined term.
- I hope the author can define their 360 multiview videos at the beginning since there are several kinds of 360 videos. For instance, DiVa360 captures 360-degree inward videos with multiple cameras at different locations at the same timestamp.
Questions
- I hope the author can verify that the viewpoints are diverse enough by discussing the difference between a multiview dataset that can capture images from different locations at the same timestamp and a dataset that can only change the camera orientation at the same timestamp.
- The dataset contains a large amount of data, which may vary in quality. I hope the author can discuss the impact of the low-quality data in the dataset. Is it negligible?
- Iines 178-179 mentions that it is infeasible to guarantee the uniqueness of video content. Hence, how do you make sure there is no overlap between training and testing set? How do you make sure the training dataset does not contain the testing cases in other dataset? Will it be unfair for the benchmark?
- The dataset contains diverse data. How is the data distribution in terms of motion? Will high-motion data, such as scenes with rain, have a negative impact?
- Lines 126-128 need experimental support. Please consider trying it on a subset of the dataset.
- The work uses Depth Anything as the depth estimator. This is a monocular depth estimator with two types of checkpoints pretrained on two different datasets. I wonder if this causes a domain gap in the proposed dataset when using different checkpoints. Do you finetune the estimator on your dataset? Additionally, it is unknown how good the multiview consistency is on your data with this estimator.
- What is the tradeoff between using this dataset and others? From the experiment section, we know that the dataset can increase performance. But how about the training time compared to existing datasets? Maybe the author can consider adding the training time from the appendix to the table.
- How sensitive and stable is the motion masking hyperparameter in Eq. 3? How should it be tuned?
- What is the performance when the input image contains many dynamic objects?
Limitations
I agree with the limitation section in the paper.
- One potential limitation of the large-scale dataset is to maintain the data quality and high fps.
- Another potential limitation is to make sure there is no overlap between training and testing set.