Waveshell-vst 9.2x64.dll is a type of DLL file associated with WaveShell-VST 9.2.0.10 developed by Waves Audio Ltd. For the Windows Operating System. The latest known version of Waveshell-vst 9.2x64.dll is 9.2.0.10, which was produced for Windows 7. This DLL file carries a popularity rating of 1 stars and a security rating of 'UNKNOWN'.
- Free Ableton Vst Plugins
- Ableton Vst Free
- Ableton Vst Files
- Waveshell Vst Ableton Download
- Ableton Live Vst
- Waveshell Vst Ableton Plugins
- Recently I got Reel ADT and added it to Ableton VST. It appears in the plugins menu under the WaveShell 9.2 in the VST folder, but when I click on it, nothing happens. Sometimes the hourglass (loading) icon will appear briefly then disappear. Further context: I recently changed from Ableton v8 to v9.1.7 and am currently using 32-bit in Ableton v9.
- Up to version 10.0 Ableton Live only used VST (2.4) plugins format, which our could only display waveshells separately as you are experiencing. As of Ableton Live 10.1, VST3 format is supported.
Just a quick question for those of you who are using the Waves Gold bundle plugins with Live. I have a silly question regarding installation of the various components as I don't think they have installed correctly or they may have installed in the wrong place.
Free Ableton Vst Plugins
Ableton Vst Free
Installation of the bundle was via the Easy Install and Activate menu on the Waves Central page... the software downloaded OK but I wasn't given a choice as to where the plugins were finally installed. As it was, the Waves plugin folder automatically installed in the C: drive Program Files (x86) directory. It contained 5 folders: Applications, Data, Plug-Ins V9, ReWire and Waveshells V9. The Plug-Ins folder contained 35 bundles plus associated documents eg Audio Track bundle, C1 bundle, C4 bundle, DeEsser bundle etc.Unfortunately, my VST plugin folder for Live is on a separate drive (M: drive) and Live will scan that nominated M: drive folder on startup - not the Wave folder in the C: drive.
I couldn't work out a way to get Live to see the Wave folder so in frustration, I copied the entire Wave folder containing the above mentioned 5 folders from the C: drive and simply pasted it into the Ableton VST folder located on the M: drive.
All of the VST Wave plugins now appear in Live and as far as I have tested, they all are working correctly including the various preset library settings.
The problem is that I now see 120 separate VSTs listed inside the Live plugin Wave folder and many appear to be variations of the same plugin eg. C4 mono vst, C4 stereo vst... Doubler2 Mono vst, Doubler2 Mono vst/Stereo vst, Doubler2 stereo vst ... Q1 Mono vst, Q1 Stereo vst ... Q2 Mono vst, Q2 Stereo vst and so on. All of these VSTs are located in the following folder hierarchy in the Ableton plugin menu: Waves / WaveShells V9 / WaveShell-VST 9.6 / vst XXX
Can you please tell me what I have done wrong or how I can re-install the plugins to the Live M: drive VST folder? Should I be seeing so many VSTs just lumped together or should they appear in their own separate bundle folder?
many thanks for your help.
Ableton Vst Files
ps - I'm using Live 9.2.3Guest 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.
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.
Waveshell Vst Ableton Download
To put it bluntly, I had problems. But the problems were neither the fault of Waves or of Cockos. 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.
Ableton Live Vst
Save
Waveshell Vst Ableton Plugins
Save
Save