Boddominator
Fix it

Audio crackles, dropouts and CPU spikes: fix them by symptom

A diagnostic guide for the problems that ruin sessions: pops at low buffer sizes, CPU meters jumping when you load a plugin, and delay that only appears on one track.

Producers often lower the buffer, update drivers and still hear crackles or see CPU spikes the moment a heavy plugin such as real-time pitch correction is switched on. Start from the symptom you hear, then work down the list.

Find your symptom

SymptomMost likely causeFirst fix
Clicks and pops while playing backBuffer too small for the sessionRaise the buffer one step
CPU meter jumps when one plugin is onA heavy or look-ahead pluginUse its low-latency mode, or freeze the track
Delay on one track onlyPlugin latency on that trackBypass plugins on the track you are recording
Delay hearing yourself while recordingSoftware monitoring at a large bufferUse direct monitoring on the interface
Random dropouts, even in small sessionsPower saving, Wi-Fi or background appsSee the system checklist below
Wrong pitch or speedSample rate mismatchMatch the DAW and interface sample rates

Heavy plugins while recording

Real-time pitch correction, linear-phase EQs, look-ahead limiters and big reverbs can add delay or load the CPU. While recording:

  • Switch such plugins to their low-latency or live mode if they have one.
  • Bypass mastering-style plugins on the master bus.
  • Freeze or bounce finished instrument tracks to audio to free the CPU.
  • Turn on your DAW's low-latency monitoring mode if it has one.

Use two buffer settings

Record at a small buffer, around 64 to 128 samples, with few plugins running. Mix at a large buffer, 512 to 1024 samples, with everything on. Switching between the two solves most problems without new hardware. Full details in how to fix audio latency.

System checklist

  • Windows: use the interface's ASIO driver and a high-performance power plan; close browsers and game launchers.
  • Mac: turn off Low Power Mode while recording.
  • Both: plug the interface directly into the computer rather than a hub, turn off Bluetooth audio, and pause cloud syncing during sessions.
  • Laptops often perform better plugged in to power.

When it is the hardware

If a small session still crackles at a 256-sample buffer after all of this, your interface driver or computer may be the limit. A modern interface with good drivers helps; see our beginner picks.

About this guide

This guide explains widely used production practice and contains no statistics or product claims that need an outside source. See our editorial standards.

Keep reading