Fixing clicks in audio edits
快速回答
To fix clicks in audio edits, add a short fade or crossfade at every cut, typically 2 to 10 ms, so the waveform ramps to silence instead of jumping. Cutting at zero crossings and removing DC offset prevent most clicks. For clicks printed inside a recording, use a de-click or spectral repair tool to interpolate over them.
Why do audio edits click and pop?
An edit clicks when the waveform jumps instantly from one value to another. A speaker cannot move from halfway up to the center line in zero time, so that jump comes out as a short burst of broadband noise: the click.
Image-Line's FL Studio manual explains it well: a cut might land in the middle of a sound wave, and if it lands at a high or low point far from the center, playback creates a sudden jump that sounds like a click.[1] The same thing happens at the start of a sample, the end of a region, a loop point, or the join between two comped takes.
Before editing anything, rule out a different problem. Crackles that come and go during playback, change with CPU load and vanish in the exported file are buffer dropouts, not edit clicks. Those are fixed in your audio settings, as covered in latency and buffer size explained. If the click is in the rendered file at the same spot every time, it is an edit or recording problem, and the rest of this page applies.
How do you find what is causing a click?
Solo the track, loop the spot and zoom in until you can see individual samples. The shape of the waveform at the click usually tells you which fix you need.
| What you see at the click | Likely cause | Fix |
|---|---|---|
| Waveform jumps vertically at a clip edge | Cut in the middle of a cycle | Short fade, or move the cut to a zero crossing |
| Jump where two clips touch | Butt edit without crossfade | Overlap the clips and crossfade |
| Whole waveform sits above or below the center line | DC offset | Remove DC offset, then re-fade the edges |
| Click at the loop point of a sample | Loop end does not match loop start | Move loop points or crossfade the loop |
| Single spike in the middle of a clip, no edit nearby | Recorded click, mouth noise or digital glitch | De-click or spectral repair |
| Click only during playback, not in the export | Buffer underrun | Raise the buffer or reduce CPU load |
- Bounce the section
Render a few bars containing the click. If the click is gone in the file, the problem is playback, not editing. - Zoom to sample level
Zoom until the waveform shows single points. Look for a vertical step, an offset baseline or an isolated spike. - Check both channels
In stereo, the left and right channels cross zero at different moments, so a cut can be clean on one side and click on the other. - Apply the matching fix
Use the table above. Fix the cause at the edit rather than masking it later with EQ or a limiter. - Listen on headphones
Clicks are easier to hear on headphones at moderate volume, especially low-level clicks in quiet passages.
Do zero crossings stop clicks?
Cutting at a zero crossing, the point where the waveform passes through the center line, prevents most edit clicks because both sides of the join start at the same height. It does not guarantee a clean edit, so treat it as the first step, not the whole fix.
Most editors can snap to zero for you. In Audacity, Select, At Zero Crossings (shortcut Z) nudges the selection edges to a rising zero crossing, which the manual says reduces the risk of clicks at editing points. It also warns that in stereo tracks the zero crossings may differ between the left and right channels, so a click can remain in one channel.[2] Logic Pro has Snap Edits to Zero Crossings in the Audio Track Editor's Snap menu, which Apple describes as helping ensure no click is produced at the edit position.[3]
When zero crossings are not enough
Two clips can both meet the center line and still click if one is heading up and the other heading down, because the slope changes abruptly. Low bass and 808 tails are the classic case: the cycles are long, so the nearest zero crossing may sit several milliseconds away from where you want the cut, which throws off timing on a grid. In those cases, keep the cut on the grid and add a short fade.
How long should fades and crossfades be?
Use the shortest fade that removes the click: a few milliseconds on percussive material, longer on sustained sounds and vocals. A fade that is too long dulls transients or leaves an audible dip.
DAW defaults show the range. Ableton Live's Create Fades on Clip Edges option applies a short declicking fade of up to 4 ms to clip starts and ends.[5] FL Studio's declicking defaults to Out only, a 10 ms cosine S-shaped fade-out, with a Transient mode that preserves drum attacks, 20 ms Generic, 100 ms Smooth and a 200 ms Crossfade mode for touching clips.[1]
| Material | Starting fade or crossfade length | Watch out for |
|---|---|---|
| Drum hits, one-shots, chops | 1 to 5 ms fade-out, no fade-in on the attack | Softened transients if the fade-in is too long |
| Vocal comp joins | 5 to 20 ms crossfade in a gap or consonant | Doubled syllables if the overlap is too wide |
| Bass, 808 tails, pads | 10 to 50 ms fade | Audible volume dip on sustained notes |
| Loop points in a sampler | 10 to 100 ms loop crossfade | Phasing or chorus-like wobble on long crossfades |
| Joining two different takes | 10 to 30 ms equal-power crossfade | A dip in level mid-fade if you use a linear curve on unrelated audio |
Place crossfades where the audio is quiet or noisy: breaths, consonants like S and T, or just before a drum hit. A join hidden under the next transient is inaudible even when the waveforms do not line up perfectly. For vocal work specifically, how to comp vocals without over-editing covers where to put the seams.
What is DC offset and why does it cause clicks?
DC offset is a constant voltage added to the audio, so the whole waveform sits above or below the center line instead of around it. Apple's Logic Pro guide notes that some interface hardware can layer DC over the signal and that DC offset can cause crackling sounds at the start and end of a region during playback.[4]
It clicks because silence is at zero while the offset audio is not. Every time a region starts or stops, the level jumps from the offset value to zero, and zero crossing snapping cannot help because the waveform barely crosses the true center line.
- Logic Pro In the Audio File Editor, select the file and choose Functions, Remove DC Offset. Apple notes this is not available on Apple Loops, surround files or Flex Pitch tracks, so bounce in place first.[4]
- Ableton Live Saturator's context menu has a Pre-DC Filter mode that activates a DC filter at the device input.[6] Bounce the result if you plan to chop the audio.
- Any DAW A gentle high-pass filter around 10 to 20 Hz removes DC. Print it, then redo your edge fades, since the old fades were built around the offset waveform.
- At the source If fresh recordings keep arriving with offset, test another input, cable or interface. Fixing the hardware beats cleaning every file.
How do you make sample-accurate cuts on chops and loops?
Turn off grid snapping, zoom to sample level and place the cut exactly where the waveform crosses zero or where a fade will hide it. Then check the result looped, because loop points expose problems that a single playthrough hides.
Samplers add their own traps. Moving the start offset of a sample can land playback mid-cycle. FL Studio's manual notes that its declicking options work with Start Offset to remove clicks when non-zero start points are used.[1] For drum chops, the Transient declick mode keeps the attack intact while still ramping the first few samples.
- Disable grid snap
Switch snapping off or hold your DAW's snap-bypass modifier so the cut can land between grid lines. - Zoom to single samples
Place the cut at a zero crossing that matches the direction of the waveform on the other side of the join. - Add a micro fade
Add 1 to 3 ms at the cut even if it looks clean. It costs nothing audible on most material. - Loop it
Loop the chop or the loop region for 30 seconds. A tick at every repeat means the end and start still do not match. - Consolidate or bounce
Print the finished chop to a new file so later edits, warping or sampler settings cannot bring the click back.
How do you remove stubborn clicks with de-click and spectral repair?
When the click is inside the recording rather than at an edit, use a de-click processor or a spectral editor to rebuild the damaged few milliseconds from the audio around it. Fades cannot fix a click in the middle of a sustained note.
iZotope describes its De-click plug-in as repairing short impulse noises, including digital errors, mouth noises and phone interference, by analyzing the audio for amplitude irregularities and smoothing them out. Its Sensitivity control trades missed clicks against over-processing, and a Clicks only mode lets you hear exactly what is being removed.[7] Listening to that difference signal is the fastest way to catch a setting that is eating consonants or drum transients.
For a single loud click, a spectral editor is more surgical: select only the vertical stripe of the click in the spectrogram and replace it with interpolated audio. REAPER users can follow REAPER spectral repair for clicks and dropouts, and iZotope RX for home studios covers the dedicated repair workflow. Before release, run the final master through the checks in how to QC masters before distribution.
Practice clean chops and fades on the free sample packs and drum kits from Plugg Supply before you work on a client session.
Learning path
相关答案中心
相关目录
目录中更多教程
Plugg Supply 信息流中更多教程,按目录热度排序。
LEARNING / VIDEO TUTORIALS
MixWithTheMasters Kevin Parker Producing 'Dracula' [TUTORiAL]
LEARNING / VIDEO TUTORIALS
MixWithTheMasters Olivia Rodrigo Mix with The Masters [TUTORiAL]
常见问题
- Why does my sample click at the end?
- A sample clicks at the end when the audio stops at a point where the waveform is not at zero, so playback drops instantly to silence. Add a short fade-out of about 5 to 10 ms, or enable your sampler's declick option. FL Studio, for example, applies a 10 ms S-shaped fade-out by default with its Out only declicking setting.
- What is a zero crossing in audio editing?
- A zero crossing is the point where the waveform passes through the center line, meaning the signal is momentarily at zero amplitude. Cutting at a zero crossing lines up both sides of an edit at the same height, which reduces the risk of clicks. Audacity's At Zero Crossings command, on the Z key, moves selection edges to such a point automatically.
- How long should a fade be to remove a click?
- A fade to remove a click usually needs only 2 to 10 ms on most material. Drum hits and chops work with 1 to 5 ms fade-outs, while bass, pads and vocals may need 10 to 50 ms to avoid a dip or thump. Ableton Live's automatic declicking fade on clip edges is up to 4 ms long, which shows how short an effective fade can be.
- Why do I hear clicks during playback but not in my exported file?
- Clicks that appear during playback but not in the exported file come from the computer, not the edits. The audio buffer is too small for the current CPU load, so chunks of audio arrive late. Raise the buffer size, freeze heavy plugins or close background apps. An export renders offline, so those dropouts never reach the file.
- Can EQ remove clicks and pops?
- EQ rarely removes clicks and pops, because a click is a very short burst that contains energy across the whole frequency range. Cutting enough of it with EQ also removes the music. Fix edit clicks with fades or crossfades, and fix recorded clicks with a de-click processor or spectral repair, which rebuild only the few damaged milliseconds from the surrounding audio.
- Does DC offset cause clicks?
- DC offset does cause clicks, because the offset waveform sits away from zero while silence sits at zero, so every region start and end becomes a sudden jump. Apple notes that DC offset can cause crackling at the start and end of a region during playback. Remove the offset first, then redo the edge fades.