Rescan clear cache, one plugin

[G-Sun]

Hi!

Waves waveshell needs clear cache for every new install (new, update, delete one plugin),
and this makes a unnecessary long scan-session with typical error stops (press ok)

Could we have a right-click per plugin, to empty cache rescan for only that plugin.

Thanks!

[DarkStar]

Meanwhile, I do not have any Waves plug-ins but this might work:
-- make a back-up copy of the reaper-vstplugins.ini file,
-- edit the reaper-vstplugins.ini file and remove the Waves line(s),
-- save it,
-- open Reaper and it should detect the Waves plug-ins as new and "deep-scan" only them.

(At your own risk, as I've never tried it.)

[G-Sun]

Originally Posted by DarkStar

Meanwhile, I do not have any Waves plug-ins but this might work:
-- make a back-up copy of the reaper-vstplugins.ini file,
-- edit the reaper-vstplugins.ini file and remove the Waves line(s),
-- save it,
-- open Reaper and it should detect the Waves plug-ins as new and "deep-scan" only them.

(At your own risk, as I've never tried it.)

Yes, that's a nice hack

[jesussaddle]

I have a similar problem. I like to have all my plugins available. But since there are hundreds, periodically one or two become problems. What this occasionally results in is Reaper crashes, and apparently corruption of the Reaper plugins .ini file.

Just now I suddenly have a situation where my omnisphere plugin is missing. I have keyscape, trillian, omnisphere, and Stylus RMX. But omnisphere vanished from the list. When I look in the .ini file its missing from there as well.

My fear is that I need to (and am about to) rescan everything - a 20-40 minute process in which I occasionally need to be present and interact with dialogs. It would be nice to have a workaround. Unfortunately I can't add back in the line from the .ini file since I don't have a backup on hand. But I suppose I will make a back up and do just that sort of thing if a similar situation occurs. We should be able to re-scan a single item only, by pointing Reaper to it via a string of some sort, (e.g. omnisphere) no?

Also, I don't like the way these plugin errors, when severe enough, apparently turn off my Windows machine - if that's what's doing it. I wish there was some way to do it as a sort of test run - and log the error so windows isn't forced to bail. Its happened with plugin scans twice in the last 24 hours.