Condenser microphones are brutally honest. They pick up the voice you want, but they also pick up every reflection, hum, fan, and keyboard clack your room produces. In an untreated room, you cannot fix the acoustics themselves with settings — but you can get remarkably close by choosing the right gain structure, polar pattern, filters, and noise reduction chain. This guide walks through every setting that matters, in the order you should apply it.

The priority order matters: get physical placement and gain right first, then apply filters, then apply noise reduction last. Reversing that order is the most common reason people end up with processed, underwater-sounding audio. Everything below assumes a USB or XLR condenser into an interface, recorded or streamed on a Windows PC.

Setting Recommended value Why
Distance to mic 15–20 cm (6–8 in), slightly off-axis Reduces room reflection pickup while keeping proximity-effect bass full
Polar pattern Cardioid Rejects sound from the rear, where most untreated-room reflections return from
Pad 0 dB (off) Voice at close range rarely exceeds the mic’s headroom; the pad costs you signal-to-noise
Low-cut / high-pass filter 80–100 Hz, 12 dB/octave Removes rumble, desk thumps, and HVAC hum energy below the voice
Gain / input level Peaks at −18 to −12 dBFS, average around −24 dBFS Maximizes signal above the noise floor without risking clipping
Sample rate / bit depth 48 kHz / 24-bit 24-bit gives massive headroom; 48 kHz matches video and voice standards
Noise gate threshold Just above measured noise floor, roughly −50 to −45 dBFS Cuts fan and room hiss between phrases without clipping word endings
Compression ratio 3:1, attack ~10 ms, release ~100 ms, 3–6 dB gain reduction Evens out delivery without pumping or exaggerating room noise

Setting-by-Setting

Gain (Input Level)

Exact value: Set gain so your normal speaking voice peaks between −18 and −12 dBFS, with the loudest exclamations staying under −6 dBFS. On an Audio-Technica AT2020 USB-style mic, this is typically the 40–60% mark in the manufacturer’s software; on a Focusrite Scarlett interface, gain knobs usually sit between the 9 and 11 o’clock positions for close-up speech. If your mic or interface has no meter, use the free Reaper recording software or Audacity: record ten seconds of normal speech and watch the peak indicator.

Trade-off: Too much gain raises your room’s noise floor with your voice, and once you clip, nothing can fix it. Too little gain forces you to boost later in software, which amplifies hiss identically. In an untreated room, low gain plus close positioning almost always beats high gain plus distant positioning.

Polar Pattern

Exact value: Cardioid, always, in an untreated room. If your mic has switches (for example, a multi-pattern NT1-style or AT4040-style body), physically flip the switch and confirm the indicator LED or label. On the mic, the side marked with the cardioid symbol faces your mouth; the rear of the capsule points at the noisiest part of your room.

Trade-off: Omnidirectional sounds more natural and has no proximity-effect bass buildup, but it picks up reflections from every wall equally — a disaster in a bare room. Figure-8 rejects the sides but grabs reflections from directly behind the mic, which in a typical bedroom means your windows and bare wall.

Low-Cut / High-Pass Filter

Exact value: Enable the hardware low-cut at 80 Hz if the mic has one (many condensers label it as a bent-line switch). If not, apply a high-pass filter in software: in OBS Studio, add a Filters entry on the mic source, choose “Highpass Filter,” and set 90 Hz with a Q of 0.7. In Reaper, use ReaEQ: check band 1, set type to High-Pass, frequency 85 Hz.

Trade-off: Below about 100 Hz, a treated studio would still capture useful chest energy, but an untreated room captures mostly desk vibration, footsteps, and HVAC rumble down there. Cutting at 80–100 Hz costs you almost nothing perceptible in voice and buys you dramatically cleaner gating and compression downstream. Do not go above 120 Hz unless your voice is deep, or you will thin out the low end.

Noise Gate

Exact value: First, measure your noise floor: in OBS, View > Stats won’t show it, so instead open the mic’s Advanced Audio Properties (right-click the gear in the mixer) and enable “Monitor,” or simply record five seconds of silence and read the peak in Audacity (Analyze > Plot Spectrum helps). Then set the gate threshold 3–6 dB above that floor — commonly −50 to −45 dBFS. In OBS Filters, add a Noise Gate with Open Threshold −45 dB, Close Threshold −50 dB, Attack 5 ms, Hold 200 ms, Release 150 ms.

Trade-off: The gate is the single most audible giveaway of sloppy settings — clipped word endings (“hold” the release too short) or a “swimming” sound (threshold too high, cutting quiet syllables). Hold time of 150–250 ms is what makes a gate inaudible; start at 200 ms and only shorten it if you hear the room between phrases.

Noise Suppression

Exact value: In OBS Studio 30 and later, add a “Noise Suppression” filter and choose NVIDIA RTX Voice / AMD Noise Removal if you have a compatible GPU, set to roughly 60–70% intensity. Otherwise, choose RNNoise (the built-in option). Avoid stacking two suppressors.

Trade-off: AI-based suppression (RTX Voice, Krisp-style processing) is remarkably effective on constant noise like fans but chews into sibilance and breath, producing a slightly robotic edge at high intensity. RNNoise is lighter and more predictable but weaker on broadband hiss. If your noise is mostly constant fan hum, fix it at the source or with the gate instead; save suppression for keyboard and household noise.

Compression

Exact value: In OBS, add a Compressor filter: Ratio 3:1, Threshold −18 dB, Attack 10 ms, Release 100 ms, Output Gain 0 dB, aiming for 3–6 dB of gain reduction on loud phrases (watch the meter on the filter while you talk). In Reaper, ReaComp with the same numbers works identically.

Trade-off: Compression raises the perceived level of your voice, which also raises the perceived level of the room between words. The tighter your gate is set first, the safer compression is. Ratios above 6:1 on untreated-room audio tend to “breathe” audibly as the room noise swells back in each time you pause.

Sample Rate and Buffer

Exact value: Set 48,000 Hz everywhere — in Windows (Settings > System > Sound > your mic > Properties > Advanced > Default Format), in your interface’s driver panel, and in OBS (Settings > Audio > Sample Rate). Mismatched sample rates between the OS and the app cause resampling artifacts and latency. For XLR interfaces, set the buffer to 128–256 samples; if you hear crackles, raise it to 512.

Trade-off: 24-bit depth is free headroom — there is no reason to use 16-bit for voice. Sample rates above 48 kHz offer no benefit for speech and increase USB bandwidth and CPU load.

By Hardware Tier

Budget (USB mics like the AT2020USB+, Fifine A6V-style, Samson Q2U in condenser mode)

Work entirely inside the mic’s own software and one app. Set gain in the vendor utility so peaks hit −18 dBFS, enable the built-in low-cut if present, and do gating and suppression in OBS with RNNoise only. Avoid applying gain in Windows AND in the mic software — pick one, leave the other at 0 dB/100%, or you double-boost and clip. Expect to sit closer (12–15 cm) to compensate for less sensitive preamps.

Mid (XLR condenser plus a 2-channel interface — Scarlett 2i2-class, MOTU M2)

This is the sweet spot for untreated rooms because the interface’s physical gain knob and pad give you clean, forgiving control. Use the interface’s own Air/transform switch off (Air boosts highs, which also boosts room harshness), pad off, low-cut on. Apply your filter chain in software as described above. The MOTU M2’s onboard DSP loopback can handle the gate at the driver level if you prefer to keep OBS’s chain short.

High (Large-diaphragm condenser into a dedicated interface — SM7B-class dynamics aside, think TLM 103-class into an Audient or RME unit)

High-end condensers are the most revealing of bad rooms, so discipline matters more than gear. Keep the pad engaged only if you record loud sources; for voice, 0 dB. Use the interface’s built-in DSP effects (RME’s FX DSP, for example) for the low-cut and gate so they apply at near-zero latency to everything, not just your streaming app. Consider a reflection filter behind the mic and treat this as the ceiling of what settings alone can achieve — beyond this tier, acoustic panels return more per dollar than any hardware upgrade.

Common Mistakes

Gain Staging Twice

What causes it: Boosting input level in both the mic/interface software and Windows or the recording app.

How to check: Speak normally and watch the Windows input meter (Settings > System > Sound > Input) — if it sits near 100% while your app’s meter clips, you are double-staged.

What to do: Pick one gain control point. Set Windows (or the interface driver) so the raw signal peaks at −18 to −12 dBFS, and set every downstream input to 0 dB / 100%.

How to undo: Reset Windows input level to 100% default, then re-adjust only your interface or mic software gain.

Gating Before Filtering

What causes it: Adding a noise gate while low-frequency rumble is still present, so the gate constantly triggers on thumps.

How to check: Walk across the floor or tap the desk with the gate active — if the meter shows the gate opening, rumble is getting through.

What to do: Reorder the OBS filter chain: Noise Suppression first, then Highpass Filter, then Noise Gate, then Compressor. OBS applies filters top to bottom.

How to undo: Drag the filters back in the wrong order if you ever need to A/B test; there is no permanent change.

Over-Suppression

What causes it: Running AI noise suppression at maximum intensity because the room is noisy.

How to check: Record thirty seconds and listen for smeared “s” sounds and clipped-off breaths — classic artifacts of over-processing.

What to do: Drop suppression intensity to 60%, fix the underlying noise at the source (fan curve, door, window), and rely on gating plus distance instead.

How to undo: Set the filter intensity back to its previous value or delete the filter; suppression leaves no lasting change to the file.

Mic Too Far From the Mouth

What causes it: Framing aesthetics on camera — the mic sits an arm’s length away for a clean shot.

How to check: If your mouth is more than about 30 cm from the capsule, you are recording more room than voice. Record a clip and compare the ratio of direct voice to reverb tail.

What to do: Get to 15–20 cm with a boom arm, and angle the mic 15–30 degrees off-axis so breath plosives miss the capsule directly.

How to undo: Return the mic to its boom’s original position; nothing else in your chain needs to change.

FAQ

Should I use a dynamic mic instead?

Often, yes, if your room is very noisy and you cannot change anything physical. Dynamics like the SM58 or Q2U reject room sound far better by design. But a condenser at 15 cm with cardioid pattern, low-cut, and a proper gate gets close enough for most streams and calls — and sounds noticeably more detailed when you do eventually treat the room.

Does a reflection filter behind the mic count as treating the room?

Partially. It stops the strongest single reflection — the sound leaving the back of the mic and bouncing off the wall behind you — from returning into the capsule. It does nothing for ceiling, floor, or side-wall reflections, so it is a useful supplement, not a substitute, for panels or soft furnishings.

Can software fix a bad room completely?

No. Suppression and gating can mask constant noise and cut silence, but they cannot remove reverb baked into your voice between words. Think of the settings in this guide as a 70% solution; acoustic treatment, even just a duvet behind you and a rug under the mic, covers the rest.

What should I change first if my voice still sounds thin?

Move the mic closer before touching EQ. Proximity effect from 10–15 cm adds several dB of low-end naturally, which is cleaner than any software bass boost. If it is still thin after that, add a low-shelf EQ at 100–150 Hz with 2–3 dB of gain — not more, or the room’s bass buildup gets boosted with it. By 2026 standards, a well-staged close-mic setup with minimal processing outperforms heavy corrective EQ in nearly every blind test.

Related guides