Fix It Fast with a Simple Checklist (and Understand Why It Happens)
REAPER Has Input But No Sound
You can see signal coming into REAPER.
The meters are moving.
But there’s no sound.
This is one of the most common (and frustrating) moments for new users — because it looks like everything is working.
The good news is:
if you can see input, REAPER is already receiving audio correctly.
What’s missing is almost always a monitoring or routing step — not recording.
This guide will help you:
- Get sound back quickly
- Identify exactly where the signal is stopping
- Understand why this happens (so it doesn’t keep happening)
Let’s start with the fastest way to fix it.
Quick Fix — No Sound in REAPER (Start Here)
If you can see input meters moving, work through this list in order:
1. Turn on Input Monitoring
Click the small speaker icon on your track
→ If this is off, you will see input but hear nothing
2. Check the Master Track
- Not muted
- Fader up
- Meter moving
3. Check Hardware Output
The Master track must be sending to your interface
→ Typically Output 1–2
4. Check Your Interface Outputs
Go to: Preferences → Audio → Device
→ Make sure outputs match where your speakers or headphones are connected
5. Check Track Routing
- Open Routing (I/O)
- Ensure Master/Parent Send is enabled
✅ If sound comes back at any step, stop — you’ve found the issue.
If not, the sections below will show you exactly where the signal is stopping.
Why This Happens in REAPER
REAPER separates recording from monitoring.
That means:
- You can record audio perfectly
- While hearing absolutely nothing
This isn’t a bug — it’s intentional.
It gives you control, but it also means you need to understand where sound is meant to travel.
How Sound Actually Moves in REAPER
REAPER’s signal flow can be understood as a straight line:
Input → Track → Master → Hardware Output → Your ears
If you can see meters moving but hear nothing, the signal is stopping somewhere along that path.
👉 If this concept feels unclear, it’s worth understanding How Signal Flow Works in REAPER — because it makes problems like this predictable instead of confusing.
Where Is the Signal Stopping?
- Track meters moving, Master not moving → problem is before the Master
- Master moving, no sound → problem is after the Master
Once you know where it stops, the fix becomes straightforward.
Input: Audio Is Already Reaching REAPER
If your track meter is moving:
- Your microphone or instrument is connected correctly
- Your audio interface is working
- REAPER is receiving audio
So the issue is not input.
At this point, it’s almost always monitoring or routing.
Track Monitoring: Hearing and Recording Are Separate
This is the most common cause of this issue.
In REAPER:
- Recording writes audio to disk
- Monitoring sends audio to your speakers
You can record perfectly usable audio while hearing nothing.
What to check
- Input (Record) Monitoring is enabled (speaker icon ON)
- Track is not muted
- Fader is at a sensible level
- Pan is centred (unless intentional)
If monitoring is off, silence is expected — not a failure.
Track Routing: Is the Audio Going Anywhere?
By default, tracks send audio to the Master.
But this can be disabled.
Open the track’s Routing (I/O) panel and confirm:
- Master/Parent Send is enabled
If this is off, you’ll see meters — but hear nothing.
If routing feels unclear at this point, it can help to explore how the REAPER routing matrix works in the article, The REAPER Routing Matrix Explained.
Folder Tracks: Parents Control Their Children
In REAPER, folder tracks act as routing parents.
If your track is inside a folder:
- The folder must not be muted
- The folder must be routed to the Master
Even if your track shows input activity, a muted or misrouted folder will block the sound.
The Master Track: Final Internal Checkpoint
Everything you hear passes through the Master (unless you’ve built a custom routing system).
Check that the Master:
- Is visible
- Is not muted
- Has its fader at a sensible level (often 0 dB)
- Shows meter activity
- Has a Hardware Output assigned (usually outputs 1–2)
If you don’t see the Master, enable it in the View or Mixer options.
Hardware Outputs: REAPER Won’t Guess
REAPER doesn’t assume where your speakers are connected.
You need to confirm:
In Preferences → Audio → Device
- Correct audio interface is selected
- Output range matches your physical outputs
On the Master track
- A Hardware Output is assigned
- It matches where you’re actually listening
If these don’t align, REAPER may be sending audio perfectly — just not to the place you expect.
👉 If you haven’t set this up yet, see how to set up your audio interface in REAPER in REAPER Audio Device Settings (Setup/Fix Guide).
Common Traps (These Catch Everyone)
These aren’t mistakes — they’re normal workflow collisions.
Hardware Monitoring vs REAPER Monitoring
Many interfaces provide direct monitoring.
Choose one:
- Monitor through the interface
- OR monitor through REAPER
Trying to use both can cause confusion or silence.
Solo Logic
A single solo button elsewhere (including folders) can mute everything else.
Look for yellow solo indicators.
Buffer Size and Stability
If sound drops out intermittently:
- Increase buffer size slightly
- Confirm your interface driver is stable
👉 You can learn more in Buffer Size and Latency in REAPER
A Quick MIDI Note
If you’re seeing MIDI activity instead of audio:
MIDI does not produce sound on its own.
It needs a virtual instrument to generate audio.
A Reliable Way to Diagnose Any Silent Project
When things go quiet, avoid random changes.
Instead:
- Play audio that should be audible
- Watch meters step by step:
- Track
- Folder / bus
- Master
- Identify where the signal stops
That point is where the fix lives.
My Final Thoughts
Seeing input but hearing nothing is unsettling — but it’s also one of the clearest signs that REAPER is behaving exactly as designed.
Once you understand the path:
Input → Track → Master → Hardware
This problem stops feeling mysterious and starts feeling mechanical.
And mechanical problems are fixable.
When it clicks, it tends to stay clicked.
I’d Love to Hear Your Thoughts…
Which part of the signal path has tripped you up most often?
Was there a moment when routing finally clicked for you?oment when routing finally clicked for you?