Make the VST2 SDK available #51
Comments
* The currently required version (`vstsdk368_08_11_2017_build_121.zip`) seems to have fallen off the Internet. * The latest version (`vst-sdk_3.6.14_build-24_2019-11-29.zip`) can be automatically downloaded from Steinberg's servers, however it does not contain the VST2 SDK headers needed by Airwave. * I've raised an issue on the [Steinberg VST SDK GitHub](steinbergmedia/vst3sdk#51) to make the VST2 SDK easily available. * In the meantime, I propose this fix. It's the only way I've managed to build Airwave from nixpkgs; caveat, I am yet to test it with any real Windows VSTs.
|
VST2 SDK is not anymore supported. |
|
VST2 plugins are still out there and being used, including some old ones which will never be upgraded to VST3. Feel free to mark the old version as abandoned, unsupported and generally "not your problem", but what economic sense does it make to effectively destroy years of plugin developers' work by making new hosts unable to load old plugins? I understand that this is probably a business-motivated decision, but you folks should really do the right thing and preserve the v2 SDK's availability. |
|
I understand that, in our current neoliberal climate, large organisations such as Steinberg (or even the BBC for that matter) have difficulties accommodating issues of digital preservation, but the consensus in the software engineering community is that "old" platforms that don't make sense to maintain anymore are best left in the hands of the community of developers and creators who make use of them - not just erased from history as if they were suddenly worthless. Making technologies of historical interest such as VST2 available to the public would elevate Steinberg as a company that is a responsible steward to the software ecosystem that you have sparked. |
|
#1 rule of a platform is: don't change. in my view, as soon as your platform becomes used for other people to build things on - you should no longer have domain over it. applications yes, platforms no. no company can scale to accommodate the world. |
|
It's not even an "platform", it's an API. It's like saying browsers are not allowed to implement HTTP because we now have HTTP2. |
|
@dromer It's more like being unable to implement HTTP because one morning someone at Google decides, "hey, the Internet is HTTP2-only as of today", and magically deletes all copies of the old API spec from the Internet. It's also similar to deprecating acoustic guitars in favour of going all-electric. Since @steinbergmedia is probably not up to as much scrutiny as SV tech giants, and thus less likely to be as feedback-oriented, right now they can easily get away with such "magical" business decisions. After all, Virtual Studio Technology a proprietary ecosystem. Given sufficient time, the community can reverse engineer anything. In the future, one would hope right-to-repair laws would cover cases like this, in the interest of digital preservation. @steinbergmedia how soon until I need to maintain an extra PC with an old DAW to support the old VST2 plugins that take part in my signature sound? I don't know, maybe I'm not expected to be that consistent as an artist? Please publish the VST2 spec again and license it to the community. If necessary, we'll provide our own implementations. I also can't help but wonder if this is just another ripple of the win10/macos11 wave of deprecation, similar to the dumping of 1394 cards on the market once driver support was dropped for gear with perfectly fine converters. |
|
@egasimus there is already a reverse engineered VST2 header since 2006 called VeSTige. It allows you to build a to-spec VST2 plugin. It doesn't have any of the SDK features of course, but that's not really the point here (the SDK is probably the worst part about all of VST*, that and being completely closed to any revisions). You can find examples of projects using vestige all over the place https://github.com/x42/lv2vst/blob/master/include/vestige.h |
|
@dromer Nice! Perhaps I should redirect my efforts to porting Airwave to use VeSTige. |
|
Yeah I didn't know anything about this either. Awesomeeeee
…On Fri, Feb 26, 2021, 1:00 AM Adam Avramov ***@***.***> wrote:
@dromer <https://github.com/dromer> Nice! Perhaps I should redirect my
efforts to porting Airwave to use VeSTige.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ3Q245TR3ZOESGKF3UT4DTAY3UVANCNFSM4LGALG3A>
.
|
|
The HTTP vs HTTP2 argument is pretty solid. |
|
@anton-danielsson use |
|
F-U, Steinberg, nobody liked what you guys did! |
|
They may try to erase it.. but the internet always remembers...
|
Hi folks,
I'm trying to build the Airwave VST bridge under NixOS. Currently, this requires a download of a 90MB archive and manual interference with NixOS's mostly automated build workflow just to fetch 136K of SDK code.
Would it possible to make the VST2 SDK available on GitHub as a separate repo? This would make certail users' lives a lot easier.
Cheers
The text was updated successfully, but these errors were encountered: