Noel Borthwick [Cakewalk
]

If vst3 does not consume CPU when no signal present that's really smart. I know another DAW that lets you automate bypass of effects to eliminate unnecessary CPU consumption. That always made sense to me. If in fact that's how Vst3 functions automatically that would seem like number 1 priority in any DAW.

All cakewalk products have had this functionality since the 90's. Our DX sdk had an IDeferZeroFill interface that Ron thought of way back then. If anything I think this capability in VST3 came from there :) Additionally SONAR has always optimized to not stream through plugins that do not have an active audio stream. Only channels that have audio or are input monitored or have a synth feed actually pass through audio to plugins. That has been done from day one so its most certainly not something new you will get.

The huge misconception that many people advocating VST3 have is that the feature list posted is something you magically get for free by adopting the VST3 standard. VST3 is a plugin standard, nothing more nothing less. i.e like VST 2.4 all it does is publish a set of API's (a communications protocol) by which the DAW and plugin communicate. It facilitates a few new things like expression parameters and hierarchical parameter grouping, but its still up to the DAW to choose to implement these. Steinberg lists these because they are features they chose to do in their DAW. Nothing wrong with that but it most definitely doesn't mean that other DAW's will implement them - in the same way that VST2.4 has optional extensions. The other misconception is that the features in VST 3 are things unavailable to VST2. As I've said several times in the past - VST 2 may not be the prettiest API but it is extensible and pretty much anything in VST 3 could be accomplished in VST 2 with extensions. The entire prochannel API is written as a VST 2.4 extension for example and our requirements for these are not even met in VST 3.  In fact VST 3 could itself have been an extension to VST2 but Steinberg chose to redo the entire specification which requires an expensive rewrite from host vendors to support it. 

Anyway to summarize, support for VST3 is on the table for us. I cannot say when it will happen since it hasn't been scheduled in our product plan yet. We acknowledge that some plugin vendors in the future will ultimately choose to publish only VST 3 compatible versions (primarily to save development resources) or won't have the time to do things like sidechaining in VST 2.4 (which is possible and documentation published)  What I can say with certainty is that when we do VST3, you will not get any new functionality in SONAR other than the support for plugins that do not have equivalent VST 2.4 counterparts.

Noel, you missing the point! VST3 is here and it here to stay, period.
 
Its not about if Cakewalk like it or not. As you point out, some plugins only support VST3 You say that it doesn't bring anything new to the table, still if I can't use it it must bring me something?...
 
Anyhow its definitely a bumper for any users that need it.
As for today and the future of X2, I can't even use some of the plugins because of the lack of VST3 support. 
 
Let's look further down the road... What about the new x64bit UAD plugins that going to be release very soon? As far as I know, they will ONLY SUPPORT VST3! So basically If you have UAD card/UAD user you can't use it with SONAR X2? 
 
After that next up is WAVES: This is the last version of WAVES that will include VST2.4 support. What about Native Instruments, Spectrasonics plugins etc 2013?  Shall we stop use them too if you are SONAR user because there are no VST3 support? 
 
 
Have you at Cakewalk though about that?  
 

I've still got my fingers crossed that they

HEED THE PIPER

and when they release the Win 8 patch they include VST 3

but I'm NOT going to hold my breath...

Cheers!

Freddie please calm down and stop writing BS about UAD. It is not going to happened that it will be only VST3 All we want to say here is that VST3 is not important now.

BluerecordingStudios


Freddie please calm down and stop writing BS about UAD. It is not going to happened that it will be only VST3 All we want to say here is that VST3 is not important now.

BS? I don't think so.. Its not what I have heard and read... You should check the UAD website and the FORUM..
 
http://www.uaudio.com/
 
Check WAVES when you are at it too...they say vst2.4 waveshell will die next major update 
 
http://www.waves.com/
 
 
I don't know...time will soon tell! What I do know is that SONAR is the only professional DAW that doesn't support VST3!

Noel Borthwick [Cakewalk
]

We acknowledge that some plugin vendors in the future will ultimately choose to publish only VST 3 compatible versions

Thank you for your considered overall response.. but FYI that time is now, not in the future.. I cannot integrate my $2200 synthesizer with VST as the editor is written solely for VST3..

Noel Borthwick [Cakewalk
]

If vst3 does not consume CPU when no signal present that's really smart. I know another DAW that lets you automate bypass of effects to eliminate unnecessary CPU consumption. That always made sense to me. If in fact that's how Vst3 functions automatically that would seem like number 1 priority in any DAW.

All cakewalk products have had this functionality since the 90's. Our DX sdk had an IDeferZeroFill interface that Ron thought of way back then. If anything I think this capability in VST3 came from there :) Additionally SONAR has always optimized to not stream through plugins that do not have an active audio stream. Only channels that have audio or are input monitored or have a synth feed actually pass through audio to plugins. That has been done from day one so its most certainly not something new you will get.

The huge misconception that many people advocating VST3 have is that the feature list posted is something you magically get for free by adopting the VST3 standard. VST3 is a plugin standard, nothing more nothing less. i.e like VST 2.4 all it does is publish a set of API's (a communications protocol) by which the DAW and plugin communicate. It facilitates a few new things like expression parameters and hierarchical parameter grouping, but its still up to the DAW to choose to implement these. Steinberg lists these because they are features they chose to do in their DAW. Nothing wrong with that but it most definitely doesn't mean that other DAW's will implement them - in the same way that VST2.4 has optional extensions. The other misconception is that the features in VST 3 are things unavailable to VST2. As I've said several times in the past - VST 2 may not be the prettiest API but it is extensible and pretty much anything in VST 3 could be accomplished in VST 2 with extensions. The entire prochannel API is written as a VST 2.4 extension for example and our requirements for these are not even met in VST 3.  In fact VST 3 could itself have been an extension to VST2 but Steinberg chose to redo the entire specification which requires an expensive rewrite from host vendors to support it. 

Anyway to summarize, support for VST3 is on the table for us. I cannot say when it will happen since it hasn't been scheduled in our product plan yet. We acknowledge that some plugin vendors in the future will ultimately choose to publish only VST 3 compatible versions (primarily to save development resources) or won't have the time to do things like sidechaining in VST 2.4 (which is possible and documentation published)  What I can say with certainty is that when we do VST3, you will not get any new functionality in SONAR other than the support for plugins that do not have equivalent VST 2.4 counterparts.

Noel, thank you for this information! At least we know that Cakewalk has this on the table. We'll just have to wait a bit.

BluerecordingStudios


 All we want to say here is that VST3 is not important now.

I dont know how self absorbed you need to be to make such a statement... perhaps there are others where the lack of vst3 support is crippling their workflow and causing needless extra hours (and hours) of additional setup work?..
 
 
 

This is quite disturbing,especially with the Waves deal,I just indebted myself to, due to Waves 64bit no iLok change,and spent up big[for me] with Waves,and tonight,earlier I just prepaid for X2 with the $29 box[$35 postage!!]

Also once UAD went x64 I was hoping to try those[in the future]looks like that won't happen!

It's weird I was just looking at some horrors[GS/utoob] Logic users are having with Lion/Mountain Lion,things like GUI so slow its TOTALLY unusable,and was counting my lucky stars,and now THIS......arrrrghh,I hope I can just use the current version of Waves forever then?

Now very confused!
Bob

I don't know much about VST3 , but I do believe that the improvement in automation in X2 is more important than VST3 for people that looking for a "pro" DAW.  
I think (and hope) that the bakers have done a great job with X2, but everything can't be done in one update.
And as Noel says in this thread, VST3 is comming......

(I didn't see the webinar, but it seems like most of you guys/girls liked what you did see)

Around this time each year, we tend to reflect on the past, and look forward to the future. 2011 has been a particularly good year for Universal Audio and the UAD platform, with the introduction of the UAD-2 Satellite and some exceptional new plug-ins. This year also marks the 10th anniversary for the UAD platform — a milestone we could not have achieved without your support.

Since we introduced the UAD DSP Accelerators in 2001, we've grown from just a few hundred users, to more than 45,000 owners worldwide. Over the past decade, we've introduced powerful new UAD hardware, as well as more than 50 new plug-ins, including groundbreaking titles with Ampex, EMT, Lexicon, Manley, Neve, SSL, Studer, and more.

Importantly, the high quality of these UAD products is directly related to your support — which literally funds the development of what we believe are the best audio processors in the world. Without this support, we would not be able to spend six months, nine months, or up to a full year developing our highly complex individual plug-in titles.

So for that, we sincerely thank you.

Looking forward, one increasingly common request is for UAD plug-ins to become fully 64-bit compliant. Rest assured, the UAD plug-in transition to 64-bit architecture will be completed in 2012.

Importantly, this 64-bit compatibility will come at no cost to our users. You have chosen to support us, and we will support you as audio processing standards evolve.

Again, thank you for using UAD Powered Plug-Ins. And please know that the best is yet to come.

Sincerely,

Bill Putnam Jr.
Founder
Universal Audio Inc