Just recently it still said X1-X2 as supported for VST.
 
And I expected if any change it would say X1-X2(VST2) X3(VST3) or something.
 
Is there an explanation for this - nothing about X3 and X1 was removed?
 
I saw that the release of Studio One 2.6 in august is listed already.
 
How does this work - are Waves charging for test and Cake is awaiting X3c, or?

I can't speak for Cakewalk, but I'd be willing to bet they will NOT be going back to X1 or X2 to implement VST3. Waves plugins have worked well for me in every version of Sonar other than some GUI issues, the knobs/controls need to be moved slowly and side-chaining was not available.
 
The GUI issues for me were fixed in Waves 8, the knobs and controls were better as long as you don't try to move them super fast, and side-chaining isn't something I need because I know how to make instruments work in a mix without it, so I could care less about it. :) That said, I can understand why those who were looking forward to that feature would be upset. But everything for me with Waves worked from Cakewalk Pro Audio 9, all the Sonar versions from 1-8.5 and they have worked in X1,2 and 3 for me.
 
Moving to present time, Sonar X3 is of course available and it supports VST 3 and works well with Waves on my end. Side chaining is even supported due to VST 3. I'm not sure what you read or if you have misunderstood what you read possibly, but there are people using Waves with Sonar like me on a daily basis with no issues....some have small issues with work-arounds. Whether Waves claims to support Sonar or whatever the deal is with what you read, I have no clue but they work fine for me.
 
If I'm misunderstanding your post, my apologies.
 
-Danny

Thanks - no, I think you got it just about right - apart from that X1, X2 obviously will not be updated anymore, that I understand.
 
Now on X3, I had no real issues either. Have not tried Tune yet - if that runs though. The specs at Waves are worse now on the new site - the old table specs were much more clear what to expect from every plugin on every host.
 
Had trouble in other daws with Dorrough meters - but that worked just fine even in S8.5.
 
Just a bit puzzled - that X1 was removed suddenly and X3 not there yet?
What I expected was X3 to be added to the list as VST3 compliant.
 
Presonus were really quick to get S1 2.6 up there.

Even if Tune fails....in X3, you get Melodyne, which in my opinion, destroys Tune. Let me test Tune right now.....
 
I got Tune working perfectly in X3 and X2.
 
Dorrough is also working fine in X2 and X3. I had no problems switching views or toggling options.
 
Sometimes what you read may not be the case. :) Your best bet is to do what you did and post questions here. You know the forum guys here will definitely tell you if something works or not. I've been one of the lucky ones though....Waves has never given me any issues EVER yet I've had some of my friends tell me they could barely make them work at all. Hope some of this helps....good luck.
 
-Danny
 
 

Many thanks.
 
I've got X3 basic, and Melodyne is extra, so Tune has been good to me.

You're very welcome. Tune is working as good as Antares Auto Tune on my end so you should be ok. :)

When it comes to VST 3, Presonus had that through the whole Studio One v2.0 series and 2.6 was a point release.
From the Sonar perspective, VST 3 has only been available since Sonar X3 which has only been out a month. I cant see Waves qualifying it for a little while yet.

When you add the fact that Camewalk and Waves have had discussions to work out some early problems then there doesnt seem anything to get worried about.

Hey Danny,
Are there some particular Waves plugs you have or did you get something like the Mercury bundle.

I keep thinking about them but now i have a UAD quad card to feed with expensive plugins. Toi many choices, not enough funds.

lfm
Just recently it still said X1-X2 as supported for VST.
 
And I expected if any change it would say X1-X2(VST2) X3(VST3) or something.
 
Is there an explanation for this - nothing about X3 and X1 was removed?
 
I saw that the release of Studio One 2.6 in august is listed already.
 
How does this work - are Waves charging for test and Cake is awaiting X3c, or?

I'm sure it's just that "supported" means they tested it, and can confirm the plugins will work with said host. It doesn't mean the plugins won't work on any other version of Sonar, or that Waves will ignore your emails if you have a problem, it just means they're not going to go out of their way to ensure compatibility. Why? Because a company can't realistically be expected to support every major version of every major host. So Waves is saying, "hey, we're testing our stuff to make sure it works on X2."
 
Now, X3 was just released in October. Studio One 2.6 was released in August. It's also quite likely that Waves just hasn't had the chance to put X3 through it's paces yet. I'm sure at some point they'll say "X2/X3" are the only supported versions, and eventually just "X3" before switching to "X3/X4" sometime next year.
 
There's nothing to panic over. Universal Audio did the same exact thing with the UAD's, and everyone on the forum started freaking out. Meanwhile, everything's been fine, and the plugins are still working (there was an issue with Cubase 7, but that appears to have been Stieny's fault). So basically: nothing to worry about.

Funkybot
 
I'm sure it's just that "supported" means they tested it, and can confirm the plugins will work with said host.

It's this perception that got a kick in the butt this summer - I tested Samplitude ProX trial, and Waves Element crashed like crazy - and it was listed as supported by Waves. Also later looking for info allover this was a wellknown issue also to Waves - Magix has reported it and Waves are looking into it. Still it listed as supported.
 
I wonder how much that is worth with this approval thingy?
 
That's partly what I would like to find out with this thread - how does it work really?
Do Waves list as tested by vendors themselves - or do Waves do actuall testing.
 
Testing Digital Performer trial not long ago - I asked Waves support when and if it will be supported for Windows as well, since AU was supported already for DP8.
 
Waves support aswered that their team is taking these decisions what to test etc.
"For official support of Waves plug-ins, Waves QA department is testing and qualifying DAWs."
 
In DP Element was scanned - but nowhere to be seen when to insert on a track. I assume depending on that it identifies as effect but is a synth.
 
I saw no exception of Element for AU - which would have the same problem I assume.
 
So that still raise the question - how did Element get listed as supported for Samplitude if they really tested it?
 
Questions, questions....