scanning individual plugins or a range of plugins?

badibeat

It takes currently some 30 minutes to scan all my plugins, with ScanApp3 crashing about three times. It would be extremely helpful to be able to scan individual plugins or ranges of plugins to isolate and disable a misbehaving / outdated plugin and to scan only the freshly updated plugins.

I was trying to go through the crash report and the currently open files of ScanApp3 (Mac), but this wasn't helpful to isolate a plugin.

Or is this already possible and I missed something?

JesterMgee

Not missing anything, requests to have more useful info for the scanning has been requested for years.

Usually the issues stem from a flakey plugin or sometimes due to a plugin not being registered. I have never had the scanner crash but have had it take considerable time initially.

First I would suggest check your plugin settings in the KK app and remove all paths other than your main VST3 path for mac, forget VST2 now. I have helped some people that said it constantly crashes or scans for hours only to find they decided to just add their root OS drive as a scan path so it scanned every file on their system 😏

Clean up your plugins. Often people have a literal trash bag of plugins with old demos, ****** free plugins they "may use some day", get rid of everything that is no longer used or activated as a start.

You can then simply grab half your plugins in the VST3 folder, move them out, start KK and see if it still crashes. If not, copy some more back in and try again. That is the only real way to nail down these issues.