![waves mercury bundle not working with pro tools 12 waves mercury bundle not working with pro tools 12](https://i.ytimg.com/vi/YrJUFj-keIk/maxresdefault.jpg)
- #WAVES MERCURY BUNDLE NOT WORKING WITH PRO TOOLS 12 UPDATE#
- #WAVES MERCURY BUNDLE NOT WORKING WITH PRO TOOLS 12 SOFTWARE#
- #WAVES MERCURY BUNDLE NOT WORKING WITH PRO TOOLS 12 DOWNLOAD#
- #WAVES MERCURY BUNDLE NOT WORKING WITH PRO TOOLS 12 MAC#
Go to Mac HD > Library > Application Support and delete the “ Waves” and “ Waves Audio” folders.Īfterwards, please launch REAPER and re scan again for the plug-ins.Īs a long-time waves user, I’ve been slowly accumulating a collection of plugs prior to this subscription being available.Delete the folder “ Waves” located at HD > Current User > Library > Caches (this folder is accessed by opening the Go menu and holding down the key.
![waves mercury bundle not working with pro tools 12 waves mercury bundle not working with pro tools 12](https://i1.wp.com/www.recordingrevolution.com/wp-content/uploads/2017/03/Stock-Plugins.jpg)
#WAVES MERCURY BUNDLE NOT WORKING WITH PRO TOOLS 12 SOFTWARE#
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).Quit all the audio related software on your Mac.This time there was no crash, and at the end of the scan I had all of the missing plugins.Ĭlean any Waves versions you may have installed: When I loaded REAPER again, I cleared the cache and re-scanned again. The whole process took a couple of hours, but by the end of it all I was back up and running. 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. After trying a couple of things, we were able to remedy the problem with a clean install. When I re-launched REAPER, there was still no sign of the missing VST3 plugins, and MixCentric was one of them. So I decided to clear the cache in the plugins preferences and rescan the plugins folder.Īs it scanned the VST3 plugins from Waves, it stalled at Greg Wells MixCentric. The same plugs would show up in VST and AU formats, which indicated that the plugins were in fact installed on the system. 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. With that being said, here’s what happened: Your best bet is to contact support at Waves or Cockos and see if you can get assistance with the issue. If you’re having issues, there may be other factors that are causing your issues. Note that I’m not advising you to take these steps yourselves. 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. But the problems were neither the fault of Waves or of Cockos. As a long time REAPER user and long time Waves user, I didn’t anticipate any problems.
#WAVES MERCURY BUNDLE NOT WORKING WITH PRO TOOLS 12 DOWNLOAD#
I decided to give this a try and download the Mercury Bundle. Waves recently announced a new subscription plan which allows users to subscribe to their Silver and Mercury bundles. Any clues to solving problems like this are gold. He got through it and I asked him to share the experience to help others in the same situation. Brandon recently went hell with getting his Waves VST3 plugins all into REAPER.
#WAVES MERCURY BUNDLE NOT WORKING WITH PRO TOOLS 12 UPDATE#
In fact, whether you bought your plugins 5 years, 10 years, even 20 years ago – as long as your Waves Update Plan coverage is current, you’ll receive the AAX Native update at no additional charge.ĭon’t forget I saw beta versions of their plug-ins when I was at NAB last month.Guest post by Brandon S. This means you can breathe easy, knowing that the plugins you purchase now will be fully supported today, tomorrow and into the future. Waves would like to take this opportunity to remind our valued users that we are firmly committed to meeting your needs, and are currently working closely with Avid on AAX Native support in time for the Pro Tools 11 release. This is what they said…Īs the release of Pro Tools 11 draws near, more and more users have been asking about Waves support for the AAX Native platform, in accordance with our announcement at this year’s NAMM show. Waves have released an update on their Support site basically to advise users not to panic, they are working on AAX Native plug-ins ready for Pro Tools 11.