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
Edit Director - Hybrid Pipeline
When To Use
This stage creates the layered edit logic for a source-led video with support elements. The order matters: anchor cut first, support layers second.
Prerequisites
| Layer | Resource | Purpose |
|---|---|---|
| Schema | schemas/artifacts/edit_decisions.schema.json |
Artifact validation |
| Prior artifacts | state.artifacts["assets"]["asset_manifest"], state.artifacts["scene_plan"]["scene_plan"], state.artifacts["script"]["script"] |
Source/support assets and timeline intent |
| Playbook | Active style playbook | Typography and motion consistency |
Process
1. Lock The Anchor Cut First
The viewer should understand the story before support overlays are added. If the anchor cut is weak, support layers will not save it.
2. Add Support In Priority Order
Typical order:
- subtitles,
- speaker or context labels,
- diagrams or stat cards,
- optional inserts,
- CTA elements.
3. Protect Readability
Never stack too many support layers in one moment. If subtitles, labels, charts, and overlays collide, simplify.
4. Use Metadata For Layering Logic
Recommended metadata keys:
anchor_cut_noteslayer_orderoverlay_windowsvariant_edit_rules
5. Quality Gate
- the anchor cut works on its own,
- support layers clarify instead of distract,
- mobile readability survives,
- variants remain consistent.
Common Pitfalls
- Trying to fix a weak cut with extra graphics.
- Letting support layers compete with the source.
- Building each platform variant as a separate editorial philosophy.