Good lord - now you have to turn on each individual low cut and high cut knob BEFORE using them on the channel inspector because they are BYPASSED BY DEFAULT?
The High- and Low-Cut Pre-Filters now use dedicated Activate/Deactivate buttons, which can be operated independently of the frequency sliders.
Knobs are fine for me - have always used them (most similar to a console) … but hey, at least you can choose, right?
Point is they are disabled by default … so now you have to enable each knob individually before you can engage the high or low cuts.
There is no global way to enable them as far as I can tell … so you have to do this to every single channel you want to use high/low cuts on … which is a lot of channels.
Ahh that looks like it’s unintentional then … (a bug?).
The rest of the bands of the EQ behave in the way you’re indicating - as soon as you engage the knob, they enable.
However, with LC and HC frequencies (in knob mode) they do NOT enable when you start using them - you have to switch it on first by a tiny little button to the top right of the knob.
I guess the change with the filters getting on/off buttons is because of an old bug where they would disengage by themselves randomly when newly loading an existing project or while mixdown when filter automation was involved. This made renders completely unreliable if you used pregain area locut/hicut and you always had to check if they are engaged or not.
But I agree the oversight/bug is that even if you activate them and save Pregain/filter area as default preset the on state doesnt get saved when you create a new track so you alwas have to engage the anew- but i doesnt interfere with my workflow too much- I always open channel editor and operate the filters from there.
Yes i agree- it would be best if they autoengaged when you move the slider/knob.
But in some way the also didnt before this change and this was the main problem- If you automated it directly from the arrange by opening an automation lane and selecting the locut automation from the list and drawing an envelope it wouldnt auto engage and pickup the automation- you had to open the channel editor and touch the locut slider and it would magicaly activate but then you saved the project and reopen it a day later and the automation again wouldnt pickup because locut maigcaly disengaged itself again. this really caused issues.
Yep I know that problem very well - when I would want to automate cuts you had to do this weird click thing to enable the access to the cut lanes in automation before you could do it.
Its a shame- the concept of channel strip in CB is great but this kind of quirks totally ruin the experience. I bought Tonebooster VCF when it came out to replace the internal LC/HC because it was so unreliable.
It’s not a bug , a little knob has been added to each of the Cuts to activate the filter , bit silly now , i know it’s only one click but with the AI knob you have to use the mouse first to click the filter on then use the CUT , why on earth ???
I think the bug is that when you start using it, it doesn’t enable itself.
The buttons being there in order to make automation work correctly is great … but it doesn’t behave the same way other EQ bands do.
These kinds of things add up over a full week of making tunes for every single track that you want to do a cut of some sort on. This is going to take some serious relearning (like the reverse zoom scroll direction did) and then you’ll have to re-un-learn it again months later!
Oh my goodness! I just checked and it’s true !!! Seriously ESTEINBERG ??? I’m going to start believing people who say that Steinberg to fix something, he DAMAGES other functions.
I would not like to abandon cubase for these things … of course the developers don’t care about that … anyway …
