Nope. Everything I do on VST2 gets a signed binary, Apple Silicon-native version alongside the original 'retro' version.I don’t know but I moved away from VST2 years ago. Not just because VST3 is better, but also because I always had an eye on the future, and the writing’s been on the wall for a loooong time. Not to mention, anything that isn’t VST3 also isn’t Apple Silicon anyways, so I don’t think this affects any of us on Mac that much.
And is also my preferred format for ME to work with because it's all made with 'double replacing' enabled, so the 64-bit audio buss works with Reaper, and that's my preferred choice for digital processing. In fact I worked out how to do that in Pamplejuce for future GPLed VST3 plugins and have that set up even in the meter I'm working on. Once I work out VST3's stupid and baffling messaging system that prevents me even attaching a control to the audio thread, I'll be able to do, for instance, a gain plugin that alters the audio thread.
The VST2 version is about 150k in size, pretty much bulletproof as a rule, no-fuss no-trouble.
The VST3 version (with JUCE) is close to fifty megs, and half a gigabyte of space on my hard drive. Remains to be seen if it's anything like reliable.
I would also note that it's deeply weird to see people talking about 'migration'. Do you think that somehow old mixes you need to revisit will work once you've 'migrated' plugins from one format to another, from one version to another? I keep all the old releases downloadable in their original form for a reason: I get people frantic because they've updated something or other, lost the original plugins, and have mixes that require it. I've seen it myself and I MAKE the dumb things.
It's a bit like the fire at the Universal Studios vaults in 2008, where the masters to a lot of our recorded history burned. The masters will die. Except it's arson. It's… disappointing.
Statistics: Posted by jinxtigr — Mon Mar 18, 2024 10:27 am