- Rating
- 3
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
SmartDirector generates single-shot and multi-shot videos from keyframes at specified temporal positions. Director-Gen encodes video chunks independently at keyframe boundaries, then jointly models them using global attention and boundary-aware temporal coordinates. Director-SR uses high-resolution keyframes to refine the generated video. Evaluation on 220 KeyFrame-Compass cases shows improved keyframe execution over a baseline using the same backbone. Additional experiments assess super-resolution and a separate proprietary implementation.
Critical strengths
- The combination of independent chunk encoding, global attention, and MC-RoPE addresses a concrete representation mismatch caused by causal temporal compression. The components have clear roles and provide a practical way to enforce multiple visual anchors while sharing context across the video.
- Against the same-backbone pairwise baseline, Director-Gen improves all six reported metrics; KPA rises from 0.590 to 0.905 and KFS from 0.634 to 0.783. Component ablations also consistently favor the full model. These comparisons provide substantive evidence for the generation contribution.
Critical weaknesses
- Accurate keyframe timing does not establish natural event progression or transitions between anchors. The main evaluation emphasizes keyframe execution and overall visual quality, without directly establishing the pacing quality of the MiniMax H3 implementation. The pacing study in Appendix B uses a different proprietary backbone, so its conclusions cannot be directly attributed to the main model. This limits support for a central claim.
- The added value of Director-SR is not isolated. In Table 4, refinement increases resolution but reduces KFS from 0.783 to 0.749, SVQ from 0.856 to 0.824, and DVQ from 0.774 to 0.762. Resolution-normalized evaluation may miss genuine detail gains, but these results do not establish improved perceptual quality. Table 3 quotes SparkVSR results under incompletely matched reference conditions, and Director-SR lacks an ablation without keyframe guidance. Its specific contribution therefore remains uncertain.
Questions for authors
- For the main MiniMax H3 implementation, do you have pacing judgments or additional results, such as PAK and RU, that distinguish natural transitions from brief keyframe flashes or prolonged static holds?
- What are the source, number, and positions of the high-resolution reference frames in Table 3, and are they comparable to SparkVSR? On generated inputs, can a comparison with simple upsampling and Director-SR without keyframe guidance establish the benefit at a common output resolution?
- In Table 2, why does standard RoPE reduce HR from 1.000 to 0.767 when keyframe latents remain fixed? Can you separate reconstruction at the specified timestamps from failures introduced by shot assignment or keyframe matching windows?
2 comments
Thank you to the authors for their detailed response. After carefully reading the rebuttal, I find that it has largely addressed my previous concerns. Taking into account the comments from the other reviewers, I have decided to maintain my current score.
We thank the reviewer for the detailed reading and for the concrete questions on pacing and on isolating the SR stage. We answer the three weaknesses in order and will carry the changes into the revision.
Q1 · Pacing evidence for H3 (W1)
The evaluation reports six metrics fixed in advance — HR, KFS, KOC, KPA, SVQ, DVQ — of which KPA is the only timing-aware measure; PAK and RU are not computed. KPA establishes that the keyframe event occurs at the requested position within the benchmark's tolerance, so a misplaced or absent keyframe cannot obtain 0.905. It says nothing about the rate of in-between motion: a method may hold a frame nearly static for most of an interval and still satisfy KPA, and only a duration or onset measurement separates a natural transition from a brief flash or a prolonged hold. KPA is a timing metric, not a pacing metric.
The closest evidence is the supplementary material, whose clips are generated from keyframes spaced unevenly in time: the in-between motion is paced by that spacing rather than a fixed rate. The clips are an illustration rather than a measurement, because no established metric exists for how motion should be distributed in time and no reproducible model exposes keyframe timing as a control.
The only pacing-specific values come from the Narrative Pacing dimension of the blind human study in Appendix B: 50.2% of 317 responses prefer SmartDirector versus 13.3% for Dreamina, and 65.8% versus 12.0% on multi-shot cases. That study uses the 32B internal backbone, not H3, so a revision would retitle to "…with Temporal Control" and demote Appendix B to portability evidence.
Q2 · Isolating Director-SR (W2)
Reference conditions. All four benchmarks are public (UDM10, SPMCS, YouHQ40, RealVSR). Following SparkVSR, the reference is a single image obtained by upsampling the first low-resolution frame with PiSA-SR; in the reviewer's terms, the source is the first frame of the low-resolution video, the position is frame 0, and the number is one.
Provenance. Our row follows this protocol; the SparkVSR row is the value reported in its paper. The reference configuration is therefore matched, and the revised caption will state both facts.
Table 4. We agree that it cannot establish a perceptual gain. KeyFrame-Compass resizes before SVQ and DVQ, so the near-constant values indicate preservation of control and quality rather than a sharper 1080p image; our evidence for detail recovery is Fig. 4 and the LPIPS column of Table 3.
The two controls. The right controls are bicubic upsampling at 1080p and Director-SR without keyframe guidance; without the second, keyframe guidance is not isolated, and we will add both.
On the KFS decrease after SR. The decrease follows from the design, not from an artifact. Director-SR is conditioned on a high-resolution reference and moves the video away from the low-resolution input wherever that input is wrong; that is the function of the stage, and the reason the faces and text in Fig. 4 are recovered. KFS and SVQ compare the refined video against the reference and, at resized resolution, against a quality model, so a refiner that corrects identity drift and distorted faces does not always raise a pixel-faithful similarity score and can lower it when the correction departs from the low-resolution content. The same mechanism explains the PSNR/SSIM losses against SparkVSR alongside the LPIPS gains.
Q3 · Positional indexing and HR (W3)
Fixing a latent does not fix the time the model assigns to it, nor the content it must carry. With r = 4 a regular latent spans four frames and a boundary latent one, yet native indexing advances both by the same step. The model cannot distinguish them and must compromise at every boundary between the two densities; the coordinate is also over-extended by 0.75 steps per boundary — three steps, or twelve frames, for five keyframes — so the modeled duration drifts from the real one, and frames next to a boundary decode as mixtures with their neighbors. This is why SVQ and DVQ move with the coordinate scheme, and why the effect is not a small positional shift. For HR and KFS, the presence of keyframe content is not in question because the latents are clamped; what is in question is whether the event detection finds it at the requested time with sufficient similarity, and the aggregate metrics cannot indicate which of the two failed.
On separating reconstruction from matching-window failures, the aggregate metrics cannot do so on their own, although one dissociation in Table 2 is informative: direct insertion has a higher KPA than standard RoPE (0.582 vs 0.525) but a lower HR (0.661 vs 0.767), so the two failure modes move the metrics in different directions.