Because waveshell VST file usually doesn't change by that there is some problem with your installation of your Waves plugins. As Reaper detects new plugins according to what's changed in VST directories, it doesn't detect anything after adding of new Waves plugins. Instead of that, there is one VST waveshell file, which is just wrapper to actual architecture independent plugins located at different directory. I finally tested the program and actually I'm as pleasantly surprised as everyone else is! I need to calibrate my headphones for a better experience but first I must find a tape measure big enough to measure my headĪctually reason for that is, Waves plugins are kinda special, because they don't use standard one plugin-one file approach.
It still asked for a few Waveshell folders which I cancelled as whichever Waveshell folder I pointed it to it didn't seem to like. I done exactly what you said and restarted Reaper. ini files were located in a hidden folder (within another folder) in my Users folder.
Well Michal, I have to say a big thanks to you for your advice. Second option will force anything in respective plugin folder to be rescanned. open Reaper's preferences, locate Plug-ins/VST and click button labeled "Clear cache/re-scan"įirst option will affect just Waves plugins, which are rescanned at next Reaper's start. Open it in text editor like notepad and remove all lines (entries), where is word waveshell and restart Reaper locate reaper-vstplugins.ini or reaper-vstplugins64.ini (depending on your architecture) at your Reaper resource directory. There are two usual tricks, which might help. I mean, already installed plugins are normally in the available FX list, but new ones aren't displayed there.
Waves plugins are sometimes problematic after adding to the system.
0 kommentar(er)
