![]() I also tried removing VST3 and keeping VST2 with no luck. Removing the VST2 Waves shell and keeping VST3 Waveshell in place did not make a difference other than the file classification in Wavelab plug-ins. So I can conclude they are not stored in a cache in Cubase. All Waves plugs are grayed out in the plug-in manager. As expected, Cubase did not show any Waves plugs once booted. Today I removed both the VST2 Waves shell and the VST3 Waves shell to see if Cubase would still show the Waves plugs. What else should I try and thanks in advance?īTW, possibly Cubase has the settings stored in a cache. That did make all Waves plug-ins show up, but once I did a “Force Plug-in Detection at next launch” it’s back to the bad behavior of only 1/4s of Waves plugs showing up. The only success I have had in Wavelab showing all Waves plug-ins to show up, is take a Wavelab Preferences folder that I had saved from last November, and place it at C>users>user name> app data>Wavelab pro 9.5. Steinberg support just forwarded a System Information File to the “development team” which doesn’t sound very encouraging. What is left to try? Is there deeper Wavelab residue that needs to be deleted? it didn’t show 3/4ths of the Waves plugs, then ran the Wavelab 9.5.50 update, and there was no change.
0 Comments
Leave a Reply. |