Crackling, choppy music, and delayed sound in retro emulators usually come from audio buffer settings or the wrong output driver, and this guide fixes the common cases step by step.

Great emulation hides itself when picture and sound feel natural, but audio problems reveal the emulation layer fast: pops during music tracks, voices half a second behind actions, or steady hiss when a scene loads. Most issues have nothing wrong with the game files; they sit in the emulator’s audio section, which defaults to broad compatibility rather than best latency, and a few setting changes remove the symptoms without touching graphics options.

Why sound crackles in the first place

Emulators stream short chunks of audio called buffers. If the CPU cannot fill a chunk before the sound card wants it, the gap becomes a pop or crackle heard as dropouts. Small buffers keep sound tightly timed to graphics but risk underruns on weaker machines; large buffers stay stable but add lag between a jump and its sound effect. Different cores synthesize audio differently: PS1 music streamed from CD data, N64 chips mixed real-time channels, and Genesis used a dedicated Yamaha chip. The fix balances buffer size, driver choice, and synchronization mode for that core.

Pick the right output driver on Windows, Linux, and Android

On Windows, RetroArch and most standalone programs offer XAudio2, DirectSound, and WASAPI. XAudio2 gives the best default balance; DirectSound works on older setups but adds latency; WASAPI exclusive mode tightens timing when nothing else holds. On Linux choose ALSA for a lightweight box or PulseAudio PipeWire on a desktop; Bluetooth headsets force a high-latency path and crackle easily, so use wired speakers for diagnosis before blaming the core. Android audio stutters when the device throttles in warm rooms; close background apps and test on charger power. Change one driver, restart the core, and listen ten seconds before moving on.

Buffer size, synchronization, and resampling rate

Audio settings usually expose three knobs. Buffer size in milliseconds: start around 64 to 128 ms for desktop, raise to 192 to 256 ms if pops remain, and lower below 64 only on a fast stable machine. Synchronization mode switches strict, relaxed, and unsynchronized timing; strict keeps music in step with frames but drops audio on overloaded hardware, relaxed trades tightness for fewer cracks, and unsynced suits slow turn-based RPGs. Resampling ratio should match the system sample rate, often 48000 Hz; forcing 44100 or an odd multiplier adds conversion noise without fast DSP support. Standalone emulators mirror these ideas under buffer, block size, or frame delay labels.

Per-core notes for common systems

PSX cores such as Beetle PSX keep CD streaming independent of frame speed; crackling often traces to frame-pacing settings rather than the audio buffer, so enable the core’s built-in frame throttling before adjusting sound. N64 cores mix channels rapidly and reward a slightly larger buffer; for a full setup walkthrough of that platform see the N64 emulator guide, which covers audio plugin choices alongside graphics. Genesis and SNES cores run light on resources, so their cracks usually mean a driver conflict with another app holding the device; close a browser with heavy video playback or a voice call before retesting. Arcade cores built on FBNeo expose a dedicated sound sample rate option that defaults safely but can be tuned to the sound card output.

When the strange sound is actually faithful to the original

Not every odd noise counts as a bug. Early digital tracks sounded tinny compared with modern audio, cartridge games limited channel count, and some console audio skipped on real hardware during busy effects. Consult a reference video recorded on original hardware before assuming the core is broken: low fidelity and simple drums belong to the era, while sudden pops, cut loops, and misaligned channels point back to settings. If music starts late on each level, the core may be waiting on CD seek emulation; raising disc-read speed or disabling accurate seeking on weaker machines clears it.

A short repair checklist before giving up

• Update the emulator or core to the latest stable build, since audio fixes land often.
• Change the output driver to the recommended default for your OS and retest.
• Raise the buffer in moderate steps and listen for the exact moment pops stop.
• Confirm the sample rate matches the system output and disable unusual upmixing effects.
• Close background video, streaming, and recording apps that share the audio device.
• Compare against original-hardware footage to separate faithful quirks from real defects.

Keep a note of the working settings per core, because a value perfect for one chip may crackle on another; save-state habits and menu shortcuts covered in the emulator basics guide pair naturally once audio settles, and the session finally feels like a living room rather than a debug window.