How to stop separately rendered segments drifting out of sync when you join them

Last updated 2026-09-10 · 8 min read

What is the short version?

A long film built segment by segment is a chain of small rounding errors. Each one is invisible. Twenty of them in a row is half a second, which is the difference between a cut landing on a word and landing after it.

1. Go to Vizard Agent with the assembled picture.
2. Say the sync slips as the film goes on.
3. Ask for exact frame counts, segment by segment.

What do you need before you start?

The segments and the intended timings. Vizard Agent works from the difference between what each segment was supposed to be and what it actually came out as, so the plan matters as much as the files — without it, there is nothing to measure the drift against.

• The rendered segments. All of them.
• The edit plan or timings. What each one should be.
• The frame rate. Everything must share it.
• The voice track. Kept separate, ideally.
• Where you first notice it. A useful cross-check.

What do you type into Vizard Agent?

Describe the symptom rather than diagnosing it yourself. Sync that is fine early and clearly wrong late is a specific shape of problem, and saying so out loud points Vizard Agent straight at accumulated rounding rather than sending it hunting for one bad clip somewhere in the middle.

Prompt

Variants worth knowing:

• "Fine at the start, off at the end." Names the shape.
• "Frame counts, not seconds." Seconds hide the error.
• "Verify before the audio goes back." Cheaper order.

What does Vizard Agent actually do?

Here is the sequence on a real documentary assembled from a few dozen separately rendered segments. Note that the fix is not a nudge at the end — it is making every segment come out at the length it was asked for.

1. Concatenates the picture and separates the voice track.
2. Checks each segment's frame count.
3. Compares each against the intended count.
4. Finds the drift is per-segment rounding, not one bad clip.
5. Rewrites the renderer to produce exact frame counts.
6. Re-renders every segment with that timing.
7. Verifies the counts before joining anything.
8. Concatenates again and checks continuity across the joins.
9. Confirms the last spoken word against the source length.
10. Puts the voice track back and re-measures.

Step three is where the diagnosis actually happens. Durations in seconds round away the evidence, so a segment that is two frames long looks correct until Vizard Agent counts frames instead.

Step five is the real repair and the reason nudging does not work. If the renderer keeps producing approximately-right segments, every future change reintroduces the same drift, so Vizard Agent fixes the production of the segments rather than their alignment.

Step seven is worth insisting on separately. Verifying the counts before anything is joined means a bad segment is caught while it is still one file, rather than after it has been baked into a thirty-minute concatenation that has to be taken apart again.

Step nine is a check people skip and regret. A tail that ends a few frames short clips the last word, and it is much easier to catch before the mix than after somebody watches it.

What does the result look like?

A joined picture whose total length is exactly what the plan said it would be, with the voice sitting where it did in the first minute all the way through to the last. The cuts land on the words again, and the ending arrives where it was supposed to.

Because the segments Vizard Agent produced are now exact, a later change re-renders one segment without shifting everything that follows it.

When does this not work well?

Not every late sync problem is accumulation, and Vizard Agent will tell you when it is not. A mismatched frame rate, variable frame rate source footage from a phone, or an audio track that was itself stretched somewhere upstream will all produce very similar symptoms from a completely different cause.

• Mixed frame rates. Convert first, then measure.
• Variable frame rate phone footage. Needs conversion.
• Stretched or resampled audio. A different fault.
• A single bad clip. That is not drift, it is a jump.
• Sync wrong from frame one. An offset, not accumulation.

How do you fix a result that came back wrong?

Tell Vizard Agent where it still slips and how far in. If the accumulated drift is gone but one single moment is off, that is now a different problem with a different fix, and it is worth saying so plainly rather than asking Vizard Agent for another whole timing pass.

• "Still drifts." Vizard Agent re-counts and finds the survivor.
• "One cut is off, the rest are fine." A clip issue, not drift.
• "The last word is clipped." The tail gets extended.
• "It is off from the start." A fixed offset instead.

How does Vizard Agent compare to doing it yourself?

By hand people fix this at the end, by sliding the audio until the middle looks right, which trades a growing error for two smaller ones either side of wherever they were looking. Vizard Agent removes the error at its source instead.

Common questions

Why frames and not seconds? Seconds round. Vizard Agent counts frames because that is where the error lives.

How much drift is normal? None, once the renders are exact. Any accumulation is a bug.

Can it fix it without re-rendering? Sometimes, but Vizard Agent will usually recommend against it.

Does the audio need re-cutting? No. Vizard Agent puts the same voice track back onto a correct picture.

What if my sources are mixed frame rates? Say so. Vizard Agent converts before measuring.

Will this change the look? No. Only the segment lengths change.

Can it tell me where it starts? Yes. Vizard Agent reports the drift segment by segment.

What about variable frame rate footage? Convert it first; Vizard Agent will tell you if that is the cause.

Does it check the ending? Yes, against the source, so the last word is not clipped.

Can I re-render one segment later? Yes, once the counts are exact. That is the point.

Is this the same as an audio offset? No. An offset is constant; drift grows.

Will it catch a single bad clip too? Yes, and Vizard Agent will say it is a jump rather than drift.

Does it work on very long films? Yes. The longer the film, the more this matters.

Why did nobody notice earlier? Because two frames is invisible and forty is not.