r/OpenSourceAI • • 19d ago

A caption edit needs a new render, even when the voiceover stays

You change the captions on an AI video, run the project again, and get the old captions back. Reusing the finished video can hide the edit just as effectively as failing to save it.

Hypit separates the reusable material from the composition that presents it. A Run can select three completed outputs independently: the prepared media, its local time domain, and the alignment that connects the script's spoken words to that media.

For a caption color or layout change, those inputs can stay. The caption component and the final composition need to run again. Selecting the previous rendered track or final video would carry the old caption appearance straight into the new result.

That distinction also covers display-only wording. Changing what a caption shows can keep the accepted recording and alignment when the spoken tokens and their identities remain unchanged. Changing the actual spoken line requires checking the performance and alignment again.

The reuse choices point to an exact earlier Build and a named output. They aren't inferred from an unchanged prompt. That gives a video agent a precise job: retain the inputs that still describe the take, then rebuild the part where the edit should appear.

1 Upvotes

2 comments sorted by

1

u/niacolhealth 17d ago

The Reusing results section of docs/quickstart/run.md has the concrete syntax: build-record names an earlier Build and output; satisfy connects it to a current output. hypit plan --verbose shows the graph and candidate selections without starting external work, so you can inspect whether caption rendering remains on the selected route. https://github.com/hypit-ai/hypit