KVR Audio

arakula · Post by **arakula** » Wed Mar 05, 2014 5:54 pm

chk071 wrote:I think the result would become different, if Steinberg forced VST3 further, by, say, totally removing VST2 support from Cubase or Nuendo. Which one day, if VST3 gets a bit more popular, and every developer develops VST3, couldn't be so unrealistic anymore...

Pffff, first thing to appear on the market would be a VST3->VST2 converter, presumably based on their own sample...

osiris · Post by **osiris** » Wed Mar 05, 2014 5:57 pm

Which they would have to immediately take down. Remember the whole AAX debacle....

arakula · Post by **arakula** » Wed Mar 05, 2014 5:59 pm

VST is not as closed an environment as AAX.

osiris · Post by **osiris** » Wed Mar 05, 2014 6:04 pm

Then I ask again, why not just VST v3?
At this point I have 4 different versions of some plugins.

osiris · Post by **osiris** » Wed Mar 05, 2014 6:08 pm

With separate folders for every version.
Put 32 bit here, because you can't put it with the 64 bit version but don't put it in the VST3 folder or it won't work.
Steinberg is obviously off its nut. First the ILok, now this.
It's like Betamax vs. VHS all over again.
I petition for ONE VST standard across the board. An industry standard. No BS. It would save developers a lot of headaches, and save my sanity.

trimph1 · Post by **trimph1** » Wed Mar 05, 2014 6:19 pm

I also would like there to be a standard for these things. This business of having umpteen different formats, like osiris mentioned is really making it more of an issue for file management....

Ingonator · Post by **Ingonator** » Wed Mar 05, 2014 6:23 pm

trimph1 wrote:I also would like there to be a standard for these things. This business of having umpteen different formats, like osiris mentioned is really making it more of an issue for file management....

VST 2 is alraedy a kind of standard but some DAW/host developers (e.g. Logic, ProTools) decide not to support it.

Ingo

Numanoid · Post by **Numanoid** » Wed Mar 05, 2014 6:31 pm

arkmabat wrote:I don't care about VST3 is at 61% haha

Did it take you almost three years to make up your mind about that?

hibidy · Post by **hibidy** » Wed Mar 05, 2014 9:03 pm

Finally, someone got it! (though I liked my keep calm post

)

Seriously though, I could give a rats ass. For one thing, my vst 2 plugs work just fine in studio one and I believe I get better performance out of VST 2. Live doesn't have vst 3 so it's moot.

I am personally tired of having all the different plugs on my computer. FFS, just make it all one

aciddose · Post by **aciddose** » Wed Mar 05, 2014 9:40 pm

I like having different targets (x64, win32) in different binaries and anything of that nature because it provides information and functionality that would otherwise be hidden.

Of course people will prefer to hide information that isn't important to them... Ideally we'd have something like .vst to identify which are vst plugins, and some additional compatibility to allow hosts to identify the platform.

It's all Steinberg's fault!

Nobody is prevented from adopting this change immediately though. I already do this. Renaming .dll to .vst and editing your host to search for .vst is trivial.

The x64 issue is a little more complex and requires some kludgery but it isn't excessive:
http://stackoverflow.com/questions/4952 ... t-or-64bit

Get your hosts to do this and all your problems will be solved, and stop using Cubase!

osiris · Post by **osiris** » Wed Mar 05, 2014 11:00 pm

For me it's not that simple...
The VST2 Waves plugin Element only shows up as an FX in FL. Only the VST 3 version will work....
Sorry, only the 32 bit VST3 version will work, the 64 bit VST3 version's GUI goes blackish gray if you try to touch the GUI.
Steinberg just needs to clean up its mess.
Agreed. .vst for all.

aciddose · Post by **aciddose** » Wed Mar 05, 2014 11:36 pm

the "only FX in FL" is easily hackable as well, you just need to get it to use a different ID when returning from a particular function. Alternatively the FL VST wrapper could implement a classification system where you can reclass plugins manually. This would be ideal and quite easy to implement but you're reliant on the author to implement it.

Basically a file containing plugin names and class,
waves_elements.dll = instrument

Something like that.

If that isn't the problem, it's also possible FL's VST wrapper just doesn't like something about the plugin, in which case that's the fault of the FL wrapper. Perhaps it only likes if the plugin responds to specific can_do strings or so on.

Andywanders · Post by **Andywanders** » Thu Mar 06, 2014 10:15 am

VST3 is important to me. I won't consider buying a host unless it supports VST3.

EvilDragon · Post by **EvilDragon** » Thu Mar 06, 2014 10:30 am

VST3 is completely unimportant to me. I've no need for note expression - poly AT is just fine for me.

KVR Audio

How important is VST3 support for you as a customer

How important is VST3 support for you: