Why is Steinberg working so hard to kill off VST2 when it works so well?

DSP, Plugin and Host development discussion.
Post Reply New Topic
RELATED
PRODUCTS
VST Audio Plug-ins SDK (C++)

Post

bungle15 wrote: Thu Apr 04, 2019 10:55 am Same flamin' way that Native killed off the pro 53 :clap:
PROFIT!!!
What a terrible thing for a company to do - actually make money! You would think they had set out to be successful or something...
Sweet child in time...

Post

Hi Ben-jamin Bunny!!

Tin foil and a flux capacitor, plus an Argon Accumulator.I can then get in my flying teapot and discover the universe
You must admit the best music was 60s,70s and 80s's. After that MOOOOO moooMoo!! music and rap.
I am of course a old fart and a futurist and the old music of the 70s was far advanced of today's repetitive stuff. Bring on the mods and rockers,the bikers, hairy's and the Ozric Tentacles. Oh!!, i might need cream for the last one!! :D
At the moment Steinburg Cubase is ok with vst 2's. I am still annoyed at the pro 53 going down, but Arturia came to the rescue.
Oh well cannot stop time from galloping onwards and i am not getting any younger!! :scared:

All the best
Captain Scarlett!! :party:

Post

Deep Purple -- CLASS!!

Post

bungle15 wrote: Thu Apr 04, 2019 1:13 pm Deep Purple -- CLASS!!
yay! ball-squeezed falsettos for the win. :lol:
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

wrl wrote: Thu Apr 04, 2019 9:23 am In VST2.3, Steinberg added a constant to the VstEventTypes enum, kVstParameterType, ostensibly for transmitting sample-accurate parameter changes to a plugin. They deprecated it as of VST2.4, and the 2.4 SDK I have does not define a corresponding structure for what a VstParameterEvent would look like. Hence, we don't actually have any idea how sample accurate parameter changes would have looked in VST2 because Steinberg never actually implemented it.

That said, there was nothing preventing them from implementing it. The scaffolding is all there. They could even have done parameter ramping! There's nothing preventing it, they just didn't do it. Supporting parameter automation events certainly doesn't require throwing out all of the rest of the plugin standard.
Thanks wrl. That's exactly what I was trying to explain.

Post

Hilarious how much crying is going on. Don't support VST3 then if you don't like it. You're not forced to do so :shrug:

Post

HSum wrote: Thu Apr 04, 2019 2:25 pm Hilarious how much crying is going on. Don't support VST3 then if you don't like it. You're not forced to do so :shrug:
No, as of recently, if you want to start creating VST plugins, you are being forced to do so.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

There are other plugin formats too. You don't have to code VST. It's *your* decision.

Post

HSum wrote: Thu Apr 04, 2019 3:14 pm There are other plugin formats too.
That's outside the scope of the discussion. What's being discussed is the situation you're in if you do want to code VST plugins. Which in the plugin developer forum is pretty likely to be the case.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

HSum wrote: Thu Apr 04, 2019 2:25 pm Hilarious how much crying is going on. Don't support VST3 then if you don't like it. You're not forced to do so :shrug:
Apparently, not everyone got the memo. This is primarily a VST2 market, Steinberg is taking legal action and an aggressive legal posture to attempt to force a voluntary market to use VST3. People don't like freedoms stripped away, it's a human trait.

If on the other hand, you already knew. Translation of your statement:
I laugh at your pain and losses, if you don't like being forced and threatened, don't develop anymore VST plugins, despite all your countless hours of hard work, energy, capital investment, and time away from friends and family, to make an honest living and contribute something good to the world.
SLH - Yes, I am a woman, deal with it.

Post

Devs new to coding will get used to VST3. They don't know VST2, have no comparison and that's it. Devs already coding VST2 have a license agreement (if not, it's their fault) and can do so forever. The problem is self made.

Post

HSum wrote: Thu Apr 04, 2019 3:31 pm Devs new to coding will get used to VST3. They don't know VST2, have no comparison and that's it.
Yeah, because every reference to VST2 will have vanished for them. :roll: :idiot:
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

Why should Steinberg's actions be blamed on a developer? Steinberg must be held accountable for their actions.

VST2 was adopted in good faith, and most developers never assumed Steinberg would suddenly do something so vile. Most did not routinely check with Steinberg about this nonsense, nor should they ever have had to. The standard was adopted to be a public standard, not a controlled one. If developers had known, they would never had bother with the VST
format from the start.

Many developers are throwing out years of work as a result of Steinberg's actions. Losses are heavy for many due to Steinberg's arrogance. A trait generally frowned upon, and best avoided.
SLH - Yes, I am a woman, deal with it.

Post

Anyone coding VST2/3 knows this is a format developed by a single company, Steinberg. Anyone who's coding AU knows, this a Apple thing can suddenly be dropped anytime. Same for RTAS/AAX, MAS, NKI, whatever. Being surprised now is just naive.

Unfortunately I don't see the big complaint thread in the Steinberg forum nor any other fusion of big devs telling Steinberg that it's crap. I don't see the legal actions either taken by devs. I don't see someone building up the next, open source free available easy adaptable VST2 format maintained by a whole lot of independants.

But I see all major plugin companies already having VST3 format for years. Same for DAWs. I see the coding SDK like JUCE having it for years too without hassle.
Vertion wrote: Thu Apr 04, 2019 4:00 pmMany developers are throwing out years of work as a result of Steinberg's actions. Losses are heavy for many due to Steinberg's arrogance. A trait generally frowned upon, and best avoided.
Which losses? Can you please give me an real life example, not just pathetic thoughts?

Post

HSum wrote: Thu Apr 04, 2019 4:11 pm But I see all major plugin companies already having VST3 format for years. Same for DAWs. I see the coding SDK like JUCE having it for years too without hassle.
Ableton added vst3 support in Feb. 2019 - more than 10 years after the vst3 "standard" was published.

The truth of the matter is, VST3 was a major failure for Steinberg. It was not embraced by the industry the way VST2 was. Not by the plugin manufacturers, not by the DAW manufacturers, ... for all the reasons explained above.

Instead of accepting it as a failure and listening to the industry, Steinberg decided to force vst3 into the industry by making vst2 illegal for new developers.

Post Reply

Return to “DSP and Plugin Development”