Establish a version you can compare against
After accepting a base film, record its script, asset selections, aspect ratio, audio and graphics. Keep the associated Run and Build Result, not just the final MP4.
If the base version is unstable, changing the character, copy and style together makes it hard to know which change helped.
Match the work to the change
Whether another model call is needed depends on which assets already exist and how components are organized. A variation is not automatically free.
- New title, keywords or call to action: inspect the text and graphic layers first.
- New narration: you may need new audio, alignment and checks of related graphic events.
- New character or product: review asset generation, consistency and every affected shot.
- New language: check speaking rate, duration, caption length and pronunciation together.
Explicitly reuse accepted results
Tell the agent which assets are accepted and ask it to explicitly select those existing outputs in the new Run. A result being on disk does not mean the next Build will automatically use it.
Starting from the accepted version, change only the opening copy and closing call to action. Reuse the accepted character, product shots and music. Before submitting a Build, list the tasks that will run again, explain why, and review any additional cost.
Let each version answer one question
Try a question-led, result-led or scene-led opening while keeping the main demonstration consistent. This makes it easier to compare how viewers respond to the beginning.
Use clear version names in files and tasks, such as hook-question and hook-result. Keep actual publishing results separate from subjective preferences.
After a failure, inspect what already exists
A failed Build does not necessarily mean every step produced nothing. Inspect completed assets and the point of failure before choosing what to repeat.
Stopping a local waiting command may not stop work in the background. Check the Runtime’s actual state before submitting another potentially paid generation task.
Source and scope
This is an independent guide, not an official Hypit instruction. Adapt the steps to your project environment.
Read the source documentation ↗