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.7 KiB
1.7 KiB
Scene Director - Hybrid Pipeline
When To Use
You are translating the hybrid structure into a visual system that keeps the source visible and the support layers under control.
Prerequisites
| Layer | Resource | Purpose |
|---|---|---|
| Schema | schemas/artifacts/scene_plan.schema.json |
Artifact validation |
| Prior artifacts | state.artifacts["script"]["script"], state.artifacts["idea"]["brief"] |
Hybrid structure and source truth |
| Tools | frame_sampler, scene_detect |
Optional source inspection |
| Playbook | Active style playbook | Layout consistency |
Process
1. Keep The Anchor Medium Visible
If the piece is source-led, the source must remain visually primary in the scene plan. Do not hide the anchor behind constant overlays.
2. Reserve Support For Clear Jobs
Use support scenes for:
- chapter transitions,
- clarifying diagrams,
- stat emphasis,
- CTA or summary moments,
- gap-filling inserts.
3. Plan Variant Safety
If the project needs multiple aspect ratios, define where:
- subtitles live,
- speaker labels live,
- chart or code safe zones live,
- crop-sensitive source media becomes unsafe.
4. Use Metadata For Balance Rules
Recommended metadata keys:
anchor_rulessupport_rulessafe_zonesvariant_rulesoverlay_density_limits
5. Quality Gate
- the anchor medium stays primary where intended,
- support layers are limited and purposeful,
- aspect-ratio planning is explicit,
- no scene relies on invisible future magic.
Common Pitfalls
- Turning source-led scenes into overlay soup.
- Forgetting variant-safe zones until compose.
- Using generated inserts for every transition.