No difference - both the VST2 and VST3 versions of all my WAVEs plugs get scanned in. Here's what I originally had Sonar scanning on startup: c:\program files\common files\vst3Ĭ:\program files\vstplugins After reading some WAVES documentation I added: c:\program files (x86)\common files\vst3 Anyone know what might be going on? Thanks, Danny V. So it seems to be an issue with the WAVES VST3 plug-ins only.
I have other VST3 plug-ins from FabFilter, Softtube, and Izotope - all of these can be added to tracks successfully. I was able to add WAVES VST2 plug-ins to a track, but no luck with WAVES VST3 versions. I went back and unchecked the two options in the VST Settings, and then both VST2 and VST3 plug-ins were being scanned in. Followed by a "Cakewalk Missing Plug-In Stand-In" popup. 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. So only the VST3 versions were being scanned. 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. My WAVES VST3 plug-ins are being scanned - they appear correctly in the Sonar Browser. WIN7 (all up to date)/24GB Memory/Dell XPS Tower/Intel i7.
Waveshell vst 10.0 install#
New install of Sonar Pro - today - latest 2017.10 version. Waves VST3 PlugIns Not Loading in New Install of Pro - 2017.10
0 kommentar(er)
