![]() 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. New install of Sonar Pro - today - latest 2017.10 version. Waves VST3 PlugIns Not Loading in New Install of Pro - 2017.10
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |