How to cut to the rhythm of a track you cannot include in the file

Last updated 2026-09-15 · 8 min read

What is the short version?

Short-form platforms let you attach a track from their own library, and that is the only legitimate way most of those tracks reach your video. It also means the edit has to be built to music that will not exist until after you upload.

1. Go to Vizard Agent with the footage and the track's name.
2. Say you will add the audio in the app.
3. Ask for a silent cut built on that track's beat grid.

What do you need before you start?

The footage and the track's identity. Vizard Agent works from the track's published tempo rather than from an audio file, so you do not need to supply the music — you need to name it precisely enough that the right tempo can be looked up.

• The footage. Enough for the length you want.
• The track name. Specific, so the tempo is the right one.
• Where it will be posted. The library differs per platform.
• The target length. In beats, ideally, not seconds.
• Any fixed cards. Logos and proof shots need beats too.

What do you type into Vizard Agent?

Tell Vizard Agent that the audio is going on afterwards, in the app. Without that piece of context you get a cut with its own music in it, and stripping that music out later leaves you with an edit that was paced against a completely different track.

Prompt

Variants worth knowing:

• "Deliver it silent." The instruction that matters.
• "Structure the cuts on its beat grid." Not by feel.
• "In exact frame counts." Where drift is prevented.

What does Vizard Agent actually do?

Here is the sequence Vizard Agent worked through on a real fifteen-second sports reel built for a platform track. Notice that the tempo here is researched rather than measured, because there is no audio file in hand for it to measure in the first place.

1. Checks the track's published tempo.
2. Converts the tempo into a beat grid for the target length.
3. Works out the structure — a thirty-two beat, fifteen-second shape.
4. Retimes the silent cut onto that grid.
5. Locks the action block to an exact frame count.
6. Times the title and proof cards onto beats rather than into gaps.
7. Removes anything unsynced left over from an earlier version.
8. Reviews the storyboard against the intended beat positions.
9. Measures the retimed shots and corrects the ones that drifted.
10. Delivers a silent master at the exact duration.

Step one is the step that makes this possible at all. A track you cannot download still has a published tempo, and that single number is enough to build a grid that the real audio will line up with when you attach it.

Step five is what stops the cut sliding. Beats expressed in seconds accumulate rounding across a fifteen-second edit, so Vizard Agent converts the grid to frame numbers and builds to those — the same discipline that keeps any beat-matched edit honest.

Step ten matters because a silent file feels wrong to deliver and is exactly right here. Anything embedded would be stripped or muted by the platform, and a master with no audio track is the cleanest thing to attach music to.

What does the result look like?

A silent video at an exact length whose cuts sit on the beat grid of a track it does not contain. You attach the track in the app, and the edit lands — the action hits on the downbeats and the cards change on the bar.

Vizard Agent tells you the tempo and structure it built to, so a different track at the same tempo drops straight in.

When does this not work well?

This depends on the published tempo being right and the platform starting the track where you expect. A track with a tempo change, a long intro, or a version that differs from the one in the library will not line up, and the fix is to try the attachment and adjust.

• Tracks that change tempo. One grid will not fit.
• Long intros. The app may start you before the beat.
• Different versions. The library's cut may differ.
• Live or loose recordings. No steady grid to build on.
• Platform trimming. Where it starts is not always yours to set.

How do you fix a result that came back wrong?

Say what actually happened when you attached the audio in the app. Because Vizard Agent built the cut to a stated tempo, "it drifts after the first few seconds" and "it is offset right from the start" are two different faults with two different corrections.

• "It is offset from the start." An intro offset, not drift.
• "It drifts as it goes." The tempo was slightly wrong.
• "The cards miss the beat." Re-timed onto the grid.
• "Make it thirty-two beats." Structure stated in beats.

How does Vizard Agent compare to doing it yourself?

By hand the cut gets made to a rough copy of the track, then the music is stripped for upload — and the timing is now built against whatever that copy's tempo and start point happened to be. It lines up in the timeline and not in the app.

Common questions

Why deliver it silent? Because the licensed track is attached in the app, not embedded by you.

How does it know the tempo? Vizard Agent looks up what is published for that track.

What if the tempo is wrong? Say how it drifted and Vizard Agent rebuilds on a corrected grid.

Can it handle an intro offset? Yes. Tell Vizard Agent where the app starts the track.

Does the length matter? It helps to state it in beats. Vizard Agent converts to frames.

Will the cards land on beats? Yes, if you ask. Otherwise they sit where the edit needs them.

Can it build for two candidate tracks? Yes, one grid each, if the tempos differ.

What about a track I own? Then supply it and Vizard Agent measures rather than looks up.

Does it add sound effects? Vizard Agent can, though anything embedded will play under the app's music.

Will the export have an audio track at all? Tell Vizard Agent which you want; a silent file or a muted track both work.

Can it check my attachment? Send Vizard Agent the posted version and it will check the alignment.

Why not just use any music? Because the platform's own library is what your audience expects to hear on that feed.

Does this work for longer videos? Yes, though drift matters more, so Vizard Agent leans harder on frame counts.

Why did mine slip in the app? Because it was paced to a copy of the track rather than to its grid.