Fair question.
In my experience (since 2011) every major release of S1/SP8 has always "tightened" the bolts, added features, added quality of life features etc.
My understanding of one of these "bolt tightening" exercises - is quite obscure and rarely gets any notice but it's a thing.
It's the ongoing review and revision of the VST SDK (originally developed by Steinberg) that governs the rules in the VST engine for VST instrument and plugin operation.
Every so often (exactly how often is unknown) the dev team will perform tweaks and updates to the engine to ensure it meets current spec. While this is always a good thing long term - it can have a tendency to sometimes expose specific plugins that were not following the rules in a prior version of S1 where the spec may have been more loose and some things that a plugin might be taking liberties with in say - v7 - are now being caught in v8. Sometimes leading to unpredictable behaviors - like you are seeing
Lukas (one of our admins) mentioned this a few weeks back when V8 was just a few days old and reports started coming in about plugins. I cannot confirm this VST update HAS occurred in v8 - but based on current reporting - it seems very likely.
This is why some plugins are now acting weird (where they weren't before) and others just keep trucking along - version to version.
And yes - there may very well be some kinda of major problem with the VST Engine too - but like I mentioned in that prior post - this crew has been polishing this VST engine for decades now - can't really see them sabotaging it within v8 - just for kicks.
There were some additional tweaks in v8.01 that addressed specific plugins misbehaving - so it appears more work was done.
But I think this overall issue is VERY plugin specific rather than a major engine failure across the board.
VP
