View Single Post
Old 02-22-2020, 03:56 PM   #11
Transmisser
Human being with feelings
 
Transmisser's Avatar
 
Join Date: Feb 2020
Posts: 9
Default

Quote:
Originally Posted by schwa View Post
Ah, that's actually a clue. It's possible the Slate plugins are not unloading all of their resources properly, so the scan process is equivalent to trying to open all of the plugins at the same time. Eventually some resource limit is reached and the next plugin fails to load.

I know it's a pain, but what I'd suggest is running the scan process until it completes. Then open the REAPER resource path (you can do this from within REAPER: Actions > Show REAPER resource path in finder), and open reaper-vstplugins64.ini in a text editor. The plugins that failed scan will have lines like this:

Code:
whatever.vst=80F57B7D4EACD501
With nothing after the hex code. Delete the failed-scan lines, save the file, and reopen REAPER. The scan process should then skip over anything that already scanned properly, and rescan only the ones that failed. If this theory is correct, you may be able to get everything properly scanned by repeating this process.

You friggin' rule. I couldn't get to the resource path folder through the actions drop down menu, but after some googling I was able to find an alternate way of getting there.

Sure enough though, when I looked in that file those two plugins didn't have the info you were talking about. Deleted them and restarted and they both scanned successfully!

Thanks again for all your help! This was really bothering me.
Transmisser is offline   Reply With Quote