- Rating
- 3(+1)
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
AnySpaceTime addresses space–time novel view synthesis from images with known camera parameters and timestamps. It extends a pretrained spatial NVS model through a motion encoder, a shared low-dimensional motion basis, target-time-conditioned feature updates, and lightweight renderer adaptation. One model is trained across static multiview, dynamic monocular, synchronized multiview, and asynchronous multiview observation patterns. Experiments demonstrate strong dynamic reconstruction results and largely preserved static-scene capability.
Critical strengths
-
The architecture is coherent, and a single model supports all 4 input patterns without setting-specific fine-tuning is practically useful.
-
Table 1 reports substantial improvements across three dynamic benchmarks, including relevant monocular baselines.
-
Component ablations provide supporting evidence for the motion basis and renderer adaptation.
Critical weaknesses
-
The comparisons do not cleanly separate architectural gains from training exposure. In Table 1, the monocular eval is tested with 8 reference image, which is exactly how anyspacetime is trained, while other models might not be exposed to such train inference matching. For example, 4DGT’s documented training uses 16 and subsequently 64 images, while NoPo4D targets synchronized multiview capture rather than the evaluated monocular setting. In Table 2, AnySpaceTime uniquely reports explicit training on both evaluated multiview patterns among the compared methods, while all other do not report equivalent training exposure to both patterns, so making the comparison kind of mixed. If I view this as a method paper, I would like to see training data and exposure controlled to determine how much of the improvement comes from the proposed framework versus better alignment between training and evaluation. However, that said, if it is standard practice in this field to compare methods at a system level only, then I am open to removing this weakness.
-
Positioning against closely related predecessors is incomplete. BTimer is cited but not compared, despite being a relevant feed-forward predecessor using similar posed, timestamped observations and supporting target-time reconstruction with target-view rendering. This does not establish that it already matches AnySpaceTime across all four settings, but it might be more suitable as a direct comparable candidate than the baselines author used. As some of them are more narrow-task-specific methods and take in different inputs. Additionally, CAT4D and 4DiM should also be discussed as alternative predecessors as they also share similar input interface with anyspacetime. I understand they are diffusion based models, but I would not ignore their existance. As the problem they are targeting is similar to anyspacetime and have been around for about 2 years. Therefore, the novelty should be distinguished more precisely from the broader space–time synthesis objective.
-
The asynchronous experiment uses a regular four-camera offset pattern, with target times represented among the reference observations. It does not fully establish performance for irregular camera availability combined with unseen target times. Separately, Table 3 includes only two dedicated static baselines, so it supports retention of static capability more strongly than broad competitiveness with specialized static methods.
Questions for authors
-
Can you provide a focused comparison with a compatible predecessor, such as 4DGT or BTimer? may be using matched training data and observation sampling to better isolate the architectural contribution. If its not possible, please explain the constraints.
-
How sensitive is the Table 1 gap to reference count? may be try more out of distribution reference count for anyspacetime and other baseline methods.
-
Were Table 2’s baselines adapted or trained for synchronized and asynchronous inputs? may be specify checkpoints and method-specific input adaptations if available.
-
What distinguishes the formulation and method from BTimer? and why was BTimer omitted from comparison?
Please Engage in the Author–Reviewer Discussion
Dear Reviewers,
As the author–reviewer discussion period is approaching its deadline (November 18, AoE), I would like to kindly remind you to review the authors' rebuttals and actively engage in the discussion as soon as possible. Please address any outstanding questions or concerns and update your assessments and ratings if appropriate. Thank you very much for your time and efforts!
Best regards, Area Chair