Problem recognising Waves Waveshell*.dll plugins

[daxliniere]

Hey all,
I discovered a bit of an issue with Waves plugins (using the stupid waveshell.dll) when the option Preferences>Plug-ins>VST>"Get VST names/types when scanning" is disabled.

Personally, I prefer this option disabled so I can manage my plugins manually, however it causes Waves plugins to not be recognised.

Perhaps REAPER should always 'Get VST names/types when scanning' any waveshell*.dll plugins?


All the best,
Dax.

[dennisnv]

I too have the problem and must evoke the "clear cache and rescan" command to get any newly purchased WAVES plugins to appear in the REAPER plugin inventory. This, however, takes a long time since I have a lot of plugins some of which require my attention during the rescan such as my Korg Kronos VST interface. It seems like a simple code correction in REAPER would save me a lot of down time.

[karbomusic]

Originally Posted by dennisnv

I too have the problem and must evoke the "clear cache and rescan" command to get any newly purchased WAVES plugins to appear in the REAPER plugin inventory. This, however, takes a long time since I have a lot of plugins some of which require my attention during the rescan such as my Korg Kronos VST interface. It seems like a simple code correction in REAPER would save me a lot of down time.

That's a Waves related issue because all Waves plugins flow through that single shell DLL then reaper adds what it gets back to the cache. I don't think reaper has a lot choices in this one that isn't special code just for Waves which would be non-standard and a bit of a hack IMHO.

[ivansc]

Agreed 100%. With waves as it is right now we just have to conform to their idea of whats best and put up with the occasional aggravation. At least nowadays they sorta support reaper and Waves Central seems to have helped immensely.