Make the decision from the signal path
Loopback brings a device or application output back as an input for recording or streaming. Mix-minus is a destination-specific mix that contains what a remote participant needs while subtracting that participant’s own return. They solve related but different jobs.
A loopback label does not prove that a remote return can be excluded from its own send. Build that exclusion into the route and verify it with the actual calling application.
Eight decision factors
Check these in order. Sources and Destinations decide whether the route works; the remaining factors refine operation and convenience.
- Sources: List local microphones, game/app audio, alerts, music and every remote return.
- Destinations: List stream, recording tracks, creator headphones, local guests and remote sends.
- Loopback need: Mark which computer playback must re-enter the production.
- Guest exclusion: Remove each guest’s return from the mix sent back to that guest.
- Monitoring: Keep the creator mix complete without sending delayed program audio back unnecessarily.
- Track plan: Choose whether local recordings need isolated sources in addition to the live mix.
- Device roles: Map hardware outputs and virtual buses by exact name.
- Mute behavior: Decide whether a mute affects stream, guest send, monitor, recording or all destinations.
Constraints that change the answer
Start with Feedback risk. The conditions below can change the choice or the next troubleshooting branch.
- Feedback risk: An open speaker or duplicated return can create acoustic or digital feedback.
- Per-destination logic: One universal mix is insufficient when guests need different exclusions.
- Software labels: Monitor, stream, virtual input and chat buses vary by product; document names.
- Track assignment: An isolated track does not reach the live stream unless the stream track also contains it.
- Unsupported inference: Do not infer mix-minus merely from a loopback checkbox or headphone jack.
A practical connection and configuration workflow
Follow the steps in order. Confirm the hardware in the operating system before selecting it in OBS or another routing application, and change one cable, mode or route at a time.
- Step 1: Draw a source-by-destination table.
- Step 2: Add local microphones to stream, monitor and guest sends.
- Step 3: Add each guest return to stream and monitor but exclude it from its own send.
- Step 4: Add computer playback through the documented loopback/virtual path once.
- Step 5: Record and call a test participant; confirm every destination separately.
Examples
For one remote guest, the guest send can contain both local microphones and necessary program audio while excluding the guest return. The live stream contains all three voices.
For two remote guests, each send needs a different subtraction: Guest A’s send excludes A but can include B; Guest B’s send excludes B but can include A.
Use audio routing builder and OBS routing guide for the adjacent checks.
Four common failure modes
Match the symptom below first, then change one variable at a time and make a short local recording before changing the destination.
- Remote guest hears echo: Their return is inside their send or the room speaker is feeding the microphone.
- Stream misses application audio: The loopback/virtual source is not selected on the stream mix.
- Creator hears delayed voice: Program monitoring duplicates direct monitoring; choose one path.
- Recording track empty: The source is absent from that track even if it is present in the live mix.
Prove the result
Make a local recording while the remote participant speaks and while local program audio plays. The remote return must be audible locally but absent from the feed sent back to that participant.
Monitor both ends of a short call. If the remote voice returns as echo, correct the bus or application send before adding processing or changing microphones.
Equipment for these connections
Start with the needed role. Check the complete profile before adding a product to your setup.
A single XLR microphone with Wave Link routing
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 →Check price on Amazon ↗Two XLR voices and two headphone mixes in a compact interface
Elgato Wave XLR Pro
Connect the streaming computer to the USB host socket. Reserve the auxiliary USB connection for the second device and assign each return separately.
Connections & full profile →Check price on Amazon ↗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 →Check price on Amazon ↗Combine one HDMI capture and microphone routing path
RØDE Streamer X
Set capture output separately from the display passthrough mode. Configure the audio returns before going live so HDMI audio and computer loopback do not reach OBS twice.
Connections & full profile →Check price on Amazon ↗Two local voices plus guest and computer audio
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 →Check price on Amazon ↗