The hook
Mid-rehearsal, the worship leader turns toward the booth and taps her ear: "Can I get more of me?"
You push her fader up. The room gets louder. She shakes her head — nothing changed where she's standing. You push more. Now the congregation side is swimming in vocal, the front row is wincing, and she still can't hear herself. You're turning the only knob you know, and it's wired to the wrong room.
Here's what nobody explained: your mix doesn't feed her wedge. The console is quietly running several separate mixes at once, and the fader you keep pushing only controls one of them. This lesson is about the others: where they live, how to feed them, and the one setting (pre or post) that decides whether your faders touch them at all.
The lesson
Start with the word that unlocks the whole topic.
You've been mixing onto one bus since Level 0: the main. Here's the shift this lesson makes: the aux knobs on every channel (you met them in 0.1) are each a fader for a different mix. Aux 1 might be the worship leader's wedge. Aux 2 the bass player's. Aux 3 feeds the reverb. Each aux bus collects its own blend of every channel, has its own master level, and goes out its own output.
So the console isn't one mixer. It's a stack of mixers sharing the same inputs.
Monitors: the pre-fader mix. The worship leader's wedge mix is built from the Aux 1 knob on every channel: lots of her vocal, some keys, a little kick. Now the design decision that matters, a checkbox or button on every console: that send is set pre-fader. It taps the channel's signal before the fader.
That one checkbox resolves the hook. Pre-fader means your fader moves don't touch her mix. You can ride the vocal all service in the room, pull it during the sermon, push it for the big chorus, and her wedge stays exactly as she asked. The two rooms are decoupled. Front-of-house belongs to your faders; the stage belongs to the send knobs. When she says "more of me," the answer is her aux send on her vocal channel, and the room never hears the change.
Effects: the post-fader mix. Now the reverb, and the opposite choice. The reverb unit (built into every digital board) is fed by its own aux, but this one set post-fader, tapped after the fader. Reason: the effect should follow the mix. If you pull the vocal fader down for the sermon and the send were pre-fader, the dry voice would vanish but its reverb would keep washing through the room like a ghost. Post-fader, the reverb rides the fader with the voice: less vocal, proportionally less reverb, automatically.
The reverb's output comes back into the mix on a return (or just a spare channel). And that's the trick: the effect runs in parallel. The dry vocal goes to the main bus untouched, a copy goes to the reverb, and the wet-only return is blended underneath. Want more reverb? Push the return. The dry voice never degrades, because the effect never sat in its path.
All of it collapses into one rule worth taping to the desk: monitors pre, effects post.
Groups: one handle for many channels. Buses have a third use. Assign all eight drum channels to a group (a subgroup) instead of straight to the main, and the group's fader becomes the whole kit's volume. Balance the drums against each other once, then ride one fader all service. On digital boards you'll also meet the DCA, which looks identical but works differently: a group actually sums the audio down one path; a DCA is a remote control that grabs a set of channel faders and moves them together, with the audio still flowing through each channel individually. For "turn the drums down," both work. The differences show up later (processing, for instance: you can compress a group's summed audio; a DCA has no audio to compress). For now: group = summed audio, DCA = a hand on many faders. Either one turns the 3.2 full-board reset into a single motion.
Go deeperoptional
Pickoff points, precisely. "Pre-fader" is really a family of tap positions, and consoles let you choose within it. A send can tap pre-EQ (the raw post-preamp signal — some engineers feed in-ears this way so their channel EQ, voiced for the PA and the room, doesn't color the band's ears) or post-EQ/pre-fader (the polished but fader-independent signal, the common monitor default). Post-fader taps after both EQ and fader, and is itself usually post-mute. Mute behavior is its own fine print: on most modern desks a channel mute kills pre-fader sends too (muting a channel silences it everywhere), but some consoles and settings allow pre-fader sends to survive a mute. Test that once on your board, before the Sunday you mute a talkback channel and it stays live in every ear on stage.
Gain staging didn't stop applying. Every bus is a gain stage in the 2.2 sense. An aux path has three levels in series: the per-channel send, the aux bus master, and the powered wedge or IEM pack at the end. The corridor logic transfers exactly — sends near their nominal range, aux master near unity, amplifier doing the final lift. The classic broken monitor rig is the same disguise from 2.2 wearing new clothes: every send knob at 10% because the wedge amp is cranked, leaving no resolution on the knobs; or every send maxed to feed a wedge that's barely on, driving the bus hot. Middle of the range, every stage, nobody rescuing anybody.
Why parallel effects beat inserted ones. Patching a reverb as an insert (in series, from 3.1) forces the entire signal through the unit, and its wet/dry balance becomes a setting inside the box — one channel, one effect, one relationship. The aux/return topology instead builds one shared effect that every channel can feed by degree: a lot of send from the lead vocal, a whisper from the snare, nothing from the pastor. One processor serves the whole band, its return sits on a fader like any other source, and it can be muted instantly between songs — which is exactly what you want when the sermon starts and any lingering wash would read as haze. Serial for corrective tools (EQ, compression) that must process everything; parallel for additive ones (reverb, delay) that get blended in. That division holds from a church wedge rig to a touring festival desk.
The monitor console, implied. Follow the pre-fader idea to its endpoint: if stage mixes are independent of the FOH faders, they could be mixed by a different person on a different desk entirely — and at scale, they are. Larger productions split the mic signals to a dedicated monitor console side-stage, whose entire output is aux mixes: one per wedge, per ear pack, per side-fill. Your church board running four pre-fade auxes is the same architecture folded into one chassis and one operator. And one more door this opens: a bus that contains "everyone except yourself" — the mix-minus — is how broadcast feeds and livestream returns avoid echo. That one matters enough to get its own treatment in the livestream level (6B.1).
Remember
- A bus is a summing point: many channels in, one combined signal out. The main mix is just the bus you already knew.
- Every aux is a separate mix of the same channels, with its own sends, its own master, its own destination.
- Monitors pre, effects post. Pre-fader decouples the stage from your fader moves; post-fader makes effects follow the mix.
- Effects run in parallel: dry signal untouched, wet copy blended in on a return. More effect = push the return.
- Groups sum audio onto one fader; DCAs move many faders with one hand. Both make big mixes manageable.
Your turn
- Map your board: identify what every aux bus feeds, and label the aux masters with tape.
- Check the pre/post setting on every send that feeds a wedge or in-ear mix. Fix any monitor send that's post-fader.
- With permission during rehearsal, answer one "more me" request the right way: the musician's aux send, not the fader. Confirm the room didn't change.
- Find the reverb's send and return on your console. Pull the vocal fader down and verify the reverb dies with it — if it lingers, you've found a pre-fader effects send to fix.