Is there a fix for Komplete Control freezing on scanning plugins?

WilliamAshley

I am just a little confused why plugins that it gets stuck on aren't just skipped and logged as an error in the scanning log such as occurs in daws. Its a little silly to need to hide my vst2 and vst3 folders to even get past the start screen - attempts to actually scan the plugin folders that NKS is suppose to work with are major plugin folders such as VST3. VST3 needs to contain a whole lot of VST3 plugins. When you have thousands of plugins its a little silly to put trouble shooting on the enduser to figure out what plugin is freezing the scan. While more popups can be seen once you are in the plugin there seems to be a buffer or something that fills resulting in the scan process to freeze up completely. During the plugin load screen those pppups arn't even displayed. I'm a little confused why the plugin has been left in such a clearly broken state and why a standard error log for plugins isn't used or the ability to somehow know what plugins are unable to be scanned or for plugins that require authorization or otherwise to popup on the load screen?

Q1. is there an actual fix for Komplete Kontrol being unable to finish plugin scans so that komplete control is usable with plugins?

Q2. Also if NKS only works with certain plugins why don't they only scan for NKS compatible plugins?

I've wasted a few hours running scans today and havn't found a solution. I am very hopeful someone has found a way that Komplete Kontrol can actually complete the plugin scan. Is there a way to turn off scan on load as in other NI scans in the past? I have scanned through posts related to this bug and havn't found an actual solution - currently things like don't scan the folders, or keep looking for the bad plugins just is not sane when there are 5000+ plugin files to scan through. It seems lost on me why they don't just fix the plugin scanner so that errors are omited and bypassed and logged like every other plugin scanning and verification software.

Yearofthegoat

Total re-install of KK did the trick - which might mean that deleting the db was the actual thing. Looking forward to the update, thanks.

Vocalpoint

"I have scanned through posts related to this bug and havn't found an actual solution - currently things like don't scan the folders, or keep looking for the bad plugins just is not sane when there are 5000+ plugin files to scan through"

Respectfully - if you actually have 5000+ plugins installed - I am not sure what you are expecting.

You do not list your machine type, it's hardware, your OS or anything.

For contrast - my DAW is a bleeding edge mid 2024 custom assembled workstation with all NMVe drives, 128GB of RAM and a i5 13th Gen processor - I have exactly 413 plugins and my scantime is 3.2 secs using KK v2.9.6. I do not use any VST2 plugins and all mine are brand name popular usual suspects.

Yes - the KK plugin scan has been the subject of much scorn and ridcule over the last few years and yes the process could be made better - but I can tell you without reservation that it was never tested to plow thru 5000+ plugins in any sort of record time. You will get what you get with this setup.

You have two options - you can either wait it out or lighten the workload - substantially.

VP

Yearofthegoat

Please explain why it gets stuck with just my measly 60-odd? Waited a whole morning - surely it shouldn't take longer than that?!

I have the same issue, KK just hangs scanning. It also hangs in DAWs when trying to use NI's own stuff - Hypha, for example.

This only started to happen with the last 3.4.0 update, as far as I can tell.

Win11 23H2, Ryzen 5900X, 32GB DDR4. Otherwise works perfectly.

Vocalpoint

https://community.native-instruments.com/discussion/comment/214322#Comment_214322

If it is hanging indefinitely - it is probably hitting a plugin that requires authorization and cannot make that connection (for a variety of reasons). Or one that is simply not compliant. I found the more VST2 plugs I had (on my prior DAW) - the more painful the scan times. As soon as I built a new DAW in Spring 2024 and ditched ALL VST2's - scan times went down to mere seconds

And if it is hanging on NI's own stuff - that sounds like a much bigger issue that just KK.

I do not use KK v3.x (yet) so I cannot comment.

Another trick that has worked for me in the past is to simply delete the Komplete.db3 file found here:

C:\Users\Username\AppData\Local\Native Instruments\Komplete Kontrol

And then restart Komplete Kontrol. This will of course take some time but will write a fresh clean DB file which should give you some improvement.

VP

Kymeia

https://community.native-instruments.com/discussion/43043/is-there-a-fix-for-komplete-control-freezing-on-scanning-plugins

Q1 - if the scanapp is hanging on a particular plugin you can try killing the process - it will just restart then and move onto the next plugin

Q2 - Any plugin can potentially support NKS so that would be unrealistic

However I do agree a well designed scanapp (such as has been in Logic for years and also UAD Luna now has a good one too) should not just filter out incompatible or potentially problematic plugins but it should also

• remember them and not keep rescanning them
• list them so the user knows which ones have been causing problems
• enable a rescan on demand such as if the plugin has been updated and no longer needs blacklisting

This is something I have been arguing for, for a long time. I suspect a big part of the issue with 3.4 is NI have actually introduced a redesigned scanapp (the same one that is in Maschine 3) which is actually faster as it multi tasks. However it is unlikely that this scanapp could have been tested with every plugin people possibly have so some degree of getting stuck on plugins should be expected, and also it may be slower on the first scan given it is a new thing. Over time one would hope that feedback about problematic plugins helps make it more efficient, but being able to actually identify those more easily would seem a logical step for development of this app.

I do hope though that the above suggestions get incorporated into making it not just faster but also smarter

However I have no idea why there is a report of KK getting stuck on Hypha as that has nothing to do with plugin scanning so may be a seperate and unrelated issue

Jeremy_NI

Hey there, we should have a hotfix coming for scanning issues, it might help for your issue. It's going to go Beta soon, let me know if you want to try this version and I can send it to you to test when it's ready.

Yearofthegoat

Total re-install of KK did the trick - which might mean that deleting the db was the actual thing. Looking forward to the update, thanks.