It seems like I'm frequently frustrated by the lack of automation basics in plugs. I'm just using the Sonitus delay for the first time and I love it. However, is there some good reason why the bypass switch is not automatable? Am I doomed to have to simulate on/off by automating the mix slider? There's a left mix and a right mix. That means that unless I have them linked, I'm going to have to set up automation lanes for both left and right mix sliders just to turn the effect on and off? 

EDIT: oh great - even if you have the L&R mix sliders linked in the plug, the automation still affects them separately. Which means I'm going to have to use two automation lanes anyway. 

I have yet to see bypass automation for anything. It sure would be nice. I use work arounds like lower the threshold for comps.

Rocky

It's ridiculous isn't it? I want to grab whomever makes these design decisions by the shoulders and shake them! When compiling a list of automation parameters, what possible reason could you have for excluding "bypass"? It's one thing I miss about the stock Pro Tools plugs, they all had automatable bypass buttons. 

I don't believe that Cakewalk has modified the features of the Sonitus plugins since they acquired them. You can put the Sonitus Delay in an FX chain. With an FX chain button you can automate a fixed left and right mix level on and off or with an FX chain knob you can automate both mix levels at the same time.

Couldn't get the FX Chain button to work properly. For some reason, it let me assign it to the right mix, but not the left mix. There is definitely something going on there. 

I could assign an FX Chain knob to both mix sliders though, so thanks for that!

Although the downside is that when automating an FX Chain knob, the scale that the automation shows is 0% - 1% shown in 0.1% increments. This of course bears no resemblance to the scale of the parameter the knob is assigned to, which in this case is 0-100% in 1% increments. 

I feel Sonar has a lot of work to do on its automation functionality. The biggest problem for me, apart from this one, is that if you're automating an effect in an FX Chain, the dropdown parameter selecter in the automation lane is not labeled with the parameter you're automating. So for instance if you're automating a parameter on a Guitar Rig effect that's in an FX Chain, the lane will be labeled "Volume" by default, and you can't change it. When you have a lot of FX Chain parameters to automate, it becomes an unmanageable nightmare because you cannot see at a glance which lanes represent which parameters. I don't understand why the Bakers couldn't have put the proper parameter labeling on the lane. The program has the name of the parameter - obviously because you've just selected it from a menu. So why not label the lane with it, or at least give the user the option to define their own lane labels. Seems like a pretty obvious feature to me. 

FWIW, I had no problem add both the LMix and RMix to a knob or button. The one thing I did notice, when automating a button using a curve other than jump, the Sonitus mix sliders would move like they were controlled with a knob rather than simply on/off like I would expect with a button.

A good work around in Sonar is to automate the switching from Setup A to Setup B which can be done easily. Simply make Setup B with no delay or wet/dry mix control fully dry. That is if you don't mind working with only one delay setup at a time.

Other possibilities:

1. If it's on a send/return loop, you can automate the send value down to -INF
2. again, on a send return, automate the volume of the return buss to -INF
3. if the delay is only on a section of your track, split the clip to isolate the section you're interested in and insert the delay as a clip effect