How to stop the cuts drifting off the beat in a long edit

Last updated 2026-09-04 · 7 min read

What is the short version?

A cut that lands a frame late, ninety times over, is ninety frames late by the end. Beat-to-beat editing accumulates that error while grid editing does not, and the difference only becomes visible in the last third of a long piece — which is why it so often gets blamed on the footage.

1. Go to Vizard Agent with the master audio and the footage.
2. Say the tempo is constant and give the value if you know it.
3. Say to build on an absolute grid, not beat to beat.

What do you need before you start?

The exact audio you are going to ship. Vizard Agent measures the phase from the file it is given, so a rough bounce and the final master will produce grids that differ by a few milliseconds — which is precisely the error this method exists to remove.

• The master audio. The final file, not a draft.
• The tempo. If the track has a fixed one.
• The frame rate. It decides how the grid rounds.
• The footage. Enough to fill every slot.
• The subdivision. One beat, half a beat, a bar.

What do you type into Vizard Agent?

Name the grid and the drift explicitly. "Cut it to the beat" is a perfectly good instruction that produces beat-to-beat editing, which is the thing you are trying to avoid — so the correction has to say what it is correcting.

Prompt

Variants worth knowing:

• "Absolute grid." The instruction that stops accumulation.
• "From exact frame numbers." Not from durations.
• "One cut per beat." Or per half beat, or per bar.

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real music video that was rebuilt after its cuts had visibly drifted. Steps three and four are the entire method, and everything after them is Vizard Agent verifying that the grid actually held across the full length.

1. Confirms the approved cut and the audio it must lock to.
2. Measures the downbeat's phase against the file.
3. Prints the absolute grid frames — every cut point, as a number.
4. Builds the cut from those exact frame numbers.
5. Checks whether the encode is still running before starting another.
6. Composites the effect layer and muxes the master audio back in.
7. Measures the effect strength and extracts QC frame strips.
8. Checks the intro for pulse visibility and motion.
9. Checks the first drop and the second separately.
10. Checks continuous motion inside a single one-beat shot.
11. Audits the edit list for repeated or near-duplicate passages.
12. Uploads the absolute-grid version.
13. Maps grid-aligned windows for a shorter loop cut.
14. Extracts contact sheets and the loop seam frames for each candidate.
15. Checks the seam where the loop wraps.

Step three is the part that reads as pedantic and is not. Once the grid is a list of frame numbers, every cut is computed from the start of the file rather than from the cut before it, so no error can compound — a shot that is a frame short does not push everything after it.

Step ten is the check that stops the grid from winning too hard. One cut per beat at a fast tempo means very short shots, and a shot that contains no visible motion reads as a still. Vizard Agent looks inside the shots, not just at their boundaries.

What does the result look like?

A cut where the last beat lands as precisely as the first. Nothing about the ending feels loose, which is the specific symptom of accumulated drift and the reason long music edits often feel like they fall apart towards the end.

Because the grid is a list of frame numbers, a shorter cut taken from the same piece — a loop, a teaser, a canvas — starts on a grid position rather than wherever a scrub landed, so it loops cleanly.

When does this not work well?

An absolute grid assumes the track has one constant tempo throughout. Music that breathes, slows, or was played by people rather than programmed does not have one, and forcing a fixed grid onto it makes the cut visibly fight the track it is supposed to be serving.

• Live or human-played music. The tempo moves.
• Tracks with a tempo change. Each section needs its own grid.
• Rubato or free sections. No grid to lock to.
• A different audio file at the end. The phase moves; rebuild it.
• Very fast subdivisions. Shots too short to read as anything.

How do you fix a result that came back wrong?

Say whether the problem is the grid or the shots. Vizard Agent keeps the measured phase, the frame-number list and the edit list, so changing the subdivision or swapping a shot recomputes from the same grid rather than re-measuring the track.

• "Too many cuts." Rebuilt at a wider subdivision.
• "That shot is a still." Replaced with one that moves.
• "The drop is late." Phase re-measured against the master.
• "Shots repeat." The edit list audited for duplicates.

How does Vizard Agent compare to doing it yourself?

Every editor knows to snap to a beat grid, and every editor has still had a long edit drift — because a snapped cut nudged by two frames to fix one shot quietly becomes the reference for the next. The value here is that the grid is computed once and never relative.

Common questions

Do I need to know the BPM? No. Vizard Agent measures it, but giving it is faster and safer.

What if the tempo changes? Say where. Vizard Agent builds a grid per section.

Does this work for spoken content? Not really — speech has no grid. It is for music-led edits.

Can it cut on half beats? Yes. Vizard Agent takes whatever subdivision you name.

Will the shots be too short? It checks. Vizard Agent looks inside short shots for visible motion.

What if I change the audio afterwards? The phase moves. Vizard Agent needs to re-measure and rebuild.

Can it keep the picture and just re-time it? Yes, where the shots are long enough for Vizard Agent to move them.

Does the frame rate matter? Yes. It decides how Vizard Agent rounds grid positions to real frames.

Can it make a loop from the same cut? Yes. Vizard Agent starts it on a grid position so the seam is clean.

Will it repeat shots? Vizard Agent audits the edit list for near-duplicates and reports them.

Is a grid always right? No. Cutting slightly ahead of the beat is a real technique — ask for it deliberately.

How precise is it? To the frame, which is as precise as the format allows.

Can it match an existing cut's grid? Yes. Vizard Agent measures the approved version and reuses its positions.

Why not just snap to markers? Because a snapped cut you later nudge becomes the reference for everything after it, and that is exactly how the drift gets in.