Podcast and Spoken-Word Audio

How to fix a remote guest's bad audio in REAPER (with stock plugins)

By StudioRescue Editorial

Published August 1, 2026

Remote interviews are where podcasts most often fall apart. Your own mic sounds fine, but the guest comes back thin, boxy, echoey, full of hiss, or noticeably quieter than you. The good news is that most of these are separate, fixable problems, and REAPER's stock plugins handle nearly all of them. The important caveat up front: post-processing improves a bad recording, it does not un-record it. Know which parts you can clean and which you cannot before you spend an hour fighting a file.

This guide assumes you have the guest on their own track, which is the single most important thing. If your guest is glued to your voice in one stereo file, every fix you apply to them also hits you, and you are stuck. If you can still get a separate file, do that first.

Why remote guest audio goes bad

Four different causes stack up, and each needs a different fix. Naming them first saves you from reaching for the wrong plugin.

• Internet codec loss. Call software compresses audio hard to survive the connection. That is what makes a guest sound underwater, robotic, or swirly. It is damage baked into the file.
• Laptop or webcam mic. Built-in mics are thin and boxy, and they sit far from the mouth, so they pull in the whole room.
• Untreated room and no headphones. A live, bare room adds echo. If the guest used speakers instead of headphones, your voice bleeds back into their mic as echo too.
• Level mismatch. Guests rarely set gain the way you do, so their track often lands much quieter or hotter than yours.

Before you open a single plugin

The biggest quality win is not a plugin, it is the source file. Check these before you start processing, because a better file beats any amount of repair.

Diagnose before you process

Solo the guest track and listen once through without touching anything. Decide what is actually wrong, because you do not need every step below. A guest who is just quiet needs level work, not noise reduction. A guest in a good room with a bad codec cannot be helped by a gate. Match the fix to the symptom.

The cleanup order in REAPER

Order matters. Clean up noise and echo first, then shape tone, then control level last, so the compressor is not amplifying hiss you could have removed earlier. Add these to the guest track's FX chain, top to bottom.

1. High-pass the rumble

Add ReaEQ and set the first band to a high-pass shape around 80–100 Hz. Spoken voice has almost nothing useful below that, so this clears desk thumps, footsteps, and low room rumble without thinning the voice. On a very deep speaker keep it nearer 70–80 Hz.

2. Reduce steady background noise with ReaFIR

Add ReaFIR and set its mode to Subtract. Enable Automatically build noise profile while you play a section that is only the background noise you found earlier, then turn that option off so the profile freezes. ReaFIR now subtracts that steady noise from the whole track. If you hear a robotic or watery artifact, you are pulling too hard, so ease the profile down until it sounds natural. This works on steady noise like hiss or a fan, not on one-off clunks. For a fuller walkthrough of this plugin, see how to reduce background noise in a podcast in REAPER.

3. Tame the room echo with ReaGate

If the guest's room is echoey, add ReaGate to quiet the gaps between words, which cuts the tail of the room sound between phrases. Set the threshold just above the room noise so speech opens the gate cleanly, and lengthen the release so words are not chopped off. A gate reduces echo in the pauses, it does not remove echo that rings under the words themselves. For heavier room sound, the same approach as vocals applies in how to reduce reverb from a vocal in REAPER.

4. Restore presence with ReaEQ

Laptop and webcam mics usually sound boxy and closed in. Back in ReaEQ, try a gentle cut of 2–4 dB somewhere around 300–600 Hz to clear the boxiness, and a small lift of 2–3 dB up around 4–7 kHz to bring back clarity and consonants. These are starting points, so move them by ear on the actual voice. If you are new to which range does what, the vocal EQ cheat sheet for REAPER maps them out.

5. Even out the level with ReaComp

Remote guests wander closer to and farther from the mic, so their level jumps around. Add ReaComp with a ratio near 3:1, a medium attack, and a threshold set so the loudest words pull the gain reduction down a few dB. Aim for a steadier, more consistent level rather than a squashed one. If the whole track is simply too quiet, raise the item's clip gain first so the compressor has something to work with.

6. Match the guest to you, then to delivery

With the guest cleaned up, balance their overall loudness against your track so neither one makes the listener reach for the volume. Then set the final episode to your delivery target when you export. Podcast loudness has its own conventions, covered in how to hit -16 LUFS for a podcast in REAPER.

What this will not fix

Setting honest expectations saves you from chasing a file that cannot be saved.

• Codec damage. That underwater, robotic quality from a bad connection is missing information, not extra noise. No stock plugin, and no paid one, rebuilds detail that was never recorded.
• Heavy echo baked into the words. A gate cleans the gaps, but reverb ringing under the speech itself stays. A dedicated de-reverb tool helps a little, but a bad room is best fixed at the source.
• Clipping and distortion. If the guest recorded too hot and the peaks are crushed, that is destroyed audio, a different repair with its own limits.
• Bleed in a single mixed file. If you and the guest share one track, you cannot process one without the other. You need separate tracks.

Fix it once, at the source

Every problem above is cheaper to prevent than to repair. Before your next remote session, send the guest a short setup note: use any external microphone rather than the laptop, wear headphones so your voice does not echo back into their mic, sit close to the mic in the quietest room available, and record locally if the platform offers it. Two minutes of guest setup beats an hour of ReaFIR, and it protects the one thing post cannot recover, which is the detail in the original recording.