Aux vs Matrix on a Mixer: Live Sound Routing Explained

TL;DR — An aux bus usually builds a destination mix from individual input channels, making it suitable for performer monitors or effects sends. A matrix usually builds an output from completed buses such as main left/right, groups, or other mixes, making it useful for front fills, delays, foyer feeds, recording, or broadcast. Console architectures vary, and some matrices also accept input channels. Document the source bus, send point, output patch, destination, processing, and owner rather than relying on labels alone.

Table of contents

1. Start with the routing difference
2. Use aux buses for input-based mixes
3. Use matrices for bus-based outputs
4. Choose the right route
5. Build and verify the output path
6. Document buses and destinations
7. FAQ

Start with the routing difference

An aux bus and a matrix bus both combine signals and can reach physical outputs. The practical difference is what normally feeds them.

• An aux commonly receives sends from individual input channels and returns. Each source can have a different level in that aux mix.
• A matrix commonly receives sends from other buses, such as main left/right, groups, or mixes. It creates another version of an already combined program for a specific output destination.

input channels ──> aux bus ──> monitor / effects / utility output

input channels ──> groups or main bus ──> matrix ──> zone / delay / record feed

This is a mental model, not a universal console schematic. Some digital consoles let input channels feed matrices directly, allow flexible send points, or use mix as a configurable aux/group label. Read the console documentation and verify the show-file configuration.

Neither name guarantees a particular connector, signal format, pre/post-fader point, processing order, or mute behavior.

Use aux buses for input-based mixes

An aux creates a parallel mix by taking a controllable send from each input channel. For example, a vocalist's monitor aux may contain a strong vocal send, moderate keyboard and guitar sends, and little or no drum kit. The main audience mix can have a completely different balance.

Performer monitors

Monitor and IEM mixes are common aux applications because each performer needs an independent balance. The aux master controls the overall destination level while the channel sends establish the mix inside it.

A monitor send is often pre-fader so FOH fader moves do not change the performer balance. That does not prove where the send sits relative to EQ, dynamics, mute, or other processing. The pre-fader versus post-fader guide explains why the exact pickoff point matters.

Name the bus by its destination, such as MIX-01 MAYA IEM, instead of leaving it as AUX 1. A useful monitor-mix plan also identifies the performer, wedge or IEM type, output, and provider.

Effects sends

A post-fader aux commonly sends selected input channels to reverb or delay. The processed return is then blended into the main or another destination. When an input fader moves, a post-fader effects send follows it, preserving a useful relationship between dry and processed sound.

Do not confuse an effects send with the effects return. The send bus collects source signals; the return brings processed audio back into the console. Confirm that the return is assigned only to the intended destinations and avoid an accidental feedback loop.

Utility and external feeds

An aux can also create a backstage, recording, stream, or press mix directly from inputs. This may be appropriate when that destination needs a balance independent from FOH. The tradeoff is operational: someone must monitor and mix it, and its sends may not follow changes made elsewhere.

Use matrices for bus-based outputs

A matrix takes one or more completed buses and combines them into another destination output. This creates a controlled layer between the mix and the physical zone or receiver.

Front fills and under-balcony zones

A front-fill matrix may receive the main mix, then apply independent level, EQ, delay, and limiting appropriate to the fill system. If the console and system design require a modified source balance, a group or direct matrix input may supplement the main feed. Do not assume that every fill should receive an identical full-range signal; follow the system design.

Delay loudspeakers

A delay matrix can receive the main program and add output-specific delay, level, EQ, and processing before the console output. The delay value is a system-alignment decision based on measured geometry and the complete processing path, not a generic number copied into a rider.

Recording, broadcast, stream, and press

A matrix can combine main, group, audience, announcement, or other buses into a program feed without changing the PA master. This is useful when a receiving team needs a recognizable show mix plus destination-specific adjustments.

However, a matrix derived only from FOH may not contain enough of sources that are already loud acoustically in the room. A recording or broadcast operator may need additional groups, direct inputs, ambience microphones, or a separate mix. Assign who owns that balance and where it is monitored.

Matrix is not the system processor

A console matrix may provide output EQ, delay, dynamics, and level, but it does not automatically replace the loudspeaker system processor. Venue processing may also perform crossover, driver alignment, protection, and locked system functions. Keep responsibilities clear and do not bypass approved system processing to simplify the console route.

Choose the right route

Begin with the destination's listening requirement, not the free bus count.

Use a matrix when the destination should largely follow one or more existing mixes. Use an aux when the destination needs a new balance made directly from input channels. If the console permits both approaches, choose the route that makes ownership, monitoring, and failure isolation clearest.

Do not confuse buses, DCAs, and outputs

A bus carries audio. A DCA or VCA controls the levels of assigned channels without becoming an audio path. A physical output sends a patched internal bus or channel to another device. Moving a DCA can change levels feeding several buses, but the DCA itself cannot be patched to an output as audio.

The word mix can describe an audible balance or a console-specific bus type. The word output can describe a bus master, a physical socket, or a destination. Write all three layers explicitly: internal bus, output patch, receiving device.

Build and verify the output path

1. Define the destination

Write what the listener or receiving system needs: a performer-specific mix, main-program copy, zone feed, effects send, record mix, or communication path. Name the operator responsible for it.

2. Choose source buses and send points

For an aux, decide which inputs feed it and whether each send is pre- or post-fader at the intended pickoff. For a matrix, decide which main, group, aux, or direct sources feed it and whether those sends follow their source masters.

3. Configure output processing

Apply only processing owned at this layer. Record EQ, dynamics, delay, mute-group, and limiter responsibilities. Avoid duplicating alignment or protection processing already owned by the venue system processor.

4. Patch the physical or network output

Map the bus to an output socket or network channel, then document format, nominal level, connector or protocol, channel mapping, receiving input, and clock ownership for digital paths. Matching bus and socket numbers are convenient but not guaranteed.

5. Test behavior as well as signal

Send a controlled known source and confirm:

• the intended inputs or buses reach the destination;
• unrelated sources do not;
• channel, group, main, aux, matrix, DCA, and mute changes behave as expected;
• the physical or network output reaches the correct receiver;
• destination level and processing remain safe;
• the assigned operator can monitor the feed;
• fallback routing is understood where the show requires it.

A moving matrix meter proves only that audio exists at that internal point. It does not prove the correct output patch, cable, processor input, amplifier, loudspeaker, recorder, or encoder.

Document buses and destinations

Use stable functional names across the rider, console file, output patch, and cable labels.

Examples show the fields, not a universal patch. Confirm terminology and behavior on the actual console.

Connect this output map to the stage-box and subsnake patch list where physical stage outputs are involved. Use the live sound signal-flow guide to trace each path through processing and receiving equipment.

In Techrider.live, invite the relevant FOH, monitor, or production lead to edit the same Rider, save agreed monitor and routing notes, and inspect history when an output assignment changes. Export a dated PDF after the source buses, destinations, and owners are approved.

Output handoff checklist

• Every aux and matrix has a functional destination name.
• Source channels or source buses are identified.
• Pre/post-fader and pickoff behavior is verified where relevant.
• Stereo pairing, panning, and channel order are explicit.
• Bus processing and system-processor responsibilities are separate.
• The physical or network output patch is current.
• Format, level, connector, mapping, and receiving input are documented.
• The destination has an operator and monitoring point.
• Mutes, DCAs, scenes, and master moves have been behavior-tested.

FAQ

What is the difference between an aux and a matrix on a mixer?

An aux normally makes a mix directly from individual input-channel sends. A matrix normally makes another output from completed buses such as main left/right, groups, or auxes. Exact routing and available source points vary by console.

What is a matrix output used for?

Common matrix destinations include front fills, delay loudspeakers, under-balcony or lobby zones, recording, broadcast, streaming, and press feeds. A matrix lets the engineer combine source buses and apply destination-specific level and processing without changing the main PA mix.

Should monitors use an aux or matrix?

Performer monitors normally use aux buses because each performer needs an independent balance of input channels. A matrix may distribute or derive a completed monitor bus in a specific system, but it is not the usual starting point for building the performer's input mix.

Can a matrix feed delay speakers?

Yes. A matrix commonly feeds delay loudspeakers because it can follow the main program while providing zone-specific level, EQ, delay, and routing. The actual delay and processing must follow the measured system design and venue processor boundaries.

Can input channels feed a matrix?

Some digital consoles allow input channels to feed matrices directly, while other consoles limit matrices to main, group, or mix-bus sources. Check the console model, firmware, configuration, and show file instead of assuming one architecture.

Route by destination, not by habit

Build a Rider in Techrider.live to keep monitor destinations, output routes, stage connections, and production ownership in one current plan. Clear bus names and verified handoffs make complex console routing easier to build, test, and troubleshoot.