Quote:
Originally Posted by Khazul
The other problem that I see with the whole VST3 thing is that Steinberg took a very long time after the Cubase 4 launch to release the VST3 SDK. Had they played 'nice' with the rest of the industry and released the VST3 SDK when C4 was released, or even put it out to beta long before then, then many other DAWs would be able to host VST3 plugins, which in turn would be a considerable incentive to plugin writers to support it.
|
Yes agreed. No question.
Steinberg wanted to have the exclusivity of being the only VST3 host for months. It looks like they thought they would be better off doing this than releasing the SDK to devs who might have released VST3 plugs before Cubase 4 was out of the door.
I can understand the competitive advantage they were looking for but I think they misjudged the relatively low level of interest in VST3.
Now they want everyone to support it but maybe there is a bit of a developer backlash to deal with now. I think Ableton and Cakewalk are looking at each other to see who bites first. Ableton might.
I have also read that VST3 is not a radical enough change from VST2.4 to even warrant the
3 tag.
I think this is possibly the biggest hassle for devs right now...they seem to have complained about a *huge* amount of work porting their plugs over to VST3 and that Steinberg did not consult 95% of devs about the changes to VST3 while they were working on it.