Steinberg: No more VST2 Development

DSP, Plug-in and Host development discussion.
KVRer
11 posts since 5 Jun, 2011 from London

Post Wed Sep 04, 2013 3:19 am

http://www.steinberg.net/en/newsandeven ... -2504.html
Steinberg announces that it will no longer continue to develop and maintain the VST 2 software interface but focus efforts entirely on the Software Development Kit, or SDK, development of VST 3.

Steinberg's host applications, such as Cubase, Nuendo and WaveLab, will continue to support VST 2, but the SDK for VST 2 will be made unavailable by the end of this year.

The VST 3 development kit not only generates VST 3 plug-ins, but also is capable of rendering to VST 2 and AU formats.

This day came sooner than expected... :(

KVRian
1376 posts since 27 Nov, 2008 from uk

Post Wed Sep 04, 2013 3:53 am

What exactly does that mean for the user?
Massive, Serum. Diva, Repro-1, HIVE, Spire presets, Reason ReFills more! https://NewLoops.com

User avatar
KVRAF
6063 posts since 5 Jul, 2001 from Just about .... there

Post Wed Sep 04, 2013 4:12 am

faun2500 wrote:What exactly does that mean for the user?
nothing .. it's a bunch of todo about nothing. They just aren't going to add/change/fix/update that part of the SDK anymore. Someone said they were surprised to see that so soon. I'm surprised it took this long. But, devs can continue to crank out V2.x plugins as long as they want.
If you have to ask, you can't afford the answer

KVRist
231 posts since 15 Apr, 2012 from Toronto, ON

Post Wed Sep 04, 2013 4:58 am

SJ_Digriz wrote:
faun2500 wrote:What exactly does that mean for the user?
nothing .. it's a bunch of todo about nothing. They just aren't going to add/change/fix/update that part of the SDK anymore. Someone said they were surprised to see that so soon. I'm surprised it took this long. But, devs can continue to crank out V2.x plugins as long as they want.
We technically can, yes, but according to Steinberg, Cubase and their other hosts will stop loading VST 2 plug-ins "someday". Who knows when other hosts will follow suit. As such, adopting VST 3 for new plug-ins might be the prudent course of action..

KVRian
522 posts since 19 Jul, 2007 from Netherlands

Post Wed Sep 04, 2013 4:59 am

It simply means that you should download the VST 2.4 SDK while you still can and hang onto it (backup etc).
Grtx, Marc Jacobi.
VST.NET | MIDI.NET

Pick Me Pick me!
8929 posts since 12 Mar, 2002 from a state of confusion

Post Wed Sep 04, 2013 4:59 am

But it also states the v2 SDK is being made unavailable by the end of the year which means they are (attempting to) pushing developers towards v3. I guess the v3 adoption rate wasn't going fast enough for them..

KVRian
522 posts since 19 Jul, 2007 from Netherlands

Post Wed Sep 04, 2013 6:28 am

Yes, count on Steinberg host's to ditch the 2.4 plugin shortly after that. But there are a lot of other hosts out there, some not even supporting VST 3 at this time...
Grtx, Marc Jacobi.
VST.NET | MIDI.NET

KVRAF
3344 posts since 29 May, 2001 from New York, NY

Post Wed Sep 04, 2013 10:16 am

and probably they will only release vst3 versions of their plugins, so if you are writing a host, you will need to support vst3.

User avatar
KVRAF
21436 posts since 7 Jan, 2009 from Croatia

Post Wed Sep 04, 2013 10:18 am

Well, HALion 5 is both VST3 and VST2...

KVRist
128 posts since 15 Aug, 2012 from Western Australia

Post Wed Sep 04, 2013 5:54 pm

VST3 has been around for five years. Developers seemed to prefer VST2.4 because it has wider support from hosts, and because there is more information available.

But actually, VST3 can render to VST2 (and AU!), and the documentation is actually useful, unlike VST2.4. Most hosts do seem to support VST3 now anyway.

KVRer
10 posts since 29 Jun, 2013 from Seattle

Post Wed Sep 04, 2013 11:06 pm

Unavailable! I get that they want to push devs towards v3, but as a new dev, I found the documentation to be very tricky and incomplete, for v2 or v3. There was no offical Getting Started guide, or hello world example.
<geekygenius/>

Banned
6657 posts since 10 Oct, 2005 from Toronto, Canada

Post Thu Sep 05, 2013 3:33 am

Ninja_Edit wrote:VST3 has been around for five years. Developers seemed to prefer VST2.4 because it has wider support from hosts, and because there is more information available.

But actually, VST3 can render to VST2 (and AU!), and the documentation is actually useful, unlike VST2.4. Most hosts do seem to support VST3 now anyway.
They SAY it can make VST2s, but last I heard all developers who are trying to do this are still having crash bugs. Don't believe the hype. (If anyone is using the VST 3.x SDK to make stable VST 2.4s, please correct me.)

Yes, the only real issue is that there won't be any strictly legal way for newcomers to get a copy of the VST 2.4 SDK after year end. Leave it to Steinberg to try to force people into adoption of their stillborn abortion, VST 3.x by removing "support" for a single file download. Disgusting!

If they want to not be assholes, they should release it into the public domain. (I wouldn't hold my breath waiting on THAT one! They are doing this with the specific intention of strong-arming people into using VST 3. Arne admitted as much on the VST email list.)

:x
Last edited by AdmiralQuality on Thu Sep 05, 2013 3:40 am, edited 1 time in total.

Banned
6657 posts since 10 Oct, 2005 from Toronto, Canada

Post Thu Sep 05, 2013 3:38 am

geekygenius wrote:Unavailable! I get that they want to push devs towards v3, but as a new dev, I found the documentation to be very tricky and incomplete, for v2 or v3. There was no offical Getting Started guide, or hello world example.
It came out half baked and didn't work, thus the near zero adoption. And without developer adoption, the bugs never get worked out. A classic chicken/egg problem. Steinberg want us to do their due diligence FOR them, discover, and solve all their bugs. So even now, 5 or 6 years after its release, it's still, from what I'm hearing, an unstable mess with far more problems than it's worth.

And the whole justification for the unnecessary complexity of VST 3.x was that they wanted to allow the GUI and the process to run on different machines. 6 years later, WHO is doing that? WHO even has a product that supports it? What HOST do I use for that? AFAIK anyone who's tried has run into the same old brick wall that this stuff is nothing more than a bill of goods and doesn't actually do what Steinberg say it does.

User avatar
Urs
u-he
25550 posts since 8 Aug, 2002 from Berlin

Post Thu Sep 05, 2013 3:49 am

AdmiralQuality wrote:Yes, the only real issue is that there won't be any strictly legal way for newcomers to get a copy of the VST 2.4 SDK after year end.
They also won't sign the license agreement I guess, and we can't register VST2 Unique IDs anymore. Not sure if anyone has done any of those two things in recent years.

Banned
6657 posts since 10 Oct, 2005 from Toronto, Canada

Post Thu Sep 05, 2013 3:55 am

Urs wrote:
AdmiralQuality wrote:Yes, the only real issue is that there won't be any strictly legal way for newcomers to get a copy of the VST 2.4 SDK after year end.
They also won't sign the license agreement I guess, and we can't register VST2 Unique IDs anymore. Not sure if anyone has done any of those two things in recent years.
:tu:


How's the VST 3 SDK treating you guys lately, Urs? Are you making stable VST 2.4 plug-ins with it? On both platforms? (Or I should say, all 6 platforms. Win VST x86, Win VST x64, OSX VST x86, OSX VST x64, OSX AU x86, OSX AU x64. Sigh... what our job has become in recent years. And Apple have a new OS and XCode to match coming any week now! Arrrrrrrrgh!!!)

Image

Return to “DSP and Plug-in Development”