Waveshell Vst Cant Find Plugins
If you can’t find your plugins after connecting a USB flash drive to a computer that already has some Waves plugins installed, try following the steps below, using Waves Central’s Version Organizer. Waves V11— Frequently Asked Questions. Waves plugins use what's called a VST Shell. It is a single DLL file (or.VST3 file) that points the host to all the individual plugins. As long as Reaper can find the VST Shell and the actual plugin files can be reached by the VST Shell, Reaper should be able to find the plugins.
Guest post by Brandon S. Hire of The Noise Floor. Brandon recently went hell with getting his Waves VST3 plugins all into REAPER. He got through it and I asked him to share the experience to help others in the same situation. Any clues to solving problems like this are gold.
Drum kit vst plugin free. Waves recently announced a new subscription plan which allows users to subscribe to their Silver and Mercury bundles. I decided to give this a try and download the Mercury Bundle. As a long time REAPER user and long time Waves user, I didn’t anticipate any problems.
When I remove WaveShell-VST 9.6.1x64.dll from the vstplugin folder and leave only WaveShell-VST 9.3x64.dll in the vst folder then all of the waves plgins will load except of course the waves plugins assoicated with WaveShell-VST 9.6.1x64.dll are no longer available. Mac youtube downloader free download.
- 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.2x64” and you will find the odd key with IgnoreFreeLibrary associated.
- If you can’t find your plugins after connecting a USB flash drive to a computer that already has some Waves plugins installed, try following the steps below, using Waves Central’s Version Organizer.
- After putting the respective 'WaveShell1-VST 10.0x64.so' in the same folder scanning fails on Mixbus4. I tried with updating via Waves Central, and also via removing all installed plugins, moving license back to the Waves cloud and using 'Easy install & activate' from Waves Central.
To put it bluntly, I had problems. But the problems were neither the fault of Waves or of Cockos. /free-vst-guitar-amp-simulator-plugins.html. The folks at Waves’ tech support team were awesome at helping me figure out the problem, and I want to document the issue here in case any of you are experiencing something similar.
Note that I’m not advising you to take these steps yourselves. If you’re having issues, there may be other factors that are causing your issues. Your best bet is to contact support at Waves or Cockos and see if you can get assistance with the issue. With that being said, here’s what happened:
To make a long story short, I noticed that about half of the Mercury bundle plugins weren’t showing up in VST3 format in REAPER. The same plugs would show up in VST and AU formats, which indicated that the plugins were in fact installed on the system. So I decided to clear the cache in the plugins preferences and rescan the plugins folder.
As it scanned the VST3 plugins from Waves, it stalled at Greg Wells MixCentric. Then REAPER flat out crashed. When I re-launched REAPER, there was still no sign of the missing VST3 plugins, and MixCentric was one of them.
So I contacted Waves support. After trying a couple of things, we were able to remedy the problem with a clean install. This required that I go through a few steps to uninstall everything Waves related on my system, and then allow only the newest versions of everything to be installed by Waves Central. The whole process took a couple of hours, but by the end of it all I was back up and running. When I loaded REAPER again, I cleared the cache and re-scanned again. This time there was no crash, and at the end of the scan I had all of the missing plugins.
Waves Tech Support Representative
- Quit all audio related software.
- Launch Waves Central and login. Choose: Install->Uninstall Products (at the top).
- Choose All Waves plugins V9 click ‘Uninstall‘.
- Once the uninstall is finished – quit Waves Central.
- Quit all the audio related software on your Mac.
- Please use the Waves uninstaller to remove all the Waves software from your computer, located in Applications > Waves > Utilities > Waves uninstaller and check “Remove All” to remove also the old versions. (If not available skip to the next step)
- Delete “Waves” folder located in your Applications folder
- Go to the following locations and delete any WaveShell file/s of any version number found:
- HD > Library > Audio > Plug-ins > Components
- HD > Library > Audio > Plug-ins > VST
- HD > Library > Audio > Plug-ins > VST3
- HD > Library > Application Support > Avid > Audio > Plug-Ins*
- HD > Library > Application Support > Digidesign > Plug-ins*
* This location is only present if Protools is installed
- Delete the “Waves Preferences” folder located at HD > Users > Current user > Library > Preferences (this folder is accessed by going to the Go menu and holding down the Altoption key. This will reveal the Library option)
- Delete the folder “Waves” located at HD > Current User > Library > Caches (this folder is accessed by opening the Go menu and holding down the [Alt/Option] key. This will reveal the Library option)
- Go to Mac HD > Library > Application Support and delete the “Waves” and “Waves Audio” folders.
- Download the latest version of Waves Central from this direct linkand install it on your computer.
- Follow the instructions on theInstalling your Waves products and demos article on our support page in order to reinstall your activated products.
As a long-time waves user, I’ve been slowly accumulating a collection of plugs prior to this subscription being available. That means I’ve been installing them intermittently over the last two years on this machine, and there have been updates since then. Those updates most likely were conflicting with previous files I’d installed, causing some to go missing and others to trigger a system crash. That’s why performing a clean install of everything worked. There was no longer old stuff mucking up the works and conflicting with the new stuff.
As mentioned above, if you’re having an issue with the new subscription working properly in REAPER, you should be certain that you’re using the VST3 version of the plugin in question. If it didn’t show up, a clean install may be the answer. I would do this with Waves tech support, as there may be further issues. Now that I’m up and running with the supported VST3 plugins, everything is running exactly as it should. I couldn’t be happier.
Thanks to Brandon for writing this up and sharing the info.
Save
Save
Save
Thread Rating:- 1 Votes - 5 Average
Download Waveshell
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 |
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 » |
User(s) browsing this thread: 1 Guest(s)