Quick answer: first decide whether the sound is baked into the edit or appears only during playback. A click at a cut usually comes from an abrupt waveform jump, a clip edge or a hard mute. A crackling playback problem can come from monitoring, buffer load, sample-rate mismatch, media decoding or an overloaded timeline. The fixes overlap, but treating both as “bad audio” wastes time.
For a click at an edit point, zoom into the waveform, move the cut toward a zero crossing when possible, add a very short crossfade or fade handle, and listen again. For clicks inside the recording, isolate the event and repair the smallest region that contains it. Do not cover every pop with a long fade; that can dull consonants and transients.
Diagnose the sound before editing
Click happens at the start or end of a clip
This is usually an edit discontinuity. The waveform is cut while it is away from zero, so the speaker or music jumps from one amplitude to another. A short fade-in or fade-out is often enough.
Click happens at a crosscut between two clips
Two clips may meet at different levels, phases or waveforms. A short crossfade can smooth the transition. If the clips overlap badly, choose the cleanest region and rebuild the edit instead of hiding it with a large transition.
Click is inside one continuous recording
The source may contain a mouth click, cable movement, edit artifact or digital glitch. Find the exact sample region, split or isolate it, and use a local repair. A global noise processor is not designed to remove one isolated transient cleanly.
Crackling follows playback load
If the exported file is clean but the Viewer or Fairlight playback crackles, inspect the monitoring path and system load. Reduce timeline complexity, render cache-heavy effects and confirm the audio device and sample-rate settings. The site’s render cache guide explains how to separate playback performance from final media.
Fix a click at a clip edge
- Open the Edit or Fairlight page and enlarge the audio track.
- Zoom until the waveform around the cut is visible.
- Place the cut near a zero crossing if the edit still works musically or in dialogue timing.
- Drag a short fade handle from the clip edge, or add a short crossfade where two clips overlap.
- Listen at normal level and again with the waveform visible.
- Check that the fade did not remove the first consonant, room tone or transient you need.
A zero crossing is a point where the waveform passes through its center line. It is not a guarantee of a perfect edit because phase, ambience and neighboring clips still matter, but it reduces the size of the discontinuity you are asking the listener to hear.
Use the right crossfade
Resolve offers different fade shapes for different transitions. A linear fade changes level predictably. An equal-power-style crossfade can preserve perceived loudness better when two clips overlap, but it may not be the right choice for every spoken cut.
Use the shortest transition that removes the artifact:
- for a hard clip edge, begin with a tiny fade-in or fade-out;
- for two similar room-tone clips, use a short crossfade and match their levels;
- for music, choose a curve that preserves the musical energy rather than creating a dip;
- for dialogue, protect consonants and breaths before extending the fade.
The site’s audio fade guide covers the basic handles and timing choices. The goal here is the same: make the transition continuous without hiding a larger edit problem.
Repair an isolated click inside a clip
Find the click on the Fairlight waveform and mark a small range around it. The repair might be a tiny cut with a short crossfade, a volume dip or a dedicated restoration tool available in your edition and version. Keep the repair local; processing the entire clip can change the noise floor and voice texture.
If you cut the click out, preserve room tone around the edit. A silent hole can sound worse than the original click. Copy a nearby clean ambience region only when it matches the recording and does not create a loop that the listener can detect.
For a mouth click or lip smack, a small gain reduction is often more transparent than muting the whole syllable. For a digital spike, inspect the surrounding samples and compare the repaired region against the original at normal listening level.
Clicks caused by automation or abrupt mutes
Volume automation that jumps from one value to another can make a click. So can a hard mute on a bus or a plugin that switches state between frames. Smooth the automation with a short ramp and bypass the suspected processor to locate the source.
If the click follows a Fairlight effect, test the clip with the effect bypassed, then re-enable processors one by one. Heavy noise reduction, gates and limiters can make playback sound unstable when the system cannot process them in real time, even if the final render is clean.
Playback crackling is a different problem
Use this sequence when the click is not present in the rendered file or moves when you change the playback position:
- Play the same section after caching or rendering the heaviest effects.
- Check the selected audio output device and operating-system sample rate.
- Reduce the audio buffer size only if the system can sustain it; otherwise increase the buffer for stability.
- Bypass heavy Fairlight plugins and test the clean timeline.
- Check for mismatched sample rates or media that needs to be conformed.
- Render a short test file and listen outside Resolve.
If the export is clean, do not keep cutting the waveform to fix a monitoring issue. If the export contains the crackle too, return to the source clip, bus routing and processors.
Check the waveform and meters
A click may be a tiny spike that barely changes the overall meter reading. Zoom into the waveform and use the meters while listening. If the artifact coincides with clipping, reduce the clip or bus level before adding a fade. If the waveform is clean but the monitor crackles, stay in playback diagnosis.
Resolve’s audio meters also help separate a clip problem from a bus problem. If the clip meter spikes before the bus, inspect the clip. If every clip sounds distorted only after a bus processor, inspect that bus and its gain staging.
Do not confuse clicks with background noise
Noise reduction can lower a steady hiss or room tone; it will not reliably repair a discontinuity at an edit point. A de-click style process can target short artifacts, but it cannot replace a clean edit when the cut itself is wrong. The site’s background-noise guide and noise-reduction guide cover different problems.
Common mistakes
- Adding a long crossfade to every cut. This creates audible dips and blurred dialogue.
- Fixing playback crackling with waveform edits. Test a render and the monitoring path first.
- Muting the entire syllable. Repair the smallest area that contains the click.
- Ignoring level matching. A level jump can sound like a pop even when the waveform crosses zero.
- Processing the master bus too early. Find whether the artifact starts on the clip, track or bus.
- Listening only in headphones. Check speakers and a rendered file before deciding the fix is complete.
Final click and pop checklist
- The artifact was classified as an edit click, source click or playback problem.
- The waveform was inspected at the exact event.
- The cut was moved to a practical zero crossing where possible.
- The shortest transparent fade or crossfade was used.
- Room tone and consonants remain intact.
- Track, bus and master processors were tested separately.
- A short render was checked outside the timeline.
Clicks become easy to fix when you stop treating every sharp sound as the same failure. Repair the waveform discontinuity at the edit, isolate a source artifact inside the clip, and reserve playback troubleshooting for the monitoring path and system load.
