Solved fixes in bold.
Knew it would.
I’m sure you’ll be fine.
I have way too many plugins.
Will report back once I track down which 3rd party offender(s) it is, this time.
Every. Single. Update.
The VST framework is simply too brittle.
These “misbehaving” plugins work in a previous version and then break in a minor update (not even a major version).
It stretches the imagination as to how that is continually the fault of the 3rd party developer.
At what point will Steinberg harden their VST container?
I realize JUCE and other plugin frameworks are, at the end of the day, just libraries running in C++ and that “anything goes,” but is there really no way?
I’m starting to think they need to do something drastic, like, load the VST plugins into protected VM sandboxes, or something.
I mean, if an entire OS can run in a VM container, why can’t a plugin?
I’d take the performance hit and memory footprint overhead, if it meant retaining recall-ablity with past projects.
I have a choice now: New version of Cubase, or forever lose recall on affected past projects. What horrible decision to have to make 3 times a year.
You know, come to think about it, I don’t think I have a single Cubase project that can be recalled, except the simplest of rough draft “starter” projects.
It really is an insidious form of not having something you once had, that is tantamount to “data loss.”
I did make a bootable image backup of 8.0.10 right before I updated. So I can revert, but why bother. 8.0.10 is not a version I can live with due to the z-order bug (which appears they didn’t fix in .20, but surely will have to eventually). May as well face the project loss now.