Direct Out vs Aux Send on a Mixer: Choose the Right Feed
7 min read · Updated September 22, 2026 · FOH and monitor engineers, recording engineers, production managers, venue technicians, and working bands
Learn when a channel direct out or a shared aux mix is the right live sound feed, how tap points change behavior, and what to document for recording and monitors.
TL;DR — A direct out sends one channel to another destination; an aux bus combines chosen channels into an independently controlled mix. Choose direct outs when a recorder or processor needs separate source feeds, and aux sends when a performer or device needs a selected blend. Neither name guarantees pre-fader, unprocessed, or mute-independent behavior. Confirm the console's tap points, channel count, routing, level, and destination by testing the actual patch before the show.
Table of contents
- Define the two outputs
- Choose by destination
- Confirm tap points and control
- Test and document the patch
- FAQ
Define the two outputs
A direct out takes signal from one input channel and sends it to a separate output or digital route. Depending on the console, that output can leave before or after EQ, dynamics, mute, or fader. It may also follow head-amp gain and digital trim differently from other channel paths. “Direct” identifies the one-channel relationship; it does not specify a universal point in the signal chain.
An aux send sends a chosen amount of a channel to a shared aux bus. Other channels can join the same bus at their own send levels. The resulting aux mix has a master level and destination. Yamaha's routing guidance describes aux buses as shared paths used for effects or monitors, while its direct-output configuration shows that a direct-out source point can vary by hardware setup.
| Question | Direct out | Aux send / bus |
|---|---|---|
| How many sources feed one path? | Normally one input channel | Any assigned channels |
| Main control | Channel tap and output routing | Per-channel send plus bus master |
| Typical use | Isolated recording track, broadcast split, processor input | Wedge or IEM mix, FX send, utility mix |
| What must be checked? | Tap, processing, mute, fader, gain, patch | Send tap, membership, master, mute, destination |
| What does the name guarantee? | Channel-specific feed | A mix path with send controls |
An aux mix can be routed to a physical jack, audio network, or interface. A direct out may use those same transport types. The connector does not tell you which signal is present.
Choose by destination
Separate recording tracks
Use one direct out per source when the recorder needs separate microphone, DI, and playback tracks and the console provides the required count. Decide whether the track should be dry or include processing, whether fader moves should print, and who owns preamp gain. A true analog or digital split may be preferable when recording must remain independent of the FOH console. The multitrack recording rider covers clock, format, monitoring, and file delivery.
A performer's monitor mix
Use an aux bus when the performer needs a blend: their vocal, other players, playback, and agreed talkback or cues. A single direct out could carry one vocal but cannot by itself create that multi-source balance. Count actual mono or stereo output channels, wedges or IEM transmitters, and bus masters. The monitor mix guide helps translate performer requests into destinations.
Effects or external processing
A shared time effect commonly receives an aux send from several sources and returns through a separate input. A one-channel serial processor may use an insert or another defined one-channel path instead. The insert versus send/return guide covers that topology; do not assume a direct out by itself returns processed audio to the original channel.
Stream, press, or remote feed
First ask whether the destination needs isolated sources, a complete program, or a custom mix. A stream operator may require individual feeds; a press point may need a controlled program mix; a remote guest needs a return that excludes their own call audio. See the mix-minus guide for that special routing relationship.
Confirm tap points and control
Pre-fader and post-fader describe a signal's relationship to the channel fader, but do not by themselves say whether it is before EQ, dynamics, mute, or delay. A direct out may have a configurable pickoff, and an aux send may offer more than one pre-fader point. Yamaha's IM8 documentation, for example, identifies distinct direct-output positions with different processing and fader behavior. Other consoles can differ.
Ask these questions before accepting either feed:
- Does changing analog preamp gain alter the feed? Who controls shared head amps?
- Is digital trim included? At what point do EQ, dynamics, inserts, and delay enter?
- Does channel mute or DCA mute affect the output?
- Does the channel fader move change it?
- Can scene recall change the route, tap point, send level, or output patch?
- Is the physical or network output at the level and format expected by the receiving device?
Read the pre-fader versus post-fader aux guide for fader relationships and the preamp gain versus digital trim guide for shared-gain ownership. Neither replaces testing the configured show file.
Test and document the patch
- Label one source in the input list and patch it to the intended channel.
- Send a controlled, recognizable signal and confirm it at the receiving device.
- Change one control at a time: gain, trim, EQ, dynamics, mute, fader, send level, and bus master as relevant.
- Check other destinations after each change so a recording or monitor feed does not change unnoticed.
- Load the expected scene or show file and repeat the critical checks.
- Record the tested output number, tap point, control behavior, nominal level, connector or protocol, owner, and fallback.
| Rider field | Example to record |
|---|---|
| Source | CH 07 Lead vocal, matching input list |
| Feed purpose | Isolated recording track or lead-vocal IEM mix |
| Route | Direct out 07 to recorder input 07, or Aux 03 to IEM transmitter |
| Pickoff | Console-specific pre/post processing, fader, and mute state |
| Format | Analog level or digital channel, sample rate and clock if needed |
| Owner | Person allowed to change gain, route, and scene |
| Acceptance | Who listens at the final destination and when |
Use exact destination names rather than Out 3 alone. In Techrider.live, keep input, output, and monitor labels in one Rider; invite the engineer who owns the patch to edit and save it, inspect history after a routing change, and export a dated PDF for the venue.
FAQ
What is the difference between a direct out and an aux send?
A direct out provides a feed from one channel. An aux send contributes a controllable amount of that channel to a bus that can combine multiple channels. Both require a defined tap point and destination.
Can a direct out feed a monitor?
It can feed a device that needs only that one channel. A performer usually needs a blend of sources, so an aux mix is the more useful routing tool. Verify level and control behavior in either case.
Should you use direct outs or aux sends for multitrack recording?
Direct outs are a common way to deliver separate tracks when channel count and tap points fit the recording plan. An aux bus produces a mix, not separate source tracks. A split may provide greater independence from FOH changes.
Is a direct out always pre-fader?
No. The pickoff can be configurable or fixed at a different point, depending on the console. Confirm the manual and test whether the channel fader, processing, and mute affect the actual output.
How do you test a mixer direct out?
Patch one known source to its receiving input, listen or record there, then change one console control at a time. Verify gain, processing, mute, fader, scene, and output patch behavior and document the result.
Name the feed before the patch
Build one current Rider with Techrider.live so every channel feed, aux mix, receiving input, and responsible operator can be checked against the same plan.
Last updated: 2026-09-22 · Reviewed against Yamaha aux-routing and direct-output documentation.
Related guides
What Is a Stage Plot? (And How to Read One)
A stage plot is a top-down map of your band's stage setup. Learn what goes on it, how it differs from an input list and tech rider, and what makes one engineer-readable.
6 min readBasicsWhat Is a Tech Rider? (Sections Explained)
A tech rider is the full technical package a band sends a venue — console, monitors, PA, backline, power, stage plot, input list, hospitality. Learn every section.
7 min readBasicsStage Plot Symbols & Legend Explained
A visual glossary of stage plot symbols — mics, DI boxes, wedges, IEM packs, drums, amps, keys, power drops. Learn what each icon means and how to read any stage plot.
7 min read