Crackling, popping and stuttering sound is the most common complaint in emulation, and it is rarely a broken speaker. Audio is the strictest part of an emulator’s output: the picture can drop a frame and few players notice, but a gap in the audio stream is a click you cannot unhear. When sound crackles, its timing pipeline slipped somewhere.
As an Amazon Associate, we earn from qualifying purchases.
The good news is that nearly every case traces back to a short list of causes: a buffer that runs dry, a sync mode fighting the frame pacing, a sample-rate mismatch with Windows, another program holding the audio device, or a backend that misbehaves on your hardware. This guide works through those causes in the order you should try them, using the settings exactly as RetroArch, PCSX2, DuckStation and Dolphin document them. Everything here uses legal emulator software with your own game backups.
This article contains affiliate links; if you buy through them, we may earn a commission at no extra cost to you.
Quick Answer
Start with the buffer: raise the audio latency setting (RetroArch: Settings → Audio → Output → Audio Latency; PCSX2: Output Latency) until the crackle stops, and confirm audio sync is on. If the game is not holding full speed, fix the speed first, because no audio setting repairs a stream the emulator cannot generate in time.
Why Emulator Audio Crackles
A console produces audio locked to its own hardware clock, and an emulator inherits that obligation: it must hand your sound device a continuous stream of samples at the game’s rate, in real time, forever. Between the emulator and your speakers sits a buffer, a small reservoir of pre-generated audio. As long as the emulator refills it faster than the device drains it, playback is clean.
Crackling is the sound of that reservoir hitting empty, an event called a buffer underrun. It happens whenever frame pacing slips: a shader compiles mid-scene, a busy area spikes CPU load, or the display’s refresh rate disagrees slightly with the rate the emulator expects. Libretro’s synchronization documentation makes the point that audio and video are timed together, so a video timing error becomes an audio defect. The ladder below attacks each cause in turn, cheapest and most likely first.
Step 1: Raise the Audio Latency or Buffer Size
A bigger buffer is more slack: a brief CPU hiccup that would have emptied it gets absorbed instead. Raise the value in small steps and retest after each change, because every extra millisecond is also a millisecond of delay between an action and its sound.
In RetroArch the control is Settings → Audio → Output → Audio Latency (ms), which defaults to 64; stepping to 96 or 128 settles most systems. PCSX2 exposes Output Latency in Settings → Audio. DuckStation’s equivalent is the Buffer Size in Settings → Audio, and Dolphin has a Latency field in Config → Audio. Stop once playback is clean; if crackling survives high values, the buffer was never the problem, so move down the ladder instead of stacking delay.
Step 2: Settle the Sync Mode
Sync decides who paces the emulator. In RetroArch, leave Settings → Audio → Synchronization on, and leave Dynamic Rate Control enabled: per libretro’s documentation it nudges the output rate by a tiny fraction (the default delta is 0.005) to keep the buffer from emptying or overflowing, absorbing small clock differences. Turning sync off lets audio drift instead. Libretro’s guide stresses that the Vertical Refresh Rate under Settings → Video → Output must reflect your real display rate.
PCSX2’s version is Synchronization Mode in Settings → Audio. TimeStretch, the default, stretches audio slightly to follow speed dips and is right when the game mostly holds speed. Async Mix decouples audio from emulation speed, which can hide crackle on a struggling PC at the cost of drift, so treat it as a diagnostic: if Async Mix silences the crackle, your real problem is speed, not sound.
Step 3: Match the Sample Rate to the Windows Device
If the buffer is generous and sync is sane yet a regular click remains, suspect a rate mismatch. When Windows runs your playback device at one sample rate and the emulator outputs another, the driver resamples in real time and the seams can click. Most emulators output 48 kHz, so make Windows agree: open your playback device’s Properties → Advanced and set the Default Format to 16 bit or 24 bit, 48000 Hz. In RetroArch, set Settings → Audio → Output → Audio Output Rate (Hz) to 48000, and leave the Resampler on its default sinc setting.
Step 4: Clear Exclusive-Mode and Enhancement Conflicts
Voice and capture software, headset suites and other audio tools can seize exclusive control of the device or insert enhancement processing that starves the emulator’s pipeline. In the same Advanced tab of the device properties, untick the option that lets applications take exclusive control, and disable audio enhancements on the Enhancements tab. Then close competing audio apps and retest. If the crackle vanishes, reintroduce programs one at a time to find the culprit.
Step 5: Swap the Audio Backend or Driver
The last rung is the backend, the code path between emulator and Windows. RetroArch offers WASAPI, XAudio and DirectSound audio drivers; WASAPI is the modern default, but XAudio is a legitimate fallback when one path crackles. PCSX2 and DuckStation both build on the Cubeb backend, with PCSX2 also offering SDL. Dolphin offers WASAPI, Cubeb and XAudio2 in Config → Audio. Change one backend at a time, and keep your motherboard or sound-device driver current, because a stale generic driver underruns under load.
The Same Settings, by Emulator
| Emulator | Buffer setting | Sync setting | Backends |
|---|---|---|---|
| RetroArch | Audio Latency (ms), Settings → Audio → Output | Audio Sync plus Dynamic Rate Control | WASAPI, XAudio, DirectSound |
| PCSX2 | Output Latency, Settings → Audio | Synchronization Mode: TimeStretch or Async Mix | Cubeb, SDL |
| DuckStation | Buffer Size, Settings → Audio | Sync Mode: Resampling | Cubeb |
| Dolphin | Latency, Config → Audio | Audio Stretching for below-full-speed play | WASAPI, Cubeb, XAudio2 |
Gear That Sidesteps the Whole Fight
Settings fix most systems, but a noisy output path can keep reintroducing clicks. These five items remove the hardware-side variables: output device, connection type and storage speed.
FiiO K11 Desktop DAC and Headphone Amplifier
A desktop DAC gives the emulator one fixed, well-behaved USB output device instead of the shared motherboard codec.
Specs:
- DAC chip: Cirrus Logic CS43198
- Formats: PCM up to 384 kHz/32-bit, DSD256
- Inputs: USB-C, optical, coaxial
- Outputs: 6.35 mm, 4.4 mm balanced, RCA line out
- Output power: up to 1400 mW into 32 ohms, balanced (maker’s figure)
- Size and weight: 147 x 133 x 32.3 mm, about 407 g
Apple USB-C to 3.5 mm Headphone Jack Adapter
Apple’s dongle is the simplest way to move a laptop’s headphone output off the internal codec and onto a single-purpose USB device Windows treats consistently.
Specs:
- Model: MU7E2AM/A
- Connector: USB-C male to 3.5 mm female
- Sample rate: not stated by Apple
HyperX Cloud III Wired Gaming Headset
Wired headphones remove Bluetooth’s compression, latency and dropouts from the equation, making them the cleanest test of whether remaining crackle is really the emulator.
Specs:
- Drivers: 53 mm angled dynamic drivers
- Frequency response: 10 Hz to 21 kHz (maker’s figure)
- Connections: 3.5 mm, USB-C and USB-A dongle included
- Microphone: detachable 10 mm, noise cancelling
- Weight: 308 g without microphone
- Frame: aluminium, memory foam cushions
8BitDo Pro 2 Bluetooth Controller
A pad that keeps reconnecting over Bluetooth can hitch the whole system in bursts that sound exactly like audio faults.
Specs:
- Connection: Bluetooth and USB-C wired
- Sticks: Hall effect analog sticks on this variant
- Extras: two remappable back buttons, profile switching
- Compatibility: Windows, Switch, Android and macOS, per 8BitDo
Samsung T7 Portable SSD 1TB
Games streamed from a slow or failing drive stall the emulator in bursts. The T7 keeps image reads far ahead of the audio pipeline.
Specs:
- Model: MU-PC1T0T/AM
- Interface: USB 3.2 Gen 2
- Read speed: up to 1,050 MB/s (maker’s figure)
- Capacity: 1TB
How to Choose
Match the rung to the symptom pattern instead of changing everything at once. Crackle that appears in busy scenes and eases in menus is a speed or buffer problem, so work steps 1 and 2 and check the emulator’s speed readout. A metronome-regular click even in quiet scenes points at the sample rate, step 3. Crackle that only appears while streaming or chatting points at exclusive mode, step 4. Crackle confined to a single emulator while others play cleanly points at that emulator’s backend, step 5. Change one thing at a time and retest the same scene; the fix that works is the one matched to your actual cause.
Who Should Skip
Skip this ladder if the same crackle appears in music players and videos, because then the fault is the cable, headphone or device itself, and no emulator setting will touch it. Skip it, too, if your games cannot hold full speed on your hardware: crackling there is a performance ceiling, and the honest fixes are lighter settings or stronger hardware. Rhythm-game players chasing the lowest possible latency should stop at the smallest clean buffer instead; for them the trade-off runs the other way.
FAQ
Why does the crackling get worse in busy scenes?
Because that is when emulation speed dips. The emulator generates audio as it emulates, so a scene that drags it below full speed starves the buffer. Fix the speed, with lighter graphics settings or a sync mode that tolerates dips, and the audio usually follows.
Is a bigger buffer always better?
No. A bigger buffer only buys tolerance for hiccups; it also delays every sound effect by the same amount. The right value is the smallest one that stays clean on your system, which is why the ladder raises it in steps.
Can Bluetooth headphones cause crackling?
They can add their own dropouts and compression artefacts, and their latency stacks on top of the emulator’s buffer. When troubleshooting, test with wired headphones first so you chase one variable at a time.
Why does my audio drift out of sync instead of crackling?
Drift is the opposite failure: the buffer never empties, but the emulator and device clocks disagree slowly. That is a sync problem, so check that audio sync is enabled, that Dynamic Rate Control is on in RetroArch, and that PCSX2 is in TimeStretch rather than Async Mix or None.
Final Verdict
Emulator audio crackling is almost never random. It is an underrun with a cause, and the cause sits in one of five places: buffer size, sync mode, sample rate, device conflicts or the backend. Work the ladder in order, one change at a time, and most systems go quiet at step 1 or 2. The players who stay stuck are usually the ones who changed six settings at once, or whose real problem was emulation speed wearing an audio disguise.










