So today I was just working as normal, trying to edit and produce something before the end of the day. I had a few of my long-used Izotope and Waves plugins running. I tried adding a Waves DeEsser, then Cubase just quit. I went through a PC restart and did the same thing three times, trying to carry on working each time. On the next restart, Cubase 10 informed me it had blacklisted all my VST2 Izotope x64 plugins. I looked around online and saw some people saying to delete the blacklist XML file. I tried that, no joy. I updated all my Izoptope and Waves plugins. I installed a new Izotop plugin that I’d never had before as well. Launching Cubase it immediately blacklisted it. The thing is though, I’ve realised all my Izotope plugins still work even though they are blacklisted. If I try to rescan it makes no difference. If I try to reactivate it fails and I’m told to contact the vendor.
I checked in Wavelab Elements 9.6 x64 and it seems happy about these plugins, no problems.
So what’s this about? Cubase is blacklisting perfectly legitimate and fine plugins that it has been happy about for months and months. Nothing changed bfefore this happened. And they still seem to work. I have clients in next week and now I feel unconfident about what’s going on with the system. I see a lot of people having this kind of problem but nobody really understanding why. What does Steinberg have to say about this?
Cubase 10 10.0.20 Build 187 / Windows PRO x64