I then set Reaper’s VST Plugin path to the WaveShell-VST 9.3_圆4.dll file (it is in the Waveshells folder). It automatically is installed in C:\Program Files (x86). I installed Waves on the computer without any problem and activated my license. For most posters this fixes the problem and they can use their Waves plugins (but most have been using earlier versions of Waves – not version 9.3, which I am using). I know that Reaper is not supported by Waves but I have read dozens of postings involving problems with Reaper and Waves which are generally resolved by pointing Reaper’s VST Plugin path to the WaveShell-VST 9.3_圆4.dll file. I am running Reaper on a Windows 7, 64-bit machine. I hope someone might be able to help me with a similar issue that I am having with Reaper not seeing the Waves API-550 plugin.
and that may have been the issue all along with the 3 Waves plugs.Īt any rate, all 3 of my current Waves plugs now work fine (Bass Rider, API 550 EQ and S1 Stereo Imager. but then again, I hadn't tried clear cache/rescan yet. I also did roll back however to Version 9.5 (V9r18) after purchasing the API EQ and getting the newer V9.7 (V9r19) and having the issues. it's clearly an issue with "clear cache/rescan". ( Program Files (x86)/Waves/Plugins/API Bundle/Contents/64.
It seems to me, that Reaper has no problem finding their Waveshells in their normal folders that load up when you allow their chosen path.
they always mention that Reaper is not supported, but then they go on to help me out. I will say that due to my multiple purchases from them, they have been much more helpful as of late with me.
could not get it to load up in the list, and as someone mentioned above, until I pressed "clear cache/rescan. last one the API 550 EQ plugin was on sale so I purchased. Had problems over and over with Waves products recently.
0 kommentar(er)
