nsataxi.blogg.se - Waves mercury bundle not working with pro tools 12

HD > Library > Audio > Plug-ins > Components.

Go to the following locations and delete any WaveShell file/s of any version number found :.

Delete “ Waves” folder located in your Applications folder.

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.

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.