Linux DJ
REAPER DAW interface on a Linux desktop with audio meters active
DAW Workflow·/notes/

REAPER on PipeWire: Setup, Buffer Size and XRun Fixes

Connect native Linux REAPER to a working PipeWire graph, verify the route, then tune the buffer against a real recording project.

On a desktop already running PipeWire, start with native Linux REAPER and use its JACK audio system through PipeWire’s JACK compatibility library. Confirm that REAPER’s ports join the intended graph before changing quantum, sample rate or the kernel. If you already rely on standalone JACK2, keep that working setup until you can rehearse a migration.

Install the native Linux build

Run uname -m and choose the matching build from the official REAPER download page. The Linux 7.86 release checked on 18 November 2026 lists x86-64, i686, aarch64 and armv7l. The file and directory names below are from the x86-64 archive; substitute the names from your own download and use a user-owned directory.

tar -tf ./reaper786_linux_x86_64.tar.xz
tar -xf ./reaper786_linux_x86_64.tar.xz
cd reaper_linux_x86_64
cat readme-linux.txt

The archive contains install-reaper.sh and the executable REAPER/reaper. Use the included instructions for a permanent installation. For a trial, you can enter the REAPER directory and run ./reaper without a system-wide install. REAPER offers a 60-day evaluation, not a permanently free licence. Archive layout was checked; the audio workflow here is a verification procedure, not a report of a hardware test.

Connect REAPER to the intended audio graph

  1. Run wpctl status in your normal desktop session and check that the interface is visible. If it is missing, solve detection or profile selection first. Confirm capture and playback with a simple known source.
  2. Make sure your distribution has installed its PipeWire JACK compatibility library for your application architecture. If the distribution supplies pw-jack and it is required, start the extracted build with pw-jack ./reaper. If the library is already the default, launch REAPER normally. Do not start a separate JACK server for this workflow.
  3. In Options > Preferences > Audio > Device, choose JACK as the audio system. Look for REAPER’s ports in pw-link -o and pw-link -i, and check the intended capture and playback connections. A JACK selector alone does not tell you which server provides the library.
  4. Arm one track with the intended input. Confirm an input meter and test playback with a known clip at a safe level. Check hardware direct monitoring separately; it can make a silent software monitoring route sound as though it works.

For the detailed backend comparison, see the PipeWire vs native JACK analysis.

If your existing workflow uses ALSA directly, keep that option as a diagnostic for the exact device. Direct access to a hardware PCM may contend with PipeWire for that device. An ALSA device called default can instead route through a configured plugin, so the word ALSA alone does not prove you bypassed PipeWire. For the rest of this guide, test the native REAPER build with JACK, not a Windows build or a sandbox whose runtime can load different libraries.

Follow the signal through four checkpoints

CheckpointWhat success looks likeIf it fails
Interface captureThe selected physical input is connected and carries a clean signal.Check physical gain, input type and the hardware mixer before adding plugins or changing rate.
REAPER trackAn armed track set to that mono or stereo input shows signal.Check the input range in Audio Device preferences and the actual capture-port links.
Master playbackA known clip moves the master meter and reaches the intended playback pair.Check master hardware sends, the track's master send and the graph links.
Headphone cueYou hear the intended mix without a doubled signal.Compare the interface's direct monitor with REAPER input monitoring, enabling only the path you intend to test.

Record a short take, stop, disarm the track and play the take back. A moving input meter proves capture reached the track; it does not prove the return from the master to the headphones. Save this minimal project as a routing baseline before importing a session template.

Set the buffer after a clean recording

Open pw-top and find the driver for the graph in which REAPER is running. Note the actual RATE and QUANT while the project plays. At 48 kHz, 256 frames corresponds to one nominal 5.33 ms graph period, not the full monitoring delay. Start at a stable setting like 512 frames, then choose a stable PipeWire quantum using the same tracks, plugins, routing and workload each time. Check for new ERR increments rather than comparing lifetime counter totals.

For tracking, bypass latency-heavy plugins on the monitoring path, or use hardware direct monitoring where appropriate. For mixing, a larger buffer is often better than straining to keep a low setting you no longer need. Verify physical delay separately with the latency measurement guide.

Verify recording alignment separately

A performer hearing delay and a recorded item landing late are different faults. To check alignment, use a safe line-level loopback and record a short transient on a separate track with other processing bypassed. Compare the recorded item position with the source, document the compensation in use and repeat. If you change REAPER's recording offset, check the result again at the same rate and buffer. Do not apply an offset derived from the graph-period formula or from an unrelated interface.

If there is no sound, an XRun or a UI problem

SymptomFirst check
REAPER has no JACK ports in PipeWireCheck the installed JACK library, how REAPER was launched and whether its audio device is open.
Signal on the track, but nothing at the speakersCheck the master hardware sends, PipeWire port links and the interface mixer.
Glitches when the session gets busyReturn to the previous stable quantum and repeat the test without the suspected plugin or extra workload.
A plugin window or drag-and-drop failsCheck echo "$XDG_SESSION_TYPE", test without the third-party plugin, and compare with an X11 session if your desktop offers one. This is a display diagnostic, not an audio backend fix.

Recover a real session before tuning it

After an interruption, save the project and note the affected take or passage. Restore the stable buffer and retest in a copy of the project with the same routing. Bypass one suspect effect at a time, including effects on the master: a synth or lookahead processor can affect the monitoring route even when the input track itself is clean. If a project plays fine but glitches only while a track is armed, compare armed and unarmed results before changing anticipative processing or thread-count settings globally.

Treat plugin loading, window rendering and audio distinctly. Start with a stock effect in the native build. Then add the suspect plugin with the version and format recorded. If the audio continues but the plugin UI fails, compare the stock and third-party UI in the current session before trying an X11 session. Windows plugins need a separate compatibility path; a plugin bridge failing to scan or draw is not evidence of a JACK problem.

Remove any temporary graph override you applied, verify that the previous driver rate and quantum return, then reopen the minimal routing project and confirm a short recording and playback. Check the affected project only after that baseline works. Keep a record of the REAPER, PipeWire, kernel and interface versions so a later test is comparable.

  • REAPER
  • DAW
  • PipeWire
  • Low Latency
  • Linux Audio
  • 2026

Related Notes

← All notes