Podcast and Spoken-Word Audio
One podcast voice on a laptop mic, one on a real mic: how to make them sound closer in REAPER
Published October 29, 2026
You cannot make a laptop mic sound like a good microphone, because the missing low end and detail were never recorded. What you can do is meet in the middle: clean the weak track first, match the two voices' loudness, then use EQ to take a little away from the good track and add a little to the weak one, so the jump between speakers stops pulling the listener's attention. Work with both voices playing back to back, keep every move small, and stop before the good track starts to sound damaged. It is realistically improvable, not fully fixable.
This is one of the most common problems on two-person shows and interviews. The host is close to a decent USB or XLR mic and sounds full. The guest, or a co-host who forgot their mic, is on a laptop's built-in microphone and sounds thin, distant and roomy. Each track might be acceptable on its own. Cut back and forth between them every few seconds and the contrast is what the listener hears.
This article is about that contrast. If the weak track also has noise, echo or dropouts, start with how to fix a remote guest's bad audio in REAPER, and if your own recording went to the laptop mic by accident, see what can be saved when you recorded on the laptop mic. Come back here once each track is as clean as it will get.
Why the two voices will never fully match
Three things separate them, and only some of them can be changed afterwards:
- Distance and room. A laptop mic usually sits at arm's length, so it hears more of the room and less of the mouth. The close mic hears mostly voice. You can reduce the difference, but you cannot fully remove the room from the far track.
- Low end the laptop never captured. Directional microphones pick up extra bass as the source gets close to them, called the proximity effect. Sound On Sound's explainer notes it happens in pressure-gradient (directional) microphones and not in omnidirectional ones, and that it grows as the mic gets closer. So the close mic carries a warmth the far laptop mic simply does not have.
- Processing on the way in. Laptops and call apps often apply noise suppression or automatic level control before the audio is saved. That can leave a slightly watery or pumping sound that no EQ undoes. If you hear it, see fixing a voice recorded with noise suppression on.
The practical rule that follows: you can always remove something from the good track, but you can only partly add to the weak one. Boosting a frequency on the laptop track raises whatever is there, including noise and room, not the voice detail that was never captured. That is why the goal is to meet in the middle rather than to drag the weak voice all the way up.
Before you touch EQ: three checks
Each voice on its own track
Everything below assumes the two people are on separate tracks. If both voices are on one file, you cannot change one without changing the other, and this method does not apply.
Clean the weak track first
Do any high-pass, noise reduction and echo work on the laptop track before you match tone. EQ boosts raise noise too, so cleaning after matching undoes the match.
Match loudness before tone
Our hearing is less sensitive to low and high frequencies at lower levels, which is what the equal-loudness contours in ISO 226 describe. The quieter voice therefore sounds thinner than it is. Match the two first, using the method in how to match podcast host and guest loudness in REAPER, or every EQ decision afterwards is biased.
The meet-in-the-middle method in REAPER
All of this uses stock plugins. ReaEQ's band types include high pass, low shelf, band and high shelf, and its band width is set in octaves, which is the unit used below. Treat every number as a starting range to adjust by ear, not a setting to copy.
1. Set up a fair comparison
Find a 30 to 60 second stretch where the two people trade lines quickly, and loop it by dragging across the timeline and turning on repeat. Do not solo either track while you decide. The problem only exists in the switch, so you have to hear the switch. If you want a visual check as well, REAPER includes a frequency spectrum analyzer plugin: put one on each track and compare the general shape. Use it to confirm what you hear, not as a target, because two different voices never have identical curves.
2. Give both tracks the same low-end floor
Add ReaEQ to each track with a high-pass band. On the laptop track, start somewhere around 80 to 120 Hz; below that it usually holds desk thumps and hum rather than voice. On the good mic, set a high pass in a similar place, then decide whether its extra warmth is the main difference. If it is, add a low shelf on the good track around 150 to 250 Hz and pull it down by about 2 to 4 dB. That moves the good voice partway toward the thinner one without making it thin.
The tempting fix is a big low boost on the thin track. The laptop mic did not capture much real voice down there, so a large boost mostly raises room rumble, handling noise and hum. If you do add warmth, keep it small (about +1 to +3 dB on a wide band or shelf around 150 to 250 Hz) and listen for noise coming up with it.
3. Take the boxiness out of the laptop track
A voice recorded at a distance in an ordinary room often has a hollow, boxy quality in the low mids. On the laptop track, add a band cut, sweep it slowly between about 300 and 700 Hz while the loop plays, and settle where the boxiness drops most. Start around -2 to -5 dB with a width of about one octave. This is usually the single move that helps a far-away voice most.
4. Line up presence, carefully
Clarity in speech lives roughly between 2 and 5 kHz. Compare the two voices there. If the laptop voice sounds dull next to the good one, try a wide boost of +1 to +3 dB in that range. If it starts to sound harsh or the noise turns hissy, the detail is not there to lift, so back off. If instead the good mic sounds noticeably brighter or crisper than the laptop can ever be, a gentle high shelf cut of 1 to 2 dB above about 8 to 10 kHz on the good track can narrow the gap. Podcast Engineering School suggests the same either-or-both approach for a bright condenser next to a duller dynamic mic.
5. Consider the room difference last
If the two now sound tonally close but one still sounds like it is in a different space, you have two honest options. Reduce the room on the laptop track as far as it will go cleanly (see how to reduce reverb on a voice in REAPER), or accept it. Some editors add a very small amount of short room reverb to the dry close mic so both voices seem to share a space. If you try that, keep it barely audible: it makes your best track slightly worse to make the pair more consistent, and that trade is only worth it when the room on the weak track is obvious.
6. Compress both to a similar degree, then re-check loudness
If you use compression, aim for a similar amount of gain reduction on each voice so one does not sound more squeezed and forward than the other. EQ changes level, so re-check the loudness match after all of the above and nudge the track gain if needed.
When to stop
Listen to the loop at a normal volume and ask one question: does the switch between speakers still make me notice the microphones? If the answer is no, you are done, even though the two voices still clearly sound different. Then play the loop on earbuds and a phone speaker, because a low-end mismatch that is obvious on headphones can disappear on a phone and the reverse.
Stop earlier if either of these happens: the good voice starts to sound thin or dull compared with how it sounded at the start, or the laptop voice gets louder in hiss and room than in voice. Both mean you have gone past what the recording can give.
A laptop mic next to a decent microphone will still sound like a laptop mic when you are done. A good result is that listeners stop being distracted by the difference and follow the conversation. That is a real improvement and usually the best available without a re-record.
What this will not do
- It will not recreate missing detail. Low end the laptop never captured and high-frequency detail removed by a call app's compression are gone. EQ can only reshape what is there.
- It will not separate voices on one track. If both people are on one file, matching tone between them is not possible after the fact.
- It will not undo baked-in processing. Noise suppression artifacts or level pumping from the laptop or call app stay, even if the tone gets closer.
- It is not a fixed preset. Two different voices, two different mics and two rooms mean the settings above are starting points. Copying them onto another episode without listening will not give the same result.
Stop it happening next time
The cheapest fix is before the recording. A guest with any close mic, even a basic USB mic or a headset mic near the mouth, will sit closer to your sound than the best laptop mic at arm's length. If the guest is remote, have each person record their own mic locally and send you the file, as described in how to record a double-ender without drift. And when you know in advance that one person will be on a laptop, place them close to it in the quietest, softest room available. Distance and room are the parts no plugin can fully put back.
Clean the weak track, match loudness, then meet in the middle with small EQ moves on both tracks: a shared high-pass, a small low shelf cut on the good mic, a low-mid cut on the laptop track, and careful presence matching. Judge it with both voices trading lines, stop when the switch no longer draws attention, and fix the microphone situation before the next episode.
Sources
- Geoffrey Francis, REAPER ReaPlugs and JS Effects Guide (supplement to the REAPER User Guide), version 3.04 - ReaEQ band types (Low Shelf, High Shelf, Band, Low Pass, High Pass and others) and bandwidth in octaves; ReaFir Subtract mode noise profile; the Frequency Spectrum Analyzer; JS Loudness Meter (LUFS momentary, short-term and integrated). dlz.reaper.fm
- Cockos, REAPER User Guide, updated for version 7.84, the current release checked on the day of publication. reaper.fm/userguide
- Sam Inglis, “Proximity Effect”, Sound On Sound (November 2021) - proximity effect occurs in pressure-gradient (directional) microphones, not pressure (omnidirectional) microphones, and increases as the source gets closer. soundonsound.com
- ISO 226:2023, Acoustics - Normal equal-loudness-level contours - standard describing how perceived loudness varies with frequency and level. din.de listing
- Podcast Engineering School, “One Participant Using a Condenser Mic, the Other Using a Dynamic Mic” - practitioner tip to roll off highs on the brighter track, lift highs on the duller one, or both. podcastengineeringschool.com (practitioner context)