Use VST2 for now.

Uhe's Diva definitely is out of tune in vst3 mode... I am using vst2
 

The Arturia VST3 issue for the V Collection has been posted now 2-3 times in this forum.
 
The workaround is to uninstall and then install only the VST 2 versions of the modules.  This takes maybe 10 minutes to do.
 
The VST 2 modules SOUND IDENTICAL to the VST 3 modules, and work just fine.
 
When the issues are resolved, you can then go back and install the VST 3 modules again.
 
It is NOT a big deal, as the VST 2 synths work fabulously.
 
The current sale price for the Arturia V Collection is a GREAT deal, for a bunch of REALLY nice vintage synths, done very nicely.
 
The Moog Modular V is my favorite synth, outside of Kontakt.
 
Bob Bone
 

That's all true, but it's still a workaround. I suspect the industry has a way to go before everyone's on the same page concerning the VST3 spec.

I just downloaded the Wuzik 4000 demo VST3 and when I insert soft synth it doesn't show up on the left of a track but does show up in the SYNTH RACK when I pass midi notes to it nothing happens... :( wah waahhh....
 
checkout my touchscreen musical keyboard with SONAR X4! HA! -Shawn
 

Any real adavantage ofvusing vst 3 ?

I know what vst 3 is suppose to but the 2 mainnthing that interest me ( zero processing when no audio and gui resize) seems to be never implemented .....vst 2 here and for a long time unless Craig convices me to take the risk to go vst 3 !!!

I believe for the end user (us), there is native support for side-chaining in VST 3.
 
Other than that, I think it may be a bunch of internal stuff that might make it easier/better for developers.
 
There might possibly be some routing improvements, but I cannot tell you that I know that for sure.
 
I don't have any particular burning desire for anything other than sound, which is not different between VST 2 and VST 3, though the side-chaining seems helpful.
 
Others will likely chime in with more/better info.
 
Bob Bone
 

VST 3 will apparently offer support of individual expression per note. One can see this could have great potential but would not be easy to use.

I have not had issues with VST 3 effects but VST 3 synths have been very problematic.

VST 3 does not seem to yet be consistently implemented by vendors, as of yet, and I agree that some components seem to be a bit shaky/problematic.
 
My VST 2 Arturia components are SHINING however, as I wait for a fix for their VST 3 problems.
 
Bob Bone

robert_e_bone
...it may be a bunch of internal stuff that might make it easier/better for developers.

It's actually just the opposite: VST3 was a major PIA for developers, who almost unanimously resisted it for as long as they could.
 
There is one reason to use VST3, and that's specifically for synths or samplers that can use the note expression feature. If you don't know what that is, then you're probably not an orchestrator and you probably don't give a rat's ass about note expression. Your MIDI drum tracks don't need it, your piano libraries don't need it, and your kickass EDM pumping supersaws certainly don't need it.
 
For effect plugins, there is no benefit to VST3 over VST2.
 
So if you're experiencing problems with the VST3 version of a plugin, just uninstall it and use the VST2 version. You won't be missing out on anything.