Help with auto duck please?

Firast off: Love the product, of it weren’t for musescore, audacity, free vst’s, synthesia, and my thrift store synthesizer I’d not be making music.

I know how to use the effect, but I’m wondering if there is an opposing effect that is the opposite of auto duck: Like, ofr example, instead of a “Duck pump” where the other track is the off beat after the kick, the track would instead go with the kick…If that makes any sense please…anyone

Moderator note: I removed your email address - partly for your own protection, you really shouldn’t post your address on open public forms like this as it will get harvested by Spambots - and secondly we cannot offer email or phone support as this is an open source project “staffed” entirely by volunteers gifting some of their spare time.

Moved to “Adding Features”.

Please be specific. Are you asking that positive Duck Amounts be allowed, so that when the volume of the control track rose above the threshold, the selected track(s) would fade up to a higher volume?


Yes absolutely, sorry to not get back to you sooner, but that would really help because a “Auto Rise” or whatnot could then make it so you could put reverb/echo on say, some random synth, then lower it down a few notches, then on the other track make a beat pattern: If the bass goes up to the beat guess what? Free wubs! Just take out the kick when you’re done.

That can be done now by using an intermediary track.

Generate a tone in a new track, and place it above the beat track. Apply Autoduck to the tone track.
Then place your synth track above the tone track - adjust the “threshold” level in Autoduck so that it picks up the changes in the tone track, and apply to the synth track.

Thank you, that works. Have a great day.

I am not completely understanding what the effect of the threshold setting is here. It seems more complex than stated in the Manual:

The level (default: -30 dB) used for detecting a signal in the control track.

I have a “tone” where the loud bits are at -4.4 dB and the quiet bits (length at least 0.12s) at -26.4 dB after applying a “Pluck” control track (plucks at 1s intervals) to the “tone” (duck of -22 dB).

The “synth” is at -14 dB.

AutoDuck max pause is at 0.05s, outer fades at 0.1s and inner fades at 0s.

When I apply the “tone” control track to the “synth”, nothing happens at threshold of -1 dB (understood), nothing happens at - 6 dB, I get the synth protruding nicely above the ducked parts at -12 dB, -18 dB and -21 dB, but at -22 dB the entire synth is faded down/up.

If I change the outer fade lengths to 0.01s then the synth still protrudes above at threshold of -29 dB threshold but is flattened at threshold of -30 dB.

Can you boil this down to how other controls interact with the threshold setting?

I’ve saved the project if needed.


I’ve not given it much thought before - I tend to set it by eye rather than a precise measurement, but it looks like it is triggered by the rms level rather than the peak level.

O.K. here’s how I did it: first I got the kick track, and the above track was the intermediate track(The tone, any loud tone will do.) Make sure to make the threshold really high, and the duck amount extreme, and clear, *NO FADE IN YET. Like, literal mute when ducking. O.K. now take the other track, and put it above the tone track: and again do the same type of auto duck (But this time use the fade in fade out technique, but only a small bit, like, .01 fade in). Afterwhich you have the track. Delete the tone track now. it is also a good technique to use a hard limiter if it’s really clippy, and what I do is reverse the track, add a pinch of reverb (With a high width), and reverse it again.