Vst3 and Waves were working when I first installed X3,
But after executing a complete reinstall of Waves(because of a recent purchase)
the scan now stops and hangs on certain Waves plugs
I have done multiple complete reinstalls of all my waves plugins(after deinstalling waves and clearing off any other lurking waves files)
but still no luck!
So I thought Why do I need Waves running in VST3, and deleted the Waves vst3 dll from the common files vst folder.
Since then all Waves plugs now Vst2 - everything works fine, and no crashes
Just thought I'd post incase someone else was struggling

The problem could also have been old installation files lurking around in the registry. If you need vst3 that bad, you may take a look in the registry and clean out any old waves folders or files next time you re-install.

Thanks Sidroe
You could be right - although I did use regedit to find any waves file in an incorrect library
But I'm quite happy using vst2
I just put the post out incase someone else was experiencing the same problems 

There's no reason to use the VST3 version of any plugin unless forced to due to it being VST3-only. There is no sound-quality benefit, no performance benefit, no extra functionality. I know of only a handful of popular plugins that are only available as VST3. Why anyone would bother with it beats the heck outa me. Fear of being left out of the revolution, perhaps.

bitflipper
There's no reason to use the VST3 version of any plugin unless forced to due to it being VST3-only. There is no sound-quality benefit, no performance benefit, no extra functionality. I know of only a handful of popular plugins that are only available as VST3. Why anyone would bother with it beats the heck outa me. Fear of being left out of the revolution, perhaps.

You're forgetting one thing...the VST3 plugs have bypass switches whereas a lot of VST2 plugs don't. I actually find this quite useful.

I just went through an experience similar to the OP. There still seems to be some issue with Waves and Sonar. I found that Waves didn't seem to like being installed in alternate locations. I was getting multiple copies of my plugs and then all VST2, and finally VST3 only and sorted by application. I picked up the free RBass but it won't install. I have the license and I have the files but it won't show up in any of my DAW's.
 
I hope this doesn't mean version 10 is coming soon. I'm wupless and half my stuff is a year old. Of all the installs and license management, I still find NI to be the least intrusive and most helpful.

sharke

bitflipper
There's no reason to use the VST3 version of any plugin unless forced to due to it being VST3-only. There is no sound-quality benefit, no performance benefit, no extra functionality. I know of only a handful of popular plugins that are only available as VST3. Why anyone would bother with it beats the heck outa me. Fear of being left out of the revolution, perhaps.

You're forgetting one thing...the VST3 plugs have bypass switches whereas a lot of VST2 plugs don't. I actually find this quite useful.

Now you're just stretching for a justification ;) Every plugin has a true bypass in SONAR.
 
'Course, you can't automate it, but I can count on one hand the number of times I've needed to automate a plugin's bypass - and I'd need far fewer fingers to count the number of times it worked without glitching.

The VST3 thing is kinda funny to me. I remember when Sonar didn't have it and there was all this hue and cry for it and then we get it... and I'm amazed at how little I have that uses it. The Waves stuff I just got does, Halion Sonic does, Melodyne does, and that is it. Everything else is 2.4 only.
 
So I see where Cakewalk was coming from on the "No really, VST3 isn't the big deal people make it out to be."
 
:)

bitflipper

sharke

bitflipper
There's no reason to use the VST3 version of any plugin unless forced to due to it being VST3-only. There is no sound-quality benefit, no performance benefit, no extra functionality. I know of only a handful of popular plugins that are only available as VST3. Why anyone would bother with it beats the heck outa me. Fear of being left out of the revolution, perhaps.

You're forgetting one thing...the VST3 plugs have bypass switches whereas a lot of VST2 plugs don't. I actually find this quite useful.

Now you're just stretching for a justification ;) Every plugin has a true bypass in SONAR. 'Course, you can't automate it, but I can count on one hand the number of times I've needed to automate a plugin's bypass - and I'd need far fewer fingers to count the number of times it worked without glitching.

You can automate the on/off button on the ProChannel FX chains, but a bug persists whereby the automation doesn't work unless the track is in focus. Automating bypass is actually quite common but I guess it depends on the genre you're working on. For instance on a dance track you may have a 4 bar break in which the drums go through a band pass filter. If your EQ has a bypass you can just set up a separate instance for the band pass and automate the on/off with one envelope. If it doesn't, then you're creating envelopes for both the cutoffs. It's just a little more convenient.

ampfixer
I just went through an experience similar to the OP. There still seems to be some issue with Waves and Sonar........

.....on *some* machines.