REAPER Audio Device Not Showing (Fix Guide)

A clear, step-by-step guide to getting your audio interface recognised in REAPER

---

Introduction

You open REAPER, ready to record or mix… and your audio device simply isn’t there.

No interface. No input. Nothing to select.

If you’ve run into the “REAPER audio device not showing” problem, you’re not alone — and more importantly, it’s almost always fixable.

The key is to approach it calmly and trace the connection chain systematically. In this guide, we’ll walk through the exact steps to get your device recognised and working again.

This guide is for when REAPER cannot see your audio device at all. If the device is visible but you still cannot hear anything, that is usually a different problem. This sits before signal flow begins — if the device is not visible, no audio path can be established.

It matters because your audio device is the entry and exit point for everything you record and hear. Without a visible device, no recording, monitoring, or playback can occur — the entire system depends on this first connection. If this connection isn’t working reliably, it affects every part of your workflow — from recording through to mixing.

---

Quick Fix (Start Here)

Before diving deeper, run through this checklist — it solves a surprising number of cases:

• Restart REAPER
• Check your interface is powered and connected
• Confirm the driver is installed
• Select the correct audio system (ASIO on Windows, CoreAudio on Mac)
• Restart your computer if the device was just installed

If it’s still not showing, let’s work through it properly. We’re not guessing — we’re tracing where the chain breaks.

---

Step 1: Check Physical Connection

This sounds obvious — but it’s the most common issue.

Make sure:

• Your interface is powered on
• The USB/Thunderbolt cable is fully connected
• You’re not using a faulty cable or hub
• The device appears in your operating system (outside REAPER)

Example / Tip

A very common scenario:
You plug your interface into a different USB port, and Windows treats it as a “new” device — but the driver hasn’t initialised properly.

Result? REAPER can’t see it.

If in doubt, unplug → replug → wait a few seconds → then launch REAPER.

---

Step 2: Confirm Driver Installation

REAPER relies on your system’s audio driver to communicate with your interface.

If the driver isn’t installed (or is incorrect), the device won’t appear.

What to check:

• Download the official driver from the manufacturer
• Install it fully (including any control panel software)
• Restart your system after installation

Common mistake

Using generic drivers instead of the proper one.

• Windows default → often uses basic audio drivers
• What you want → ASIO driver from the manufacturer

Without that, REAPER may not list your interface at all. This usually shows up when a new interface has been installed but the correct driver hasn’t been selected yet — everything looks connected, but REAPER has nothing to talk to.

---

Step 3: Select the Correct Audio System (ASIO/CoreAudio)

This is where things often go wrong inside REAPER itself.

Go to:

Options → Preferences → Audio → Device

Now check your audio system:

• Windows: Select ASIO
• Mac: Select CoreAudio

Once selected, your interface should appear in the device list.

You’ll often notice this issue when REAPER is set to the wrong audio system — the interface may be connected and working in your system, but simply doesn’t appear inside REAPER. In some cases, the device may appear as “disabled” or unavailable, rather than missing entirely.

---

Step 4: Check REAPER Device Settings

Even if the system is correct, the device still needs to be selected properly.

Inside the same menu:

• Select your interface as the Input Device
• Select your interface as the Output Device
• Confirm the Input Range is enabled correctly
• Confirm the Output Range is enabled correctly

What usually goes wrong

• REAPER defaults to your computer’s built-in audio
• The interface is installed — but not selected
• Input/output ranges are mismatched or disabled

If you don’t see any inputs, it often means the device is selected incorrectly — not that it’s missing.

---

Step 5: Restart and Reset Scenarios

If everything looks correct but still isn’t working:

Try this sequence:

1. Close REAPER
2. Disconnect the interface
3. Reconnect the interface
4. Power it on
5. Reopen REAPER

If needed:

• Restart your computer
• Reinstall the driver
• Try a different USB port

Edge case

Some interfaces don’t initialise properly if REAPER is already open when they’re connected.

Launching REAPER after the device is ready can fix it instantly.

---

Why This Happens (ASIO vs WASAPI vs CoreAudio)

Understanding the “why” helps this make more sense.

Windows

• ASIO → Professional driver (what you want)
• WASAPI → System audio (limited for production)

For most dedicated audio interfaces on Windows, ASIO is usually the better choice inside REAPER. If REAPER is set to WASAPI, your interface may not appear properly — or may behave unpredictably.

Mac

• CoreAudio handles everything — usually more seamless
• Issues still happen if the device isn’t initialised or selected

The core issue

REAPER doesn’t “find” devices by itself — it relies on:

• the operating system
• the driver
• your selected audio system

A useful way to think about this is as a chain: your hardware connection (USB/Thunderbolt/power) is recognised by the operating system, the driver allows communication, and REAPER connects to it through the selected audio system. If any part of that chain breaks, the device disappears.

---

Practical Scenarios (What Usually Goes Wrong)

Here are the patterns I see most often:

• New interface, driver not installed yet
• Interface plugged in after REAPER opened
• Wrong audio system selected (WASAPI instead of ASIO)
• Windows silently switching audio devices
• USB port change breaking driver recognition

If you recognise one of these, you’re already close to solving it. In most cases, the fix is not complicated — it is usually a missed connection, driver issue, or device setting.

---

Where to Go Next

If your interface now shows up but you still have issues:

• 👉 See How to Setup Your Audio Interface in REAPER if you’re configuring things from scratch
• 👉 See REAPER Has Input but No Sound if audio is present but silent
• 👉 See Buffer Size & Latency in REAPER if performance or glitches are the problem

Each one builds on what you’ve just fixed — not replaces it.

---

My Final Thoughts

This is one of those frustrating moments that every REAPER user runs into at some point.

The important thing to remember is this:

Nothing is “broken” — it’s just a chain that hasn’t lined up yet.

Once you understand how REAPER connects to your interface — through drivers, systems, and settings — this stops being a mystery and becomes a simple checklist.

And once that clicks, you’ve just removed one of the biggest early hurdles in your workflow.

---

I’d Love to Hear Your Thoughts…

• What ended up being the cause when your audio device wasn’t showing in REAPER?
• Was it a driver issue, a setting, or something unexpected?