- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
FilmFlow presets an agentic system for generating camera trajectories in static and dynamic 3D scenes either from test descriptions or reference videos. The interpreter identifies the main subjects and the camera keywords, the scout searches for an initial viewpoint in conjuction with a critic. The director adds the camera motion and operation timeline. The camera operations are composed of atomic operations where each one can be specified with the corresponding timelines. FilmFlow is evaluated on a new benchmark and compared with several baselines.
Critical strengths
- The paper tackles a relevant problem where agentic workflows for mapping cinematic intent to camera operations.
- The separation of an initial view makes sense since this is easier to specify/adjust the camera framing while the camera motion can be added later.
- A new and good scale benchmark is presented.
Critical weaknesses
- The proposed method has an initial view planning stage. It might make sense to adapt this to the baselines as well otherwise the transfer of camera trajectories from baselines (LAMP, GenDop, VGGT) is not trivial and it seems often results in the camera looking at empty spaces.
- Another baseline/ablation can be a single agent instead of the four agents as interpreter/director etc. This can help to strengthen the contribution of the need of four different agents.
- The method evaluates only on its own Benchmark which might be more tailored for this specific method. Providing results on previously used baselines would be useful.
- No video results are provided and hence it's not too easy to judge the overall quality of the camera trajectories.
Questions for authors
- How much of the improvement remains when LAMP and GenDoP receive the same suitable opening as FilmFlow? For reference-video baselines, how are reconstruction scale and placement resolved in the target scene beyond converting coordinate conventions?
- How does a single agent perform with the same operation library, scene evidence, demonstrations, rendered feedback, and total inference budget?
- Previous work like Auteur also emphasizes the importance of framing, but also use specific metrics to measure this. Can you report direct camera trajectory metrics, such as collision frequency, framing error etc?
3 comments
Response to Reviewer 2hW7
W2/Q2. Single-agent comparison
We thank the reviewer for suggesting a single-agent comparison to better understand the contribution of FilmFlow’s workflow. We provide results for a single agent using the same backbone and camera-operation representation.
The control uses the same gpt-6-astra model, scene evidence, 22-operation library, executor, and access to the 50-example demonstration bank. One agent selects the opening and generates the complete operation timeline in a single planning pass. This keeps the model and available camera controls consistent while replacing the specialized workflow with direct planning. Higher is better for all metrics.
| Task | Method | Alignment ↑ | Quality ↑ | Motion ↑ | Probe ↑ |
|---|---|---|---|---|---|
| T2V | Single-pass agent | −1.531 | 44.26 | 0.431 | 0.733 |
| FilmFlow | −1.461 | 47.60 | 0.555 | 0.829 | |
| V2V | Single-pass agent | −1.323 | 38.29 | 0.232 | 0.701 |
| FilmFlow | −1.224 | 41.77 | 0.289 | 0.750 |
FilmFlow outperforms the single-pass agent on all four metrics in both tasks. The absolute gains in Alignment, Quality, Motion, and Probe are 0.070, 3.34, 0.124, and 0.096 for T2V, and 0.099, 3.48, 0.057, and 0.049 for V2V.
These results support the effectiveness of FilmFlow’s complete workflow beyond a single direct planning pass with the same model and operation library. Because this control uses one planning pass, the comparison evaluates the combined contribution of specialized planning and feedback-guided refinement; it does not isolate agent specialization under matched feedback and total inference budgets.
Response to Reviewer 2hW7
W3/W4/Q3. External evaluation, direct trajectory metrics, and video results
We thank the reviewer for the helpful suggestions to evaluate beyond CinemaBench, report direct camera-trajectory metrics, and provide full video results. We address these points below.
External evaluation and direct metrics. We additionally evaluate FilmFlow on CinemaTraj’s ScanNet++ scenes and fully specified prompts using its evaluation protocol. This complements CinemaBench with an established external setting.
Motion MSE measures deviation from a hand-crafted reference trajectory after arc-length resampling. CLaTr measures text–trajectory similarity. Collision rate is the fraction of sampled camera positions inside scene geometry; occlusion rate is the fraction of samples at which the target object is blocked. These metrics assess trajectory fidelity, geometric feasibility, and target visibility.
CLaTr is reported as cosine similarity multiplied by 100. Collision and occlusion rates are fractions in [0, 1].
| Method | Motion MSE ↓ | CLaTr ↑ | Collision rate ↓ | Occlusion rate ↓ |
|---|---|---|---|---|
| LAMP | 9.542 | 22.116 | 0.103 | 0.559 |
| GenDoP | 7.741 | 19.461 | 0.209 | 0.580 |
| CinemaTraj | 1.741 | 28.982 | 0.056 | 0.503 |
| FilmFlow | 1.358 | 28.542 | 0.034 | 0.478 |
FilmFlow achieves the lowest Motion MSE, collision rate, and occlusion rate among the compared methods. Relative to CinemaTraj, it reduces Motion MSE from 1.741 to 1.358 (22.0%), collision rate from 5.6% to 3.4%, and occlusion rate from 50.3% to 47.8%. CinemaTraj retains a slightly higher CLaTr score (28.982 vs. 28.542). These results provide direct evidence of improved trajectory fidelity and fewer collisions and occlusions on an external benchmark.
The geometric metrics complement the video-based evaluation: collision measures camera feasibility, while occlusion measures target visibility. Compositional framing error is a distinct property, so we interpret the occlusion results specifically as evidence about visibility.
Video results. We thank the reviewer for highlighting the importance of viewing the complete camera trajectories. Full rendered videos for both text-directed and reference-video-directed comparisons are included in the supplementary material. Please open demo.html in the supplementary package to browse the comparisons. The videos show how camera motion and subject framing evolve throughout each shot, complementing the sampled frames presented in the paper.
Response to Reviewer 2hW7
W1/Q1. Shared-opening comparisons and scene-aware V2V placement
We thank the reviewer for highlighting the importance of initialization and for suggesting these controlled comparisons. We provide shared-opening results for LAMP and GenDoP and clarify how the V2V trajectories are placed and scaled in the target scene.
Shared-opening T2V comparison. We rerun LAMP and GenDoP with FilmFlow’s Scout-selected camera position, orientation, and focal length at the same scene-animation frame. Each baseline retains its original motion-generation and translation-scaling procedure and is evaluated on the same test instructions. Higher is better for all metrics.
Sharing the opening improves both baselines across all four metrics. FilmFlow retains 72.0% of its original Alignment advantage over LAMP (gap: 0.286 → 0.206) and 75.2% over GenDoP (0.307 → 0.231). It also exceeds shared-opening LAMP by 5.47 in Quality, 0.322 in Motion, and 0.238 in Probe, and shared-opening GenDoP by 3.49, 0.254, and 0.208, respectively. These results confirm the contribution of opening-view selection and show that substantial gains remain in the subsequent camera trajectory.
V2V scale and placement. Beyond coordinate conversion, we align each extracted trajectory’s initial pose to the Scout opening and share its focal length and scene-animation start frame. Relative translations are uniformly rescaled using a fixed subject-size-based rule. Relative rotations and temporal structure are preserved, without replanning or per-frame tracking.
The table below compares the original transfer settings with these scene-aware adaptations. Higher is better for all metrics.
Scene-aware placement improves Alignment from −1.472 to −1.307 for LingBot-Map and from −1.491 to −1.352 for VGGT-Ω. FilmFlow retains the highest Alignment, Quality, and Probe scores, while scene-aware LingBot-Map achieves a slightly higher Motion score (0.290 vs. 0.289). These comparisons show how improved placement benefits trajectory transfer and identify the remaining advantages of FilmFlow’s scene-conditioned planning.