Vocal Reverb Send Automation: Feed the Word, Preserve the Tail

For a phrase-ending reverb throw, automate how much of the selected word feeds the reverb. Lowering the send afterward stops or reduces new excitation while the existing tail can continue. Muting the wet return instead cuts what you hear, so the two automation moves produce different endings.

This technique gives a particular word or gap extra space without feeding every syllable equally. It is an arrangement decision rather than a fixed preset. The useful settings depend on phrase timing, consonants, routing and the following line, not just the song’s BPM.

Separate three possible automation targets

A send controls signal entering a shared effect path. A return fader controls the processed path’s output. A decay parameter changes the engine’s response according to its implementation. Automating one is not automatically equivalent to automating another.

The send-versus-insert guide explains the routing foundation. Confirm whether the send is pre-fader or post-fader and whether muting the source affects the send in your DAW. Those details can change the throw even when the visible automation curve looks identical.

Use the reverb calculator for a tempo-based timing reference. It does not edit a vocal, detect phrase boundaries or write DAW automation. Treat its values as starting points to compare with the actual performance.

Write a timeline before drawing the curve

For an original 120 BPM example, one quarter note lasts 500 milliseconds. Suppose a selected word begins at 7.50 seconds and its useful voiced portion ends at 7.90. Plan a send rise from 7.45 to 7.50, hold it through 7.90, then reduce it by 7.95.

An illustrative phrase-ending send plan
TimeSend actionPurpose
7.45–7.50 sRaise selected feedReach the intended level at the word
7.50–7.90 sHold feedExcite the response with the selected portion
7.90–7.95 sReduce feedAvoid feeding the next material
After 7.95 sLeave return audibleAllow the existing tail to continue

The fifty-millisecond transitions are chosen for the illustration, not universal anti-click settings. Some DAWs smooth automation; others expose different interpolation or parameter behavior. Listen to the actual routed result instead of assuming every ramp has the same shape.

Account for pre-delay and the next phrase

With an illustrative forty-millisecond pre-delay, input at 7.50 seconds can begin contributing to the delayed response around 7.54, depending on the engine’s onset definition. Sound fed near 7.90 may contribute around 7.94. A nominal decay should be considered after excitation, not simply from the start of the word.

The pre-delay calculator provides numerical divisions. The pre-delay-versus-decay guide explains why an onset offset and a tail duration must not be confused.

If a new vocal line begins at eight seconds, the throw may overlap it intentionally or obscure it. Shortening the source feed, changing the wet level, filtering the return or planning a fade are different solutions. Do not assume a tempo-synchronized number automatically leaves every consonant clear.

Compare automation with ducking

A sidechain ducker reduces the wet path in response to a detector signal, then releases according to its dynamics settings. Manual send automation instead follows a written timeline. The two can be combined, but they solve different control problems.

The reverb ducking guide separates detector routing from audio routing. If the vocal is muted during a stem export, its detector or send may behave differently. A source-only solo test may therefore fail to reproduce the complete arrangement.

Manual automation is useful when only one known phrase needs emphasis. Ducking can respond continuously to varying material. Neither is universally superior, and neither removes the need to inspect the next phrase and final render.

Keep articulation and gain references clear

A selected word can contain a strong sibilant or breath that excites a bright tail. Decide which part of the word should feed the effect rather than boosting the entire event blindly. Source editing, filtering and wet-level control affect different stages.

The vocal reverb guide covers articulation and arrangement context. The reverb EQ guide distinguishes shaping the input from shaping the output. Save the routing position with the curve so the result can be reproduced.

For comparison, keep the dry vocal unchanged and adjust the effect path deliberately. A louder overall result may seem more impressive without serving the line better. Document whether a level match refers to the dry signal, wet return or full mix rather than using the word “matched” without a reference.

Export the event, not just the source region

A throw can continue after the selected clip ends. Include the return and enough timeline after the word in the render. The tail export checklist explains why a clip boundary is not necessarily a musical ending.

Check the rendered file in context, especially if the handoff uses separate stems. State whether the vocal stem contains the effect or whether a shared return is delivered separately. Preventing an accidental double effect during assembly is part of a clear delivery.

Frequently asked questions

Should I automate the send or the return?

Use the send to choose what excites the effect; use the return when you intend to change or stop the audible wet output. The correct choice depends on the desired envelope.

Will lowering the send erase the existing tail?

Normally it reduces new input while the engine’s current state continues, but routing and device behavior matter. A return mute or processor bypass can behave differently, so verify the actual path.

Is a throw always a delay effect?

No. The term can describe selective feeding of delay, reverb or a combined path. State which processor receives the signal and what timing behavior you intend.

Can I set the curve entirely from BPM?

BPM provides a rhythmic reference, not the word’s actual start, consonants or phrase gap. Use the performance and arrangement to place the automation, then compare the timing reference.

Why does the throw disappear in a stem?

The export may omit a return, change solo behavior or remove a sidechain source. Check the full routing and render settings rather than assuming the source clip contains the effect.

Does this site generate the automation?

No such capability is claimed. Its timing tools provide numbers. The timeline here is a manual planning example to enter and verify in an appropriate DAW.

Scroll to Top