![]() ![]() Surely when having gigs and gigs of sample libraries in that folder it takes longer to read, because every single file (although not read entirely) needs to be opened to check whether it's a. Sue me for ignorance, but here, reading a VST folder of about 2.3 GB the scan takes about three seconds on startup. and many others a scan could take several minutes if you had a little (maybe even one byte) change in your VST folder, while Reaper just examined the changes instead of the whole folder. Scanning VSTs in Vegas, Soundforge, Cubase. In fact (having worked with a slow computer for a long time) to my experience Reaper (YMMV) is quite fast. The first thing that would come up is the question "Reaper doesn't find my VSTs. It has hundreds of options to en-/disable and it's quite easy to mess things up. I'm not too familiar with FL (anymore) but Reaper is different in many ways. (Of course nothing else works well in FL Studio, but that's another matter. ![]() This is for the same computer and same plugin folder - everything. No scan until you tell it to, and when you do it's quickly done, not like in Reaper. If you keep an eye on where files go while you install things it should be no PITA to change things later. Having executables (which VST-dlls are) and data files in one place generally slows down the system. Sample libraries can get quite huge and would crowd i.e. your system, programs and plugs on an SSD. This is especially reasonable, if you have e.g. 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. 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. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |