I’ve searched the site regarding this problem but latest news was from 2021 so I thought I should report it again. Simply, putting 3rd party plugins on master bus like Ozone for a quick review for the master then disabling it messes the whole structure. Although stock Cubase plugins stay neutral when turned off but still in the chain, Plugins like Ozone still stay active although it is turned off but still in the chain. And I mean OFF not bypass as highlighted in earlier reports. So if you finish your mix thinking Ozone is disabled and and satisfied with the results and decide to delete Ozone and use anything else for mastering then you whole mix gets messed up.
Using Cubase Pro 15.0.30 on Windows 11 25H2 on Ryzen 9/32gb/Nvidia5090
I would consider double-checking it against other plugins. I’ve definitely had more problems with iZotope plugins than with other brands. I don’t have a lot of plugins, but still.
Hi there. yes I narrowed it down to Ozone. It definately keeps acting somehow at the back no matter if it is bypassed or disabled. but the odd thing is that it does not apply the exact parameters as if it was on. This is sooo dangerous. I’m uninstalling ozone and not touching it ever again. But given the fact that ON-OFF and BYPASS buttons are stock Steinberg feature shouldn’t Steinberg also have a responsibility to turn it off from the bus no matter what 3rd party plugins decide to do.
It does really and shocks me too. Finished the mix. -3db level. Applied Ozone. Tried a dummy master. brought it down to 0db. I disabled ozone and kept mixing. Then I wanted to send the mix to an engineer. Things were looking 0db still and I though it was the mix. So when I decided to delete ozone from the möaster bus. Everything went down to -12db. And because I was mixing thinking ozone was off, when it is deleted all the fake readings I was mixing against was one and vocals were too high, drums were off etc. So at the background it was actually live somehow. Uninstalling ozone for ever and not touching it again.