Notifications
Clear all

Add "Quick VST Scan" option


Lowell
(@lowell)
Trusted Member
Joined: 2 years ago
Posts: 89
Topic starter  

So the more VSTs you get, a full VST scan takes forever when you install some new instruments. And sometimes, the location of where the new VST installed is not obvious so I'd have to look through 4-5 folders to find it in order to manually drag and drop.

Cantabile (live performance app like Mainstage), whenever it starts, does a very quick scan and I see it only ever updating new or updated VSTs. Eventually, it'd be nice to have an option to do a manual "quick scan" that would compare the files in each of the folders against a known file and version list in Unify, and only scan files that have changed in the various VST folders.

Thanks again for the amazing development of Unify!


heyjosh liked
Quote
Topic Tags
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2844
 

Unify also does a "quick scan" and only updates new plug-ins. It does have to actually check the date on each plug-in file, to see whether or not it has changed (this is what it's doing when you see the names flash by very fast), and this is not instantaneous.

I recently learned that many commercial hosts actually run dozens of threads to scan plug-ins more quickly. This is not simple to set up, and as a 1-man shop I must prioritize issues that are more critical (like bugs).


ReplyQuote
Lowell
(@lowell)
Trusted Member
Joined: 2 years ago
Posts: 89
Topic starter  

@getdunne Oh, OK. Some of the plugins don't go by fast at all, but most do. It's like Unify is checking them to see if they connect/work or not, not just checking ones whose file date has changed, or for only new ones. It's not a really big deal as I only have to run a scan when I get new VSTs and if I don't quickly know where they got installed.

I have roughly 260 plugins that show up in Unify and between VST2 and VST3 individual scans, it takes about 3min on an 8th gen Core i7, NVMe SSD to do the scans.

Testing with Cantabile, which identifies 222 plugins, it takes about 7 seconds to scan on startup.

Again, not a really big deal, and if you're already scanning as optimally as possible for now that's great. I don't need to scan on startup every time anyway. There are a few plugins where Unify sits for 20-30 seconds so I'm probably going to remove them. I don't use them anyway.


ReplyQuote
mschiff
(@mschiff)
Member
Joined: 1 year ago
Posts: 317
 

@getdunne 

Would it be possible to have an option to JUST add the new library and not check everything else? 

I am addicted to plugins 😉 , so it takes a VERY long time even when just adding a new library when I know nothing else has changed. 


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2844
 
Posted by: @mschiff

Would it be possible to have an option to JUST add the new library and not check everything else? 

I am addicted to plugins 😉 , so it takes a VERY long time even when just adding a new library when I know nothing else has changed. 

[emphasis mine]

The next release of Unify will include optimized patch-database rebuilding when adding new libraries. Note the speed of rebuilding the patch database has nothing to do with the number of plug-ins you have. The latter affects the known plug-ins list, which has no connection with the patch database whatsoever.


ReplyQuote
mschiff
(@mschiff)
Member
Joined: 1 year ago
Posts: 317
 

So is it the number of libraries that is the issue with the patch database?


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2844
 
Posted by: @mschiff

So is it the number of libraries that is the issue with the patch database?

Yes, or more specifically, the number of patch files (.upf.unify). Each file already referenced in the patch database must be checked to see if it has been updated or deleted, and then every file is checked to see if it is already in the database or not, and if not, it will be read and partially parsed to create a new database entry.

The next version of Unify will include a new change, whereby only the library (or libraries) affected when unzipping a .guru file will be examined, resulting in a much quicker scan.


thsve liked
ReplyQuote
Share: