Waveshell Vst Cant Find Plugins
- Download Waveshell
- Waveshell Vst Free
- Waveshell Vst 9.2
- Waveshell Fl Studio
- Waveshell Vst Cant Find Plugins Chrome
- Waveshell Vst Cant Find Plugins Download
- Waveshell Vst 10
I had a 15 hour struggle in the studio recently. All my Cubase 7 (64 Bit) projects refused to load without crashing. Even projects that I was working on the very day before.
I re-installed, searched, cleaned, refreshed preferences, you name it, I tried it…
15 hours later I was still unable to load any of my projects without Cubase disappearing into the dark depths where all dead project go.
If some of your Waves plugins are missing after you installed them with Waves Central, consult one of the following pages in order to find them. If only recently installed plugins do not appear in your DAW, visit our Plugins Missing in DAW and select the instructions specific to your DAW. I also deleted any other copies of Waveshell dll's that were floating around in my vstplugin folder. I also had trouble determining where the actual Waves plugs resided. I thought it was C: Program Files VstPlugIns, where the 2 Waveshell dll's lived, but the correct location turned out to be C: Program Files (x86) Waves Plug-Ins V9. In Roaming, locate the folder named “Waves Audio” and move it to the Desktop. Launch your host application with a fresh session. If prompted to locate the Waves Plug-ins Folder, direct to the above location. Waves nightmare - SOLVED! Hi, I had one Waves plug installed - it was working fine. Today I got a second one - and everything has to install from Waves central. I just copy the Waves shell file to my VST folder (to keep it with everything else) but the problem is this: The old file was called WaveShell-VST 9.2x64.dll (Kramer Tape) and the new one is WaveShell-VST 9.6x64.dll (Kramer Tape. Try scanning again with 'Rescan Existing Plug-ins' checked, this will rescan everything. If that still doesn't work, uninstall all the Waves plug-ins (and delete any WaveShell DLL's that you have moved), and then reinstall all the Waves plug-ins from their original installers and let Audition scan the default folders again.
The next morning I woke up and with a fresh head, found myself a cure within 30 minutes (based on the research I had done the day before). So I thought this would be worth sharing, as during my search I found many folks with similar trouble and no solution.
The first step was realising that if I removed the Waves plugins from my system the problem went away.
Symptoms:
- Windows 64 Bit System
- 64 Bit DAW Host
- Usually Windows 8 but can be Windows 7 – Must be 64 Bit
- Cubase crashes when loading a project that contains ANY Waves plugins
- Cubase crashes when inserting ANY Waves plugin into a fresh project
- I am using Cubase here but it could be any 64 Bit DAW host application
I found a post related to a different issue that suggested renaming the WaveShell-VST3 9.2_x64 file. This file is found here and this put me on the right path:
C:Program FilesCommon FilesVST3
I renamed the file to WaveShell-VST3 9.2_x64_BLAH.vst3
Wow! Success!
All my projects loaded again… But it is not over yet.
Download Waveshell
/vibe-pro-vst-free.html. Waveshell crashes again and now the projects will not load again even with the renamed file, unless it was renamed yet again. Renaming it back to the original WaveShell-VST3 9.2_x64.vst3 still causes crashes… What is going on?
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…
Finally 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. After which, any subsequent load of the Waveshell causes the host (Cubase) to crash.
Full Solution:
- Windows 64 Bit is affected (although it mentioned 8 it can also be 7)
- Waves (shell) crashes once
- Waveshell gets added to the reg key with “IgnoreFreeLibraries” with reference to Cubase (or whatever caused the crash).
- Waveshell will now crash every time it is loaded / used (unless the shell is renamed)
- Solution – DELETE the registry DATA contained in this key (as highlighted in my screenshot) that relates to your DAW host
How to find the key: Search registry for “WaveShell-VST3 9.2_x64” and you will find the odd key with IgnoreFreeLibrary associated.
Do not search for AppCompatFlags as it will bring up tons of irrelevant stuff.
Here is my reg key area:
This may of course be different for another machine so it probably better to use the search method as mentioned above. Notice in my screenshot that Wavelab also had the same problem.
Bookmark 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.
Back It up first if you are concerned.
So anyone on Win 64 experiencing Waves crashes – And I mean total Waves crashes – ie. /free-edm-bass-vst-plugins.html. Nothing VST3 works. It may be worth checking.
Waveshell Vst Free
I have contacted Waves and they are working on a solution.
Waveshell Vst 9.2
OK that is all. Thank you and goodnight.
Thread Rating:- 1 Votes - 5 Average
Cannot see Waves individual plugins |
03-08-2016, 03:12 PM (This post was last modified: 03-08-2016 03:40 PM by AndyJG.) |
| Cannot see Waves individual plugins Hello everyone. I'm new here and have searched the forum and the Internet for an answer to this question and cannot find anything I haven't already tried so here goes ... I'm running Mixbus 3.1 on a Windows 7 64bit laptop. I have successfully installed the Waves Gold bundle (with Ben's help) and it works fine. However, I have recently bought the Waves Abbey Road J37 and the Waves NX Mix Room plugins individually. They've installed successfully on my laptop (according to the Waves installer, anyway) and can be found in C/Program Files (X86)/Waves/Plug-Ins V9 folder. This folder contains 'J37.bundle' and 'NX.bundle'. Each bundle contains an icon and a 'Contents' folder. Both contents folders contain both 32bit and 64bit folders in which are found the respective dll files. Sorry for the long-winded description above but I've tried all sorts of file paths to try to get the 64bit versions to show up in Mixbus 3.1 but have so far failed, although they often appear on the plug-in scan itself. I've tried clearing the plug-in cache and blacklist (every time before I rescan). I've tried copying all permutations of the dll files and folders into the Program Files/VSTPlugIns folder in which the WaveShell-VST 9.6_x64 file was installed by the Gold Bundle but nothing happens there, either. Having, as far as I can tell, exhausted my options I need help: how do I make these plugins appear in Mixbus 3, please? Thanks in advance for any help. Cheers! Andy. |
Post: #2 |
| RE: Cannot see Waves individual plugins Do you have another DAW and have you managed to detect them using that? It took me a while to understand this new waves installer even on mac. Thinking I've installed and not showing, install again but didn't show and finally I understand, I have to install and activate at the same time. |
03-09-2016, 09:07 AM (This post was last modified: 03-09-2016 09:09 AM by AndyJG.) |
RE: Cannot see Waves individual plugins (03-08-2016 05:01 PM)BHBstudio Wrote: Do you have another DAW and have you managed to detect them using that? It took me a while to understand this new waves installer even on mac. Thinking I've installed and not showing, install again but didn't show and finally I understand, I have to install and activate at the same time.Hello BHB. Thanks for the reply. I have Reaper 4 so will try them on there. I'll post again at the weekend to say how I got on. Cheers! Andy. |
Post: #4 |
| RE: Cannot see Waves individual plugins Did you re-scan in Mixbus? My Studio Specs(and possibly set Mixbus' rescan timeout to zero, and clear cash and blacklist first) I track, eidt and manage tracks in Studio One Pro V5/CbB. I try to always mix in Mixbus32C. “It did what all ads are supposed to do: create an anxiety relievable by purchase.” ― David Foster Wallace, Infinite Jest |
Waveshell Fl Studio
Post: #5 |
| RE: Cannot see Waves individual plugins Try and set time-out to 2 minutes and re-scan. I had the same problem when the Waves plugins did not show. I noticed the plugin scan hanging on Waveshell 9.6 and 9.7 and reaching the standard time-out. Hope it works for you! |
Post: #6 |
| RE: Cannot see Waves individual plugins Having Waves Mercury, SSL suite and Abbey Road suite I had to set my timeout to zero because even the max time on the slider still timed out Waves. My Studio SpecsI track, eidt and manage tracks in Studio One Pro V5/CbB. I try to always mix in Mixbus32C. “It did what all ads are supposed to do: create an anxiety relievable by purchase.” ― David Foster Wallace, Infinite Jest |
Post: #7 |
| RE: Cannot see Waves individual plugins Thanks for the replies, everyone. I updated to Mixbus 3.2 and at the same time tried everything suggested here except the zero timeout option (I'll give that a look tonight) but nothing has happened so far. BHB, I can get the Waves Gold Bundle to show in Reaper 4 but not the individual J37 and NX plugins! The waves gold bundle seems to be accessed via the Waves Shell but the J37 and NX seem to sit outside of it, but I'm not sure what difference that should make as I have plenty of other non-Waves plugins working in both Mixbus and Reaper via a single dll. It's perplexing and infuriating at the same time and it'd be nice if Waves came up with something other than 'it's not our problem'. But hey-ho, I'll keep trying. Cheers! Andy. |
Post: #8 |
| RE: Cannot see Waves individual plugins I feel your pain. For me, Waves NX works fine in Mixbus. Waves plugs have been very troublesome for me in Reaper 5. With every update of Wavescentral, Reaper might not see new Waves plugs, and/or lose many other non-Waves plugins. I fixed that problem by deleting entries in reaper-vstplugins64.ini and let Reaper re-scan for new plugins / clear cache (always make a backup). I also deleted any other copies of Waveshell dll's that were floating around in my vstplugin folder. I also had trouble determining where the actual Waves plugs resided. I thought it was C:Program FilesVstPlugIns, where the 2 Waveshell dll's lived, but the correct location turned out to be C:Program Files (x86)WavesPlug-Ins V9. All individual 32 and 64-bit dll's are in there. Set Mixbus to scan for that location. Hope this info will be useful to alleviate your problems. |
Post: #9 |
| RE: Cannot see Waves individual plugins I've never pointed MB3 or any DAW to C:Program Files (x86)WavesPlug-Ins V9. I just point to C:Program FilesVstPlugIns (which is my chosen 64bit VST path). My Studio SpecsThe shell knows where the plugins are, unless you manually move them and that is just wrong IMO. I track, eidt and manage tracks in Studio One Pro V5/CbB. I try to always mix in Mixbus32C. “It did what all ads are supposed to do: create an anxiety relievable by purchase.” ― David Foster Wallace, Infinite Jest |
Post: #10 |
| RE: Cannot see Waves individual plugins I have recently deleted my Mixbus preferences folder and started with a clean Mixbus. I indeed have to point to C:Program FilesVstPlugIns. There must have been something wrong before . Bapu is right. |
« Next Oldest Next Newest » |