Since I do have the choice of having the plugins scanned or not when installing a new release, is scanning itself something that must be done every time a new release of Melda plugins sees the light ? That's 102 of them, takes some time.
I have the choice since I do not run the plugins directly but rather via a OS bridge since I run Linux. Each .dll has an equivalent .so file. The Linux DAWs (Bitwig, Harrison Mixbus32C) are only seeing the .so files. The .dll can be swapped underneath.
I've done w/o scanning for the past two releases and everything seems to be all right. The Melda installation program has replaced all .dll files, the new version number is displayed in each plugin, operation so far is as usual.
Need for a DAW to scan all plugins at each release ?
-
- KVRAF
- 3729 posts since 3 Nov, 2015
-
- KVRAF
- 10376 posts since 2 Sep, 2003 from Surrey, UK
I would think that that depends on the DAW and what it is scanning for.
Here it takes about 15 seconds after a new install, and a few seconds at other times. To be on the safe side I would just let the DAW scan after each new install..
Here it takes about 15 seconds after a new install, and a few seconds at other times. To be on the safe side I would just let the DAW scan after each new install..
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Different hosts are different, for example Reaper's scanning is extremely fast, but Wavelab and Logic are horrific. Either way it is usually nothing you can avoid. They do that to check the specs of the plugins and verify they actually work, usually in some sandboxed way. It's not very needed, but we have to live with that anyways 
.
.-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
Well, as I've mentioned I do have the choice in my case. So I'll keep the non-scanning for a few next releases.
Cheers.