- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
DualCast fine-tunes Wan2.2-I2V-14B to generate a presenter showing a product, given a product image, a presenter image and a script. The two images are VAE-encoded and attached to the video latent as an extra first frame (product) and an extra last frame (presenter), marked by an indicator channel; their CLIP features are appended to the text context. Training adds a mask-weighted flow-matching loss (overlap 3, product 2, face 2, background 0.5) and 50/25/25 dropout over dual/product-only/human-only inputs, and keeps Wan2.2's high/low-noise expert split. The 10K training clips are synthetic: first frames from GPT-Image-2, videos from Wan2.7, filtered by GPT-5.5. Evaluation uses ViCLIP, a CLIP-based subject-consistency score (S2V-C), Qwen3.5 judge ratings, VBench metrics and a 50-person user study.
Critical strengths
The task is practical and the design is light: two extra latent frames and one indicator channel on an existing I2V model, with one checkpoint serving dual, product-only and human-only inputs. The comparison covers four open-source and four commercial systems and includes a user study.
Critical weaknesses
-
The central claim is never tested. The thesis is that fixed front/rear positions remove role ambiguity and feature competition between product and presenter, but no experiment isolates position. "w/o Dual-End" (Table 2) is not defined, and App. F states that its identity drop "is not a positional-effect estimate"; Sec. 3.1 adds that roles are also carried by CLIP-token order and role-specific text. Temporal concatenation of VAE reference latents is already used in HuMo, which the paper cites, so position-as-role is the main new element, and it is the one left unverified. The obvious controls are missing: both references on one side, swapped sides, and a plain dual-reference fine-tune of the backbone (or VACE) on the same 10K clips. Without them, Table 1 cannot separate the conditioning design from domain fine-tuning.
-
The evaluation skips the task's key requirement and is confounded by the data. Product fidelity, the first requirement in the abstract, is absent from the main comparison: ProdID and ArcFace ID-Ret appear only in ablations on a different case set. The one objective subject metric in Table 1 (S2V-C 0.596) ties VACE and is below the base model (0.717), and the user study gives 52% product preference vs. VACE. The headline wins are LLM-judge scores on six mid-clip frames at ≤512 px, with margins around 0.02 (≈0.1 on the raw 0-5 scale) and no variance. Training targets are Wan2.7 outputs, and Wan2.7 is also a comparator. Training and test prompts come from the same generator (Qwen3.6-27B), and training clips were pre-filtered by GPT-5.5 for quality and prompt compliance, close to what the judge rates. After fine-tuning on 10K e-commerce clips, winning on "EcomStyle" and "Interaction" against general-purpose models is expected. The user study leaves out all commercial systems, and the signed-rank test specified in its protocol is not reported (App. A.4).
Questions for authors
- Can you run position-controlled ablations on the same data (same-side slots, swapped slots, roles given only by text/CLIP order) and a plain dual-reference fine-tune of the backbone? This would change my assessment more than anything else.
- Please add ProdID, a product-region similarity (e.g., DINO features on the segmented product) and ArcFace ID-Ret for every method in Table 1, with per-case variance. Please also report how often each method drops one of the two subjects, since that is the failure mode the paper is built around.
- App. A.4 says the signed-rank test cannot be computed "without participant/case records and test outputs." Do you have the raw study data? Why were the commercial systems, Wan2.7 in particular, excluded from the study?
- How are frame-level masks aggregated onto temporally compressed latent positions? App. E describes the issue but not the procedure used.
- How was the single-image Wan2.2-I2V given two references in Table 1, and what exactly does "w/o Dual-End" keep?