Buses, Sends and Aux Channels in Logic Pro

A practical map of Logic Pro sends, bus routes, aux returns, subgroups, Summing Stacks and pre/post-fader behavior.

11 min read
Logic Pro mixer routing with track sends, glowing buses, aux returns, shared effects and a drum subgroup
A send controls the branch, the bus carries it, and the aux receives and processes it.

In Logic Pro, a send controls how much signal leaves a channel, a bus is the route that carries it, and an aux channel strip receives and processes that route. Use a send when you want a parallel copy, typically for reverb, delay, or parallel compression. Change the channel’s Output to a bus when the main signal path should pass through one subgroup. Existing sends remain separate routes.

This guide uses “bus” for the route and “aux” for the receiving channel strip, even though producers often use the words interchangeably in conversation.

For the full sequence from levels to the finished mix, use our Logic Pro mixing workflow. This guide covers the routing: shared effects, subgroups, and which controls affect each path.

Fast answer: click an empty Send slot, choose an unused bus, and Logic creates an aux channel for that route. Put the shared effect on the aux, set a conventional reverb or delay return fully wet, then balance each source with its send knob and the whole return with the aux fader. For a subgroup, route each source’s Output to the same bus instead of using a parallel Send.

Send, bus, aux and output: four different jobs

ObjectWhat it isQuestion it answers
SendA controllable branch from a channel stripHow much of this channel goes to the parallel route?
BusAn internal signal path identified by a bus number or nameWhich internal route carries the signal?
Aux channel stripA mixer channel that receives a bus inputWhere is the routed signal processed, balanced, and sent next?
OutputThe channel’s main destinationWhere does the main channel path go?

Apple’s channel-strip guide describes aux strips as the place for send returns, grouping, and distribution to multiple destinations. It also explains why a modern Logic project doesn’t usually show a separate “bus channel strip”: aux channel strips handle those routing functions.

Logic Pro mixer with Keys and Lead channels sending on Bus 1 and Bus 2 to reverb and delay aux strips
Blue send slots feed Bus 1 and Bus 2 while each instrument keeps its Stereo Out path, so the aux strips add reverb, delay and pitch effects in parallel.

Choose a send or change the Output

The fastest routing decision is whether the dry channel should continue on its original path.

GoalRouting moveWhy
Add shared reverb or delaySend → Bus → AuxThe dry channel remains audible while a controllable copy becomes wet.
Blend parallel compression or distortionSend → Bus → AuxThe processed return mixes beside the original.
Process all drum tracks as one kitTrack Outputs → Bus → Aux subgroupThe main drum output paths pass through the subgroup; separate sends may bypass it.
Build an alternate headphone mixPre-Fader Sends → Bus → Aux/physical outputMonitor balance can remain independent of the main mix.
Control several channels without rerouting audioVCA or Mixer GroupControl changes without creating another audio-summing path.
Organize and process tracks inside one visible parentSumming StackLogic builds the bus/aux subgroup and exposes it as the stack’s main track.

If the routing already arrives too hot, fix the source and processor handoffs with the Logic Pro gain-staging workflow instead of using an aux fader to hide upstream overload.

Build a shared reverb aux

  1. Open the Mixer with X and select the first source track.
  2. Click an empty Send slot and choose an unused bus.
  3. Find the aux channel Logic creates with that bus as its Input.
  4. Rename the aux by purpose, such as Vocal Plate, and use I/O Labels only if you want the bus name to apply across projects.
  5. Insert ChromaVerb or Space Designer on the aux.
  6. Turn the reverb’s Dry level fully down so the aux returns no direct signal. ChromaVerb and Space Designer have separate Dry and Wet controls. Leave Wet audible and adjust the effect level with the send and aux fader.
  7. Raise the source send until the amount of reverb supports the mix.
  8. Assign other tracks to the same bus and give each its own send amount.
  9. Use the aux fader to balance the complete shared return.

Why fully wet? The source channel already supplies the dry signal. If the aux reverb also returns dry audio, you add another correlated copy and change the source level before you have judged the reverb itself. Apple describes ChromaVerb’s separate Dry and Wet controls and Space Designer’s Dry-mute setting for aux returns.

Filter and shape the return after the reverb when the effect builds mud, repeats sibilance, or occupies too much space. Process the effect, not the original vocal by accident. The stock vocal-mixing guide shows this dry/aux split in a complete vocal chain.

Understand Post Pan, Post Fader and Pre Fader

The send tap point determines which later channel controls affect the branch. Apple documents three modes in the Send pop-up menu:

Send modeWhat it follows and when to use it
Post PanFader: yes. Pan: yes. Use for natural shared effects that should follow both balance and stereo placement.
Post FaderFader: yes. Pan: no. Use when effect level should follow volume while its pan position stays independent of the source pan.
Pre FaderFader: no. Pan: no. Use for independent headphone mixes, special effects, or parallel feeds that must survive source-fader moves.

For reverb sends I’d start with Post Pan, the least surprising choice: lower the source and its reverb contribution falls with it. Pan the source and the feed follows. Post Fader still follows level but taps before the pan control. Pre Fader ignores both, so pulling the source fader down can leave the effect return audible.

Choose the mode from the Send pop-up menu rather than trusting a remembered default. The knob ring gives a quick read: green for Post Pan, blue for Post Fader, and a Pre Fader send keeps the blue ring but moves its knob to the left of the Send slot. When an effect seems detached from a moving source, inspect the send mode first.

Logic Pro send menu with Bus 1 to Aux 1 checked, Post Pan selected and Post Fader highlighted
The Send menu shows the real tap point, Post Pan, Post Fader or Pre Fader, so check it rather than assuming how the send follows the fader.

Use Independent Pan when the send needs its own position

To place an effect or headphone feed differently from the source, use Independent Pan. Apple’s Independent Pan documentation explains how it works with Sends on Faders. To set it up, choose Independent Pan in the source’s Send menu, then choose Sends on Faders from that menu. Adjust the send level with the channel fader and its position with the Pan control. Turn Sends on Faders off in the Mixer when you want those controls to edit the main channel again.

Create a drum or vocal subgroup

Route each source channel’s Output to the same bus to make a subgroup. Its aux then controls the combined main output path. Existing sends on those sources can still feed other returns outside the subgroup, so lowering or muting the subgroup does not necessarily silence every effect. Trace those separate routes before relying on the subgroup as a complete mute or level control.

  1. Select the related channel strips, such as all close drum mics and overheads.
  2. Change their Output slots from Stereo Out to the same unused bus.
  3. Confirm that Logic creates or uses one aux whose Input matches that bus.
  4. Rename it Drum Subgroup rather than leaving Aux 7.
  5. Keep the aux Output routed to Stereo Out or the intended next subgroup.
  6. Add shared EQ, compression, or saturation only when the whole group needs it.
  7. Check that no source still reaches Stereo Out through an unintended duplicate route.

Apple’s mix-subgroup guide confirms this structure: multiple channels route through one bus to one aux, which provides one control and processing point for the group.

For one fader to control both drums and their reverb, use a drum-only reverb return and set that aux’s Output destination to the Drum Subgroup bus, alongside the dry drum outputs. Subgroup processing will then affect the wet return too. Keep a reverb shared with vocals outside this route. Trace the full path first, and do not send Drum Subgroup back to the bus feeding that reverb return: that would form a feedback loop. Routing, rather than the aux name, determines what belongs in a drum stem.

Summing Stack versus manual bus

A Summing Stack is Logic’s organized track-area version of an audio subgroup. When you create one, Logic routes the subtrack outputs to a bus and assigns the receiving aux to the main stack track. Apple documents that exact relationship in its Track Stacks overview. The Folder versus Summing Stack guide separates visual organization from a true shared audio path before you rebuild the routing.

Choose a Summing Stack when you want the parent and children visible together, collapsible organization, stack-level processing, and convenient automation. Choose a manual aux subgroup when tracks should stay in their existing layout, when sources are spread across different stacks, or when you need a routing layer that isn’t also an arrangement folder.

A Folder Stack is primarily organizational and doesn’t create the same summed audio-processing path. A VCA changes the level of assigned channels without summing their audio into a new aux. Those differences matter when a compressor, meter, or print route must receive the combined signal.

Build parallel compression without accidental doubling

  1. Create a send from the source or subgroup to a new bus.
  2. Insert Compressor on the receiving aux.
  3. Process the return aggressively enough to provide the intended density or sustain.
  4. Match or manage the compressor output so the return does not win solely by being louder.
  5. Start with the aux fader down and raise it under the dry signal.
  6. Check transients, low-end phase, noise, and mono translation.

The compressor itself may provide a Mix control, but a dedicated aux offers independent return EQ, automation, mute/solo, and routing. For a straightforward stock Compressor aux, set its Output-panel Mix to 100% so the return supplies the compressed signal. Blend it with the dry path using the aux fader. A lower Mix setting also passes dry signal through that return. Use it only when you intend the extra blend. The Logic Pro Compressor guide explains its Mix, Make Up and Output controls. The complete Logic Pro parallel-compression workflow shows both the plug-in Mix route and the bus-and-aux route on drums and vocals.

Create an aux track for automation

Aux and output channel strips normally appear in the Mixer, not as region tracks in the Tracks area. That’s expected. If you want to automate the return, select the aux in the Mixer and choose Options → Create Tracks for Selected Channel Strips, or press Control-T.

Apple’s signal-flow track instructions confirm that these tracks contain no regions. They expose the existing aux or output strip for automation and arrangement access. Creating that track doesn’t create a second audio return.

For effect throws, automate the source send level when only selected words or hits should feed the effect. Automate the aux fader when the whole existing return, including its tail, should move. The Logic Pro automation guide explains the safe Read, Touch, and Latch workflow.

When you’d rather not draw every move, let the return duck itself. Insert Compressor on the reverb or delay aux, then choose the dry vocal track in the Side Chain pop-up menu in the plug-in header. The vocal now controls how hard the return is compressed, so the effect pulls back on busy phrases and comes up again in the gaps. The vocal only triggers that Compressor; it isn’t processed by it.

Keep a large routing system readable

  • Name the aux by purpose: Vocal Plate, Quarter Delay, or Drum Crush is more useful than Bus 3.
  • Use Mix → I/O Labels to name bus menu entries. These labels are Logic Pro settings shared across projects. For session-specific labels, rename the aux itself. See Apple’s I/O Labels instructions.
  • Color related returns consistently without reusing the exact source color for unrelated paths.
  • Put time-based effects, parallel returns, and subgroups in predictable Mixer order.
  • Create Tracks only for auxes you need to see or automate in the Tracks area.
  • Check every aux Output if its meter moves but you cannot hear it. No Output prevents an audible return through that output path, though it can be intentional for a detector-only sidechain route.
  • Avoid routing a subgroup back into itself or into a downstream bus that returns to it.

When preparing stems or handing a project to another mixer, routing decisions determine whether shared effects, subgroup processing, and sidechain relationships survive. Use the Logic Pro stem-export checklist before assuming “all tracks” includes every aux return.

Troubleshoot buses, sends and aux channels

SymptomLikely causeFirst check
Effect makes the source much louderAux plug-in returns dry signal as well as wetSet a conventional reverb/delay return fully wet and re-balance the aux.
Aux receives no signalSend bus and aux Input do not match, send is down, or source is inactiveShift-click the send to flash its destination, then inspect the matching Input.
Effect stays audible after lowering the source faderSend is Pre FaderChange to Post Fader or Post Pan if the effect should follow source level.
Reverb does not follow source panningSend is Post Fader or independently pannedUse Post Pan or inspect Independent Pan.
Reverb disappears while recordingLow Latency Monitoring disabled the sendInspect Low Latency Monitoring mode and use Low Latency Safe only for a suitable monitoring send.
Aux is visible in Mixer but not TracksSignal-flow strips do not get tracks automaticallySelect the aux and press Control-T.
Subgroup processing seems doubledSources still reach Stereo Out beside the subgroupRoute their Outputs to the subgroup bus instead of adding parallel Sends.
Muting one return kills unrelated effectsOne return may feed another return or a shared subgroupTrace the muted aux’s Output and Sends. Sharing a bus Input alone does not make one aux fader control the others.

Logic’s Low Latency Monitoring documentation says the mode turns off sends on the focused instrument track and tracks with Input Monitoring or Record Enable active. Eligible monitoring routes can be marked Low Latency Safe. If the larger recording setup is delayed, use the Logic Pro latency troubleshooting guide.

Final routing audit

  1. Solo the source and identify every place its signal arrives.
  2. Confirm whether the route should be parallel or replace the main Output.
  3. Match each send bus to the intended aux Input. To check who else feeds that bus, choose Select Channels with Same Destination from one source’s Send pop-up menu, and Logic selects every channel strip sending there.
  4. Verify Post Pan, Post Fader, or Pre Fader behavior by moving the source fader and pan.
  5. Check every effect return for unintended dry signal.
  6. Follow subgroup and aux Outputs to Stereo Out.
  7. Test mute, solo, automation, Low Latency Monitoring mode, and export behavior.
  8. Rename the route so the next session can explain it without guessing.

More signal-flow, mixing, and delivery workflows are organized in the Logic Pro tutorials hub.

Frequently asked questions

What is the difference between a bus and an aux in Logic Pro?

A bus is the internal route; an aux is the channel strip that receives that route and provides plug-ins, a fader, pan, sends, and an output destination.

What is the difference between a send and an output?

A send creates a controllable branch while the main channel path continues. Changing Output redirects the main channel path to the selected destination; existing sends can still feed other routes.

Should reverb on an aux be 100% wet?

For a conventional parallel reverb return, yes: the source channel already supplies dry audio, so the aux should return only the effect. With ChromaVerb or Space Designer, turn Dry fully down and keep Wet audible rather than looking for one wet/dry knob. Creative routings can differ, but watch for accidental dry-signal doubling.

Should I use Post Pan, Post Fader or Pre Fader sends?

Use Post Pan when the effect should follow source volume and pan, Post Fader when it should follow volume but not source pan, and Pre Fader when the send must remain independent of both.

Why is my aux channel not visible in the Tracks area?

Auxes are signal-flow channel strips and normally live in the Mixer. Select the aux and choose Options → Create Tracks for Selected Channel Strips, or press Control-T, when you need a track for automation.

Is a Summing Stack the same as a bus?

A Summing Stack uses bus routing: subtrack outputs feed a bus whose destination aux becomes the main stack track. The stack also adds visible hierarchy, organization, and stack-level controls.

How do I delete an aux channel in Logic Pro?

Remove or redirect any sends and outputs that still use the aux, select the aux channel strip in the Mixer, and press Delete. Apple’s channel-strip instructions warn when a selected strip is assigned to a track or still receives an active bus, so confirm the exact destination before deleting it.

Can I route an aux or bus into another bus in Logic Pro?

Yes. Set the aux channel strip’s Output to the bus feeding the next subgroup. This is useful for nested routing, such as individual drum returns feeding a drum subgroup, but trace the destination first so the route cannot feed back into itself.

Why does my send effect disappear in Low Latency Mode?

Logic can disable sends on monitored or record-enabled tracks in Low Latency Monitoring mode. Check the mode and mark an appropriate monitoring send Low Latency Safe only when needed.