How to get rid of the tick you can hear at every cut
Ask Vizard Agent to smooth the edit joins first and then hunt the leftovers separately. A tick created by cutting is fixed with a short crossfade at every join; a tap that was in the original recording survives that entirely, and is removed as a transient after checking on a spectrogram that it is not sitting on top of a word.
What is the short version?
After a tightening pass, a talking-head edit often develops a faint tick at each cut. Some of those ticks are the cut, and some of them were always in the room — and telling them apart is the whole job, because the two repairs do opposite things.
- Go to Vizard Agent saying you hear ticks.
- Ask for short crossfades at every join.
- Ask about whatever you can still hear afterwards.
What do you need before you start?
The cut and roughly where you hear it. Vizard Agent can find joins on its own, but a timestamp for a tap you can hear is worth a great deal, because the ones left after the smoothing pass are the interesting ones and they are easy to miss.
- The edited video. After the tightening pass.
- Where you hear it. One timestamp is enough.
- Whether the source was clean. It changes the odds.
- How it was recorded. Handling noise is common on phones.
- Whether the wording is final. Repairs sit next to words.
What do you type into Vizard Agent?
Describe the sound to Vizard Agent rather than assuming what is causing it. "The transitions are glitchy" points at the edit while "there is a tap" points at the recording, and starting from the wrong one of those costs you a whole round.
Prompt
Variants worth knowing:
- "I am not sure." Honest, and it stops a wrong diagnosis.
- "Smooth every join first." The cheap half.
- "Whether anything is left." Separates the two causes.
What does Vizard Agent actually do?
Here is the sequence Vizard Agent worked through on a real talking-head edit that had been tightened word by word. The first repair took care of most of it, and the taps that survived that pass turned out to be an entirely different problem underneath.
- Checks the joins around the point you named.
- Measures the audio and video durations so the fix stays in sync.
- Adds short audio crossfades at every edit join.
- Aligns the smoothed audio exactly to the picture.
- Reviews the waveform for clean, click-free joins.
- Listens around the taps you can still hear.
- Builds a waveform and a spectrogram of that section.
- Separates handling noise from speech on the spectrogram.
- Checks the word timings so nothing is cut through.
- Removes the transients while keeping the speech underneath.
- Verifies the wording and timing did not change.
Step seven is what makes the second half possible. A waveform shows you that something is there; a spectrogram shows you what kind of thing it is, and a knock against a desk looks nothing like a consonant once you can see both.
Step nine is the safety check. A transient removal placed carelessly takes the front off the next word, so Vizard Agent maps the tap times against the transcript before touching anything and works in the gaps between words wherever it can.
Step two matters more than it sounds. Any audio-only pass risks drifting against the picture, so measuring both durations first is what stops a smoothing fix from becoming a sync problem.
What does the result look like?
Speech that runs cleanly through the cuts, with the room noise that was always there now gone from the few places you could hear it. The voice is unchanged — the repair should be inaudible rather than obviously processed.
Vizard Agent confirms the words and their timings are identical to before, which is the thing a transient repair can quietly break.
When does this not work well?
A tap sitting exactly on a word cannot be removed without taking part of the word with it. Very frequent handling noise is a recording problem rather than an editing one, and cleaning it everywhere starts to flatten the voice.
- Taps on top of words. Removal costs the word.
- Constant handling noise. That is a re-record.
- Heavy processing already applied. Less room to work.
- Music under the speech. It masks and complicates.
- Very short gaps between words. Nowhere safe to repair.
How do you fix a result that came back wrong?
Say whether it is better, exactly the same, or different in some new way. Because Vizard Agent handled the joins and the recorded transients as two separate passes, knowing which of them helped is what tells it which one to push further.
- "Better, but still at 0:14." A leftover transient there.
- "No change at all." The cause was not the joins.
- "The voice sounds processed now." Too aggressive; backed off.
- "It is out of sync now." The alignment needs re-measuring.
How does Vizard Agent compare to doing it yourself?
By hand a tick at the cuts gets treated as one problem and fixed one way — usually crossfades everywhere, applied generously. That removes the join clicks, leaves the recorded taps untouched, and softens the speech slightly everywhere as a side effect.
| By hand | Vizard Agent | |
|---|---|---|
| The diagnosis | One cause | Two, separated by a pass |
| The join fix | Long crossfades, everywhere | Short ones, aligned to picture |
| Recorded taps | Left, or smeared over | Found on a spectrogram |
| Safety | Removal near words is risky | Word timings checked first |
| Verification | Listening once | Wording and timing re-confirmed |
Common questions
Why does cutting create a tick? Because the waveform jumps at the join. A short crossfade bridges it.
Why did the crossfades not fix mine? Because those taps were in the recording, which Vizard Agent handles separately.
What is a spectrogram for? It shows Vizard Agent what a sound is, not merely that something is there.
Will the voice change? Not if the repair is localised, which Vizard Agent keeps it.
Can it fix a tap on a word? Rarely well. Vizard Agent will tell you when it cannot.
How long should a crossfade be? Short enough to be inaudible. Vizard Agent avoids long ones, which soften speech.
Will it go out of sync? Not if the durations are measured first, which is why Vizard Agent does that step.
Can it check the whole file? Yes. Ask Vizard Agent to sweep every join rather than one.
Does music make it harder? Yes, it masks the transients. Vizard Agent works on the stems if it can.
What if it is a hum, not a tap? A different problem needing a different filter. Tell Vizard Agent what you hear.
Will the transcript change? No, and Vizard Agent verifies that afterwards.
Can I hear before and after? Yes. Vizard Agent renders the section rather than the whole file.
Is this the same as noise reduction? No. Vizard Agent repairs a few specific moments rather than the whole track.
Why did it appear after the tightening pass? Because tightening creates joins, and every join is a place a tick can live.