Mix-Minus for Remote Guests: Route a Clean Return Without Echo

TL;DR — Mix-minus is a return mix that contains what a remote contributor needs to hear while excluding that contributor's own incoming audio. Build it from a dedicated bus or supported interface route, then verify both directions through the real call. Include local voices, essential playback, and cues as agreed; exclude the remote return from its own send. Label the device, channel, bus, operator, and fallback in the technical rider.

Table of contents

1. Define the two audio directions
2. Build the guest return
3. Test the complete path
4. Document the handoff
5. FAQ

Define the two audio directions

A mix-minus feed is a mix sent to a participant with that participant's own signal removed. For a remote guest, the call return enters the production mixer as an input. The outgoing mix to that guest contains the local host and other agreed sources, but excludes that call return. The guest hears the conversation without a delayed copy of their own voice.

Do not treat the house PA, program record, stream feed, and guest return as one output. They serve different listeners. The public mix may include the guest; the guest return must omit that same guest's incoming channel. A delayed self-return can be heard as echo, and a loop through a loudspeaker can also create feedback. A separate software-monitoring loop can cause similar symptoms, so trace the full path before changing gain.

An aux bus, matrix, interface mixer, or dedicated conferencing device can create the return if it offers the necessary routing. “Mix-minus” is a required signal relationship, not a promise that any button with that label works the same way on every device. Yamaha documents both aux-based exclusion and device-specific mix-minus switches; confirm the actual product routing before show day.

Build the guest return

1. Name the call boundary. Record the incoming device or software channel, the outgoing device input, connector or digital route, channel count, and operator.
2. Create a dedicated send. Assign local speech and the playback the guest needs. Choose pre- or post-fader behavior deliberately; the aux send guide explains how those choices respond to FOH fader moves.
3. Remove the guest return from its own send. Check both direct assignment and indirect paths through groups, matrices, software loopback, and interface monitoring.
4. Keep private paths private. Send cues or talkback only to named listeners. A production intercom and a guest return may have different audiences.
5. Set a safe starting level. Ask the guest to use headphones, agree on return level, and test speech before adding loud playback.

For two independent remote contributors, each may need a different minus. Guest A's return can include Guest B while excluding A; Guest B's return can include A while excluding B. A conferencing platform may already handle some participant returns, so map the platform and hardware paths rather than adding duplicate buses by habit.

Example routing for one remote guest

This is an example, not a console preset. The exact tap points, mute behavior, and USB or network patch depend on the equipment. Allen & Heath describes a remote-guest mix-minus as a return containing the studio voices without the guest's echo; Yamaha's console documentation describes excluding selected channels from an aux send. Use the actual signal flow and device manual to reproduce the result.

Test the complete path

Test with the real guest endpoint and connection, not only a local meter. Have the guest speak while every local microphone is silent. Their voice should reach the intended program destination, but should not be audible back in their own headphones after the round trip. Then speak locally and confirm that the guest hears you clearly. Test playback, mute, scene recall, and any stream or record route independently.

If the guest reports echo, isolate the first loop: guest return assigned to its own send, operating-system loopback, conferencing software monitoring, loudspeaker pickup, or another call participant's device. Lowering a fader may hide the symptom while leaving the routing fault. Recheck the return after changing interface mode, scene, computer, or call platform.

For a show with remote contributors, add this check to the livestream audio rider and schedule it in the show advance. A recording or stream also needs its own approval and delivery plan.

Document the handoff

Record the source and destination names, who supplies each device, bus or interface route, send contents, excluded channel, pre/post-fader behavior, mute and scene behavior, return level, private-cue policy, acceptance listener, test time, and reconnect fallback. Distinguish the guest's audio into production from the mix back to the guest.

In Techrider.live, list these paths beside the input list and monitor destinations. Invite the audio owner to edit and save the same Rider, inspect history after a routing change, and export a dated PDF for the venue team. The corporate event AV rider shows where a remote-contribution handoff fits in a wider event plan.

FAQ

What is a mix-minus feed?

It is a return mix sent to a participant with that participant's own incoming signal excluded. The listener receives the other agreed sources without a delayed copy of themselves.

Why does a remote guest hear an echo?

Their audio may be routed back through the guest send, software loopback, monitoring, or an open loudspeaker and microphone. Follow both directions through the actual call to identify the first loop.

How do you set up mix-minus on a mixer?

Create an output or bus for the guest, add the local sources they need, and exclude the guest's return channel. Patch that bus to the call input, then test the complete round trip. Device-specific routing and tap points vary.

Does each remote guest need a separate mix-minus?

Often yes when they arrive as independent call returns: each send must exclude its own recipient. A conferencing platform may combine or manage participant returns internally, so map its behavior first.

How do you test a mix-minus return?

Ask the guest to speak and confirm their voice reaches the program but not their own headphones; then test local speech, playback, mute, scene changes, and reconnection through the real call.

Make the guest return explicit

Build one current Rider with Techrider.live and name both audio directions before the rehearsal. The next operator should know exactly which channel is excluded and where to listen for proof.

---

Last updated: 2026-09-22 · Reviewed against Yamaha mix-minus routing documentation and Allen & Heath remote-guest guidance.