I know there has been communication about the VST3 and possible other compatibility issues (possible intermittent crashes etc.) But can't speak as to what depth the effort might be. "Certified" means little to me except that perhaps more testing has been done. VST3 testing in MX9 is ongoing.… I am personally testing some now. If given the option, install the VST2 versions. VST3 appears to be giving problems in multiple DAW's at this time. 40 Waves titles work for me so far in Mixcraft.įor MX8 users, I suggest not bothering with the VST3 option during installation. Its a bit of an odd setup.īut as previously stated in another thread, all but one of approx. But yes, the installation issues persist. IE: don't move things around trying to "fix" the installation. Jus' sayin'Īs stated, don't "mess" with the installer. If and when that happens they may lose a lot of customers. This may at some later time become a problem as some new titles are produced that may require the new version. You can however install most new Waves plug-in purchases on your old version. Waves plug ins with expired update plans may not work if you update to a new Waves shell version. Second, these updates are problematic if like me, (and apparently many users) you don't keep up with your Waves update plans. I would suggest avoiding the update to Wave v11 at this time.įirst, (from what I understand) its primary change is to support Mac OS Catalina (Blah blah.) which apparently is causing widespread havoc with plug-in producers. (I have it installed, but have not yet had occasion to actually use it, so I cant speak to its functionality)īTW: I also suspect its a heavy hit on the computer resources. I THINK it is also VST3 only, which MAY be a problem in MX8. So if you can't get the plugins to work in Studio One after the above instructions, try reinstalling your Waves Licenses through the Installer/Manager.Plug in is 64 bit only. Before the Studio One fix, I did request to reset my licenses in the Waves Installer/Manager by sending ALL licenses to the Cloud and then reinstalling back to my computer. Apply/Save the settings and rescan in Studio One. C:\Program Files (x86)\Steinberg\VstPlugins\Waves\JJP-Strings-Keys.bundle\Contents\Win32ģ. C:\Program Files (x86)\Steinberg\VstPlugins\Waves\Abbey Road TG Mastering Chain.bundle\Contents\Win32 I added a new file location for EACH of the plugins that were missing by including the "Contents" folder in the path: At the home/start screen in Studio One, select the Locations tab and the VST tab up top.Ģ. Here's how I got the new ones from Waves to show up in Studio One:ġ. All the older ones worked, but these last 2 refused to show up in Studio One plugin scanner. Hi All, I also got Abbey Road and JJP Strings/Keys as a Christmas gift and was having the same problem. I think suggestion number 2 could be worth a try. The plugins then appeared in Studio One as they should. Rebooting the PC and then moving the licences back down to the PC. The last time I had this issue I resolved it by moving all my Waves licences back up to their cloud. Launch AUDACITY, create a new session with a Supported Sample Rate and try to load your Waves plugins. Go to Waves Audio and drag the Preferences folder to your desktop (this folder can be removed after troubleshooting is over). I have found that to overcome this I need to remove every last scrap of Waves from the PC, Then do a full reinstall of Waves Central. Press the Win Key R, type in appdata and hit Enter. or is it a reinstall with the new plugins? My experience has been that Waves seems to do wonky things when I do an upgrade or reinstall. Is this the first time you have installed Waves in the PC?. These solutions assume you have already set and checked the file location settings in Studio One. I am sorry that I cannot give you a definitive solution but I can offer two suggestions that have worked for me in the past. It has happened when I have purchased a new Waves plugin and have needed to reinstall Waves Central.
0 Comments
Leave a Reply. |