feature request Automate Sonitus Bypass Button or FX Rack Button

[sjoens]

Sonitus plugins have been around forever now and still no way to automate them ON/OFF?  They all have a BYPASS button so can it be added to the automation list?

For instance, when using the Equalizer, I have to separate sections of a full length clip and setup 6 automation lanes for those sections.  Or put the sections on a separate track, or...

It would be simpler to automate the Sonitus BYPASS button.... or even the track FX Rack ON/OFF button.

[Amberwolf]

It *is* annoying.  I use the Sonitus MBEQ, EQ, Reverb and Delay all the time (and the others now and then), at least one of them in every project (essentially since they came with SONAR the first time, perhaps a couple decades back).   So I end up automating the band gains in the EQ, for instance, and the individual band bypasses in the MBEQ, the Mix in the reverb and the L & R Mix in the Delay (since the L/R link retardedly only affects the sliders and not external automation you have to use two separate envelopes to do it).  

In some cases it is easier to have two separate tracks (or buses) with the fx in only one, and either have clips that need fx in appropriate places in each one, or use automation on a track to send or not send to one or the other bus, etc.  Or use per-clip fx bins for certain things, though I dislike doing that as it's very difficult to remember which ones have them and I can't automate those with in-track automation that I can copy and paste around.  (a process which is difficult enough as it is, as is drawing in the envelopes to start with; though I'm sure that's improved since my version was created). 

Would save significant time if there didn't have to be workarounds like these. 

 

FWIW, I've had this issue with numerous plugins (and synths); almost nothing I have ever used has *all* the parameters I require to be automatable; it's almost always something obviously needing to be (like a bypass, or a mix, etc). 

 

My opinion is that if it has a controllable element, it should be automatable, *and* it should correctly expose the value ranges for the automation to the host, so the host correctly labels both the envelope itself, and the values displayed in tooltips/etc (rather than a name that's different than what the onscreen control shows, and values or units that are not related to those the control itself uses).