Renoise beginners - Ducking

this is how i duck :slight_smile:

Thnx! But I use send channel for trigger its give me more freedom.

Also keep in mind that the current signal follower is not very time accurate. So it is quite hard to exactly duck a bass, even using lookahead. You would have to set the signal follower to attack = 0, and here the signal follower usually starts to produce crackles (which is a pity and could be avoided with a better algorithm IMO, e .g. adding a hold parameter, compare with gate device behaviour). So even dblue usually uses a keytracker + LFO custom curve + gainer instead - which of course won’t react dynamically on volumes. Maybe you could then control the amount of ducking using a signal follower again :blink:

Also keep in mind that the current signal follower is not very time accurate. So it is quite hard to exactly duck a bass, even using lookahead. You would have to set the signal follower to attack = 0, and here the signal follower usually starts to produce crackles (which is a pity and could be avoided with a better algorithm IMO, e .g. adding a hold parameter, compare with gate device behaviour). So even dblue usually uses a keytracker + LFO custom curve + gainer instead - which of course won’t react dynamically on volumes. Maybe you could then control the amount of ducking using a signal follower again :blink:

I use this method since 2010/ i did not see any clicking\flicking\crackling on my channels. I link signal follower to the LFO controller and curve it.
If your source sample is clean=no crackles will be produced .
I think that nobody needs that nuclear stage time accurate to sidechaine some sounds/ even 0.01 ms is acceptable

this is how i duck :slight_smile:

https://www.youtube.com/watch?v=OkWrS639QG4&t=9s

This hydra method is cool man . I think i can link many parameters and sidechaine them at once, instead of making a lots of costumed LFO controllers and so on ))))))
I will test it soon !

Thnx! But I use send channel for trigger its give me more freedom.

Мне с обложки показалось, что видео от Навального)) лол

thanks guys for taking a time …and watch the video

please remember that i’m not claiming this to be the best method…i just like the way it sounds…

one of the most important …aspects its the sound…you use to trigger the signal follower…a lot of people think that they can use…any sound …hoping the device can do the rest…

you need to set a short click 30ms top…

so the release time…doesnt affect to the sounds thats been ducked …and it recovers …faster…specially for supersaw chords …and stuff like that…

also the …attack issue that @ffx describes…maybe if you try and use the scaling curves in either the hydra or the signal follower…it would output a better response…

but again …i have no much insight…in the…topic … i almost all of the time…use this method with pretty good results :slight_smile:

Thnx! But I use send channel for trigger its give me more freedom.

bro …the sends ?

explain bro :slight_smile:

I use this method since 2010/ i did not see any clicking\flicking\crackling on my channels. I link signal follower to the LFO controller and curve it.
If your source sample is clean=no crackles will be produced .
I think that nobody needs that nuclear stage time accurate to sidechaine some sounds/ even 0.01 ms is acceptable

If you use a LFO custom curve, of course it is accurate. I was referring to signal follower + gain or eq. Then the delay is more than <1ms, it varies up to 10ms, depending on the trigger sound. Set the attack of the signal follower to 0, then modulate a sine sound. Then you will hear the crackling (or at least imprecision due the fact that the gainer and eq use smoothing inertia themselves). If there was a hold parameter, the algorithm could ignore retriggers for the duration of the hold phase, which would lead into assumingly much better results. The best of course was a compressor capable of sidechain + capable of attack 0 + lookahead, just like you can precisely do in Bitwig now.

Of course the precision is very important when it comes to mixing, e.g. a bassdrum + bass inaccurately ducked will lead into bass transients. And just limiting it away like it is common in the Renoise demo tracks is not a proper solution for this - of course only if you want to reach a really precise quality. Proper ducking is superior to limiting.

Of course the precision is very important when it comes to mixing, e.g. a bassdrum + bass inaccurately ducked will lead into bass transients. And just limiting it away like it is common in the Renoise demo tracks is not a proper solution for this - of course only if you want to reach a really precise quality. Proper ducking is superior to limiting.

I used the Signal follower’s method also. It is cool " You can check my demo song in renoise : Medievil-Music_Access wd " there is no clicking\crackling in it :slight_smile:
Again, it depends on your source samples. If they are clean, all will be okay with the ducking output.

im posting shit in this forum till i reach this member title

Composes without Wires burns Directly from Brain to DVD that is already in Store Member

bro …the sends ?

explain bro :slight_smile:

a bit messy …but it seems that it works for you :slight_smile:

cool cool cool :slight_smile:

im posting shit in this forum till i reach this member title

Composes without Wires burns Directly from Brain to DVD that is already in Store Member

You’re almost there… Only 2816 more posts to go!

even dblue usually uses a keytracker + LFO custom curve + gainer instead - which of course won’t react dynamically on volumes

My personal preference for using the LFO method has less to do with the timing or accuracy of the Signal Follower itself, and more to do with being a bit of a control freak who wants a more precise and reliable envelope shape to work with.

If I’ve set up the ducking in a particular way and I like the way it sounds, then I know it will always sound that way later because the LFO is doing exactly what I intended it to do.

On the other hand, if I’m ducking with a Signal Follower it can be incredibly sensitive to small variations in the input sound, requiring some careful fiddling around with the sensitivity level, attack, hold, etc.

If I decide to change my kick drum sample later, or tune it differently, or alter its duration, or boost the EQ a bit, or whatever… it often changes the feel of the ducking effect quite noticeably.

I simply find that to be quite annoying, so I prefer the reliability of the good ol’ LFO :slight_smile:

The LFO can’t truly respond to dynamic signals, as you’ve pointed out, but you can certainly use a Velocity Tracker (and Hydra) to alter the Offset and Amplitude of the LFO based on the kick drum velocity, which in turn gives more or less ducking depending on the basic volume of the kick. A bit crude, but it works!

its safe to say that it all comes down to personal preferences :slight_smile:

at the end of the day regardless of what method its the most accurate …or the one that offers more control over the whole thing

i can rest that this is all native to Renoise …and any user can change instantly …the setup in a matter of minutes

to have a more precise control over the …sidechain/ducking…or …any other aplication this setup may have :slight_smile:

glad i did this video …this is a now a useful thread :slight_smile: thanks to all of your comments …

I get good results from the signal follower using envelope shaped dc samples as triggers. This allows even better control then LFO graphs, as the modulation envelopes have those nice time scales of beats, milliseconds next to them in the editor, and you can mix multiple triggers, even compress them, etc. The shaped dc samples go to extra tracks via track routing, then muted, they are purely triggers.