What does scanning VST plugins actually mean?
-
- KVRAF
- 6155 posts since 4 Dec, 2004
In Studio One the first scan is a full scan and if you have a kazillion plugins it will take awhile. It (like all others I would suppose) stores all of that info.
After that (as chk01 suggested) starup scans are just "quick checks", and will add any new plugins. I keep "Scan at Startup" turned off because you can click Update Plug-Ins at any time to scan in new plugins.
After that (as chk01 suggested) starup scans are just "quick checks", and will add any new plugins. I keep "Scan at Startup" turned off because you can click Update Plug-Ins at any time to scan in new plugins.
-
- KVRian
- 964 posts since 16 Feb, 2005 from USA
Ok nice. I will turn that off. It’s probably the problem.LawrenceF wrote: ↑Tue Sep 10, 2019 3:42 pm In Studio One the first scan is a full scan and if you have a kazillion plugins it will take awhile. It (like all others I would suppose) stores all of that info.
After that (as chk01 suggested) starup scans are just "quick checks", and will add any new plugins. I keep "Scan at Startup" turned off because you can click Update Plug-Ins at any time to scan in new plugins.
- KVRAF
- 11001 posts since 15 Apr, 2019 from Nowhere
If that doesn’t work, it could be a corrupted cache that is causing a full rescan each time you start it. Not sure if the process to delete the cache, so if you have the issue still, maybe someone can provide guidance to do that.stash98 wrote: ↑Wed Sep 11, 2019 1:54 pmOk nice. I will turn that off. It’s probably the problem.LawrenceF wrote: ↑Tue Sep 10, 2019 3:42 pm In Studio One the first scan is a full scan and if you have a kazillion plugins it will take awhile. It (like all others I would suppose) stores all of that info.
After that (as chk01 suggested) starup scans are just "quick checks", and will add any new plugins. I keep "Scan at Startup" turned off because you can click Update Plug-Ins at any time to scan in new plugins.
-
- KVRAF
- 3368 posts since 2 Oct, 2004
You would think they would put that information in some sort of separate XML file attached to the VST DLL. To speed up the scanning process. The current way scanning is done can lead to crashes and all sorts of strange behaviour.Xenakios wrote: ↑Fri Aug 30, 2019 4:14 pm It looks for new or modified plugin binary files. When it finds one, it loads the plugin and gathers information like plugin and developer name, whether the plugin is an instrument or an effect and so on. Because it needs to load the plugin to get that more detailed info, the scanning process may take a long time because plugins can be slow to load due to copy protection, loading audio files etc...Correctly working hosts should cache that information and avoid rescanning the plugins.
Like was mentioned above, just going through all the files in the plugin folders can itself become a slow thing if there's also a ton of audio files, presets or something like that in those folders. (Operating systems may have fast functions for searching only files of a certain type etc, but not all hosts may be using those functions.)
Orion Platinum, Muzys 2
-
- KVRian
- 1265 posts since 9 Sep, 2005 from Oulu, Finland
Well, it's too late for that now. There are already thousands of VST2 plugins around that don't have that.
- KVRAF
- 11001 posts since 15 Apr, 2019 from Nowhere
Yep. It would involve changing or creating a new standard, along with all the baggage that usually entails.
-
- KVRAF
- 3251 posts since 30 Dec, 2014
The problem with turning off scanning in Studio One for example is that, whenever you added plugins, you often forget that you've turned off scanning and thus you wonder why the plugins don't show up whenever you go look for them. There should probably at least be a temporary flag to remind you that any new ones have been added even with plugin scanning off.
KVR S1-Thread | The Intrancersonic-Design Source > Program Resource | Studio One Resource | Music Gallery | 2D / 3D Sci-fi Art | GUI Projects | Animations | Photography | Film Docs | 80's Cartoons | Games | Music Hardware |
-
- KVRAF
- 2348 posts since 9 Oct, 2008 from UK
-
- KVRist
- 34 posts since 8 Sep, 2019
-
- KVRAF
- 3368 posts since 2 Oct, 2004
Why would a developer include wrong information with their VST?
Orion Platinum, Muzys 2
- KVRAF
- 2862 posts since 8 Dec, 2008 from Global Cowboy
At KVR "scanning plugins" has a whole different meaning...
Around these parts,it's when someone is perusing the plugin offerings on the web and then,quite often handing over money to use those plugins,so that they can feel a great sense of satisfaction and see a small decline in their GAS levels for a minute or two
Around these parts,it's when someone is perusing the plugin offerings on the web and then,quite often handing over money to use those plugins,so that they can feel a great sense of satisfaction and see a small decline in their GAS levels for a minute or two
No auto tune...
-
- KVRist
- 34 posts since 8 Sep, 2019
why should anyone copy text and info by hand which could as well read out from the document itself?Why would a developer include wrong information with their VST?
it is really easy to introduce typo´s e.g. with the unique ID or even the name, or accidentially claim an instrument would have 2 inputs.
or you update your plug-in from version 2.0.1 to 2.0.2, change something in the VST realm (for example fix a bug) but forget to change the filename, the ID, or the description xml.
validation is a process which should make SURE that THIS file works with THIS host or fullfill specs or whatever. errors can here only be avoided when you scan stuff in question live, not supply meta data.
scanning often checks for double files and stuff like that. which xml belongs to which file if there is a double?
- KVRer
- 28 posts since 27 Jun, 2016
In Cubase and Windows, a nice trick to speed-up the initial scanning process is to add to the whitelist in Windows Defender both the VST Plugin folder and the Cubase .exe file.
After doing this, I can start now Cubase in seconds, when before it was taking at least 2 minutes - all because Windows Defender was scanning every single VST called up by Cubase on start up.
This might work for other DAWs, it´s worth trying!
After doing this, I can start now Cubase in seconds, when before it was taking at least 2 minutes - all because Windows Defender was scanning every single VST called up by Cubase on start up.
This might work for other DAWs, it´s worth trying!
-
- KVRAF
- 35436 posts since 11 Apr, 2010 from Germany
Lol. I use Defender as well, but... it's a really slow antivirus. Slower than any other i tried. It takes 5 or 6 times as long to scan files. I really hope Microsoft will improve the speed at some point.JulsnJVM wrote: ↑Sun Sep 29, 2019 10:58 am In Cubase and Windows, a nice trick to speed-up the initial scanning process is to add to the whitelist in Windows Defender both the VST Plugin folder and the Cubase .exe file.
After doing this, I can start now Cubase in seconds, when before it was taking at least 2 minutes - all because Windows Defender was scanning every single VST called up by Cubase on start up.
- KVRer
- 28 posts since 27 Jun, 2016
I´m OK with Defender, it keeps my DAW protected without having to bother about it. That is, as long as it doesn´t interfere with DAW work. I mean, why does it have to re-scan the VST files on every single startup? lol
The whitelist trick solved that for me, hope it helps others!