Webcam testMicrophone testWebcam and mic test
TestsWebcam testMicrophone testWebcam and mic testHeadphone testPre-stream checklist
SetupsSetup builderSetup guidesAudio routingCamera checker
SettingsBitrate calculatorUpload calculatorSettings by platformTwitchYouTube LiveKickFacebook LiveTikTok LIVE
GearAll gearComparisonsStream Deck selector
GuidesChoose your gearConnect and set upFix a problemAll guidesAll tools
AboutCorrections and contact

Search stays on this device. Esc to close.

Loopback and mix-minus do different jobs

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.

What to plan first

Check these in order. The first two, sources and destinations, decide whether it works at all; the rest make it easier to use.

  • 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.

What can catch you out

Any of these can change your choice, or tell you what to check next when something fails.

  • 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.

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: 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.

One remote guest, or two

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.

Plan who hears what in the audio routing builder, then set it up with the OBS audio routing guide.

What usually goes wrong

Find your symptom below. Change one thing at a time, and make a short test recording after each change before you go live again.

  • 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.

Test it on a call

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 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.

Sources