Reverb ducking reduces the wet response while a chosen source is active, then allows it to rise as the source leaves space. A common method places a compressor after the reverb on a dedicated wet return and feeds the dry source to the compressor’s external sidechain. The sidechain controls gain reduction; it does not need to become an audible second source.
The useful result depends on detector level, threshold, ratio, timing, and routing. A synchronized release value alone is not a complete setup, and ducking does not automatically fix every spectral or tail-length problem.
Build a clear wet path
Keep the dry source on its intended route. Send it to a reverb return configured for the intended wet output, then place the compressor after that reverb. Select the source as the external detector input using the application’s actual controls.
The routing guide explains why a conventional parallel return avoids unintended dry duplication. A compressor placed on the dry track instead answers a different question unless the routing is deliberately arranged otherwise.
Verify the detector before changing settings
Check that the compressor receives the intended source and that its gain-reduction display responds when expected. If a detector-listen feature is available, use it as a diagnostic under the product’s definition, then return to normal output monitoring.
A missing or wrongly tapped trigger can make an apparently reasonable threshold ineffective. A pre- or post-fader detector source can also respond differently when the dry track is faded. Record which path was selected.
Use threshold and ratio as a defined comparison
In an ideal hard-knee static example with no makeup gain or envelope transition, a 4:1 ratio reduces 12 dB of detector level above threshold to three dB above threshold in the corresponding transfer relationship. The implied gain reduction is nine dB.
This is an arithmetic illustration, not a calibration of every plugin’s sidechain detector. Real knees, filtering, attack, release, and gain staging affect the result. Set the amount by the wet response in the phrase, not by copying an isolated threshold number.
Choose attack from the desired entrance
A faster attack can reduce wet energy promptly when the source enters. A slower one can allow some initial response through. Neither is universally correct: the source articulation, reverb onset, and intended movement matter.
The pre-delay-versus-decay guide explains another timing layer. If a long pre-delay postpones the wet response until after a short source trigger has ended, the compressor may be recovering before much reverb arrives.
Choose release from the gap
Release influences how gain reduction recovers after the detector falls back under the relevant conditions. Too much persistence can keep the wet path down through a desired gap; a rapid recovery can create an obvious swell or unstable movement.
At quarter note = 120, an eighth-note duration is 250 milliseconds. That can be a comparison reference, not a universal release prescription. Detector behavior and the actual word or note spacing determine how the envelope interacts with the music.
Keep decay and ducking separate
A long tail remains long under the effect’s design even if its output is temporarily reduced. When the compressor releases, accumulated wet energy can return. If the result still fills the next phrase, compare the source feed or decay rather than only increasing compression.
The mixing guide separates level, duration, spectrum, and arrangement. Ducking is one dynamic option, not a substitute for choosing a suitable response.
Compare ducking with gating
Ducking reduces the wet signal while the trigger is active. A conventional sidechain gate can instead open a wet path when triggered and close after its hold and release conditions. These are different envelope goals.
The gated-reverb guide explains the truncated-response effect. Do not assume that a gate preset and a compressor with an external trigger are interchangeable merely because both use a sidechain.
Shape the return without confusing the cause
A return may also need spectrum or frequency-dependent decay changes. A broadband compressor reduces the combined wet signal according to its detector; it does not automatically identify and remove one unwanted frequency region.
The EQ guide and damping guide distinguish those choices. Compare them separately so a darker, quieter, or shorter response is not credited to the wrong operation.
Apply the movement to a source-specific phrase
For a vocal, listen to word entrances and the gaps after phrases. For a pad, sustained energy may keep the detector active much longer. A drum trigger can generate a more rhythmic pattern. The source’s envelope is therefore part of the setup.
The vocal guide considers articulation and overlap. Use selective send automation as another comparison if only certain words need an expanded tail; compression need not be the only way to create movement.
Use calculator timing as a reference only
The homepage reverb calculator supplies BPM-based pre-delay and decay starts. It does not create the compressor route, select the detector, or calculate a universally appropriate threshold and release.
Keep the calculated musical division separate from actual detector timing. A numerical relationship can support an experiment, while the complete envelope must be checked in the arrangement.
Check the rendered routing
A wet stem or soloed source export can behave differently if the sidechain trigger or shared return is omitted. Define the intended path and verify that necessary control signals remain active under the application’s export behavior.
The tail export guide explains re-import checks. Listen to the rendered phrase and ending rather than assuming session playback and every stem mode are identical.
Save the dynamic context
Record the source, detector tap point, compressor position, threshold, ratio, timing, makeup gain, and any detector filtering. Keep the reverb settings with them. This article describes a workflow and ideal arithmetic, not a personal DAW test or a guarantee of clarity.
Frequently asked questions
Where does the compressor go for conventional reverb ducking?
After the reverb on the wet path, with an appropriate external trigger, when that is the intended setup.
Should the sidechain source be heard on the return?
It normally controls the detector rather than becoming a second audible input. Check the actual routing and any detector-listen mode.
What release should every vocal use?
There is no universal value. Compare recovery with the actual phrase gaps, detector level, and reverb onset.
Does ducking shorten the reverb itself?
Not automatically. It dynamically reduces the output under the chosen processing. The underlying tail can continue developing.
Why does the export lose the ducking effect?
The detector or wet path may be missing or behave differently under the selected render mode. Verify the actual routed output.
