Bye bye VST2

[chk071]

Steinberg has given ample warning every step of the way. They give developers a decade to adjust.

can you provide details of where Steinberg warned ahead of time it would use its contracts to actively prevent vst2 plugins being provided by third parties who had agreed to use the relevant sdks?

AFAIK, it's part of all such terms that they are subject to change. And, IIRC, the last VST2 SDK is from 2007. So, yeah, quite a long time that it's been going on, after Steinberg discontinued it.

do you never tire of missing the point? I mean, you could have actually had a go at answering the question instead of making yet another irrelevant point.

So, they discontinued VST2 15 years ago, developed the VST3 SDK in 2008 (or something), and basically told everyone that VST3 is the thing now, and VST2 will even be faded out from their DAWs, and you ask for details where they warned people ahead of time?

What more of a warning do you want? A red flashing sign nailed to your forehead?

[jamcat]

Steinberg created VST3 and discontinued VST2 decades ago because they came to view VST2 as inadequate at the very least, if not fatally flawed.

So all of their actions since need to be viewed through that lens.

[zvenx]

Indeed, the writing was on the wall..

When a plugin becomes EOL/Discontinued, I stop using it in any new projects because I know it will be only a matter of time when it will eventually be inoperable or start to give me issues that wont' be fixed.

rsp

[gaggle of hermits]

So, they discontinued VST2 15 years ago, developed the VST3 SDK in 2008 (or something), and basically told everyone that VST3 is the thing now, and VST2 will even be faded out from their DAWs, and you ask for details where they warned people ahead of time?

What more of a warning do you want? A red flashing sign nailed to your forehead?

it's incredible the way in which you wade into these discussions from a position of pure, raw ignorance. no-one (except you it seems) is arguing about whether vst2 is no longer supported in cubase.

it's them insisting on having it phased out of everything else that Steinberg doesn't sell or risk having a licence for continued vst3 support terminated.

how can you have read anything in this thread without realisi... oh wait being chk071 explains it all.

[Urs]

told everyone that VST3 is the thing now

Exactly, you just made everyone's point.

[MirkoVanHauten]

VST2 being dead for 15 years and VST3 not being the new shit everyone was waiting for, tells you all you need to know. Almost as if something was wrong with VST3 since it came up. Something that built hesitancy.

[zvenx]

Or required a lot of work to transition too.
Work cost you really couldn't relay to your customers.
rsp

[dionenoid]

Pretty bad news at least for me. The (now discontinued) Automap software by Novation works fine here with VST2 plugins but refuses to work with VST3 ones... and I really like my automapped bread and butter plugins. It allows me to make decisions more with my ears and less with my eyes. Plus the hands on approach is a always pleasure when available.

The newer Novation controllers don't need automap. For at least 10 years or so. And the latest generation directly controls anything VST3. Not only plugins but also most functions in VST3 supporting daw's.

Most of the latest gen controllers from many brands require VST3 anyway, or they offer way deeper integration with VST3. That is one of the main reasons why VST3 is so important : Hardware support.

[jamcat]

VST2 being dead for 15 years and VST3 not being the new shit everyone was waiting for, tells you all you need to know. Almost as if something was wrong with VST3 since it came up. Something that built hesitancy.

This sort of statement doesn’t become true through repetition.

The reality is that over 90% of developers had no hesitation in adopting VST3 15 years ago. It was adopted much quicker than the first iteration of VST was, which languished from 1996 until the early 2000s, with “serious” developers declaring DX as the professional plugin platform, and VST as the format for freeware hobbyists.

[MirkoVanHauten]

Can't wait for the sources & evidence of your claims. Because this sort of statement doesn’t become true through repetition.

[Audiority]

Guys, imho the problem here (at least for us developers) is not that Steinberg has deprecated a format per se or that they announced it ages ago.. but that's the WAY they decided to enforce that. Forbidding something by contract and retroactively is bad. To be honest, I don't even know if that's entirely legal but as a one-man-band I can't take the risk against a huge company like that one. The only sure thing to me, at the moment, is that CLAP will have more space in my development framework.

[jamcat]

In fact, many developers didn’t even adopt VST at all until Steinberg forced their hand by dropping DX support in Cubase 4 in 2007.

[Digivolt]

What more of a warning do you want? A red flashing sign nailed to your forehead?

Sir with all due respect, I request a neon sign

[gaggle of hermits]

The reality is that over 90% of developers had no hesitation in adopting VST3 15 years ago.

I guess if you're going to lie you might as well lie big.

that's just lolworthy.

"more than half" wouldn't look half as stupid. did you just decide to yolo it?

[zvenx]

Guys, imho the problem here (at least for us developers) is not that Steinberg has deprecated a format per se or that they announced it ages ago.. but that's the WAY they decided to enforce that. Forbidding something by contract and retroactively is bad. To be honest, I don't even know if that's entirely legal but as a one-man-band I can't take the risk against a huge company like that one. .......

This I agree with 100% well the retroactive part..always in bad taste to me, to put it mildly.
rsp