No edit points
Paragraph-sized ideas did not map cleanly to individual visual moments.
PRODUCTION SYSTEM · BUILT + DELIVERED
A video pipeline where
audio owns time.
Turning a script, generated narration, timing data, motion components, and visual review into one controlled production workflow.
- For
- A viewer with 107 seconds
- Industry
- Motion graphics
- System
- Claude workflow + Remotion
- Deliverables
- Scene schedule + final film
01 / THE FRICTION
The render wasn’t hard.
Keeping it in sync was.
A narrated explainer crosses several different systems: writing, voice generation, timing, visual design, component construction, animation, and rendering. A small change to the narration can move every beat that follows it.
If scenes are timed by feel or hardcoded directly into components, the production slowly becomes a collection of local fixes. Each correction creates another place for picture and sound to drift apart.
The narration needed to become production data—not just an audio file laid underneath the edit.
02 / BEFORE THE BUILD
The awkward parts became
the architecture.
The demonstration was built in stages, with rendered frames used as an audit trail. Four recurring failure modes shaped the finished workflow.
Guessed timing
Durations based on the script were always slightly different from the spoken delivery.
Hardcoded scenes
Timing placed inside components made every narration revision a cascade of edits.
Code-only confidence
A mathematically correct animation could still feel late, rushed, clipped, or simply wrong.
03 / THE SYSTEM
Nine stages.
One source of timing truth.
The script is divided into atomic beats. Narration returns character-level timestamps. Those timestamps become a scene schedule that every component reads. Nothing downstream gets to invent its own clock.
- 01Script
Break narration into short beats, each carrying one meaning and one visual idea.
- 02Time
Generate the voice and retain the timestamp attached to every spoken character.
- 03Schedule
Map each beat to exact visual start, speech start, speech end, and exit frames.
- 04Build
Drive reusable scenes and motion components from the shared schedule.
- 05Inspect
Render frames at sync points, watch the film, adjust, and render again.
THE OUTPUT
The Apollo 11 demonstration.
APOLLO 11 · 1:47
The finished film is the proof artifact. Its script, narration, scene timing, visual assets, motion, and rendered review all passed through the workflow described here.
04 / THE GUARDRAILS
The workflow refuses to guess.
01
No guessed duration. Audio timing comes from the generated narration, not estimated reading speed.
02
No overloaded scene. One beat carries one visual idea. A second idea requires a second beat.
03
No abrupt arrival. The visual begins before the spoken line and remains long enough for the moment to breathe.
04
No hardcoded clock. Components read their frames from the shared scene schedule.
05
No trusting the math alone. Every important sync point is rendered and inspected by eye.
05 / WHAT CHANGED
From nudging scenes
to directing a system.
BEFORE
Estimate the narration length
Place scenes by feel
Store timing inside components
Fix drift one scene at a time
Discover problems in the final render
NOW
Generate narration with timestamps
Map speech directly to visual beats
Render from one scene schedule
Reuse a tested motion vocabulary
Inspect the exact frames that matter
THE PRINCIPLE
Audio owns time. Everything else follows.
06 / THE HUMAN PART
A pipeline can keep time.
It cannot direct the film.
Approval gates sit between the script, art direction, narration, timing, asset plan, and component architecture. The workflow preserves those decisions instead of silently carrying on. Software handles continuity and production mechanics; a person decides what the viewer should understand and how the moment should feel.
This case study is based only on the independently created Apollo 11 demonstration. It contains no client or employer material.
THE OUTPUT DOESN’T HAVE TO BE VIDEO
Where does your process
keep drifting apart?
Show me the workflow When several tools and people have to stay aligned, the most useful build may be the system between them.