Podcast and Spoken-Word Audio
How to fix mic bleed between two podcast mics in REAPER
Published September 27, 2026
Mic bleed is your co-host’s voice arriving on your microphone as well as on theirs. You cannot filter it out, because it is speech, exactly like the speech you are keeping. What works is editing: cut each track down to the parts where that person is actually talking, so the other person’s own clean track carries their words. ReaGate can automate most of that pass. It is usually very fixable for normal turn-taking conversation, and not fixable where both people talk over each other.
Two people, two mics, one room. You open the session expecting two clean tracks and instead each track has both voices on it, one loud and close and one faint and roomy. Then you play both tracks together and the whole thing sounds slightly hollow or phasey, worse than either track on its own.
That is mic bleed, also called spill, leakage or crosstalk, and it is not a fault in your gear. Every microphone hears everything in the room. A directional mic hears the person in front of it loudest, but it still hears the person beside it. Here is how to work out how much of a problem you actually have and what to do about it in REAPER with stock tools.
Why both tracks together sound worse than one
The faint copy is the annoying part, but it is not the damaging part. The damage is that your co-host’s voice now exists twice in your session: once close and loud on their mic, and once distant and slightly later on yours. Sound takes about a millisecond to travel a foot, so the two copies are out of step with each other.
When you play them together, some frequencies add and some subtract. The result is the thin, hollow, slightly tunnelled sound people describe as phasey. It is the same mechanism that makes two mics on one voice sound hollow, which is covered in detail in why two vocal tracks sound hollow when you combine them.
Test how bad it is before you fix anything
Solo one track and find a gap
Solo your own track and play a stretch where only your co-host is talking. What you hear is your bleed. Note whether it is just audible or clearly intelligible.
Do the same on the other track
Bleed is rarely symmetrical. The louder talker, or whoever sits closer to the other mic, usually leaks more. You may only need to treat one track.
Mute one track while both play
Play a passage where only one person speaks, with both tracks unmuted, then mute the non-speaking person’s track. If the voice suddenly gets fuller and more solid, the bleed is causing cancellation, not just clutter. That is the case worth fixing.
This is where mic bleed differs from a click track leaking out of headphones. A click has a narrow, repeating tone you can sometimes notch out. Bleed is a human voice in the same frequency range as the voice you are keeping, so any EQ that removes it removes your host too. If your bleed problem is actually headphone spill, that is a different job, covered in removing click track and headphone bleed from a vocal take.
Fix 1: edit each track down to its own speaker
This is the fix that always works, and it is the one professional dialogue editors use. The logic is simple: at any moment, one of your two tracks has a clean close version of whoever is speaking. You only need the other track to be silent at that moment.
- Turn automatic crossfades on before you cut anything, so every edit gets a short fade instead of a click.
- Leave ripple editing off. The two tracks have to stay locked to each other in time. Rippling one and not the other will pull the conversation apart.
- Split each track at the start and end of each of that person’s speaking turns, then delete or mute the sections in between.
- Do not cut tight to the words. Leave roughly a quarter of a second of that person’s own room tone before and after each turn. Cutting to absolute silence sounds more unnatural than the bleed did.
REAPER has a bulk version of this. The user guide documents Dynamic Splitting under the Item menu, described as removing silent passages: it splits items using a gate threshold so the quiet sections can be removed in one pass. Use it for the rough pass on a long episode, then listen through and repair the seams by hand, because it will inevitably clip the start of a few quiet words. The step-by-step mechanics of splitting, crossfading and closing gaps are in how to edit out filler words and breaths in REAPER.
Fix 2: ReaGate, and the settings to start from
A gate does the same job automatically and in real time. ReaGate ships with REAPER. Cockos describes it as “a noise gate whose most common use is to filter out sound when the volume falls below a specified threshold level”, which is exactly the shape of this problem: your own voice is loud on your track, the bleed is quiet.
Put one instance on each speaker’s track and set the threshold so it sits above the loudest bleed but below that person’s quietest real word. These are starting points, not correct values. Every room, mic distance and speaking style moves them.
| Control | What Cockos says it does | Starting range for speech |
|---|---|---|
| Threshold | “the input signal level (volume) below which the gate should be engaged” | Set by ear, just above the loudest bleed in a gap |
| Attack | “the speed with which a closed gate reopens when the volume rises above the threshold” | 1–5 ms, fast enough to keep hard consonants |
| Hold | “how long the gate is held open (before closing) when the signal falls below the Threshold” | 100–300 ms, so it does not close between words |
| Release | “the speed with which a gate closes when a signal falls below the threshold level” | 150–400 ms, long enough to sound natural |
| Hysteresis | “a margin of flexibility around the Threshold level, to prevent the gate from constantly opening, closing, and ‘chattering’” | 3–6 dB if you hear stuttering |
| Pre-open | lookahead, so the gate acts “ahead of the volume actually falling below the Threshold” | 1–5 ms if word beginnings sound clipped |
Find the place where your co-host is loudest and you are quietest, and set the threshold there. A gate tuned on an easy passage will chop syllables for the rest of the episode. If you cannot find a threshold that keeps every word and rejects all the bleed, the two levels overlap and no gate setting exists that does both. Edit that section by hand instead.
ReaGate also has a detector input that can be driven by “the signal from another source (Auxiliary Input)” rather than the track’s own audio. That opens the door to keying one track’s gate from the other, but it is fiddly to set up and easy to make worse. Get the straightforward version working first.
What to do where both people talk at once
Nothing above helps here, because both tracks legitimately contain speech at the same time. Your options are to leave it, which is normal in conversation and usually fine, or to choose one track for that moment and fade the other under it. Overlapping speech is the hard limit of every bleed fix, including the paid machine-learning tools that advertise bleed removal.
Stop it at the source next time
Twenty minutes of setup saves hours of editing. None of this needs new gear.
- Use the 3-to-1 rule. Shure’s educational publications state it plainly: “the distance between microphones should be at least three times the distance from each microphone to its intended sound source”, which “will help eliminate phase cancellation”. If you each sit six inches from your mic, keep the two mics at least eighteen inches apart.
- Get closer to your own mic. Closer means more of your voice for the same gain, which means less of everything else, including your co-host.
- Point the dead side at the other person. A cardioid mic is “most sensitive to sound arriving from directly in front” with “maximum rejection at 180 degrees off-axis”. Angle the mics so each one’s back is turned toward the other speaker rather than having them face each other across a table. Check your mic’s own polar-pattern chart first: that 180 degree figure is for a cardioid, and supercardioid or hypercardioid mics reject most at an angle off the rear rather than directly behind, so the best aim is a little to one side.
- Turn the gain down. High preamp gain to compensate for sitting far away amplifies the bleed just as much as the voice.
- Record each person to their own track. Bleed is only fixable at all because the tracks are separate. If you are still setting this up, see how to record two people in one REAPER session.
What this will not do
- It will not separate two voices that overlap. Editing and gating both work by silencing a whole track for a stretch of time, so they cannot pull two simultaneous speakers apart.
- It will not undo the cancellation already printed into a section where you keep both tracks playing together.
- It will not make a shared room sound like two isolated booths. Each track still carries that room’s tone while its own speaker is talking.
- Flipping polarity on one track will not cancel the bleed. The bleed arrives at a different delay for every sound, so there is no single flip that lines it up.
A turn-taking interview cleans up almost completely, and most listeners will never know there was bleed. A lively two-host show with constant interruption cleans up partially, and the honest goal there is to stop the hollowness rather than to remove every trace of the other voice.
If it still sounds off
- Words are getting clipped. The gate threshold is too high, or the hold is too short. Raise hold first, then lower the threshold.
- The track stutters during speech. That is gate chatter. Add hysteresis and lengthen the release.
- Each track sounds fine alone but hollow together. You have not silenced enough of the non-speaking track. Go back to the edit, not the gate.
- The two voices are now at very different levels. That is a separate job, and the method is in how to match podcast host and guest loudness in REAPER.
- The gaps sound dead. You cut to silence. Put a little of that speaker’s own room tone back under the gaps.
Mic bleed is not a filtering problem, it is an editing problem. Cut each track down to its own speaker so the clean track carries the voice, use ReaGate to automate the bulk of that pass, and accept that overlapping speech is where every method stops. Then fix the mic spacing before the next episode, because three times the distance to the source beats any plugin.
Sources
- Cockos, REAPER Cockos Effects Summary Guide - ReaGate described as “a noise gate whose most common use is to filter out sound when the volume falls below a specified threshold level”, with the quoted definitions of Threshold, Attack, Hold, Release, Hysteresis, Pre-open and the Main/Auxiliary detector input. Verified September 27, 2026. reaper.fm/userguide
- Cockos, The REAPER User Guide v7.80 (Geoffrey Francis) - section 7.36, “Dynamic Splitting - Remove Silent Passages”, the Item-menu feature used for the bulk pass above. Current REAPER release confirmed as 7.80, September 13, 2026, on the Cockos home page. Verified September 27, 2026. reaper.fm/userguide
- Shure, Microphone Techniques for Drums (Shure Educational Publication) - the 3-to-1 rule: “the distance between microphones should be at least three times the distance from each microphone to its intended sound source”, which “will help eliminate phase cancellation”, and the warning about comb-filtering interference when several mics pick up the same source. shure.com
- Shure, “Microphone Directionality and Polar Pattern Basics” - a cardioid mic is “most sensitive to sound arriving from directly in front” with “maximum rejection at 180 degrees off-axis”, and unidirectional mics are “effective at isolating the desired on-axis sound from both unwanted off-axis sound and ambient noise”. shure.com
- Evidence the problem is real and recurring, used as community context only and not as technical proof: the Cockos forum thread “Best way to remove mic bleed” (forum.cockos.com), the Gearspace thread “Mic leakage in podcast recording” (gearspace.com), and several Adobe support community threads including “Removing mic bleed in podcast”, “Removing voice bleed on multi-tracks podcast” and “mic bleed and recording with two USB microphones” (community.adobe.com). These are thread titles found in a same-day search; no thread body is quoted and no user prose is claimed. A commercial machine-learning “Mic Bleed Remover” was launched for this exact problem in October 2025, which is further evidence the pain is real rather than a technical endorsement of that tool.