Notifications
Clear all

Scan process sometimes starts all over again after detecting a 'bad' plugin

11 Posts
4 Users
3 Likes
2,403 Views
(@rainbro)
Eminent Member
Joined: 4 years ago
Posts: 29
Topic starter  

Hi there,

and congrats for this fine plugin!

Want to report something to improve within the next versions. I found that the plugin scanning process does not always skip bad plugins (like almost all of the Izoptope ones, surprise) but restarts its job from scratch again and again and again sometimes (ABL Pro for example and some of the PluginAlliance stuff). I could help myself by dragging the faulty apples out of my VST-folder but this isn't the best solution as you can guess.

Other than that everything works fine, that's why I stop here and go back to creating beautiful patches. ๐Ÿ™‚

Best,
Rainer

Edit: Just saw that this problem is already mentioned in the troubleshooting section.


   
Quote
Topic Tags
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

This is perhaps the most serious technical issue we're facing right now, and I'm sorry it's giving you trouble.

Tracking down the cause is difficult, because I can't actually reproduce it on any of my computers here. Rest assured that I'm working on it, though, and I hope to have a solution soon.

-shane


   
ReplyQuote
(@rainbro)
Eminent Member
Joined: 4 years ago
Posts: 29
Topic starter  

No worries, just reporting to help iron things out.

Btw, the PluginAlliance-stuff worked using the drag'n'drop-method, but I can confirm that both ABL Pro and ABL ProFX don't work. Their latest release is from 2015 so I think AudioRealism won't update it anymore.


   
ReplyQuote
FrankSaraceno
(@franksaraceno)
Member
Joined: 4 years ago
Posts: 12
 

@getdunne

Hi Shane,

On windows 10, Unify, I successfully scanned about 600 plugins including the the infamous waves waveshell.vst3.

With my crazy collection of plugins, I always get pluginscanner crashes (usually in all my vst hosts) but I ran Unify scan several times and eventually Unify pulled everything in. I know in windows you can check the windows event log and it can list the offending .dll (vst).ย  If you need any help tracking anything down, please feel free to contact me, also a software engineer for 35 years and I absolutely love what you and John are creating here.

Congrats on a very successful version 1.0!!

-Frank


   
notebynote and mj_prod reacted
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

Thank you all for your patience. I think I now know why, on some computers, the PlugScanner app gets stuck repeatedly on the same plug-in, and I'm working on an update.

ย 


   
mj_prod reacted
ReplyQuote
(@notebynote)
Eminent Member
Joined: 4 years ago
Posts: 24
 

Hi @getdunne / Shane,

did you meanwhile worked on that topic? Iยดm asking because there is still the same annoying behaviour in 1.0.12 on Mojave. Any news?

ย 

cheers, Thomas


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@notebynote

The issue of Unify's scanner getting stuck at the same plug-in over and over should be gone by now.

ย 


   
ReplyQuote
(@notebynote)
Eminent Member
Joined: 4 years ago
Posts: 24
 

@getdunne I will do a little video to show you what I mean to prevent misunderstandings.ย 


   
ReplyQuote
(@notebynote)
Eminent Member
Joined: 4 years ago
Posts: 24
 

@getdunne, have a look to the video. As you can see the scanner starts scanning several times and always a bit more than before.

https://www.dropbox.com/s/69lgu7j6fn8011l/Bildschirmaufnahme%202020-04-09%20um%2019.01.13.mov?dl=0


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@notebynote

Thank you for the video. It shows perfectly normal behavior:

  • A few plug-ins cause the scanner program to crash, but Unify re-starts it automatically.
  • Each time it restarts, it quickly shows the names of the plug-ins it has already scanned, then carries on to scan new ones.
  • It remembers the plug-ins that crashed it before, and does not attempt to re-scan them. As a result, it gets further along the list each time, and eventually finishes.
  • When it finishes, it reports the list of plug-ins it couldn't scan properly
    • In your case, Melodyne.vst, EightyEight 2.vst, and Singles FM Piano.vst. These might be 32-bit plug-ins, installed alongside 64-bit ones.

As I said, this is exactly the normal, expected behavior. The scanner may have to re-start multiple times, but it is NOT getting stuck again and again on the same plug-ins, and thus it is able to finish eventually.


   
ReplyQuote
(@notebynote)
Eminent Member
Joined: 4 years ago
Posts: 24
 

@getdunne Yes, in the end evrything is scanned. It just takes time.


   
ReplyQuote
Share: