Audio Crackling and Pops? Buffer Size and Latency Explained

The drop lands, and right on the downbeat there is a click that is not in the track. Or the audio vanishes for a tenth of a second, as if someone had nudged a cable. The instinct is to change settings at random. That rarely works. Crackles and dropouts nearly always mean the same thing: your computer missed a deadline. Find out which one, and the fix usually takes minutes.

Why does my audio crackle and pop?

A computer does not produce sound as one continuous stream. Your DAW or DJ software calculates audio in small blocks of samples and drops each finished block into a holding area called the buffer. The audio interface collects those blocks on a rigid clock that never waits. If the next block is not ready in time, the interface has nothing to play, and that gap is what you hear: a click, a pop, a short dropout or, in bad cases, a stutter. FL Studio's manual calls this a buffer underrun.

So crackling is a timing problem, not a volume problem. Anything that delays the calculation of a block — a heavy plug-in, a driver that grabs the processor at the wrong moment, a laptop throttling itself to save power — can cause it, even when the overall CPU load looks low.

What buffer size should I use?

The size of each block is the buffer size, measured in samples. It sets how much time your computer gets per round. At 48 kHz, 128 samples gives it roughly 2.7 milliseconds; 512 samples gives it about 10.7 milliseconds. That is why raising the buffer fixes crackling so reliably: you are giving the machine more time for the same work.

The price is latency. Everything you play in, monitor or trigger arrives late by at least that amount, and in practice more, because audio has to travel in and out and the converters and drivers add their own delay. There is no single correct value, because the job changes within one session:

• Recording and playing parts in: 64 to 128 samples. Feel matters most, and the project is usually still light.
• Mixing and arranging: 512 or 1024 samples. Latency is irrelevant when you are not performing, and the computer needs headroom for the full plug-in chain.
• DJing from a laptop: 256 to 512 samples is a sensible range. Stability beats responsiveness in a booth.

The method is always the same, and it is the one Apple's own Logic documentation recommends: use the lowest buffer setting that stays free of clicks and pops. Raise it one step at a time until the problem stops, then leave it there. If even 1024 samples crackles, the buffer was never the real problem — keep reading.

Why does my DAW crackle when the CPU meter is low?

A meter at 30 percent looks like headroom, but crackling is decided by the worst moment, not the average. Ableton's manual points out that Live switches off effects that receive no audio, which lowers the average CPU load of a Set but cannot reduce the peak load. A chord that suddenly hits many voices, a reverb tail or a sharp automation move still has to be calculated in that one cycle, and it can push it past its deadline while the meter still looks calm.

A second reason is that audio work does not always spread evenly across cores. One heavy chain is often processed in sequence, so one core can max out while others idle. Splitting heavy processing across separate tracks or return channels gives the software more to distribute.

The third reason sits outside your DAW entirely: drivers. On Windows, network, Wi-Fi, Bluetooth and some graphics drivers can hold the processor for too long at a time, a problem known as DPC latency. The free tool LatencyMon shows which driver is responsible; run it while you reproduce the crackling, not while the machine is idle. Focusrite's support documentation names ndis.sys, the Windows networking driver, as a common culprit, which is why switching off Wi-Fi and Bluetooth is such a classic first test. If LatencyMon points at a specific driver, update it from the hardware maker's site.

How do I stop crackling in Ableton, FL Studio and Logic?

Ableton Live

Buffer size lives under Settings, Audio (Preferences in older versions). Live 12 shows per-track Performance Impact indicators in the mixer, so you can see which track costs the most. Freeze that track first; freezing renders its audio and switches off its devices until you unfreeze. On Windows, if the buffer field is greyed out, the setting is controlled by your interface's own control panel.

FL Studio

Image-Line's manual suggests a buffer length of roughly 10 to 20 milliseconds for most systems and recommends the smallest value at which the underrun counter in the audio settings stops climbing. On Windows, the buffer is changed through the ASIO panel button. If your interface lacks its own ASIO driver, FL Studio installs both ASIO4ALL and FL Studio ASIO; Image-Line ranks a native driver first, then ASIO4ALL, then FL Studio ASIO, which sits on top of Windows audio.

Logic Pro

Logic sets the I/O Buffer Size under Logic Pro, Settings, Audio, Devices. When you need low latency for recording but the project is already full of plug-ins, Low Latency Mode temporarily bypasses plug-ins that add too much delay, so you can play in without lowering the buffer.

Whichever DAW you use, the order of operations is the same: raise the buffer, find the heaviest track, freeze or bounce it, and only then start suspecting hardware. If you are still choosing between the first two, the trade-offs are laid out in FL Studio vs Ableton Live.

Which driver should I use: ASIO, WASAPI or Core Audio?

On a Mac, Core Audio is part of the system, most interfaces are class-compliant, and you set the buffer inside your software.

On Windows, use the ASIO driver from your interface's manufacturer. ASIO lets audio software talk almost directly to the hardware and bypass the operating system's mixer, which gives the lowest and, more importantly, the most consistent latency. Generic wrappers such as ASIO4ALL exist for devices without their own driver and are a workable stopgap, not a solution. If your software offers WASAPI in exclusive mode, that is the better fallback, because one application takes over the device and skips the shared mixer. The default shared outputs are far less predictable under load.

Crackling that has nothing to do with the buffer

Some clicks behave differently, and the pattern tells you where to look.

• Regular ticking in time: usually a clocking problem. If a second digital device is connected by S/PDIF or ADAT, only one of them may be the clock master.
• Mismatched sample rates: interface on 48 kHz, project on 44.1 kHz. Set the interface, the project and the operating system to the same rate, then restart the software.
• Crackling only on battery: laptops lower clock speeds and park components to save power. Plug in and switch the power plan to best performance.
• Same click at the same spot every time: the fault is in the audio file or an edit without a fade, not your system.
• Dropouts when you move a cable: the connection itself. Plug the interface straight into the computer, without hubs or docks, and swap the cable before reinstalling anything.

DJs face one extra trap: real-time stem separation. Splitting a track into vocals, drums and bass on the fly is among the heaviest jobs DJ software can do, and on older laptops it is a common trigger for dropouts. Many DJ applications can pre-analyse stems before the gig, which shifts that load out of the set; how the feature works is covered in our guide to DJ stems. The same logic applies when you add streaming software on top of a mix — encoding video competes for the same processor, which is one more reason to test a full rehearsal before you livestream a DJ set.

The short version

Crackling is a deadline your computer missed. Give it more time with a larger buffer, give it less work by freezing the heaviest track, and take away the interruptions — Wi-Fi, power saving, bad drivers, cheap hubs. Work through them in that order and almost every pop disappears; the rest point to your clock, your cable or your file.