Blogman


A good example of needing VST3 is when using Vocal Rider (amazing btw-) It has the option to sidechain the music so that it compensates for the music getting louder whilst riding the vocal. This function is grayed out in Sonar as VST2 doesn't support sidechaining. Sucks to spend the big bucks on WAVES plugs only to find your DAW doesn't utilize the latest technology. So now we wait for VST3 support. Must Have!!

Sidechaining in VST2 has been there forever - lots of VST2 plugs have sidechaining.
It may be that there's a different implementation of sidechaining in VST3.
But that's not the same as "VST2 doesn't support it" ... it does.
 
 
Different people will have different reasons for wanting to go VST3, or trying to avoid it.
 
Each to his own I say.
 
Myself ... I'm not aware of any reason that VST3 will make a big difference for me today (either negatively or positively) ... BUT
...that could change at any moment. All it takes is someone to point something out which I was not previously aware of, and how it could be a worthwhile thing for me.
 
So at the moment, I'm in nowhere mans land - not even on the fence, it's literally a non-issue (for me) today.
 
I'll be interested to have a good nose through this thread after it's developed a bit, and see if there's anything that changes my mind at all.
 
 
I'm interested to know what/why this issue exists with "Vocal Rider".
Maybe it is to do with the VST3 sidechaining implementation ?.
 
 
Cheers - Cliff

Blogman


A good example of needing VST3 is when using Vocal Rider (amazing btw-) It has the option to sidechain the music so that it compensates for the music getting louder whilst riding the vocal. This function is grayed out in Sonar as VST2 doesn't support sidechaining. Sucks to spend the big bucks on WAVES plugs only to find your DAW doesn't utilize the latest technology. So now we wait for VST3 support. Must Have!!

Not to mention Morphoder, any Waves comp that uses sidechain, and, worst of all for me, no Waves Surround plugin capability. I'm still using 8.5.3 and the way things are looking my next purchase will be Nuendo or something but not X1 or X2. At this point I'd rather have use of the plugins I already paid for then to upgrade to a product that won't support them. I'd be hard pressed to believe there is much that can be done in the ProChannel that can't be done as well or better with the Waves plugins. Sadly, it really is a deal breaker for me at the moment.

To me the question of this fred should be:
Why no Vst 3 in X2 ?
  If Cake  upgrades this advanced DAW (X1)  ,then I think this is no question. 

panup


Which VST3 effects would you guys buy if it was supported by X2?

I have already bought Vienna Ensemble Pro 5, and straight after i jumped ship to from X1 to Cubase, because the VST2 version is cumbersome as hell. And that is the only reason i need to want VST3 support ^^ If it comes in X2, i'm coming back to Cakewalk in a jiffy.

Another reason is.. why not?

Do we even know if VST3 support isn't going to be included yet?

I bought Waves Vocal Rider and then realized that it does not work in Sonar because of lack of VST3 support.  I want it!

for what its worth they done vst3 for z3ta 2 on the mac version

What's a VST?
 
 
 
Is it still 20%?
 
 

All my waves V9 plugs work in X1 with no problems, use them all the time

bz2838


All my waves V9 plugs work in X1 with no problems, use them all the time

There are certain plugins/features which you have overlooked as already mentioned in this thread. Morphoder does not accept MIDI input. Nor the Waves Surround Plugins. The C6-Sidechain feature does not work nor the Vocal Rider. There are others. Waves have documented this on their site.
http://www.wavesupport.net/Objects/Images/Product%20Info/Supported_Hosts_Charts/V9_pc.html