Welp. I decided to upgrade from 8.5 to 9.0.1, after all.
Is it too much to ask to have a shiny new Cubase update, oh, I don’t know, simply load a project without crashing?
Every single upgrade I go through this. Not once has Cubase “just worked.”
I know, I know. It’s not Cubase, it’s a plugin. I know the drill.
Still, as the inventors of the VST spec, it would be nice to see a highly robust implementation that can load a project, even with offending plugins.
The Sentinel is the first baby step toward a true memory / thread protected approach.
I prepared so well, too.
I reorganized my project in 8.5 and bounced all the VSTis down, removed them all and moved my VSTis to another machine to trigger remotely, upgrade all my plugins to latest, removed all my 32 bit plugins and even removed some older 64-bit plugins that were long in the tooth. Sentinel only blacklisted a couple plugins, that are not used in my recent projects and I even removed those. Zero blacklisted plugins…
My 8.5 projects still won’t load
Of all the DAWs I own, Cubase is the only one that consistently fails to load my projects when upgrading.
Not a good first impression of v9, but also was not unexpected
Now the fun process of dragging off the rest of my plugins until I find the culprit(s) begins…
Honestly, the only reason I’m staying on the Cubase train at this point is because of my CMC controller modules. I love them so much. I’m too lazy to finish my Bome MIDI Translator project that will alllow it to be used in other DAWs.