Bassfaceus Posted August 25, 2020 Share Posted August 25, 2020 without scanning all of them...which for some of us can take a couple of min or more. hello all....stuck in stage 4 covid melbourne with 8pm curfews is frustrating enough but having to scan all my vst ees to just add one is fairly irritating as well is there in way around this? Link to comment Share on other sites More sharing options...
martsave martin s Posted August 25, 2020 Share Posted August 25, 2020 (edited) it's not supose to scan already scaned plugins Edited August 25, 2020 by martsave martin s Link to comment Share on other sites More sharing options...
Bassfaceus Posted August 25, 2020 Author Share Posted August 25, 2020 thanks for that.... but all ive got in the dialog box is rescan failed plugins...which i assume a NEW plug in does not qualify and Rescan all plug ins i cannot work out how to scan for newly installed plug ins ONLY Link to comment Share on other sites More sharing options...
Songroom Posted August 25, 2020 Share Posted August 25, 2020 Deselect both 'Rescan failed plugins' and 'Rescan all plugins' then click 'Scan' Link to comment Share on other sites More sharing options...
Fwrend Posted August 25, 2020 Share Posted August 25, 2020 These are my settings and Cake only scans new and/or updated plugs. Link to comment Share on other sites More sharing options...
lapasoa Posted August 25, 2020 Share Posted August 25, 2020 When you add a new plug - in and you open a project, by deafault Cakewalk immediately scans the new plug - in. Link to comment Share on other sites More sharing options...
scook Posted August 25, 2020 Share Posted August 25, 2020 Yes, both "rescan" options should be disabled. These options are designed to be used sparingly. Neither should be left enabled. When these are disabled previously scanned plug-ins are skipped by the scanner EXCEPT for Waves. I do not use Waves plug-ins but it is my understanding because of how they are implemented the scanner must scan them in addition to any new plug-ins. Link to comment Share on other sites More sharing options...
Matthew Sorrels Posted August 25, 2020 Share Posted August 25, 2020 Any VST plugins that are using the VST shell feature (like Waves and a few others) have to be scanned every single time you start if you have the automatic background scan on. With a shell plugin the actual plugin is another file, the DLL the host (like Cakewalk) talks to is just a shell. The actual plugins can be changed/updated without any visible change to the shell DLL itself, so hosts have no way of knowing if anything has changed. So they pretty much all scan the shell plugin completely every time. Wish they could make that an option so that if the shell date hasn't changed to not scan it. Link to comment Share on other sites More sharing options...
micv Posted August 25, 2020 Share Posted August 25, 2020 thanks for the explanation. For me for the longest of time I don't understand why some plugins get re-scan and most don't. Now I know. Link to comment Share on other sites More sharing options...
Bassfaceus Posted August 26, 2020 Author Share Posted August 26, 2020 Thanks everybody...now all i have to do is remember this next time i install a plug in.. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now