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

[imrae]

I may be a minority here but I do not share all this hateful altitude towards Steinberg's actions regarding VST2 forceful deprecation. Just put yourself in Steinberg's shoes and you'll see that it waited for more than 10 years for developers to adapt new API but that did not happen. What would you do?

Maybe accept their feedback and consider the possibility that VST3 is not very appealing to them?

[Topcheese]

I may be a minority here but I do not share all this hateful altitude towards Steinberg's actions regarding VST2 forceful deprecation. Just put yourself in Steinberg's shoes and you'll see that it waited for more than 10 years for developers to adapt new API but that did not happen. What would you do?

Maybe accept their feedback and consider the possibility that VST3 is not very appealing to them?

Nobody wants to be stuck in the stone age, and so it's called progress. They've reached their end-of-life so please let it die in peace. We don't need Make Audioplugins Great Again. I'm sure you can only do so much with before it's time to move on.

Some people are just stuck in their ways and just long for the good old days of VST2. Well let me tell you it's not all that great, and it has its fair share of shortcomings. Besides, they trying to run a business and not a charity!

[Vokbuz]

VST2 was not and is not obsolete

You play with semantics here. It is obsolete because lacks many modern features.

[Vertion]

I totally agree. Progress into Steinberg's control, and let your freedoms go. No need to hold on to the past, even if it worked. If it aint't broke, fix it. What works best for the developer and the community is so five minutes ago, think of the big picture. Let the good stuff go and give into corporate pressure and subversive propaganda. Who needs the joys of yesterday when tomorrow can bring greater moral depravity. Lemmings are our future, our symbol of progress, embrace it.

Consultant Specialist at
Initech, Subsidiary of INGSOC

Initech.jpeg

[Topcheese]

I totally agree. Progress into Steinberg's control, and let your freedoms go. No need to hold on to the past, even if it worked. If it aint't broke, fix it. What works best for the developer and the community is so five minutes ago, think of the big picture. Let the good stuff go and give into corporate pressure and subversive propaganda. Who needs the joys of yesterday when tomorrow can bring greater moral depravity. Lemmings are our future, our symbol of progress, embrace it.

Consultant Specialist at
Initech, Subsidiary of INGSOC

Initech.jpeg

That was indeed wax poetic, but in order for me to even come to match that level of prose, I'd have to first trap and train a pidgeon before I could send a reply. Hey, where do you live, perhaps I can send a message in a bottle like in the one song by The Police?

I'm also pretty sure that's what one Wright brother said to the other.

Newsflash: It's still not broke and you can still drive around today in a jalopy if you so choose. Quit trying to stiffle progress in the name of ignorance. go huddle in a little corner with your VST2, and let the big boys carry the rest of the world forward.

I'm afraid that's the only thing I'm beholden to is improving my life for the better. Yes mistakes will be made along the way, but I'll not stand still thinking VST2 is all there is to life.

[SLiC]

VST3 is the future, thank God for Steinberg developing this - and now is open source! Check this out...

https://www.steinberg.net/en/newsandeve ... -4165.html

We have released version 3.6.7 of our software development kit (SDK) for VST. This update comprises several new additions that will improve the overall experience when using and developing VST instruments and processors.

The SDK update includes a preview version for Linux as well as a new license model, which allows developers to create open-source VST 3 plug-ins and distribute them with VST 3 source files. CMake has been implemented to control the compilation process and the VST 3 SDK is now also available through GitHub.

About VST 3

VST 3 is a general rework of the long-serving VST Plug-in interface. It is not compatible with the older VST versions, but it includes some new features and possibilities. We have redesigned the API to make it not only far easier and more reliable for developers to work with, but have also provided completely new possibilities for Plug-ins. These include:

1. Improved Performance with the Silence Flag

Processing can optionally be applied to Plug-ins only when audio signals are present on their respective inputs, so VST 3 Plug-ins can apply their processing economically and only when it is needed.

2. Multiple Dynamic I/Os

VST 3 Plug-ins are no longer limited to a fixed number of inputs and outputs, and their I/O configuration can dynamically adapt to the channel configuration. Side-chains are also very easily realizable. This includes the possibility to deactivate unused buses after loading and even reactivate those when needed. This cleans up the mixer and further helps to reduce CPU load.

3. Sample-accurate Automation

VST 3 also features vastly improved parameter automation with sample accuracy and support for ramped automation data, allowing completely accurate and rapid parameter automation changes.
4. Logical Parameter Organization

The VST 3 Plug-in parameters are displayed in a tree structure. Parameters are grouped into sections which represent the structure of the Plug-in. Plug-ins can communicate their internal structure for the purpose of overview, but also for some associated functionality (eg. program-lists).

5. Resizeable UI Editor

VST 3 defines a way to allow resizing of the Plug-in editor by a user.

6. Mouse Over Support

The Host could ask the Plug-in which parameter is under the mouse.

7. Context Menu Support

VST 3 defines a way to allow the host to add its own entries in the Plug-in context menu of a specific parameter.

8. Channel Context Information

A VST 3 Plug-in could access some channel information where it is instantiated: name, color,...

9. Note Expression

VST 3 defines with Note Expression a new way of event controller editing. The Plug-in is able to break free from the limitations of MIDI controller events by providing access to new VST 3 controller events that circumvent the laws of MIDI and provide articulation information for each individual note (event) in a polyphonic arrangement according to its noteId.

10. 3D Support

VST 3 supports new speaker configurations like Ambisonic, Atmos, Auro 3D or 22.2.

11. Factory Concept

VST 3 Plug-in library could export multiple Plug-ins and in this way replaces the shell concept of VST 2 (kPlugCategShell).

12. Support Remote control Representation

VST 3 Plug-in can deliver a specific parameter mapping for remote controls like Nuage.

13. Others

While designing VST 3, we performed a careful analysis of the existing functionality of VST and rewrote the interfaces from scratch. In doing so, we focused a lot on providing clear interfaces and their documentation in order to avoid usage errors from the deepest possible layer. Some more features implemented specifically for developers include:

More stable technical Host/Plug-in environment
Advanced technical definition of the standard
Modular approach
Separation of UI and processing
Advanced Preset System
Multiple Plug-ins per Library
Test Host included
Automated Testing Environment
Validator (small command line Test Host) and Plug-in examples code included

[Topcheese]

I don't understand why KVR doesn't have a section just for VST2 Throwback. I mean at some point the stone-age backwards looking troglodytes are going to get in the way of the modern forward looking pioneers of today.
NOTE: All I ask is that you have a sense of humor. We can go back and forth on the technical merits all day, but at the end of that day we move on to a new one.
Yes I did try to crack a joke at their expense, but that doesn't take away from the legitimacy of their claims. I'm still down for VST2 so it's not like I'm really arguing against it. There just needs to be that point where they start to go their separate ways. That may also give Steinyberg a more visceral clue to what's going on and what they really should be doing?

[Deep Purple]

I don't understand why KVR doesn't have a section just for VST2 Throwback.

I would guess because there is a long trail of older technologies that if you create a forum for each of them you would easily double the size of the exiting list of forums.

Instead of a section, why not ask one of the mods if they can create a sticky in each of the Instrument and Effect forums and see if that flies?

[Topcheese]

I don't understand why KVR doesn't have a section just for VST2 Throwback.

I would guess because there is a long trail of older technologies that if you create a forum for each of them you would easily double the size of the exiting list of forums.

Instead of a section, why not ask one of the mods if they can create a sticky in each of the Instrument and Effect forums and see if that flies?

Thanks that sounds like a good idea. That might enable Steinberg to be able to easily see what they're missing. Technologies only die when the people let them, and the people don't want to let this one die. We support our brothers and sisters in music.

[Vertion]

I agree that if we are to use a standard for the future. It will be one that is not 10 years old and has been repeatedly rejected by developers due to its obvious shortcomings and tedious framework. Therefore, not VST3.

It will be a new open standard that no company has control over and gives the development community what it needs
.
Steinberg has shown it's true colors with it's aggressive legal posturing. There is no going back from that.

[pottering]

VST2 was not and is not obsolete

You play with semantics here. It is obsolete because lacks many modern features.

OK, let's accept the premise VST2 was obsoleted by Steinberg.

But for me, the whole point is not letting a single company like Steinberg dictate what is obsolete or not, not to let a single company arbitrarily obsolete a industry standard pretty much every one not associated with Steinberg was happy with.

By obsoleting VST2, Steinberg created a advantage for themselves, and disadvantaged direct competitors, as Steinberg sells exactly VST2 plugins and VST2 hosts.

In fact, in the VST2 market, they outright ELIMINATED future competitors.

Sure, the current ones are still there, not much Steinberg's lawyers can do with the past signed agreements.

But the newcomers are effectively eliminated from competing with Steinberg in the VST2 market (a "retro" market, if you accept the "VST2 is obsolete" premise, but a market nonetheless).

[DPhil]

Any plugin format can be eliminated to give advantages to the owner. Like AU for Apple or AAX which already is a monopol to Avid like RTAS was (btw people and devs like the change and progress there).

You can cry how unfair it is, but unless someone comes up with a another model (which has been discussed here too and is pretty much not feasible nor maintainable), these are the rules you have to play with. You want change? Then don't support Steinberg with VST3 or DAWs/plugin devs using it

[Deep Purple]

the whole point is not letting a single company like Steinberg dictate what is obsolete or not

Should it also be the case that Microsoft should not decide when they make a particular version of Windows obsolete, or Ford should not decide when they will stop producing the Crown Victoria?

If a company produces a trademarked product, they have the right to move on and produce their future products without investing further in the previous version, no?

[Dasheesh]

Has anybody mentioned it's a good business model to have the vst format work better in your daw then anybody else's? we should be on vst6 by now lol. they are just waiting for the format to work across the board and then they will change it up again.

[Vertion]

When you give a company too much power: