On current Linux releases, PipeWire is the default audio server, and it handles jobs that once needed PulseAudio and JACK. Fedora and Ubuntu both ship it by default. For home recording, the main steps are to confirm PipeWire is running, make sure your user has realtime scheduling permission, lower the buffer for tracking, watch for dropouts, and route audio with a graph tool. Ubuntu Studio does much of this for you.
What PipeWire replaces
PipeWire provides compatibility layers so older software keeps working:
- pipewire-pulse serves apps written for PulseAudio.
- pipewire-jack serves JACK apps, so programs such as Ardour and Carla can run without a separate JACK server. On some setups, you launch them with
pw-jack.
A separate JACK server is therefore usually unnecessary. A real-time kernel is also not required for home recording.
Ubuntu Studio: what it sets up
Ubuntu Studio is a flavor of Ubuntu aimed at multimedia creation. It configures realtime privileges, the audio group, and low-latency tuning automatically. It also includes an Ubuntu Studio Audio Configuration tool and an Ubuntu Studio Installer for choosing applications.
Recent releases have changed how low-latency kernel settings are delivered, so check the release notes for your version before you tune anything by hand.
Check realtime permissions
Your user needs realtime scheduling rights to avoid dropouts. Add your user to the audio group (for example, with sudo usermod -aG audio $USER), then create the limits file /etc/security/limits.d/audio.conf:
@audio - rtprio 95
@audio - memlock unlimited
Log out and back in so the group change takes effect. Many systems also run rtkit, which grants realtime priority on request, so check whether audio already works before you change the limits.
Lower the quantum for tracking
PipeWire calls the buffer size the quantum. Many default configurations use 1024 samples. The adjustable range depends on your version and distro, but it generally runs from 32 up to 2048.
To force a smaller quantum and sample rate for the whole system, use pw-metadata:
pw-metadata -n settings 0 clock.force-quantum 128
pw-metadata -n settings 0 clock.force-rate 48000
Set either value back to 0 to release it. If you’re unsure which rate to force, see is 44.1 kHz or 48 kHz better for music.
To request a buffer for a single app, set PIPEWIRE_LATENCY:
PIPEWIRE_LATENCY="128/48000" your-daw
At 48 kHz, a quantum of 128 is about 2.7 ms per buffer, using the same math as in audio latency and buffer size. For the sample-count settings to start from, see what buffer size to use when recording.
Watch for xruns
An xrun is a missed audio deadline, and it shows up as a click, pop, or dropout. Run pw-top while your session plays to see load and xrun counts. If you see xruns at a small quantum, step up one size.
Setting the CPU frequency governor to performance can also reduce xruns. The tool that does this depends on your distro.
Route your audio
Use qpwgraph or Helvum to connect inputs, outputs, and apps in a visual graph.
Some interfaces and sound cards show a “pro-audio” profile in a sound settings tool. That profile can expose every channel as a separate output. This is useful for multi-channel work, but it can clutter your device list. Editing profile sets is an advanced task, so check your distro’s documentation before you change one.
Interfaces and plugins
- USB class-compliant interfaces follow the USB Audio Class 2.0 standard and generally work without vendor drivers.
- Mixer control can be harder. Vendor control-panel apps usually don’t exist on Linux. For Focusrite Scarlett interfaces, the kernel driver plus alsa-scarlett-gui covers much of the mixer control.
- Linux DAWs include Ardour, Reaper, Bitwig Studio, Renoise, Qtractor, and LMMS.
- Windows plugins can run through Wine with yabridge, but compatibility varies from plugin to plugin. yabridge works much like the bridged plugins some Windows DAWs use, running each plugin in a separate process.
Common misconceptions
- JACK is no longer needed. PipeWire handles JACK applications, so you don’t usually run a separate JACK server.
- A real-time kernel is required. It is not mandatory for home recording.
- The default quantum is ready for tracking. It is set for general use, so lower it yourself for recording.
- A class-compliant interface needs no setup. It works without a vendor driver, but you may still need Linux tools for mixer control.