![]() I'd move the sample libraries outside the VST folder and direct the VST to the folder(s) where I put the libraries. Most plug-ins don't install their libraries into the VST folder by default and the reason for this is to avoid exactly the problem you describe. It should be no problem to re-install the VSTs in question and direct the path somewhere else, for instance to a folder called "blabla-VST_samplelib" or so for each VST. I used to have things like that and it was a pita.Ī "no-scan" option would introduce new problems IMHO. Moving things out and getting paths to work would be a bigger job, and as i mentioned, the main point is to have everything in one place for finding things easily, backup etc. The bulk of it are sample based vst's like Wusik, Sampletank, Dimension etc etc. So I take it there is no option to stop the search at startup? I don't need it at all as I can easily start a search manually after installing something and it seems this is just a matter of a simple switch in a script? I can live with that, much more than moving things all over the hard disks to keep the vst folder size down, as backing up and searching for things will take ages and is a serious hassle (i used to have it like that before Reaper). This is after reboot, a normal Reaper restart takes only a few seconds. It's true startup time is long and probably due to a large VST folder (now 70GB, startup takes around 45-60 sec). But point still remains, how to stop it every time Reaper starts? Ok, searching, not scanning, I guess I sort of knew this but just called it scanning. Yeah thar's the real scan happening only when invoked manually this way or after an update.or when you installed your plug-ins in \REAPER\Plugins or \REAPER\Plugins\FX, those get really scanned thoroughly on every start. The "Clear cache/Rescan VST" function tries to load each plug-in too - so it takes a longer time. It think it doesn't do the former (you can remove plug-ins without the FX browser noticing, not sure if that changed meanwhile) and does the latter on a full scan, or when the file search brought up a new plug-in. ini file are all available and to store their locations. I think that it is done to make sure that the plugins listing in the. That's because your disk cache(s) has to be filled first, basically every file search operation is slower when performed for the first time after a reboot (of course depending a lot on your disk performance). The first one after a reboot is a bit more thorough, subsequent start-up scans are faster (not sure why). Reaper always does a light VST scan on start-up.Īctually it just scans the folder for new files (probably comparing with reaper-vstplugins.ini). Move these things out to their own location outside of your plug-in folder(s). This is a not so great since it slows down the file search considerably. If you didn't install your plug-ins in REAPER's plugin folder, you may have a huge number of files in your plug-in folder, possibly due to having sample libraries etc. Please see below, unless you picked the wrong location for your plug-ins, there is not actually a plug-in scan going on under normal circumstances, just a brief search for new plug-ins to be scanned. I take it you have a slow startup making you ask this question. It's so unReaperish to force something without an option, so I still suspect it's possible somehow. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |