Vst Waves How To Uninstall Specific Plugins Chrome
Vst Waves How To Uninstall Specific Plugins Minecraft
Vst Waves How To Uninstall Specific Plugins Windows 10
Vst Waves How To Uninstall Specific Plugins Plugin

If you have Waves plugins that are still at version 9, you will have to download the Waves Offline Installer. Once you download the proper version for you, uncompressed it. Open Waves Central and select Offline Installer. Navigate to the folder, click into it, and select the Installers folder. Choose your plugins. Install Waves plugins normally; In FL Studio, open the plugin selector from the mixer (see image 1 below) From the plugin selector, choose one of the 'waveshell.' Plugins (see image 2) The plugin wrapper will open showing a selector control, containing all the plugins that are available for that specific 'waveshell.' Plugin (see image 3).

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.

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.

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

Uninstall the latest v9.6 of your Waves plug-ins for the system:

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:
1. HD > Library > Audio > Plug-ins > Components
2. HD > Library > Audio > Plug-ins > VST
3. HD > Library > Audio > Plug-ins > VST3
4. HD > Library > Application Support > Avid > Audio > Plug-Ins*
5. 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.

To reinstall Waves Central and your Waves V9 products –

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.

Afterwards, please launch REAPER and re scan again for the plug-ins.

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

Introduction

Microsoft announced that it would offer Visual Studio Express free of charge forever. Though the Express version of Visual C++ (hereafter referred to as VC++) has some limitations, it’s still a great tool and it’s nice to see Microsoft taking some steps to support the developers writing software for their platform. This document will describe how to get VC++ installed and building VST plugins. It assumes that you have prior experience developing VST plugins, and are familiar with the structure and layout of the VST SDK.

If you are trying to write VST’s in a language other than C++, than this guide is not for you. There are lots of other frameworks out there for developing VST plugins in other languages (such as C#, Java, Ruby and Python, just to name a few).

This tutorial will walk you through the process of installing and configuring the tools you’ll need to build your own VST plugins with Visual Studio, and creating a simple VST plugin with optional support for a VSTGUI frontend. This guide only covers building VST 2.x plugins, as the VST3 SDK is not very widely supported yet. Note that Steinberg’s website is a bit confusing and it is easy to accidentally download the wrong version of the SDK, so double-check to make sure that you have the 2.4 SDK.

Download required packages

Steinberg’s VST SDK, which requires you to make a free Steinberg Developer account.
Microsoft’s Visual C++. This guide uses the 2010 Express edition, as it was the latest version at time of writing.
Libpng and zlib (optional)

Install Visual C++

If you already have a working installation of VC++, you can skip this step. Otherwise, download VC++ and install it. The standard installation should be OK, but you

Vst Waves How To Unistall Specific Plugins