How to stop the cuts drifting off the beat in a long edit
Tell Vizard Agent to build the cut on an absolute grid rather than beat to beat. It measures the downbeat's exact phase, computes every cut point as a frame number on that fixed grid, and assembles from those numbers. The error at ninety seconds is then the same as the error at five.
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're trying to avoid. Give Vizard Agent the master audio you'll ship, since a rough bounce and the final master produce grids a few milliseconds apart.
Prompt
What does Vizard Agent actually do?
A cut that lands a frame late, ninety times over, is ninety frames late by the end. 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. In the session behind this article it:
- Confirmed the approved cut of a music video whose cuts had visibly drifted, and the audio it had to lock to, then measured the downbeat's phase against that file.
- Printed the absolute grid frames, every cut point as a number, and built the cut from those exact frame numbers.
- Composited the effect layer, muxed the master audio back in, measured the effect strength and extracted QC frame strips.
- Checked the intro, each of the two drops separately, and the motion inside a single one-beat shot, since a shot with no visible motion reads as a still.
- Audited the edit list for repeated or near-duplicate passages, then uploaded the absolute-grid version.
- Mapped grid-aligned windows for a shorter loop cut and checked the seam frames where each candidate loop wraps.
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 doesn't have one, and forcing a fixed grid onto it makes the cut visibly fight the track. A track with a tempo change needs a grid per section.
Common questions
Do I need to know the BPM? No. Vizard Agent measures it, but giving it is faster and safer.
What if I change the audio afterwards? The phase moves. Vizard Agent needs to re-measure and rebuild.
Why not just snap to markers? A snapped cut you later nudge becomes the reference for everything after it, which is how the drift gets in. Vizard Agent computes every cut from the start.