KVR Audio

Synthman2000 · Post by **Synthman2000** » Thu May 17, 2018 11:05 am

It is my VST3 folder that hugely slows my Cubase boot time, each and every time. VST3 has mainly been a secondary choice for me cause I associate VST3 with negativity.

"VST 2 compatibility with Steinberg VST hosts will remain, however, we recommend to root for the latest version of VST."

Personally as long as that contnues I will use Cubase but it is difficult to see upgrading to a version of Cubase that ever drops VST2 at this time with so many developers not having a VST3 option. I have loved Cubase for decades but in the end everyone has to reconsider options, with more inconveniences comes re-evaluation.

There is simply nothing wrong with VST 2. I cannot think of a instance where I ever thought.. "I wish that was VST3 cause I need it to do X."

Software companies would do well to not confuse new as being by default better. Change for the sake of change is inconvenience for most and in the end that will cause decision making that may not be favourable. Stability, familiarity, comfort and a feeling of control for an end user should be underestimated at a company's peril.

We live in a world where change is like a religion, super fast, rarely with consultation (often to push new more costly/profitable services under the guise of "new and improved") and in so many cases not better for people. They work on the basis that if you are not in agreement you are old skool, behind the times, backwards or a luddite.

Often time consuming and causes complexity, 2 things alone that are not better.

LeVzi · Post by **LeVzi** » Thu May 17, 2018 11:40 am

Am I the only one who goes for the VST3 version of a plugin over the VST2 ?

I find them less taxing on my PC.

SLiC · Post by **SLiC** » Thu May 17, 2018 11:49 am

LeVzi wrote:Am I the only one who goes for the VST3 version of a plugin over the VST2 ?

I find them less taxing on my PC.

They should be less taxing by design (more modern optimised code base) but a lot of DAWS didn't truly embrace all the 'potential' VST3 advantages and a lot of plug ins had unstable or beta VST3 versions leading to a lot of people just not installing the VST3 version when installing....

Lots of info about the advantages of VST3 here, but in reality most users may not notice them!
https://www.steinberg.net/en/company/te ... /vst3.html

Burillo · Post by **Burillo** » Thu May 17, 2018 11:53 am

yes, except the vast majority these "advantages" were already possible in VST2, they just didn't work properly in Cubase due to its poor VST2 implementation. but hey, three must be better than two, amirite

EvilDragon · Post by **EvilDragon** » Thu May 17, 2018 11:53 am

Dasheesh wrote:I know U-he has refused to implement it because it renders thier plugs unstable.

Well, they didnt' refuse to implement it because they do have VST3 versions of a lot of their plugins now. More recently, Satin and Presswerk got an overhaul of VST3 layer in their framework and they seem to perform much better than their initial implementation.

SLiC · Post by **SLiC** » Thu May 17, 2018 11:58 am

VST 2 compatibility with Steinberg VST hosts will remain, however, we recommend to root for the latest version of VST.

Given that VST2 will continued to be supported in Cubase et al I cant really see anything changing for some time!

fluffy_little_something · Thu May 17, 2018 12:07 pm

I don't care about VST3, v2 plugins are enough for me. I have them and my DAW all backed up, so I will still be able to use them 10 or 20 years from now.

PAK · Post by **PAK** » Thu May 17, 2018 12:22 pm

Synthman2000 wrote:It is my VST3 folder that hugely slows my Cubase boot time, each and every time. VST3 has mainly been a secondary choice for me cause I associate VST3 with negativity.

Sounds more like a bad case of “the Waves”. I can’t say I’ve noticed the same issue, but I’ve had numerous problems with Cubase and how it scans before, so another issue doesn’t surprise me..

There is simply nothing wrong with VST 2. I cannot think of a instance where I ever thought.. "I wish that was VST3 cause I need it to do X.”

If you use a Steinberg host then side chain IS a pain without VST3. Arguments about how others figured it out for VST2 don’t apply, because ..err.. Steinberg.

Software companies would do well to not confuse new as being by default better. Change for the sake of change is inconvenience for most and in the end that will cause decision making that may not be favourable. Stability, familiarity, comfort and a feeling of control for an end user should be underestimated at a company's peril.

The question you’re posing is whether something is a consumer product, built to be replaced within 5 years, or a “professional” product where some people may have the disgraceful expectation that things should continue to work for longer than this, without excellent reasons to the contrary. Is “because VST3” an excellent reason? Steinberg hope so..

LeVzi wrote:Am I the only one who goes for the VST3 version of a plugin over the VST2 ?

No. Though, IMO, things only started turning a corner in the last 2 years or so. Before then installing a VST3 was like saying “give me a VST2, but with more bugs, please”. Though, even now, if I encounter problems my first thought is to try the VST2 version. More worrying is how often it fixes a problem!

Removing this stuff is like Steinberg saying “ok, now we expect you to make, y’know.. actual proper VST3 plugins." For users of their products, and VST3 hosts in general, it’s probably a good move. It creates potential headaches for developers though. The main concern, for end users, is whether going in this direction means they’re more likely to drop VST2 support from their hosts, and it’s hard to see how moving in this direction doesn’t make that more likely at some point..

Dasheesh · Post by **Dasheesh** » Thu May 17, 2018 12:31 pm

EvilDragon wrote:
Dasheesh wrote:I know U-he has refused to implement it because it renders thier plugs unstable.
Well, they didnt' refuse to implement it because they do have VST3 versions of a lot of their plugins now. More recently, Satin and Presswerk got an overhaul of VST3 layer in their framework and they seem to perform much better than their initial implementation.

It’s recomended in the install to use the vst2 version, my mistake. There is a blurb about vst3 being unstable in the install of thier instruments. Personally, if it’s an instrument I always install the vst2, but I have half a dozen vst3 effects installed.

swatwork · Post by **swatwork** » Thu May 17, 2018 12:36 pm

The VST 2 SDK hasn't been updated for years so all this announcement really amounts to is Steinberg no longer including the VST 2 source files in the VST 3 SDK download.

Obsolete236871 · Post by **Obsolete236871** » Thu May 17, 2018 12:49 pm

Weren't there a whole lot of developers who had issues with providing VST3 versions of their plugins due to technical issues, incompatibilities and stuff?

Caine123 · Post by **Caine123** » Thu May 17, 2018 1:01 pm

Ppl should realise how bad steinberg is and should not take a lead

.
Cubase feels still so clunky i wonder why it is so loved....

sinemotor · Post by **sinemotor** » Thu May 17, 2018 1:04 pm

Ok so now it's time for Ableton Live to wake up on this one.

felis · Post by **felis** » Thu May 17, 2018 1:07 pm

3 of my 4 vst collections - Steinberg Absolute, Arturia V collection, and AAS's Modelling collection all are running as vst 3's - no problems. The Waldorf stuff I've got (no collections) are vst 3 also.

The only stuff I've got that isn't vst 3 is N.I.'s Komplete. No real problems there either.

I don't think it'll make much of a difference for me.

EvilDragon · Post by **EvilDragon** » Thu May 17, 2018 1:15 pm

sinemotor wrote:Ok so now it's time for Ableton Live to wake up on this one.

Not necessarily.

Bye bye VST2