Vocalpoint
Well-known member
Are you suggesting that if you use an amazing plugin for years with excellent results, you would simply abandon it when it stops working after an update of a DAW because of the integrity of the coding? If so, you are prioritizing computer programming over audio engineering/production at that point
Yes. If that "amazing" plugin was put together poorly but somehow managed to dodge SDK checkpoints for several years but one day decides to crash my session AND I lose work because of that crash - I would of course check all angles - and no - I would not absolve SP straight away but sooner or later the culprit will be revealed and there is a very high likelihood - it won't end up being the DAW.
I have been an S1 user from April 2011 to today - I have used every major and minor release issued and I have documented exactly 4 crashes in that timeframe - all were due to dodgy plugins.
So after 15 straight years of usage (AND 15 years of using a finely tuned VST engine within S1/SP) - it goes without saying that I trust Studio One and will put the same trust in Studio Pro when my upgrade lands in early spring 2026. It has never let me down yet.
Plugins on the other hand - need to earn my trust. They can only do that by demonstrating stability year in and year out while passing all checkpoints and standing up to repeated and constant usage as required.
Now - does this happen often with my "go-tos?" - never that I can recall.
My only priority is the stability of the DAW (and the session that is loaded at any given time). This easily outweighs any importance of any third party plugin - regardless of how good it might be.
I have yet to install v8 but look forward to seeing if any of my standard stalwarts fail a nicely tightened and refreshed VST SDK spec checkpoint.
VP
Last edited: