Reuse a composition: variants, re-runs and Hypit Studio
The second video should cost a fraction of the first. This guide is about keeping the composition in a state you can re-run.
Keep the composition, not just the file
A rendered MP4 cannot be edited by an agent. A composition — script, timing plan and tracks — can. Keep it in the repository next to the script.
Studio for the human pass
Hypit Studio opens the composition so you can inspect sources and results, adjust timing and appearance, and hand the change back to the agent as a script or stylesheet edit.
Variants as a first-class idea
One command can produce many takes and edits. That is how a format gets tested: same structure, different hooks, different orderings.
Step by step
1. Commit the composition
Treat the project like code: script, stylesheet and run source in version control, generated assets out of it.
2. Change only the script for a new episode
New episode, same format: replace the script and the media source, then re-run.
3. Fan out variants
Run with a variant count to produce several takes at once, then compare before spending on the final render.
4. Promote the winner
Once a variant wins, freeze that script and stylesheet as the template for the next cycle.
After this
The measure of a working format is that the tenth run is boring — because nothing surprises you any more.
Keep reading
FAQ
What exactly should be in version control?
Script, stylesheet, run source and small assets. Keep large generated media out of git and reference it by path.
Can two people work on the same composition?
Yes, as long as the same conventions apply — the composition is files, so normal review practices work on it.
How do I keep styles consistent across variants?
Keep the brand rules in the stylesheet and let the script vary; that is the point of separating look from content.