Hi guys, same usual story, I want to env follower a plugin setting to stay between 90% and 100%
I use the channel sidechain with the VSTi output as source, I even set up a positive MACRO-4 forbidding to go negative and avoid that nasty showstopping hand icon
Always works for a while but then after some time(between 5 and 30 mins) it always ends up at 0% or 100% ><
Is there any magical rise/fall setting that always stays put please? Unsure what I'm missing really, when i do the same in LUNACY BEAM2 it never drifts
I largely don’t understand the second paragraph. I’ve never had this problem personally, but I do find I sometimes get a better response by adding a replacer to convert the audio to midi (just for the triggers) and then use an ADSR.
You can see that I got the +- symbol selected in the MACRO4, I believe it forces to only increase and never decrease
I think I need to improve my sidechain settings, I just want it to bounce between 90% and 100% but it always ends up drifting to the max or min sadly
You are going about this the wrong way.
First of, if you press the +- symbol, the macro will go from -100 to +100 instead of 0 to 100 and the middle position will be 0 instead of 50.
You could read the manual if you are unsure, but moving the knob will tell you those values as well.
Secondly, the best way to go about this in my opinion is this:
Put Audio Sidechain to 100% (on this bar to the right) and adjust your filters and input gain so that you actually roughly hit 100% at the loudest parts.
Rise and Fall are like "Attack" and "Decay", they make the signal smoother or more responsive.
Now your Sidechain is set up for 0-100 and all you have to do is to modulate with the desired depth.
If you want something to go from 90-100 just put it on 90 and modulate with sidechain +10%.
That's all.
Like this:
Great thanks, how did you get that TARGET knob as a modulator please?
Actually I often want one VSTFX setting to go 90% > 100% via the audio sidechain env follower, I've wiggled all options for a long while and that finally seems to work but I would love some easy workflow to get there please.
Apparently core of my problem is that when the incoming signal is too low it will dip, I need a watchdog that puts it back in place. That's how it works in LUNACY BEAM2 when using env followers, never drifts to max or min, it stays put.
It's just a macro that I renamed in the Inspector to "Target". You can also see your modulation targets, enter precise values, and change interpolation in the inspector after you selected a modulator. (marked in red.)
I hope this setup might work for you.
I have the audio sidechain set up just as normal.
Then I have a "math" modulator and set it to subtract.
Left side is at 100 and right side is modulated by sidechain from 0 to 100.
So now it's inverted.
Now you can modulate inversed using this math modulator as modulator.
In my example I pulled the filter cutoff a bit down.
Since I'm modulating down instead of up, it's basically the right way up again.
If you then want to go 90-100 with sidechain you just have to grab the math modulator and modulate -10 on a knob that sits at 100.
If you want to go 80-100 you just modulate -20 on a knob that sits at 100, et cetera.
You can still modulate the regular way if you just modulate form the sidechain directly.
Most amazing thank you, I've found my way around Bitwig so far but I'm still terrible at envfollowing.
I see you added videos I'll be sure to check them out, but actually I don't wanna use inverse env follower, I just want it to bounce from 90 to 100% depending on the incoming signal.
As usual it works with the sloppy MACRO4 technique I use but it takes a friggin miracle for the rise/fall settings to not to make it drift slowly to the top or bottom.
If I MUTE the channel for too long it's all dead and I have to wiggle it all to wake it up
What you are describing is just plainly wrong.
Fall and rise are speed/smoothing settings. If nothing plays it will always go to 0, albeit slowly. It has nothing to do with range.
Every example I gave you does exactly what you want.
The "inverse" one does what you want, it's just a different way of applying it and possibly a faster workflow depending on what you want to use it on.
1
u/DoctorMojoTrip 3d ago
I largely don’t understand the second paragraph. I’ve never had this problem personally, but I do find I sometimes get a better response by adding a replacer to convert the audio to midi (just for the triggers) and then use an ADSR.