How to find which clip is breaking the audio when you join footage together

Last updated 2026-09-10 · 8 min read

What is the short version?

When footage from different sources is joined, one clip usually has audio in a slightly different format. The join then produces a click, a burst of noise or a silent patch — and turning the music up over it hides the symptom while leaving the damage in the file.

1. Go to Vizard Agent with the assembled cut.
2. Say the audio breaks at a join.
3. Ask which clip is causing it.

What do you need before you start?

The cut and roughly where you hear it. You do not need to identify the clip — that is the job — but saying whether it happens once or at several joins tells Vizard Agent whether it is looking for one odd input or a mismatch running through the whole batch.

• The assembled cut.
• Where you hear it. Roughly is enough.
• How many joins are affected. One, or several.
• Where the clips came from. A phone, a camera, a download.
• Whether music may cover it. Preferably not.

What do you type into Vizard Agent?

Tell Vizard Agent it happens at a join rather than describing it as a mix problem. "The audio sounds bad" invites a mix adjustment; "there is a click where two clips meet" points straight at the assembly, which is where the fault actually lives.

Prompt

Variants worth knowing:

• "Where two clips meet." Locates it in the assembly.
• "Which source clip." Asks for the cause, not a patch.
• "Rather than covering it." Rules out the easy answer.

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real vlog assembled from phone clips and a separate opening. The repair is made at the input rather than in the mix, which is the difference between fixing it and hiding it.

1. Groups the frames by clip so each upload maps to its exact moment.
2. Checks the footage audio levels and listens for usable natural sound.
3. Checks the assembled chapter lengths before adding the final mix.
4. Measures the music against the camera audio so it supports rather than covers.
5. Repairs the stitched audio at the source by re-encoding the timeline cleanly.
6. Locates the exact source clip carrying the broken audio packets.
7. Reads each clip's audio stream metadata to find the mismatch at the join.
8. Matches the odd clip's format to the rest of the footage.
9. Rebuilds the clean timeline and reapplies the music over it.
10. Checks the final waveform for continuity and a natural ending fade.
11. Runs a final check on the uploaded file for sync and pacing.

Step seven is the diagnosis. Two clips can both play perfectly on their own and still be incompatible at a join — a different sample rate, a different channel layout, a different codec — and none of that is audible until they are stitched together.

Step one looks like housekeeping and is not. Mapping each upload to the moment it occupies means a fault heard at a particular second can be traced back to a specific file straight away, rather than being hunted for by opening clips at random.

Step five and step eight are the difference between a fix and a workaround. Re-encoding the whole timeline cleanly removes the damage rather than hiding it, and matching the odd input's format to the others stops the same fault reappearing the next time you add a clip from that camera.

What does the result look like?

A continuous soundtrack with no click at the join, no dropout following it, and the music sitting at the level Vizard Agent measured for it rather than being pushed up to cover something underneath it that should not have been there.

The waveform is continuous, which is the check you can actually see.

When does this not work well?

Some clips arrive damaged. If a recording has genuinely corrupt packets in the middle rather than a format mismatch at its edge, the audio there cannot be recovered — it can only be replaced, cut around, or covered deliberately.

• Genuinely corrupt recordings. There is nothing to repair.
• Very short clips. Not enough audio to work with.
• Live-streamed sources. These often carry irregular timing.
• Variable frame rate footage. Audio drifts against picture.
• A fault in the original camera file. It was there before the edit.

How do you fix a result that came back wrong?

Say what you can hear and roughly where in the cut it happens. Vizard Agent keeps the per-clip metadata it read and the rebuilt timeline, so a second pass targets another input rather than adjusting the mix over the top of the problem.

• "There is still a click." Another input's format checked and matched.
• "It drifts later on." Frame rate and timing examined at that join.
• "The music is covering it now." The bed pulled back down.
• "One clip sounds different." That clip normalised to the rest.

How does Vizard Agent compare to doing it yourself?

By hand the click is treated as a mix problem, because it is heard while listening to the mix. The music goes up, a fade goes in, and the fault stays in the file — which is why it comes back the moment somebody asks for a version without music.

Common questions

Can it tell me which clip it was? Yes. Vizard Agent names the input and what was wrong with it.

Will it fix the clip or the mix? The clip. Vizard Agent repairs the input rather than masking it.

What causes it? Usually a different sample rate, channel layout or codec; Vizard Agent reads which.

Can it happen with clips from one phone? Yes, if some were recorded in a different mode, and Vizard Agent still finds it.

Will the music need to move? No. Vizard Agent puts it back where it belongs afterwards.

Can it check every join? Yes. Ask Vizard Agent to check the whole assembly.

What if the recording is corrupt? Vizard Agent will say so; that needs replacing, not repairing.

Does it change the picture? No. Vizard Agent rebuilds the audio timeline only.

Will the levels still match? Yes. Vizard Agent normalises the repaired clip to the others.

Can I get a version without music? Yes, and it will be clean because the fault is actually gone.

What about a click at the very start? Same method. Vizard Agent checks the first input too.

Does this affect sync? It can. Vizard Agent checks picture and sound together afterwards.

Can it prevent it next time? Yes. Vizard Agent normalises every input's format before assembly.

Why not just cover it with music? Because the damage stays in the file, and it reappears in every version that does not have music over that moment.