I have wondered why devs have fought the VST3 API for years now and in the last few months I’ve read many threads by several VST developers where they candidly admit that the VST3 API is not the clearest and most consistent they’ve encountered (surprisingly, Avid’s AAX currently holds that crown, outside of the PACE code that is…) and that often requires clever workarounds to counter the deficiencies.
The difficulty of implementing VST3 and the limited additional functionality it offers over VST2.4 are the most common complaints.
So as a customer who is VERY interested in VST3 functionality (in particular the sidechaining and multi-channel capabilities), I was wondering if Steinberg is aware of this (likely) and if they are planning to do anything about cleaning things up to make VST3 more attractive, rather than just resorting to a heavy-handed deadline approach to enforce compatibility -i.e.: announcing VST2.4 will be discontinued “soon”.
I am not a programmer, but surely the multitude of devs holding out on VST3 can’t just be a bunch of lazy programmers; the latest discussions I’ve read clearly demonstrate that devs are forced to work hard to compensate for the limitations in the API.
It does a disservice to everybody involved, customers, devs and themselves, for Steinberg not to clean up the VST3 API; as a standard creator, Steinberg bears the responsibility to make VST3 as clear and as effortless to implement as possible.