Quote:
Originally Posted by Edgemeal
I'm pretty sure Reaper scans the drives on start to make sure all the VST/DLL files you've added previously are still on the drives
|
Just an FYI that doesn't scan the files as VST, reaper simply asks the OS for the list of filenames that live in the VST folders, so it can check that list against what it already knows about. This is rarely a problem unless the user installs much of or all of their non-VST data (often thousands of files that aren't VSTs) in the same folder structure as the VSTs which should only contain the VST DLLs themselves.
This is the exact reason most commercial VST installers either specifically ask you for where you want non-VST data to go, or automatically places it somewhere other than the VST folder.
Quote:
there and that shouldn't take long at all.
|
Exactly so if it does take long it's because...
1. Too many files that aren't VSTs that it has to wade through.
2. AV or something else being over protective and slowing things down.
#2 shouldn't even be an issue since Reaper is only asking for the list, not loading the files themselves. However, drop 50000 1 byte files into a folder, open it and select all, how long does it take compared to 500? It's the one time in history size really doesn't matter
it's the quantity of individual files and their enumeration.