Reaper Latency: How to Reduce & Fix Audio Delay

Reaper is flexible and fast. It lets you dial in latency with precision using low-level controls like block size, driver choice, and ReaRoute (a built-in virtual audio loopback). Get these settings right and Reaper achieves sub-5ms latency with ease.

Understanding Reaper Latency

Reaper’s latency comes from:

Audio Driver (Windows): ASIO is fastest. WASAPI Exclusive is second. Shared Mode is slowest.

Block Size (Buffer): Measured in samples, same formula as other DAWs: (Block Size / Sample Rate) × 1000 = Latency in ms.

Interface Latency: Core Audio on Mac, ASIO/WASAPI on Windows, ALSA on Linux all have different baselines.

Plugin Processing: Minimal. Reaper doesn’t add artificial compensation latency like some DAWs.

With right settings, Reaper reaches 3–8ms round-trip easily.

Step 1: Choose the Right Audio Driver

This is the biggest lever on Windows.

Windows: ASIO vs WASAPI vs DirectSound

ASIO (Best if available):

Most audio interfaces include ASIO drivers. ASIO bypasses Windows’ mixer and talks directly to your hardware. Lowest latency, typically 3–8ms total.

How to use: Options > Preferences > Audio > Device > Select your interface’s ASIO driver from the dropdown.

WASAPI Exclusive (Good fallback):

Built into Windows 10/11. Exclusive mode lets Reaper take over your audio device, bypassing the mixer. Latency is comparable to ASIO (5–10ms).

How to use: Audio system dropdown > “WASAPI” > Mode dropdown > “Exclusive” or “Exclusive (polled).”

Shared Mode (Not recommended for tracking):

Allows other apps to use your audio while Reaper plays. Much higher latency (20–40ms). Use only if tracking isn’t critical.

DirectSound (Avoid):

Older driver type. High latency, 30–50ms+. Only use if nothing else works.

Mac: Core Audio (Built-in)

No driver choice needed. macOS uses Core Audio, which is efficient and optimized. Latency is typically 5–10ms with proper buffer settings.

Linux: ALSA/JACK/PipeWire

JACK: Lowest latency. If available, use it for music production (5–10ms possible).

PipeWire: Newer, good balance. 10–20ms typical.

ALSA: Direct hardware access. Requires manual configuration. Possible sub-5ms with tuning.

Step 2: Set Block Size (Buffer)

Block size is Reaper’s term for buffer size. Smaller blocks = lower latency, higher CPU demand.

How to Access:

Options > Preferences > Audio > Device. There’s a “Block size” field or slider (named differently depending on your driver).

Recommended Values:

64 samples: Most responsive, demanding on CPU. Typical latency: 1.3ms at 48kHz.

128 samples: Good balance. Typical latency: 2.67ms at 48kHz.

256 samples: Stable, slight latency. Typical latency: 5.3ms at 48kHz.

512 samples: For mixing when latency doesn’t matter. Typical latency: 10.67ms at 48kHz.

How to Test:

1. Open Preferences and set block size to 128.
2. Play a project with a few tracks and plugins. Listen for clicks or pops.
3. If clean, try 64 next.
4. If glitches appear, increase back to 128 or 256.

Most modern computers handle 128 comfortably.

Important: Enable “Request block size” checkbox so Reaper can actually change your interface’s buffer, not just report it.

Step 3: Check Audio System Mode

Windows WASAPI and some other drivers have multiple modes. Choose wisely.

ASIO: No mode choice (it’s exclusive by design).

WASAPI:

• Exclusive = takes over device, lowest latency
• Exclusive (polled) = alternative exclusive mode, try if regular exclusive has issues
• Shared = other apps can use device, but higher latency

Choose Exclusive for tracking.

Shared mode is for background music (YouTube in another window while you work). For tracking, use Exclusive.

Step 4: Enable ReaRoute (Zero-Latency Monitoring)

ReaRoute is Reaper’s built-in virtual audio cable. You can route audio through it with zero latency for monitoring or parallel processing.

How to Enable:

Options > Preferences > Audio > Devices > Check “ReaRoute (Cockos)” if available.

A new “ReaRoute” device appears in your audio inputs/outputs.

How to Use for Zero-Latency Monitoring:

1. Create a new track set to input from your microphone or instrument.
2. Route that track’s output to “ReaRoute virtual audio 1.”
3. Create another track or instance set to input from “ReaRoute virtual audio 1.”
4. Monitor from there.

Audio loops through ReaRoute with zero buffering. It’s how you hear yourself live while recording.

Step 5: Direct Hardware Monitoring

If your interface has a mix knob, use it for the fastest monitoring.

How:

1. Open your interface’s control software (Focusrite Control, RME TotalMix, PreSonus StudioLive, etc.).
2. Route your input directly to your headphone output.
3. Adjust the mix knob so you hear yourself.

This bypasses Reaper entirely—you’re hearing yourself through hardware (~0ms latency, just hardware conversion time).

Record in Reaper normally. The recording is placed in time correctly because Reaper reports interface latency accurately.

Step 6: Adjust Automatic Latency Compensation

Reaper auto-compensates for latency, so tracks stay in sync. But you can fine-tune this if needed.

How:

Reaper > Preferences > Audio > Latency Compensation.

“Use audio driver reported latency” is checked by default. Leave it on unless your interface reports inaccurate latency (test with a loopback to verify).

If reported latency doesn’t match actual, you can manually adjust “Additional latency.”

Sample Rate (Minimal Impact)

Sample rate affects buffer latency slightly:

44.1kHz at 128 samples = 2.9ms 48kHz at 128 samples = 2.67ms

Less than 1ms difference. Use 48kHz for consistency. Don’t chase latency with sample rate.

Real Reaper Latency Numbers

Windows, ASIO, 128 samples, 48kHz: 3–6ms total round-trip

Windows, WASAPI Exclusive, 128 samples, 48kHz: 5–10ms

Mac, Core Audio, 64 samples, 48kHz: 2–5ms

Linux, JACK, 128 samples, 48kHz: 5–10ms (depending on system tuning)

Any of these is professional. Under 10ms feels responsive for real-time tracking.

Troubleshooting High Latency

Symptom: Latency is high even after switching to ASIO and lowering block size.

1. Confirm “Request block size” is checked so Reaper can control your interface’s buffer.
2. Check your ASIO control panel (button in Preferences) for any latency settings.
3. Update your audio interface drivers from the manufacturer’s website.
4. Test actual latency with a loopback to verify vs. reported latency.

Symptom: Clicks and pops at low block sizes.

Your CPU can’t keep up. Increase block size to 256 or 512. Close background apps, disable unused plugins, freeze/commit tracks with heavy processing.

Symptom: Latency is stable but feels bad for tracking.

Use ReaRoute or direct hardware monitoring instead of monitoring through Reaper.

Quick Reaper Latency Checklist

Windows:

• [ ] Install your audio interface’s ASIO drivers from the manufacturer’s website
• [ ] Set Audio System to ASIO or WASAPI Exclusive
• [ ] Set block size to 128 samples (lower if CPU allows)
• [ ] Check “Request block size” checkbox
• [ ] Enable ReaRoute for zero-latency monitoring
• [ ] Or use direct hardware monitoring from your interface

Mac:

• [ ] Set block size to 64 or 128 samples
• [ ] Core Audio is default (no driver choice needed)
• [ ] Enable ReaRoute if available
• [ ] Or use direct hardware monitoring

All Platforms:

• [ ] Test actual latency using a loopback or <a href=”https://soundlatencytest.com/audio-latency-test/”>audio latency test</a>
• [ ] Close unnecessary background applications
• [ ] Update your audio interface firmware and drivers

ReaRoute Advanced: Parallel Monitoring

You can use ReaRoute to monitor with effects while keeping the dry recording clean.

Setup:

1. Record track (input from mic, output to stereo out).
2. Create a parallel track set to input from ReaRoute.
3. Add reverb/delay to the ReaRoute track.
4. You hear yourself with effects, but the recording is dry.

This is zero-latency effects monitoring—professional technique.

Why Reaper’s Flexible

Reaper doesn’t force compensation like Ableton. It reports latency, and you use it however you want. Want to record with zero compensation latency? Set it all to “Off” in Latency Compensation. Want automatic? Leave it on. Reaper respects your choice.

This is why Reaper is favored for mixing with external hardware—you have full control over latency compensation.

---