Let the drama begin.

Work on a standard where they're not held hostage by a single vendor. It's not a realistic option but it's the only one that will sort out this mess.EnGee wrote:so what the plugins developer should do?!
People will either use the old release or backport VST3 changes, if possible, for some time yet.EnGee wrote:Half of my synths don't support VST3 but I'm still using Cubase 9 which supports VST2. Anyway, there are still hosts don't support VST3, so what the plugins developer should do?!
bollocks.We appreciate that developers and users alike gravitate strongly toward the VST 3 interface that comes with many technological advancements.
no but afaik the sdk is bloated and it is a pita to implement things like MIDI.mcbpete wrote:Weird, as the SDK has been out for a decade how come DAW developers (well, Ableton anyway) have dragged their heels so much in supporting it. Do you have to pay Steinberg to use the libraries ?
So this is really about devs - at least for now. If they removed host VST2 support it'd be a dumb move on their part. Though, in reality, even if they went that far, all that would happen is you'd get more VST3's which could host VST2's in response.Steinberg wrote:VST 2 compatibility with Steinberg VST hosts will remain
© KVR Audio, Inc. 2000-2023
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement