VST3 Eating Up DSP When Bypassed in Ableton 11?

[wce227@gmail.com]

Do any Ableton Live 11 users notice this problem? When using the newer UAD VST3 plugins, if you bypass them in Ableton it does NOT free up DSP/PGM resources. The older UAD VST2 plugins don't have this problem. With the VST2's when you bypass them in Ableton, you free up the DSP/PGM resources. (I have an Apollo Solo).

Screen record video: https://photos.app.goo.gl/fgvQhDg66TdSYBa97

UA support replied and said they can't reproducing the issue. Curious if I'm cursed or if it's indeed a bug. Let me know! Thanks,

 

[JamesNorth]

Did it really used to bypass correctly?

I’ve never known UAD plugs to completely disable DSP until you actually disabled / powered off the plugin (bypass never did it) - this is in Cubase and Studio One.

Could it be your DAW has changed how it does things?

 

[wce227@gmail.com]

Yes sir, the VST2 versions bypass correctly. (It's shown in the video link if you're interested, near the 30-second mark).

Maybe I have my verbiage mixed up when I say "bypass". I'm talking about the round yellow button in the top-left of every plug-in box in Ableton (in that bottom rack area). It's clear what I'm talking about in the short video.

 

[c3r1c]

Two things come to mind:
1. UA has a bug to fix in their VST3 implementation.
2. You've found a bug in Ableton.

REAPER had a weird issue a while back with the UAD(x) VST3 plug-ins and it took both a release from UA and Cockos to get it working correctly. It could be just on UA here, or it could be some weird combo of both interacting with each other.