Varosity
All guides

Multi-shot consistency with locked references

Enforce visual continuity across multi-shot video sequences. Lock one reference image, vary model and prompt per shot.

Multi-shot consistency with locked references

When producing multi-shot video sequences with Varosity, visual consistency across shots is critical. Without a locked reference image, each shot will diverge visually, creating jarring cuts and broken narrative flow.

This guide enforces a mandatory two-phase workflow:

1. Reference Image Selection — you explicitly pick a locked reference from candidates 2. Reference Binding — all shots use the same reference URL; only model and prompt vary per shot

When This Matters

  • Music videos — same performer, multiple angles
  • Product reels — same product, different lighting/framing
  • Brand content — same subject, multiple perspectives
  • Interview sequences — same person, varied shot types
  • Travel montages — same location context, varied framing
  • Any production where visual continuity is non-negotiable

Why Not Auto-Select?

Because consistency is a creative decision. Auto-selection removes your judgment about the aesthetic baseline. This workflow gates that choice explicitly — you lock the reference, not the algorithm.

---

Phase 1: Reference Image Selection

Goal: Lock down ONE reference image URL that will apply to all shots in the production.

Steps

1. You provide a reference or we generate candidates - If you supply a reference image directly → we lock it immediately - If not → proceed to step 2

2. Generate candidate reference images - Varosity generates 3–4 reference options - Each shows your subject under different lighting/aesthetics - Examples: "bright stage", "moody amber", "neutral", "cinematic"

3. You select the reference - View all candidates side by side - Pick the ONE that locks the visual tone for your entire video - We do not auto-select — your choice matters

4. Reference is locked - Your selection gets stored with a timestamp - Tagged as "LOCKED_REFERENCE" - This URL is now immutable for this production

Example Phase 1

You: "Create a 4-shot country music performance video. Same performer, different angles."

Varosity: "Let me generate reference options for your performer aesthetic."

[Displays 4 reference images]

Option 1: Bright, well-lit stage (clinical feel) Option 2: Moody amber lighting (intimate feel) ← Your choice Option 3: Neutral professional backdrop Option 4: Dramatic side-lit (artistic feel)

You: "Option 2 — the moody amber lighting feels right."

Varosity: "✓ Locked reference: Option 2. All shots will now use this reference. Moving to Phase 2: generating individual shots." ```

---

Phase 2: Locked Reference Binding

Goal: Generate all shots with the same reference_image_url, varying only model and prompt.

Immutable: reference_image_url (locked from Phase 1) Variable: model, prompt, shot_type

For Each Shot

1. Varosity suggests the optimal model for your shot description - "Wide establishing shot" → Kling 3.0 (environmental context) - "Close-up detail" → Veo 3.1 (fine detail + motion) - "Micro-movements" → Seedance 4.5 (smooth, fluid motion)

2. You confirm the model (or we auto-pick the top recommendation)

3. We generate the shot with: - Your shot-specific prompt (angle, framing, action) - The LOCKED reference from Phase 1 - The chosen model

4. All shots submit in parallel - Don't wait for shot 1 to finish before submitting shot 2 - Faster turnaround

Example Phase 2: Country Music Video

Shot 1: Wide establishing (kling-3.0)
  Prompt: "wide stage view of country performer at microphone, intimate venue, moody amber lighting"
  Reference: [LOCKED from Phase 1]

Shot 2: Close-up face during chorus (veo-3.1) Prompt: "close-up face during passionate chorus, warm lighting, emotional expression" Reference: [LOCKED from Phase 1]

Shot 3: Hands on instrument (seedance-4.5) Prompt: "detailed hands on guitar strings, fingerstyle technique, intimate lighting" Reference: [LOCKED from Phase 1]

Shot 4: Performer + crowd (kling-3.0) Prompt: "performer and front row audience engaged, warm moody venue lighting" Reference: [LOCKED from Phase 1]

All 4 shots submitted in parallel. All use the same reference. Only model and prompt vary. Result: Visually consistent, performance-optimized video. ```

---

Why This Matters: Visual Continuity

Without locked references: - Shot 1 rendered by Veo might show moody amber lighting - Shot 2 rendered by Kling might show bright cool lighting - Shot 3 rendered by Seedance might show neutral tones - Result: jarring cuts, broken narrative flow, viewer disorientation

With locked references: - All 4 shots reference the same aesthetic baseline - Models can optimize for detail/motion within that constraint - Result: unified look, professional feel, narrative coherence

---

Reference Image FAQ

"Can I change the reference mid-production?" No. Changing the reference mid-production breaks continuity. If you want a different aesthetic, start a new production with a new locked reference.

"What if I don't like any of the reference candidates?" Request regeneration. Varosity will generate 3–4 new options with different prompts or variations. Keep iterating until you find one that resonates.

"Can multiple productions share the same reference?" Yes, but not recommended. Each production should lock its own reference to ensure full control over aesthetics and avoid unexpected cross-production drift.

"What happens if the reference image expires?" Varosity maintains reference URLs. If a reference does expire or fail, you'll see an error and can regenerate a new set of candidates and re-lock.

"Do all shots have to match the reference exactly?" No. The reference *guides* consistency, not enforces pixel-perfect matching. Models still vary by prompt — a close-up will look different from a wide shot. The reference ensures they feel like they're in the same visual world.

---

Common Pitfalls

Pitfall 1: Not Blocking Until Selection **Mistake:** Agent auto-selects the "best" reference without waiting for your input. **Fix:** Always wait for explicit user confirmation before locking. Consistency is a creative choice.

Pitfall 2: Reference Mismatch in Late Shots **Mistake:** Shot 3 accidentally uses a different reference URL than Shots 1–2. **Fix:** Verify all shots list the same reference before submission. Most agents show you the locked reference URL for confirmation.

Pitfall 3: Sequential Generation Instead of Parallel **Mistake:** Agent waits for Shot 1 to complete before submitting Shot 2. **Fix:** All shots should submit in parallel for faster turnaround. Reference locking enables this.

Pitfall 4: Identical Prompts for All Shots **Mistake:** All shots use the same prompt (e.g., "wide stage view"). **Fix:** Vary the prompt per shot (wide → close-up → detail) while keeping the reference locked. Variety in framing + consistency in aesthetic.

Pitfall 5: Forgetting to Verify Job Status **Mistake:** Agent assumes all shots succeeded and stitches without checking. **Fix:** Poll job status for each shot before final render. One failed shot breaks the sequence.

---

Workflow Guardrails

RuleStatusViolationFix
Lock reference in Phase 1MUSTAttempt to generate without Phase 1 lockAgent FAILS. Repeats Phase 1.
Use same reference URL for all shotsMUSTAny shot uses different URLAgent FAILS. Regenerates with correct reference.
Block until user selectsMUSTAuto-select without confirmationAgent FAILS. Prompts for explicit selection.
Suggest model per shotSHOULDGenerate without model suggestionAgent WARNS. Consider calling suggest_model() for optimization.
Vary prompts per shotSHOULDAll shots use identical promptAgent WARNS. May reduce visual variety.
Generate in parallelSHOULDSequential generationAgent WARNS. Parallel generation is faster.
Poll job statusSHOULDAssume success without checkingAgent WARNS. Some shots may have failed silently.

---

Integration: Using This Skill with Your Agent

If You're Using Claude Desktop The `varosity-multi-shot-consistency` Hermes skill is available. Ask your agent: > "Create a 3-shot product reel using the multi-shot consistency skill. Lock a reference first."

If You're Using MCP Directly The skill orchestrates these Varosity MCP tools: - `mcp_varosity_pick_reference_images` — Phase 1: candidate generation - `mcp_varosity_suggest_model` — Phase 2: per-shot model ranking - `mcp_varosity_generate_video` — Phase 2: shot generation with locked reference - `mcp_varosity_get_job` — Poll job status - `mcp_varosity_render_project` — Final stitch

If You're Using the REST API Call `/v1/video/generate` with: - `reference_image_url`: your locked reference (same for all shots) - `prompt`: shot-specific prompt - `model`: chosen model

---

Next Steps