What does scanning VST plugins actually mean?

Plug-in hosts and other software applications discussion
LawrenceF
KVRAF
6099 posts since 4 Dec, 2004

Post Tue Sep 10, 2019 7:42 am

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.

stash98
KVRian
765 posts since 16 Feb, 2005 from tittyland

Re: What does scanning VST plugins actually mean?

Post Wed Sep 11, 2019 5:54 am

LawrenceF wrote:
Tue Sep 10, 2019 7:42 am
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.
Ok nice. I will turn that off. It’s probably the problem.

User avatar
Forgotten
KVRAF
3342 posts since 15 Apr, 2019 from Nowhere

Re: What does scanning VST plugins actually mean?

Post Wed Sep 11, 2019 5:57 am

stash98 wrote:
Wed Sep 11, 2019 5:54 am
LawrenceF wrote:
Tue Sep 10, 2019 7:42 am
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.
Ok nice. I will turn that off. It’s probably the problem.
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.

v1o
KVRAF
1822 posts since 2 Oct, 2004

Re: What does scanning VST plugins actually mean?

Post Wed Sep 11, 2019 6:23 am

Xenakios wrote:
Fri Aug 30, 2019 8:14 am
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.)
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.
Orion Platinum, Muzys 2

Xenakios
KVRian
1211 posts since 9 Sep, 2005 from Oulu, Finland

Re: What does scanning VST plugins actually mean?

Post Wed Sep 11, 2019 10:20 am

v1o wrote:
Wed Sep 11, 2019 6:23 am
You would think they would put that information in some sort of separate XML file attached to the VST DLL.
Well, it's too late for that now. There are already thousands of VST2 plugins around that don't have that.

User avatar
Forgotten
KVRAF
3342 posts since 15 Apr, 2019 from Nowhere

Re: What does scanning VST plugins actually mean?

Post Wed Sep 11, 2019 10:44 am

Xenakios wrote:
Wed Sep 11, 2019 10:20 am
v1o wrote:
Wed Sep 11, 2019 6:23 am
You would think they would put that information in some sort of separate XML file attached to the VST DLL.
Well, it's too late for that now. There are already thousands of VST2 plugins around that don't have that.
Yep. It would involve changing or creating a new standard, along with all the baggage that usually entails.

THE INTRANCER
KVRian
1115 posts since 30 Dec, 2014

Re: What does scanning VST plugins actually mean?

Post Wed Sep 11, 2019 12:46 pm

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.
THE INTRANCER-Digital 2D & 3D GUI / Music Artist - Orchestral Trance - Ambient - Film Scores | Soundcloud 27 | Soundclick 16 | Producing Music For 25+Years & Sound Monitoring FOH at UK Stadium/Festivals for Carl Cox, FatBoy Slim ect

jabe
KVRAF
1919 posts since 9 Oct, 2008 from UK

Re: What does scanning VST plugins actually mean?

Post Wed Sep 11, 2019 6:26 pm

Obineg+ wrote:
Sun Sep 08, 2019 1:52 pm
what does scanning mean?

well, scanning means loading:
No.
[W10-64, T5/6/7/W8/9/10, 32&64, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

Obineg+
KVRer
4 posts since 8 Sep, 2019

Re: What does scanning VST plugins actually mean?

Post Fri Sep 13, 2019 4:00 pm

v1o wrote:
Wed Sep 11, 2019 6:23 am
You would think they would put that information in some sort of separate XML file attached to the VST DLL.
a seperate file / meta data could still hold wrong info. only actually reading the file will tell the truth. :)

v1o
KVRAF
1822 posts since 2 Oct, 2004

Re: What does scanning VST plugins actually mean?

Post Fri Sep 13, 2019 7:55 pm

Obineg+ wrote:
Fri Sep 13, 2019 4:00 pm
v1o wrote:
Wed Sep 11, 2019 6:23 am
You would think they would put that information in some sort of separate XML file attached to the VST DLL.
a seperate file / meta data could still hold wrong info. only actually reading the file will tell the truth. :)
Why would a developer include wrong information with their VST?
Orion Platinum, Muzys 2

User avatar
digitalboytn
KVRian
1461 posts since 8 Dec, 2008 from Global Cowboy

Re: What does scanning VST plugins actually mean?

Post Fri Sep 13, 2019 8:51 pm

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 :)
Sorry - I don't use auto-tune....

Obineg+
KVRer
4 posts since 8 Sep, 2019

Re: What does scanning VST plugins actually mean?

Post Sat Sep 14, 2019 1:11 pm

Why would a developer include wrong information with their VST?
why should anyone copy text and info by hand which could as well read out from the document itself?

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? :)

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”