How to Set Up REAPER Audio with PipeWire

Before you start

This process runs locally on the computer where REAPER is installed. PipeWire is a local audio service, so you do not need another machine or network connection. Make sure REAPER and PipeWire are installed and that your audio session uses PipeWire rather than another sound server.

Connect the input and output devices you plan to use before opening REAPER. A connected device is easier to route when REAPER reads the device list. If you are using a microphone, place it away from obvious background noise before checking the input level.

Step-by-step instructions

Open REAPER and go to the audio device settings. The exact location depends on the REAPER version and platform, but it is usually under Preferences or Options in the Audio section.

Select an audio system that exposes PipeWire devices. On Linux builds this may be listed as PipeWire, JACK, or ALSA depending on how REAPER was installed. Choose the option that shows your PipeWire inputs and outputs.

Set the input device to the microphone or interface you want to record. Set the output device to the headphones or speakers you want to monitor through. Keep the input and output devices separate if you use a combined USB interface.

Check the sample rate and block size. Match the sample rate used by your project or interface when possible. A lower block size reduces monitoring delay but can produce audio dropouts, so raise it gradually if playback becomes unstable.

Close the settings window and create or open a project. Add one track, arm it for recording, and choose the same input device on the track. Speak or play briefly at a normal level and watch the track meter.

Adjust the input level from the device or interface first. If the signal is too low or clipping, change the gain at the microphone or interface before using REAPER's track controls. Keep the loudest part below the top of the meter.

Check the output

Play back the recorded or monitored signal through the selected output device. You should hear the same input with no unexpected echo or doubling. If you hear the signal twice, check whether both REAPER and the system are monitoring the same device.

Check that the sample rate in REAPER matches the rate reported by PipeWire. A mismatch can cause the audio to play at the wrong speed or produce errors when the device is opened.

Record a short test while you stay quiet for a few seconds and then speak. This makes it easier to hear whether background noise is present and whether the voice level is usable.

Common problems and next steps

If REAPER does not show the expected input or output device, close REAPER and confirm that the device is available to PipeWire. Then reopen REAPER so it can refresh the device list.

If another application has exclusive access to the device, stop that application and try again. In shared audio setups, REAPER normally uses the default PipeWire routing, but some configurations can still conflict.

If the output contains crackles or dropouts, increase the block size in REAPER. If you need very low latency for live input, reduce it gradually until monitoring becomes stable.

If the recorded signal is noisy or unclear, first reduce room noise and move closer to the microphone. Then raise the input level only as much as needed, and check that the track is not clipping.

PipeWire routing can be inspected with graphical patch tools when they are installed. Use one to confirm which REAPER ports connect to which hardware devices if the simple device selection is not enough.