VST3 has been an issue since it was released - period!

I have latest versions of Cubase & Wavelab and Im having no issues with VST3 at all now, but............ as a Wavelab user it seems a bit strange that the VST3 format never worked in Wavelab before the version 9 came out!

So basic its a bit odd that VST3 works propper in a Steinberg application like Wavelab several years after it´s been released, or?

 

Who cares? I can run my DirectX plugs in my outdated WaveLab.

 

The most performance oriented new feature is the auto disable processing when there's no input.

It's not that you can't do it in VST2 (several companies did that before VST3) but with VST3 you're forced to implement that feature.

The same goes for other improvements, like side-chaining (not sure 100%).

I use VST3 versions when I can, but just because I'm lazy and I want to avoid reinstalling plugins in 10 years when there won't be VST2 anymore.
I already have my hands full reinstalling Windows...

 

Good for you!

 

I didn't want to make fun of you. Why should I? Sorry if you got that wrong.

 

DirectX plugs isnt an option in Wavelab these days!

 

It's astounding, (how) time is fleeting, madness takes its toll. But listen closley [phloopy, your turn... ]

 

From my own personal experience most (not all) VST3 plugins (3rd party) give a better cpu performance than their VST2 counterparts, it really depends on the developer.

I rarely use any EQ plugins but they have been for me a very noticeable CPU performance improvement, same working methods and results with Reverbs.

 

Last edited: May 19, 2018

Thanks to all of you for your input and special thanks to @TonyG for getting this thread back on topic. As he said, I was not looking for any description from developers as to what vst 3 does better than vst 2. I wanted a recount of your own experiences. One thing is what Steinberg tells us and another is what a particular plugin does. I thought I was alone but after reading all your responses I can say that the lack of performance gain I was experiencing seems to be normal. Again, thanks.

 

.

 

Last edited by a moderator: May 23, 2018

I wasnt offended at all No Avenger..... I just didn´t had the time for a long conversation, thats all

 

"Multiple dynamic I/Os
VST3 plug-ins are no longer limited to a fixed number of inputs and outputs. Their I/O configuration can dynamically adapt to the channel configuration they’re inserted in, meaning that any VST3 plug-in can be surround-capable with true multi-channel processing. For example, all the new VST3 plug-ins in Nuendo 4 can work in stereo-mode when inserted into a stereo channel, but switch to 6 channels when inserted into a 5.1 channel. Each audio channel is processed independently. Interaction between channels depends on the type and design of the plug-in. In addition to their flexible audio bussing capabilities, VST3 plug-ins may also offer a dedicated event bus. Typically, this is a MIDI input for control/modulation but these busses are no longer restricted to MIDI standard only. Future plug-ins may replace the common MIDI interface with alternative methods of control."


i this it will be limited to 128... what do u think?

 

Great for mixing/mastering, among other possible uses. Everything that requires/benefits more than one track.

 

Replace "VST3" with "VST2" and "host B" with "Cubase". Once you do that, your statement makes a whole lot more sense.

That's why many features of VST2, such as side-chaining, are not supported in Cubase, but are in other hosts. "Programming error" right? Or maybe deliberate to push VST3, makes you think.

Most of the time when it is the "standard itself" the plugin devs have to add a ton of hacks and this applies to VST2 too, just that it's less convoluted. I mean VST3 is even based around COM, that says everything.

Oh wait, I forgot I'm talking to people who have, literally, zero actual technical knowledge about VST3's implementation and VST2 (and mind you I'm not a fan of VST2 either, but it's the lesser of 2 evils). What's disgusting is Steinberg admitting VST3 is garbage, indirectly, because devs don't adopt it, and they want to force it on them.

Like I said, supplying a bunch of kilobyte-sized headers in a SDK of tens of megabytes in size is not exactly a "huge maintenance burden". It's completely insignificant. They do it purely to push VST3, literally no other reason.

Steinberg don't seem to get the hint of why devs are appalled by VST3. Actions speak louder than words after all. If I were them I'd be completely ashamed of myself for having thought up something so convoluted and ridiculous.

There's a thing called the "free market".

If something is good, people will use it, and devs will develop for it.

If something is trash, it will be heavily forced, marketed, etc because very few adopt it otherwise, and you'll try to kill your "competition" no matter what, despite the fact devs prefer it.

This is a big secret, I know, but once you know it, you can recognize the trash from the good out there without knowing anything else.

 

I look at your claims from the standpoint of your apparent boundless Steinberg hatred, which undoubtedly has its cause somewhere.
In 1996 Steinberg invented the VST standard. So, in your opinion, since then, this company has been forcing the other music software companies around the world to support their "convoluted and ridiculous trash". For 22 years, almost everybody uses VST technology, not because it works, but because Steinberg threatens to kill them? Wow!