Use Bus Sends for Reverb and Delay in Logic Pro
Route tracks to shared reverb and delay buses instead of inserting a new space on every channel.
A mix gets messy fast when every track has its own reverb insert. Bus sends let several tracks share one room, one delay, or one effect return while each dry track stays under control.
The mental model is simple: dry sound stays on the original channel, wet sound lives on the aux, and the send level decides how much of the track enters that space.
Quick answer
If you are in Logic Pro right now, do not start by opening every menu. Name the aux return as soon as Logic creates it. Set reverb or delay on the aux fully wet. Then move through the four checks below in order.
The order matters because mixing work usually breaks earlier than it looks. A wrong track, region, input, bus, or range can make the last setting look guilty when it is only receiving a bad setup.
Use this as the short version before reading the full guide.
- Create the send: Choose an empty send slot on the vocal or instrument channel and route it to a bus.
- Put the effect on the aux: Insert reverb or delay on the aux return.
- Blend by send level: Raise the send until the effect appears, then back off.
- Automate special moments: Delay throws and reverb lifts work best with send automation.
Before you start
- Name the aux return as soon as Logic creates it.
- Set reverb or delay on the aux fully wet.
- Start send levels lower than you think.
- Mute the aux occasionally to check whether the effect helps.
A clean pass from start to finish
Run this as one clean pass, not as disconnected tricks. Begin with the first checkpoint: create the send. Then move to the second: put the effect on the aux. Those two checks make the project readable before you make detailed changes.
After that, use the next two checkpoints as the decision stage: blend by send level, then automate special moments. This is where you stop guessing and let the screen show whether the sound, timing, routing, or edit is behaving the way the song needs.
If you change more than one thing at once, write down what you changed or save a new version. Logic Pro is fast enough that a session can go from fixed to confusing in under a minute. Small, named moves are easier to trust later.
1. Create the send
Choose an empty send slot on the vocal or instrument channel and route it to a bus. Logic creates or reveals an aux return.
Name it Vocal Verb, Slap Delay, Drum Room, or whatever the effect actually does.
2. Put the effect on the aux
Insert reverb or delay on the aux return. Since the dry signal remains on the original track, the aux effect is usually set 100 percent wet.
This makes the send level the blend control.
3. Blend by send level
Raise the send until the effect appears, then back off. Space should often be felt before it is obvious.
Use different send amounts for different tracks so they share a world without becoming equally distant.
4. Automate special moments
Delay throws and reverb lifts work best with send automation. The dry vocal stays stable while only the effect level changes.
After writing automation, clean extra points so the move remains readable.
Decision table
| Effect | Use a send when | Use an insert when |
|---|---|---|
| Reverb | Several tracks share space | One sound needs a special printed room |
| Delay | You want throws or shared repeats | Delay is part of one instrument tone |
| Parallel compression | You blend extra energy | You want normal channel control |
| Chorus | Multiple tracks need same width | Only one track needs the color |
Checkpoint table
| Checkpoint | What should be true | If it is not true |
|---|---|---|
| Create the send | Name it Vocal Verb, Slap Delay, Drum Room, or whatever the effect actually does. | Back up and fix the setup before continuing. |
| Put the effect on the aux | This makes the send level the blend control. | Do the smaller edit instead of rebuilding the whole part. |
| Blend by send level | Use different send amounts for different tracks so they share a world without becoming equally distant. | Check what is selected, then repeat the change deliberately. |
| Automate special moments | After writing automation, clean extra points so the move remains readable. | Use the mixer or playback context as the final judge. |
Before and after check
Before the change, make one short playback pass and name the exact problem in plain words: late entrance, dull vocal, wrong input, harsh consonant, missing output, messy routing, clipped bounce, or whatever the session is actually doing. If you cannot name it, you are not ready to fix it yet.
After the change, play the same section at the same volume. Louder almost always sounds better for ten seconds, so level-match when you are judging mixing decisions. The useful question is not whether the edit is impressive. It is whether the part sits better without pulling attention away from the song.
Check the edges of the fix. In Logic Pro, a repair can solve the center of a problem while damaging the bar before it, the breath after it, the bus return, or the export tail. A good before/after pass includes a little lead-in and a little space after the moment you changed.
If the after version only feels better while you are watching the screen, take a break and listen again without touching the mouse. Visual neatness is helpful for editing, but the final test is still playback. Keep the version that makes the project easier to finish.
What not to chase yet
Do not chase polish before the basic workflow is stable. For this topic, the first two checkpoints have to make sense before you worry about the smaller details: create the send, then put the effect on the aux. Fancy settings cannot rescue a confused source.
Do not copy numbers blindly from another session. Buffer sizes, EQ points, quantize strength, compression timing, send levels, and bounce choices all depend on the material. Use examples as starting points, then move the control until this project sounds and behaves correctly.
Do not keep editing because the tool is available. Logic Pro gives you enough control to over-fix almost anything. Stop when the problem is gone and the performance still feels like a performance.
What good looks like
The mixing workflow is working when you can explain what changed without pointing at a random plugin window. If the fix depends on luck, the session is not stable yet.
After the main pass, close the editor you were using and play the section from a few bars before the change. A good edit survives context. A bad edit only sounds correct when the screen is zoomed into the problem.
Keep one version before the major change and one version after it. Logic Pro projects can move quickly, and a clean fallback saves more time than trying to reverse a dozen tiny edits later.
If it still feels wrong
If the result still feels wrong, return to the signal chain. Ask whether the source is clean, whether the region edit is correct, whether the track is routed where you think it is, and whether the mixer confirms what your ears are telling you.
Do not add another processor just because the current one did not solve the issue. In Logic Pro, many problems are earlier than the plugin slot: wrong input, messy region boundaries, doubled monitoring, over-quantized MIDI, or a bus that is louder than the dry track.
When you get stuck, simplify the project. Mute everything except the source and the one track or aux it depends on. If the problem disappears, bring the session back one group at a time until the conflict shows itself.
Common mistakes to avoid
- Leaving aux reverb partially dry. Fix it by returning to the first visible control in the chain and confirming it before you touch a plugin.
- Using ten unrelated rooms in one small mix. Fix it by listening to the section in context, then changing only the thing that fails the playback test.
- Forgetting to name buses. Fix it by saving a version, making the edit smaller, and checking whether the song still feels natural.
- Making the effect louder than the source. Fix it by simplifying the session view until the routing, region, or setting is obvious again.
Practice pass
Create one short reverb and one quarter-note delay. Send the vocal to both. Then mute the auxes. If the vocal collapses without them but sounded natural with them, the routing is working.
When to move on
You are done when the change helps the song at normal listening volume. Not when the screen looks tidy, not when every meter behaves perfectly, and not when the analyzer is pretty.
Print or bounce a short reference after the fix. Listening outside the edit screen catches problems that are invisible while you are staring at regions, lanes, and meters.
Sources checked
This draft was checked against current Apple Logic Pro documentation and release notes before writing. Source links used for version-sensitive claims on May 16, 2026:
FAQ
What is a bus in Logic Pro?
A bus is an internal path used to route audio from one channel strip to another destination, often an aux.
Should reverb be on a send or insert?
For shared space, use a send. For a special sound that belongs only to one track, an insert can make sense.
What should the wet/dry setting be on aux reverb?
Usually 100 percent wet, because the dry signal stays on the original track.
Can I automate send levels?
Yes. Send automation is a clean way to create delay throws and reverb lifts.
