It seems strange, but some users have reported that after an hour of waiting, Logic's Plug-ins Manager has listed the plugin. If you're running macOS 10.14 Mojave, you could also check again after another hour of computer usage. If the plugin is still not found, close Logic, then delete your cache file, if it exists:
Make sure you have admin rights when you install the plugin. If it is, make sure Logic is closed, remove the plugin manually and install it again. If you still can't see the plugin in Logic, browse to this folder and check that the plugin is installed there (in Finder, press SHIFT-CMD-G and enter a folder name in the dialog to open it directly): If the plugin also doesn't appear on stereo tracks, open Logic's Preferences > Plug-in Manager and check that the plugin is listed and activated. In Logic, a newly created audio track is mono by default. Some of our plugins only work on stereo tracks. If the plugin in question is Kickstart, be aware that it appears in the Nicky Romero folder in Logic's Audio FX menu, not the Cableguys folder.
Some DAWs (including Ableton Live and Logic Pro X) may not recognise the plugin otherwise. I have contacted Waves and they are working on a solution.Please restart your Mac after installation. So anyone on Win 64 experiencing Waves crashes – And I mean total Waves crashes – ie. Notice in my screenshot that Wavelab also had the same problem.īookmark this key and if you suffer this problem go back and DELETE the registry DATA contained in this key that relates to your DAW host. This may of course be different for another machine so it probably better to use the search method as mentioned above.
How to find the key: Search registry for “WaveShell-VST3 9.2_圆4” and you will find the odd key with IgnoreFreeLibrary associated.ĭo not search for AppCompatFlags as it will bring up tons of irrelevant stuff.
After which, any subsequent load of the Waveshell causes the host (Cubase) to crash. I had already done a clean install of all related applications, Waves, Cubase etc., And also cleaned registry of everything that mentioned Waves before re-installing…įinally I decided to search the registry for WaveShell-VST3… Low and behold the solution – A very odd registry key gets added if the Waveshell crashes. Renaming it back to the original WaveShell-VST3 9.2_圆4.vst3 still causes crashes… What is going on? Waveshell crashes again and now the projects will not load again even with the renamed file, unless it was renamed yet again. I renamed the file to WaveShell-VST3 9.2_圆4_BLAH.vst3 Wow! Success!Īll my projects loaded again… But it is not over yet.
This file is found here and this put me on the right path:
I found a post related to a different issue that suggested renaming the WaveShell-VST3 9.2_圆4 file.