3 ms·
Steinberg discontinued and took down the VST2 SDK, but many if not most existing VST plugins are VST2 only (and many are too old to ever see an upgrade). The VS
by spacechild1 6y ago
Steinberg discontinued and took down the VST2 SDK, but many if not most existing VST plugins are VST2 only (and many are too old to ever see an upgrade). The VST3 SDK is definitely not easy to work with and not backwards compatible with the VST2 SDK.
- junon 6y agoWow really? Been a minute since I've looked last. I'm surprised they did that, VST3 isn't as ubiquitous as I think they'd like it to be. But since when has that stopped Steinberg from making a poor design decision lol I'm sure you can find a copy of the vst2 sdk somewhere on GitHub if you can look hard enough for it.
- spacechild1 6y agoIt's really infuriating because it effectively means that new DAWs or other other apps can't host VST2 plugins unless the developer happens to have a license and a copy of the SDK (Steinberg doesn't issue any VST2 licenses anymore!). Considering how many VST2 plugins there are which will never see an upgrade, this is really an unfair disadvantage. Of course, Cubase will be the last one to drop VST2 support... Some people have rewritten/reverse-engineered the VST2 headers. Steinberg claims this is illegal, but I'm not sure this would hold up in court. Finally, the whole VST2 debacle is a great example of why people shouldn't put all their trust in a single company and why industry standards need to be open!
- deleted 6y ago[deleted]
- spacechild1 6y ago> I'm sure you can find a copy of the vst2 sdk somewhere on GitHub if you can look hard enough for it. A simple Google search will do :-)