Low latency Audio

Here's the full picture on low-latency audio with PipeWire on Linux as of mid-2026:

🎵 PipeWire Low-Latency Audio in 2026

The TL;DR

PipeWire is now the default on every major distro (Fedora, Ubuntu, Arch, openSUSE, Debian). Version 1.4.x ships standard, and the old JACK-vs-PulseAudio war is over. For pro audio work — DAWs, recording, DJing — PipeWire is genuinely ready. The consensus from the Linux audio community in 2026 is: yes, PipeWire is as fast as native JACK for low-latency work, and it's much more convenient.

The Magic Number: Quantum (Buffer Size)

The central knob is the quantum — PipeWire's term for buffer size in samples:

Quantum	Latency @ 48kHz
1024	21.3 ms
512	10.7 ms
256	5.3 ms
128	2.7 ms
64	1.3 ms

Set it in ~/.config/pipewire/pipewire.conf.d/10-low-latency.conf:

conf

context.properties = {

default.clock.quantum = 128

default.clock.min-quantum = 64

default.clock.max-quantum = 1024

default.clock.rate = 48000

default.clock.allowed-rates = [ 44100 48000 96000 ]

}

Then restart: systemctl --user restart pipewire pipewire-pulse wireplumber

The Three Things You Must Get Right

1. Real-time scheduling — Without this, glitches happen even at low CPU load. Two approaches:

rtkit-daemon (works out of the box on most distros) — PipeWire asks it for RT priority
PAM limits — add yourself to the audio group and create /etc/security/limits.d/audio.conf with @audio - rtprio 95 and @audio - memlock unlimited

2. CPU governor — Set to performance:

bash

echo performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

3. Low-latency kernel (optional but recommended for sub-5ms) — Ubuntu has linux-lowlatency in the repos. No, it's not the old full-RT patchset, but it cuts scheduling jitter significantly.

The Tool You'll Live In: pw-top

bash

pw-top

Shows every audio node, its quantum, sample rate, load ratio (W/Q column), and xrun count (ERR column). If xruns climb, raise your quantum. If they're zero, you can try going lower.

DAW-Specific Notes

REAPER 7.x — Use JACK backend through PipeWire. No native PipeWire backend, but pw-jack is transparent. Toggle quantum mid-session with pw-metadata -n settings 0 clock.force-quantum 256
Bitwig Studio 6 — Has native PipeWire support (no JACK wrapper needed). Best-in-class integration.
Ardour 9.0 — JACK backend through PipeWire. Rock solid.
Windows VSTs via yabridge work, but expect 5-15% extra CPU and 50-200 MB RAM per bridged plugin. iLok and heavy DRM plugins are problematic.

Bluetooth: The One Remaining Pain Point

Good news: PipeWire supports SBC, AAC, aptX, aptX HD, LDAC, LC3, LC3plus. Force a codec with wpctl set-codec ldac.
Bad news: If you use a Bluetooth headset's microphone (HFP/HSP profile), output drops to mono SBC at 16 kHz. This is a Bluetooth spec limit, not a PipeWire bug. The fix: use a separate USB mic.
Random disconnects are usually WiFi coexistence issues on combo Intel chips. Try options iwlwifi bt_coex_active=0 in modprobe.d.

Quick Troubleshooting Cheat Sheet

Symptom	Fix
No sound after login	wpctl status → wpctl set-default <sink-id>
Crackling/popping	Raise quantum, check USB hub contention, move interface to motherboard port
Routing lost on reboot	Check ~/.local/state/wireplumber/ isn't on tmpfs
JACK app can't connect	systemctl --user status pipewire + install pipewire-jack
Screen share audio missing	OBS 31.x has native PipeWire capture; browser needs xdg-desktop-portal-*

Bottom Line

PipeWire in 2026 is stable, low-latency, and production-ready. USB 2.0 interfaces reliably hit 128 samples (2.7 ms). USB 3.0 interfaces can often do 64 samples (1.3 ms). The convenience of running Firefox, a DAW, Bluetooth headphones, and system sounds simultaneously through one audio server — without the old JACK/PulseAudio tug-of-war — makes it a clear win. Your starting point: set quantum to 256, verify xrun-free operation with pw-top, then work down until you find your hardware's stable floor.

📋 Low latency Audio