#Get waves plugins into pro tools 12 install#

settings file but somehow S1 failed at some point to write those two to the. so waves central WAS writing to the Waveshell correctly and S1 was writing before and after to plugins. settings file for RBass and MV2 but they were not there. settings file and all the WavesShells were listed BUT i did a search within the. i cleared blacklist over and over to no avail and even checked that. v10 plugs i bought before RBass and MV2 showed AND v10 plugs i bought AFTER those two showed like the recent ARMC. WOW this makes no bloody sense but it worked for me. If we can duplicate the steps you are doing and it causes the same problem, then we have a repeatable recipe that the developers can test out, thus helping all of us. but ALSO, please post the exact steps you are doing here in this forum so people here can help diagnose the problem. And voila, all my new Waves plugins show up.ДЇor those having problems and that doesn't work, I totally agree you should submit tickets to both Presonus and Waves. Then I ADD the paths back into the Locations box. I then also REMOVE the paths to the VST plugins from the Locations box. My process to get new Waves plugins to show up in S1 4 is to go to Options > Locations and Reset Blacklist, and make sure the 'Scan at startup' option is checked. I just picked up the new AR TG Mastering plugin and had to do this once again.

#Get waves plugins into pro tools 12 install#

Having said that, with every new Waves plugin I buy, I have found that it's important to RESET, RESCAN, REMOVE, and RE-ADD the plugin paths EVERY time I install a new Waves plugin for Studio One. In my case, I have NO problems with Waves v9 and v10 installed on the same system on Win with Studio One 4.1. all that info is invaluable in establishing the pattern and figuring out the potential issues for the developers to address. And some of us are willing to help out those who are having issues and see if we can replicate the problem on our side. I think it's helpful for people to post in a thread like this if they are NOT having a problem as well, granted if they are helpful with the process, because there may be a clue in their setup or process that may solve the problem for someone else. if you drag a Waves plugin onto a track and it doesnвЂ™t launch until you do it a second time thatвЂ™s s related problem that, again, should be reported. but report it!ДЄnother thing to look for if your plugins are working. My inbox at Gearslutz has 16 private messages saying вЂњme too!вЂќ ThatвЂ™s cool and all. please file CS tickets with Waves and presonus. ItвЂ™s off-topic and it clutters the discussion.ДЇor those of you who have-are dealing with this. ItвЂ™s tempting for some to pop into a thread like this to announce that it doesnвЂ™t impact them. The hanging up at startup is largely due to lingering old Waveshell paths, that don't go away, unless you manually remove them, and re clean the new path in Studio One. Then go into S1, startup, and locate the VST folders again. If in doubt, or problem still exists, delete the files/folders again, re load all of your Waves plugins from the waveshell, and once installed (as that will also ensure you have all your suppose to have). The clearing PreAl mentions has always worked for me.

Seems, either Studio One's collecting of Waveshell sources during startup, or Waves own proprietary collecting of its cyber dongle activity slows things down immensely, or even with some users, grinds S1 to a halt at startup. Most any Waves updated from 9.x to 10 have had me re load the Waveshell, then clear past Waveshell folders. clear blacklist, rescan, restart.Дitto, and good advise. PreAl wroteTry remove the folder paths, clear blacklist and rescan, restart, then put them back in. does that impact your suggestion? It seemed like in your original thread the plugin wasnвЂ™t showing up st all that was easy to follow.ДЄlso be advised, studio one is finding the waves plugins, you just arenвЂ™t able to drag them into your track.

IвЂ™ll look tomorrow, but, your referenced threat talks about changing zeros to one. Might also have to search this same file for: Where tag for each one of of those '12' V10/VST3 WAVES plugins? Do you have an entry in your 'ttings' file that looks like this'