mirror of
https://github.com/hanzoai/video.git
synced 2026-11-03 04:21:39 +00:00
11 production pipelines, 47 tools, 124 agent skills. Supports cloud APIs (fal.ai, OpenAI, ElevenLabs, Suno, HeyGen, Runway) and free local providers (diffusers, Piper TTS, WAN 2.1, Hunyuan, CogVideo). Co-authored-by: Hanzo Dev <[email protected]>
1.6 KiB
1.6 KiB
Scene Director - Localization Dub Pipeline
When To Use
Plan how each localized deliverable will handle timing, visible speech, subtitles, and on-screen text. This is where the pipeline decides whether to preserve the original cut, cover mouth-visible sections, or attempt lip sync.
Reference Inputs
docs/localization-dubbing-best-practices.mdskills/creative/video-editing.md
Process
1. Choose The Dub Mode Per Deliverable
Use one of:
subtitle_onlydub_audio_onlylip_syncedhybrid_covered
hybrid_covered means using B-roll, graphics, or text coverage during sections where visible mouth mismatch would be distracting.
2. Map Timing Risk
Identify scenes likely to drift because of:
- fast speech,
- dense legal copy,
- multiple speakers,
- fast cuts,
- visible close-up mouths.
3. Note On-Screen Language Dependencies
Record scenes that contain:
- UI text,
- lower thirds,
- title cards,
- baked-in subtitles,
- charts or labels that may need replacement or coverage.
4. Use Metadata For Variant Planning
Recommended metadata keys:
dub_mode_maptiming_risk_mapon_screen_text_replacement_maplanguage_variant_notes
5. Quality Gate
- every deliverable has a defined localization treatment,
- timing risks are mapped,
- lip-sync usage is selective,
- text replacement needs are not hidden.
Common Pitfalls
- Assuming dubbed audio will fit the source timing exactly.
- Choosing lip sync for every shot instead of only the shots that justify it.
- Forgetting about baked-in text until compose time.