Hi All,
 
Title says it all.
 
New install of Sonar Pro - today - latest 2017.10 version.  WIN7 (all up to date)/24GB Memory/Dell XPS Tower/Intel i7.  Several variants of WaveShell-VST3 9.91... in appropriate directories.
 
My WAVES VST3 plug-ins are being scanned - they appear correctly in the Sonar Browser.
 
At first I had the "Hide Related VST2 Plug-ins" and "Replace if Possible on Project Load" options ticked off in the Preferences/VST Settings.  So only the VST3 versions were being scanned.
 
When I tried to add a WAVES VST3 plug to a track's FX section I got a popup with "The following VST plug-in failed to load (80004002)" message.  Followed by a "Cakewalk Missing Plug-In Stand-In" popup.
 
I went back and unchecked the two options in the VST Settings, and then both VST2 and VST3 plug-ins were being scanned in.
 
I was able to add WAVES VST2 plug-ins to a track, but no luck with WAVES VST3 versions.
 
I have other VST3 plug-ins from FabFilter, Softtube, and Izotope - all of these can be added to tracks successfully.
 
So it seems to be an issue with the WAVES VST3 plug-ins only.
 
Anyone know what might be going on?
 
Thanks,
Danny V.

Gonna bump this up cause I'm right in the middle of trying to get my new install set up properly.
 
Can someone just confirm that they're running SONAR 2017.10 and successfully using WAVES VST3 plugins on WIN 7/64 bit?  I'm running Sonar PRO but if they're working on SPLAT please acknowledge.
 
Thanks,
Danny V.

If you cant get an answer here Waves support is very quick to reply.
Do you have Waves central installed ? I know it might not be the problem because you still use VST2 but it could be.
 
Im using Waves VST3 plug ins on this newest update. Cant say I've seen any issues yet.
 
You also might try to check the box "Rescan existing plug ins" in preferences> Vst settings.
 

danevas
Several variants of WaveShell-VST3 9.91... in appropriate directories

 
Where is that ? What directory ?

Here's what I originally had Sonar scanning on startup:
c:\program files\common files\vst3
c:\program files\steinberg\vstplugins
c:\program files\vstplugins
 
After reading some WAVES documentation I added:
c:\program files (x86)\common files\vst3

 
No difference - both the VST2 and VST3 versions of all my WAVEs plugs get scanned in.  But when I try to add the VST3 version to a track it fails.
 
Here's what I found on my machine after a search:
files:
C:\Program Files\Common Files\VST3\WaveShell-VST3 9.91_x64.vst3
C:\Program Files\VstPlugIns\WaveShell-VST 9.91_x64.dll
 
files:
C:\Program Files (x86)\Common Files\VST3\WaveShell-VST3 9.91.vst3
C:\Program Files (x86)\VstPlugIns\WaveShell-VST 9.91.dll
 
C:\Program Files (x86)\Waves\WaveShells V9\WaveShell-VST 9.91.dll
C:\Program Files (x86)\Waves\WaveShells V9\WaveShell-VST3 9.91.vst3
C:\Program Files (x86)\Waves\WaveShells V9\WaveShell-VST3 9.91_x64.vst3
C:\Program Files (x86)\Waves\WaveShells V9\WaveShell-VST 9.91_x64.dll

C:\Program Files (x86)\Waves\Plug-Ins V9\WavesLib_9.91_Win64.dll
C:\Program Files (x86)\Waves\Plug-Ins V9\WavesLib_9.91_Win32.dll

Don't know what's going in.

Danny V.

I tried a few other things including reinstalling my WAVES software - but no difference.
 
So, I renamed the WaveShell-VST3 9.91_x64.vst3 file in C:\Program Files\Common Files\VST3 so that it wouldn't be scanned in correctly.  Seems to have worked - only the VST2 versions of the WAVES plugins get scanned in and can be loaded onto a track.
 
It has nothing to do with combining VST2 and VST3 plug-ins.  I created a new project with one audio track and tried to add a WAVEs VST3 as the only plugin to the track - no luck ("...plug-in failed to load...").
 
Oh well, I can live with it - (but it should work - other vendor's VST3 plugs load fine.)
 
Danny V.

I was having this exact same problem. The strange part is some of the VST3 plugins would load (I have the Gold bundle, as well as a few one-offs). Specific ones would not load until I unchecked the box to replace VST3 with VST2. This was never a problem before, and wasn't until I installed what is now the very last update to Sonar I'll get with the "lifetime" update subscription. ;) All the plugins work fine in WaveLab and Cubase, so I do believe it's isolated to Sonar, and is not an issue with the plugins. I guess this isn't a defect that will be corrected. :(
 
Andrew