Chiaki-ng Audio Settings Explained – Fix Delay, Crackling & Mic Issues
Most chiaki-ng audio problems — crackling, delay, or a dead microphone — come down to three things: the audio buffer size slider (adjustable in 10 ms steps), your output device choice, and on Linux, whether PipeWire is running. One hard truth up front: Bluetooth audio adds latency no setting can remove — wire up if timing matters.
1. Audio Buffer Size (The Crackling Fix)
Chiaki-ng exposes the audio buffer as a slider in Settings → Audio, adjustable in 10 ms increments. A bigger buffer resists network jitter (less crackling); a smaller buffer means less delay. Start at the default, and if you hear crackling, raise it 10–20 ms at a time until it’s clean. If audio feels late, lower it — but expect crackling to return on rough networks. For the full troubleshooting flow see fix audio crackling.
2. Output Device: Bluetooth Is the Latency Trap
| Connection | Typical added latency | Verdict for remote play |
|---|---|---|
| Wired / 3.5 mm | ~0 ms | Best — use this for competitive games |
| 2.4 GHz wireless dongle | Low (~20–40 ms) | Fine for most play |
| Bluetooth | High (100–250+ ms, codec-dependent) | You’ll feel the lag — avoid for timing-sensitive games |
This isn’t a chiaki-ng flaw — it’s physics plus Bluetooth codecs. If your Bluetooth headset feels “behind” the action, that’s why. Our headset picks for remote play favor low-latency options.
3. Microphone Input
Chiaki-ng reworked its microphone path (v1.10.0) for better reliability. If your mic doesn’t work in party chat: check Settings → Audio for the input device selector (exact labels vary by version — use the in-app panel), make sure the OS hasn’t muted the mic for the app, and on Windows check the privacy setting that lets desktop apps access the microphone.
4. Linux: PipeWire Required
On Linux, chiaki-ng needs PipeWire running — it’s also what enables DualSense haptic feedback. No PipeWire, no rumble. Most modern distros ship it by default; if audio is broken on an older setup, that’s the first thing to check. (Flatpak users have a PulseAudio fallback flag, but it disables haptics — see Linux & Deck guide.)
Frequently Asked Questions
Why is chiaki-ng audio crackling?
Usually network jitter starving a too-small audio buffer. Raise the audio buffer size slider in Settings → Audio in 10 ms steps until it’s clean. Full walkthrough: fix audio crackling.
Why does audio feel delayed?
Check your output device first — Bluetooth headsets add 100–250+ ms that no setting removes. Switch to wired or a 2.4 GHz dongle headset, then try lowering the audio buffer.
Does chiaki-ng support microphone / voice chat?
Yes — the mic path was reworked in v1.10.0. Select the input in Settings → Audio and make sure the OS allows the app microphone access.
Why is there no audio on Linux?
Chiaki-ng needs PipeWire on Linux. If it’s missing or not running, audio (and DualSense haptics) won’t work. Install/enable PipeWire via your distro’s packages.
What’s the best headset for chiaki-ng?
Wired or 2.4 GHz wireless — avoid Bluetooth for latency. See our headset recommendations.