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

[Vertion]

VST3 Wrapper

vst3wrapper.jpg

[UV1]

I understand the resistance to anything new. It is normal for all of us. But, this is software. Very few things last for more than 5 years. New tools come along and replace the old ones. You have to keep learning new things to survive. In software, change is the name of the game. Get with the program or get left behind. VST3 is our new thing. Its time to embrace it.

[Vertion]

:i agree. VST3 is over 10 years old, and a massive failure Time to let go of the past and embrace LV2. Resistance is healthy when change comes along, to be expected even, but eventually we all will use an open standard. It's the future.

[Deep Purple]

[aciddose]

[EvilDragon]

Is it me or does the Danish socket look a little surprised

I LOL'd.

[Deep Purple]

Is it me or does the Danish socket look a little surprised

I LOL'd.

I've always thought that American outlets look like 8-bit game characters' faces.

[imrae]

:i agree. VST3 is over 10 years old, and a massive failure Time to let go of the past and embrace LV2. Resistance is healthy when change comes along, to be expected even, but eventually we all will use an open standard. It's the future.

This but unironically

[Vokbuz]

:i agree. VST3 is over 10 years old, and a massive failure Time to let go of the past and embrace LV2. Resistance is healthy when change comes along, to be expected even, but eventually we all will use an open standard. It's the future.

LV2 is over 10 years old too. Is it also a massive failure?

[imrae]

[Vertion]

LV2 is over 10 years old too. Is it also a massive failure?

Yep.

So pethaps the proper advice should be, keep what works, VST2 works.

Anyone can say, let go of working X of the past, and embrace the future crappy Y. With a few pokes at the ego in the mix, " don't be scared, accept Y, let go of X", or "time to man up and pick Y".

Just follow the formula, X Is bad, Y is good, and if you are good, smart, independant, progressive and strong you will pick Y, otherwise you stink.Let go of X, embrace Y.

It's all nonsense, what works works, let it remain as such.

Regardless, no rhetoric will draw attention away from Steinberg's aggressive legal actions and posturing to control this market and everyone in it. VST2 is an interface, not a licensed software product, and their actions are vile.

[vasyan]

wrappers wrapping wrappers

"Никогда такого не было и вот опять" (c)

Oh, come on. Most VST2 implementations already uses C to <your favourite language> wrappers. VST2 SDK has C to C++ wrapper. If we put Symbiosis on top of it, here you have "wrappers wrapping wrappers". There is also C to C++ wrapper for AU.

"Опять двадцатьпять"
By the way, a pretty good, however having bugs, VST2 wrapper for Delphi/FPC is known as the Delphi ASIO & VST Package, and its advanced clone
.
You can of course tinker with creating a wrapper VST3 for Delphi/FPC yourself, but it will take a lot of useful time that will not be paid in any way. So for now, let it remain as it is. VST2 plug-ins created on Object Pascal with assembler inserts that implement DSP are not worse than those written in C++ and sometimes even faster, since they use SIMD. Not to mention the fact that the GUI in Delphi has always been more advanced (VCL/FMX GUI frameworks) than what is being done in C++.

P.S. FL Studio, for example, is compiled into Delphi, quite nimble and has a beautiful GUI, although I am not a fan of this DAW.

[aciddose]

Yes there are actually numerous VST2 compatible wrappers with minimal issues. Some of them don't contain accurate documentation because the VSTSDK also didn't, so people don't know that there are two host reserved pointers in the struct and two plug-in reserved pointers.

VST2 has some major flaws like a lack of string buffer length passed with string functions (can be fixed with simple can_do("string length") and passing in the intptr parameter!) but mostly it represents albeit "rough" the basic common ground any audio plug-in needs.

[Big Tick]

VST2 has some major flaws like a lack of string buffer length passed with string functions (can be fixed with simple can_do("string length") and passing in the intptr parameter!) but mostly it represents albeit "rough" the basic common ground any audio plug-in needs.

Yes. VST2 is brilliant that way, it can be expanded through canDo, vendorSpecific calls, and new opcodes. All the promised technical advancements of the new version could have been done with these and proper documentation.

[vasyan]

Yes. VST2 is brilliant that way, it can be expanded through canDo, vendorSpecific calls, and new opcodes.

I always have enough standard options in VST2. The only thing that had to be resorted to was storing the information in the host using chunks.