Mixxx Audio Latency and Crackling (August 2026) Buffer Settings Guide

Nothing kills a DJ set faster than audio that stutters, pops, or crackles through your speakers at the worst possible moment. If you are running Mixxx and hearing those telltale dropouts, the problem almost always traces back to your audio buffer settings. This guide walks you through exactly how Mixxx audio latency and crackling buffer settings work, what values to use, and how to fix distortion for good.

I have spent countless hours configuring Mixxx across different machines and operating systems. The good news is that once you understand the relationship between buffer size, latency, and crackling, the fix is usually straightforward. Let me break it down step by step.

Whether you are mixing with a keyboard and mouse at home or performing live with a controller and vinyl control, the principles here apply to every setup. By the end, you will know exactly which settings to change and why.

What Is Audio Latency in Mixxx?

Audio latency is the delay between the moment you perform an action in Mixxx and the moment you hear the result through your speakers. When you move the crossfader, adjust EQ, or trigger a hot cue, there is always a tiny gap before the audio changes. That gap is measured in milliseconds (ms).

Latency exists because Mixxx processes audio in small chunks rather than one continuous stream. Every chunk must be computed, packed, and sent to your sound card before it reaches your ears. The size of those chunks is your audio buffer, and it is the single biggest factor in how responsive Mixxx feels.

For a DJ, latency matters enormously. If you nudge a jog wheel and hear the pitch correction half a second later, your mixes will drift off beat. Low latency gives you the tight, instant feedback you need for accurate beatmatching and scratching.

Understanding the Audio Buffer

Think of the audio buffer as a bucket that fills with audio data before handing it to your sound card. A small bucket empties quickly, so the sound card gets fresh audio fast and latency stays low. But a small bucket also empties faster than Mixxx can refill it if your CPU is busy, which causes the bucket to run dry.

When that bucket runs dry, you hear crackling, popping, or dropouts. This is called a buffer underflow, and it is the number one cause of audio glitches in Mixxx. The sound card literally has nothing to play for a split second, so it outputs garbage or silence.

A larger bucket gives Mixxx more time to prepare each chunk of audio. The sound card always has something to play, so crackling disappears. The tradeoff is that a larger bucket takes longer to fill and deliver, which means higher latency. Everything you do in the software feels slightly delayed.

Here is the core relationship to remember: smaller buffer equals lower latency but higher risk of crackling. Larger buffer equals higher latency but stable, clean audio. Finding the sweet spot between those two extremes is what this guide helps you do.

How Buffer Size Affects Latency and Crackling?

Buffer size directly determines latency in Mixxx. The buffer size is expressed in milliseconds in the Mixxx preferences, which makes it easy to understand the relationship. A buffer of 5 ms gives you roughly 5 ms of output latency. A buffer of 46 ms gives you roughly 46 ms.

So does buffer size affect latency? Yes, it is the primary control you have over latency in Mixxx. Cut the buffer in half and you cut your latency roughly in half. Double the buffer and your latency approximately doubles.

Signs your buffer is too low include crackling, popping, clicking sounds, audio dropouts, distorted output, and buffer underflow warnings. These issues often get worse when you enable effects, keylock, or multiple decks simultaneously because all of those demand more CPU time per buffer cycle.

Signs your buffer is too high include noticeable delay when moving the crossfader, lag when adjusting EQ knobs, sloppy vinyl control response, and a general disconnected feeling between your actions and the audio. You will not hear crackling, but the software will feel sluggish and imprecise.

Recommended Buffer Sizes for Different Use Cases

The right buffer size depends entirely on how you use Mixxx. Here are the ranges that work for the most common setups, drawn from the official Mixxx manual and confirmed by community testing.

Keyboard and mouse mixing: An audio buffer between 23 and 64 ms is perfectly acceptable. You are not doing anything that requires instant tactile feedback, so you can prioritize stability over responsiveness. Set it to 46 ms and you will rarely if ever hear a crackle.

DJ controller use: Aim for 5 to 15 ms. Controllers demand tighter response than a mouse because you are manipulating physical jog wheels and faders. Start at 11.6 ms and adjust down if your CPU can handle it without crackling.

Vinyl control (timecode): Keep the buffer below 10 ms, ideally around 5 ms. Vinyl scratching requires near-instant response or the feel of the platter becomes disconnected from the audio. This is the most demanding configuration and needs a capable CPU.

Sample rate: Match the sample rate in Preferences to your audio interface and music files. The two standard options are 44100 Hz and 48000 Hz. Most DJ controllers and built-in sound cards work well at 48000 Hz, but check your hardware documentation. Using a mismatched sample rate can cause resampling artifacts and extra latency.

Quick reference: Start high at 46 ms for stability, then work your way down in small increments until you find the lowest buffer that does not crackle under your typical workload.

How to Change Buffer Settings in Mixxx?

Adjusting your Mixxx audio latency buffer settings takes less than a minute once you know where to look. Here is the exact procedure.

Step 1: Open Mixxx and go to Preferences from the top menu. On Windows and Linux, click Options then Preferences. On macOS, click Mixxx in the menu bar then Preferences.

Step 2: Select Sound Hardware from the left sidebar. This is where all audio output, input, latency, and sample rate settings live.

Step 3: Under API, choose the best sound API for your platform. On Windows, select ASIO if your hardware supports it or ASIO4ALL if it does not. On Linux, choose ALSA for direct hardware access or JACK if you are routing audio between applications. On macOS, CoreAudio is the only and best option.

Step 4: Under Output, set your Main output device and optionally your Headphone output device. If you have a dedicated DJ controller, select it here rather than your built-in sound card.

Step 5: Set the Sample Rate to match your hardware. Use 48000 Hz unless your interface specifically requires 44100 Hz.

Step 6: Adjust the Latency slider or dropdown. This sets your audio buffer size in milliseconds. Start at 46 ms if you are troubleshooting crackling, then reduce gradually.

Step 7: Click Apply, then play a track and listen for crackling. If you hear none, try lowering the buffer one step. If you hear crackling, raise it one step. Repeat until you find the lowest stable value.

Mixxx applies changes immediately after you click Apply, so you can test each adjustment without restarting the application. This makes it easy to dial in the perfect buffer size quickly.

Choosing the Right Sound API by Platform

Your Sound API choice has a major impact on achievable latency and audio stability. The API is the software bridge between Mixxx and your operating system’s audio subsystem, and not all APIs are created equal.

Windows: The best options are ASIO and WDM-KS. ASIO, originally developed by Steinberg, bypasses the Windows audio mixer entirely and delivers the lowest latency available. If your hardware does not ship with an ASIO driver, install the free ASIO4ALL wrapper. WDM-KS (Windows Driver Model Kernel Streaming) is a solid alternative that also bypasses much of the Windows audio stack. Avoid DirectSound and plain WASAPI in shared mode for DJ work, as they add significant latency.

Linux: ALSA gives you direct access to the hardware with minimal overhead and is the recommended choice for most users. JACK is the alternative if you need to route audio between multiple applications, such as sending Mixxx output through a recording tool or effects processor. JACK with a real-time kernel gives excellent latency performance but requires more setup. PulseAudio adds latency and should be avoided for live DJ monitoring.

macOS: CoreAudio is the default and only API option, and it is excellent. Apple designed CoreAudio for low-latency professional audio, so macOS users generally have fewer configuration headaches. Most Mac users can achieve stable low latency simply by selecting a reasonable buffer size.

Choosing the wrong API can make low latency impossible regardless of your buffer settings. If you are on Windows using DirectSound, no amount of buffer tweaking will get you below 30 ms or so. Switch to ASIO or ASIO4ALL and suddenly 5 to 10 ms becomes achievable.

How to Fix Crackling Audio in Mixxx?

If your audio is crackling, your latency may be set lower than your system can handle. The first step is always to raise your audio buffer size in Preferences, then Sound Hardware, until the crackling stops. Here is the full troubleshooting procedure.

Step 1: Raise the buffer size. Go to Preferences, Sound Hardware, and increase the Latency setting. Jump to 46 ms first. If crackling stops, your buffer was simply too low. Gradually lower it to find the minimum stable value.

Step 2: Check your CPU usage. Open your system monitor or task manager while Mixxx is running. If CPU usage is above 80 percent, your processor cannot fill the audio buffer fast enough. Close other applications, reduce the number of active decks, or turn off keylock on decks that are not pitch-adjusted.

Step 3: Close background applications. Voicemeeter, Discord, browser tabs with video, and other audio applications compete for CPU and can cause buffer underflows. Shut them down during your set, especially if you are streaming or recording simultaneously.

Step 4: Verify your Sound API. On Windows, confirm you are using ASIO or ASIO4ALL rather than DirectSound. On Linux, confirm ALSA direct-to-hardware rather than PulseAudio. The wrong API adds latency overhead that forces you into a too-low effective buffer.

Step 5: Check your sample rate. Make sure the sample rate in Mixxx matches what your audio interface expects. A mismatch causes the system to resample audio on the fly, adding CPU load and potential artifacts. Set both to 48000 Hz for most controllers.

Step 6: Consider environmental factors. According to experienced Mixxx forum users, crackling can be caused by air humidity that is too high or temperature extremes. If your settings look correct and crackling persists, check whether your environment is the culprit, particularly if the problem appeared suddenly.

Step 7: Check for effects-only crackling. If your audio is clean until you enable effects, the issue is CPU load from effects processing rather than your base buffer size. Either raise the buffer to accommodate effects, or use fewer effects simultaneously.

One specific data point from the Mixxx community: increasing the audio buffer to 23.2 ms resolved crackling issues for multiple users across different hardware configurations. If you are stuck, try that exact value as a starting point.

Platform-Specific Tips for Lower Latency

Each operating system has quirks that affect Mixxx audio performance. Here is what to do beyond basic buffer adjustments.

Windows: Set your power plan to High Performance or Ultimate Performance. Windows throttles CPU on power-saving plans, which can cause buffer underflows even when your buffer seems adequate. Disable USB power management for your audio interface or controller in Device Manager, as USB suspend causes momentary audio dropouts.

Linux: If you need the lowest possible latency, consider a real-time (PREEMPT_RT) kernel. The real-time kernel prioritizes audio processing threads over everything else, virtually eliminating buffer underflows on capable hardware. Use the rtirq package to assign high priority to your audio USB devices. If you run JACK, configure it in realtime mode with appropriate audio group permissions.

macOS: CoreAudio handles priority management automatically, so macOS users rarely need system-level tuning. Focus instead on keeping other CPU-intensive applications closed during performance. One thing to watch: Bluetooth audio adds significant latency on all platforms, so always use wired headphones and wired speakers for DJ work.

Voicemeeter and other virtual audio software: If you run Voicemeeter alongside Mixxx for streaming or recording, be aware that the combination can cause crackling even when Mixxx alone runs fine. Voicemeeter introduces its own buffering layer. Set the Voicemeeter buffer to match or exceed your Mixxx buffer, and avoid running both at minimum latency simultaneously.

Advanced Tips for Low-Latency DJ Performance

Once your basics are dialed in, these advanced techniques help squeeze out the last few milliseconds of latency.

Monitor buffer underflows in real time. Mixxx displays audio statistics including buffer underflow counts. Watch these during your set. If underflows spike when you load a new track or enable an effect, you know exactly what is pushing your system over the edge. Adjust your buffer to handle peak load, not idle load.

Keylock and pitch handling. Keylock (time-stretching) is CPU-intensive. If you have keylock enabled on all four decks simultaneously while also running effects, your CPU may struggle even at moderate buffer sizes. Disable keylock on decks where you are not actively adjusting pitch to free up processing headroom.

Vinyl control optimization. Timecode vinyl requires the lowest buffer of any configuration. Use a USB audio interface specifically designed for timecode, ensure your sound API is set to ASIO on Windows or ALSA on Linux, and keep the buffer as close to 5 ms as your system allows. Any latency above 10 ms makes scratching feel disconnected from your hand movements.

Dedicated audio interface. Built-in sound cards and cheap USB adapters add driver latency that eats into your budget. A dedicated DJ audio interface or controller with a built-in interface processes audio more efficiently and lets you achieve lower stable buffer sizes than generic hardware.

Frequently Asked Questions

Conclusion

Fixing Mixxx audio latency and crackling buffer settings comes down to one fundamental tradeoff: smaller buffers give you lower latency but demand more from your CPU, while larger buffers give you stable audio at the cost of responsiveness. Start at 46 ms for stability, then work down to the lowest buffer your system can handle without crackling.

Choose the right Sound API for your platform, match your sample rate to your hardware, and keep background applications closed during performance. If crackling persists despite correct settings, check environmental factors and CPU load. With these steps, you will have clean, responsive audio for every DJ session in 2026 and beyond.