Notifications
Clear all

Can't complete plugin scan

15 Posts
2 Users
1 Likes
156 Views
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
Topic starter  

I have a lot of plugins on my machine..not sure how many.,..hundreds...maybe a thousand?  A lot.  Anyway, I can't get Unify to complete scanning.  It will scan a while, then quit and go back to the beginning again and rescan everything all over again until it sometimes reaches a little further before starting over again...etc..  I let it run all night over night for 12 hours, it was still spinning in this loop in the morning...and so far half the day today..still can't complete the scan.  One of the plugins FL Studio, seems to block it completely, it doesn't loop back to the start it just hangs there 72% done and I guess I can try to disable it and go again..but still...it should not take so many hours to get through the scan.

Is there something I am doing wrong or can something be done about the way JUCE scans plugins so that if it goes back to the beginning again, I presume because of a crashed validation or something..it doesn't have to go back through the whole list all over again..can't it keep track of what has been done already in a better way so that scanning can happen within minutes instead of days?

Note I have exactly the same problem with another JUCE based product, Kushview Element, which goes into the same looping behavior, so I am just guessing you are both using some built in JUCE functionality that is somehow coded in a bad way for this kind of problem.  With only a few plugins on the system its probably not too bad but with many on the system it turns out to be hours and hours of scanning and even after 24 hours of futzing around I'm still not totally scanned.


   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

@dewdman42

See this manual page for details: https://pluginguru.net/unify/manual/doku.php?id=scanning

can something be done about the way JUCE scans plugins so that if it goes back to the beginning again ... it doesn't have to go back through the whole list all over again.. can't it keep track of what has been done already

Unify's plug-in scanner does keep track of what it has done, and when it "goes back to the beginning", it just quickly displays each plug-in's name; it does not attempt to re-load the ones that scanned correctly already. There are a few rare plug-ins that will trip up Unify's scanning (and also some other JUCE-based hosts such as Element), and it seems you've run into one or more of them.

The manual page suggests a few strategies for isolating the problem plug-in. What operating system and version are you using? I may be able to provide better help once I know that.


   
ReplyQuote
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
Topic starter  

I have no idea how to tell what plugins out of 1000 that would be causing the problem.  The rescan is not quick for me due to the number of plugins.  as I said..ran it more than 12 hours in a loop, cannot finish.  Is there a log file I can inspect?

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

Posted by: @dewdman42

Is there a log file I can inspect?

If you're on Windows, put %appdata%\PlugInGuru into the address bar of an Explorer Window.

If you're on a Mac, look in /Library/Application Support/PlugInGuru.

Zip up whatever files you find there, and attach to a comment here so I can study them.

 


   
ReplyQuote
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
Topic starter  

THanks, I will look into that later tonight.  

 

By the way, today I did my entire scan of all three plugin formats using DDMF MetaPlugin, which is also based on JUCE, it ran the entire scan within minutes...it did not loop back to the beginning even once.  It does pop up a dialog if some plugin is taking a long time, asking me if I want to skip it.  But otherwise..no crash, no repeat, no loop around, and all three scans completed I less than 30 minutes.....FWIW..  which is about what it takes all my DAW's to scan all my plugins...also problem free....well DP can have some issues also...


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

@dewdman42

Maybe make a list of the plug-ins that DDMF's scanner reports as slow to respond, and try taking those out of your plug-in folder before trying Unify's scanner again.

Plug-in scanning is a very error-prone business. I could spend months just making a better scanner, but there have always been more urgent priorities.

As noted on the manual page, we recommend performing a full scan only once, and then adding new plug-ins one at a time right after installing them.


UPDATE: I just bought DDFM MetaPlugin and tested on my PC. (I will test on Mac later.) Their plug-in scanner is very good. I was able to locate its list of scanned plug-ins, which is basically identical to what Unify uses. If you are interested, I can walk you through copying MetaPlugin's scan results into Unify's PluginList.xml file, so you can skip doing a full scan with Unify entirely. Please tell me (as I asked several comments ago) whether you are on Mac or PC.


   
ReplyQuote
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
Topic starter  

Mac


   
ReplyQuote
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
Topic starter  

I will say this also in case it helps, last night I was also able to get kushview element to scan everything in a reasonable time, it provides three scanning menu buttons, one for each format Au, vst and vst3; just like unify.  Previously when I used that in kushview it also did the same behavior as unify of being stuck in a loop where it goes back to 1% finished over and over again.   However kushview also has a single “scan” button which I didn’t try before.  I tried that button and this time it behaved even better then ddmf, scanned everything in a few minutes without prompting anything.

anyway I do think the built in scanning provided by juice must be flawed in some way.  Not sure what they did to go around it.  Kushview is open source in case you wanna see what they did fir that scan button

This post was modified 3 months ago 2 times by Dewdman42

   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

@dewdman42

I'll have to get back to you about Mac, later tonight or tomorrow. I'll be tied up for the rest of the day.

In the meantime, look in ~/Library/Application Support for a DDMF or Metaplugin folder, and for a Metaplugin.settings file in there. (On my PC, there's a "64" at the end of "Metaplugin" so look for anything similarly-named.) That .settings file is an XML text file, and the scan results are in the VALUE tag that looks like this:

<VALUE name="knownPlugins">
...
</VALUE>

Unify keeps its equivalent in ~Library/Application Support/PlugInGuru/PluginList.xml, where you'll find a similar VALUE tag. If you're feeling adventurous, try copy-pasting the data from Metaplugin's .settings file into that one.

  • Make a safe copy of Unify's PluginList.xml file before changing anything, so you can recover if necessary.
  • Make sure no instances of Unify (app or plug-in) are running when you edit the PluginList.xml file.

If you're not comfortable editing XML files manually, zip up both files, attach to a new comment here, and I'll do the edit for you.


   
ReplyQuote
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
Topic starter  

I will have a look at that day.  presuming both products are using a JUCE-generic file there, that could be useful.  Kushview must have a similar thing lurking around somewhere also, but after scanning it all in Kushview, there were still dozen or so plugins that were skipped, and then I was able to load them into Kushview element anyway and they seemed to work and are on Kushview's list but were probably not actually validated, etc..  So I don't know which would be the best product to scan all my plugins..hehe.  Anyway I'll poke around today.  I left another scan running last night for Unify over night, ran 12 hours and still scanning this morning in a loop on just AU's


   
ReplyQuote
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
Topic starter  

XML looks to be the same, but the DDMF version is not including

hasARAextension

Probably DDMF is not using the same version of JUCE that you are in unify...so..that is probably the discrepancy..which may or may not matter reading it into Unify...not really sure right now, I will back up these files and give it a try though.


   
ReplyQuote
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
Topic starter  

well I tried to copy and paste just the one VALUE element, knownplugins....  but when I then opened Unify it was not showing the much longer plugin list at all...so....  There must be something else to change somewhere.  I did make sure Unify was not running when I did it unless JUCE has some other background process lingering around I need to stop also or something.  there must be some other cache somewhere.

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

Posted by: @dewdman42

well I tried to copy and paste just the one VALUE element, knownplugins....  but when I then opened Unify it was not showing the much longer plugin list at all...so....  There must be something else to change somewhere.  I did make sure Unify was not running when I did it unless JUCE has some other background process lingering around I need to stop also or something.  there must be some other cache somewhere.

Unify has no "other cache". (MacOS does use a cache for AU plug-ins, but that's probably not relevant here.)

If you zip up the Metaplugin .settings file and the Unify.settings file and attach here, I'll do the edit for you. Editing XML manually is very error-prone.

 


   
ReplyQuote
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
Topic starter  

Thanks for offering that.  So I tried one more thing, I removed all plugins from Unify using the menu options to do that, and rescanned.  this time everything scanned fine, it only looped around 2 times...all three plugin formats scanned within 15 minutes or so...and i'm good, only half a dozen didn't pass validation ultimately.  So the key was getting rid of some old XML entries that way I guess, or resetting Unify back to a clean and empty state..then somehow it scanned through no issue.

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

@dewdman42

This is really good news. Thank you for letting us know.

Unfortunately, the JUCE plug-in scanning code remains somewhat opaque to me. There's a lot I don't understand about it. I wish I knew more, or had the time to delve deep enough into it to figure it out thoroughly, but here we are.


   
Dewdman42 reacted
ReplyQuote
Share: