One headphone mix, one copy of your voice
Monitoring should let the creator hear the sources needed for performance without sending the monitored program back into its own inputs. Pick one headphone output as the monitor destination and one monitoring path for each source.
Direct hardware monitoring and delayed software monitoring can both exist, but do not send both copies of the same live microphone to the creator's headphones.
Closed-back headphones help too: they keep what you hear out of the microphone. Headphones for streaming compares the models we cover.
What to set up
Check these in order. The first two, headphone destination and voice monitor, decide whether it works at all; the rest make it easier to use.
- Headphone destination: Identify the exact microphone, interface or mixer socket feeding the creator.
- Voice monitor: Choose direct hardware monitoring when available and disable a duplicate delayed software return.
- Program sources: Add game, alerts, music and guest returns at usable monitor levels.
- Stream independence: A monitor mix can differ from the stream mix without changing what viewers receive.
- Guest exclusion: Do not send a remote participant’s return back to them.
- Room speakers: Mute or isolate speakers that can feed the live microphone.
- Latency: Trace converters and software hops before applying sync or replacing hardware.
- Mute behavior: Verify cough/mute still behaves correctly in both monitor and stream destinations.
What causes echo
Any of these can change your choice, or tell you what to check next when something fails.
- Default output: Reconnects can move monitoring to the wrong device.
- Double voice: Direct and software monitoring together sound like an echo.
- Program return: Capturing the monitoring output as desktop audio can duplicate the whole mix.
- Open speakers: Acoustic feedback remains possible even when digital routing is correct.
- Bluetooth: Wireless headphone latency and profile switching may be unsuitable for precise live monitoring.
Set it up step by step
Follow the steps in order. Check that your computer sees each device before you choose it in OBS or your audio app, and change one cable or setting at a time.
- Step 1: Plug wired headphones into the chosen owner output.
- Step 2: Enable one voice monitoring path.
- Step 3: Add program sources one by one and label their route.
- Step 4: Confirm the stream receives them independently from monitor settings.
- Step 5: Record and join a guest test while muting/unmuting each relevant bus.
Two examples: a USB microphone and a mixer
A USB microphone with a headphone jack can own direct voice monitoring while OBS sends game and alerts to that same output. The microphone should enter the stream once.
A mixer with separate headphone mixes can give two hosts different balances. That does not automatically create a safe remote guest send; the guest return still needs exclusion.
See also the mix-minus guide and the OBS audio routing guide.
If you still hear echo
Find your symptom below. Change one thing at a time, and make a short test recording after each change before you go live again.
- Voice has short echo: Disable either direct monitoring or the delayed software monitor.
- Viewer hears doubled program: The monitor/program bus is being recaptured; remove the second source.
- Headphones go silent after reconnect: Re-select the explicit monitor output instead of Default.
- Feedback rises rapidly: Mute speakers/returns, then rebuild the route with headphones at low level.
Test it with your headphones on
Speak once while listening through the normal headphones. Keep either the direct hardware copy or the software-monitored copy of the microphone, and mute the duplicate path.
Record a short local file after the change. If the recording is clean but the headphones still echo, continue tracing the monitor route rather than changing the program mix.
Equipment for these connections
Start with the kind of gear you’re missing, and read its full profile before adding it to your setup.
As an Amazon Associate I earn from qualifying purchases. How this site earns · Amazon offers a free 30-day Prime trial, with free delivery on eligible items.
A plug-in USB microphone for a simple desk
Elgato Wave Neo
Choose it for one direct USB speaking position and use its headphone jack to monitor your voice. For two separately controlled speakers, plan two microphones and an interface with two inputs.
Connections & full profile →A USB microphone with Elgato’s Wave Link software
Elgato Wave:3 MK.2
Choose the MK.2 as your audio device and set up its processing before adding it to OBS; guides for the first Wave:3 describe different processing.
Connections & full profile →USB now, an XLR interface later
Shure MV7+
Use USB for the microphone’s DSP and headphone features. On XLR, plan processing and monitoring at the interface; those USB features do not follow the analog cable.
Connections & full profile →A USB and XLR microphone: a computer now, a mixer later
RØDE PodMic USB (Black)
Choose a mount that supports the microphone’s documented weight. Use USB for its onboard processing, or plan processing and monitoring separately on the XLR route.
Connections & full profile →One XLR microphone into your computer, with Wave Link mixing
Elgato Wave XLR MK.2
Its single microphone preamp suits one XLR speaker. Choose an interface with two independent mic inputs when two people need separate gain controls.
Connections & full profile →Two independent microphone inputs for a two-person recording
Focusrite Scarlett 2i2 4th Gen
Loopback alone does not remove a guest’s voice from their return. Build a separate mix-minus route before using remote guests, or choose a mixer with that routing available.
Connections & full profile →Two people in the room, plus a remote guest and computer sound
RØDE RØDECaster Duo
Assign the stream, headphones and guest return explicitly. Exclude the guest’s own voice from their return, then record a call to check the mix before going live.
Connections & full profile →