Animatic Workflow
The edit builds scenes from animatics - rough timed previews - before full passes. This matches the authoritative editorial layer: the OMC export includes an OTIO timeline (one_small_crawl_v001) and a 45-shot list, so animatic-first is the proven path from script shots to the final edit.
Evidence on disk (August)
- Animatic - Scene 5.mp4 (Aug 10) -> later scene5.mp4 (107 MB, Aug 19)
- Scene4Animatic+Archive.mp4 (Aug 14) - animatic that already layers the archive footage (6403-our-trip-of-usa), then Scene4.mp4 (Aug 17)
- Scene 2 passes run sc02_0010 -> sc02_0072 + a sc02_v1 (146 MB) - granular versioning of the same scene (scene-cutdowns-august)
Authoritative editorial layer
- OTIO timeline one_small_crawl_v001 (otio-timeline) - the machine-readable edit decision interchange for resolve/Nuke.
- 45-shot shot list with per-shot OMC sidecars (script-and-shot-list) - animatics are timed against these shots.
- render-youtube-final-py automates the final render (render-youtube-final-py).
Why it matters
- Animatic-first lets the team lock pacing before investing in full AI/archive renders; ties directly to the AI passes of ai-agent-pipeline.
- Shot ids in animatics (sc02_0010…) match the naming schema (naming-schema).