What Is Mix-Minus? The Audio Feed Without the Echo

The short definition

A mix-minus is an audio feed that includes the sources a recipient needs while leaving out that recipient's own input. The missing source is the minus. A caller can hear the host and other program audio without hearing their own voice return from the host's mixer a moment later.

The idea is about routing, not a particular console brand. One output is tailored for one destination, and its channel balance differs from the main program mix. The recipient hears the conversation or performance around them without a delayed copy of themselves.

Why the separate feed matters

When a remote guest sends audio to a host, that sound may enter the main mix. If the host sends the entire main mix back to the guest, the guest's voice can return to them after network, software, or processing delay. Even a short delay can make it difficult to speak naturally.

A mix-minus removes that guest's incoming channel from the feed sent back to the guest. The main audience mix can still include the guest, while the guest's return contains the host microphone and other agreed sources. For more than one remote person, each person may need a different return that excludes their own input.

This routing does not remove sound reflections in a room or solve every acoustic feedback problem. It addresses a signal path that sends someone's own audio back to them. Keep those problems separate when troubleshooting.

How a mix-minus is built

On a mixer, the engineer commonly creates a separate auxiliary, mix, or matrix output for the recipient. Other channels are sent to that output, while the recipient's own incoming channel is left out or turned down. The output is then routed to the call, monitor, or communication system that needs it.

Some digital consoles offer a dedicated Mix Minus function. Yamaha's CL-series supplementary manual describes a function that removes a selected channel from signals sent to MIX or MATRIX buses and sets other send parameters. That is one documented console implementation, not a universal button layout or requirement.

On another system, the same result may be created with an auxiliary bus, a software send, or a separate interface output. The name of the bus matters less than the routing result: the person receiving the return should hear the sources they need, without their own live input coming back.

A simple remote-session example

Imagine a singer joining a producer over a call while a backing track plays in the studio. The singer needs to hear the producer and the track, but should not hear a delayed copy of their own voice from the call return. The producer can send the singer a separate mix containing the studio microphone and backing track while excluding the singer's incoming call channel.

The main program or recording path can still capture the singer. The minus applies to the feed sent back to that singer, not necessarily to the full recording or audience mix. This is why the direction of each send should be named and tested rather than guessed from a fader position.

A band using live playback may also have separate audience, performer, and cue outputs. A live playback rig and a monitor mix are related parts of a signal plan, but each has its own purpose and routing requirements.

Common setup mistakes

The most common failure is sending the recipient the main mix unchanged. If that mix contains the recipient's own live input, the return may produce a distracting echo. Another is removing the wrong channel, which can make the caller lose the person or instrument they are supposed to hear.

It is also easy to confuse a muted channel in the room mix with a channel removed from a specific bus. A separate mix can have independent sends, pre- or post-fader choices, and destination routing. Check the bus itself and verify what reaches the receiving device.

Finally, a successful mix-minus does not guarantee a clean monitor. The return may still be too loud, too quiet, distorted, or missing program material. Set the level, listen for clipping, and check the actual return path with the other person before the session begins.

A practical verification pass

Start with the channel that belongs to the person receiving the feed. Confirm that their own source is excluded from the return, then verify that every other source they need is present. Ask them to speak while you listen to the return at the destination, not only on the console meter.

Test one change at a time. If they hear themselves, trace the return path for a second route that may be feeding the call. If they cannot hear the host or backing track, check the send to the separate bus. Save the working routing notes when the setup will be reused.

A mix-minus is a compact solution to a specific routing problem. Understand who receives each output, which source is removed, and where the remaining channels go. That is more reliable than assuming every mixer has a dedicated control with the same name.