Plugin workflows
Reverb and delay sends vs inserts: control input and tails
Choose a shared wet return or dedicated insert, understand pre/post-fader behavior, and automate a phrase-ending delay without cutting its tail accidentally.
Use an insert for a dedicated effect within one track’s path. Use a send and return when several sources share processing or you need independent control of new effect input and the existing wet output. Trace where the send taps the source and where its return joins the mix.
By Spectraforge Audio3 min read
Published
Guide review: Captum Records and AS Mastering. AI-assisted writing and source checks. How these guides are made.
Choose the control you need
A shared return is also shared processing: its EQ or compressor receives the combined wet material. If one source makes the whole return react unhelpfully, consider a dedicated path for that source. This is a routing decision, separate from choosing reverb predelay or delay feedback tone.
Keep the return’s blend unambiguous
For a conventional parallel reverb or delay return, start wet only. Otherwise the return may add a second dry copy and change level or phase relationships. Pro-R 2 and Timeless 3 document wet-only send use. Preserve that setting during preset changes; Timeless offers a Mix lock.
On an insert, use the plugin’s internal blend when appropriate. Its mix percentage does not necessarily equal a send/return balance because gain and blend laws can differ. Judge actual contributions rather than matching the numbers.
Practise a last-note echo throw
Choose a lead phrase with a clear last note. Keep the dry balance fixed, raise the send for that note, then lower it before the next phrase. Listen to the return through the gap. Lowering a send reduces new input; lowering the return reduces the tail already coming out.
Try a separate insert version with its documented automation controls and compare the transition. Some mix, bypass and enable controls handle internal tails differently. Choose the route that gives the intended ending without an unexpected dry-level change.
Test fader changes against the send tap
A post-fader send generally follows the track fader; a pre-fader send can remain active when the dry fader falls. Verify the host’s exact options with a small fader move, including pan and mute behavior if you depend on them.
- Dry and effect should fade together: check post-fader behavior and any independent return automation.
- The effect should linger as the source fades: preserve the intended return path and check its level at the end.
- You want only one note to enter the effect: automate the send or documented input control.
- You want to shorten an already sounding tail: control the wet output deliberately.
Check the paths that survive the ending
Play a fade, muted passage and song ending. Check for unintended dry signal in the return and for active return-to-return feedback. Keep feedback routes disabled unless they serve a deliberate effect.
When exporting groups or stems, confirm shared returns are included once, omitted intentionally, or delivered separately as agreed. Then listen to the actual files. The route is finished when source balance, new effect input and existing tails behave as intended.
Technical references
- Ableton Live: Return tracks and pre/post sends
- FabFilter Pro-R 2: Mix setting for send effects
- FabFilter Timeless 3: Wet-only send use and mix locking
Listening exercises are proposed practice routines. Worked examples illustrate the stated setup; they are not reports of our listening tests. Editorial process and corrections.