Why does Komplete Kontrol Plugin Scanning take so long ?

1235»

Comments

  • trusampler
    trusampler Member Posts: 244 Advisor

    Hi Sunborn,

    I posted here in the forums, to see if anyone else has had the issue, there's plenty of posts with users having these SLOW Scans, while I'm thankful for the replies the only thing anyone seems to offer as advice is , to hit esc/ or remove plugins, none of which are a solution to the MISSING plugins not showing up after multiple scans and rebuilds, so I was hoping someone in the gazillion posts, would have found a solution. Do you see ? This isn't a solution, yet a work around.

    NI Tech support ? I'm still waiting over two months on them to contact me back on my s88 mk3 to be repaired.

    And NO I'm not the only one who has slow scans, or missing plugins not showing up.

    If you're a moderator here, then you know that to not be true. One google search of Komplete Kontrol and Slow Plugin scans, I get at least 20 results before even hitting the forum! The deletion of the registry,reinstall and rebuild didn't fix the issue, that's a complete head scratcher as that'd be as close to a complete fresh install that'd get me.

    My cpu specs are i9 12900k /32 gb ram / windows 11, the specs of my cpu, aren't going to help anyone when it's the software's that's causing the issue.

    Ok I think I get it, there's no real solution other than the WORKAROUNDS ! Got it ;)

  • trusampler
    trusampler Member Posts: 244 Advisor
    edited 11:03AM

    Thanks @ MorrisEd yes that seems to be the only option for me. Cheers

  • Sunborn
    Sunborn NKS User Library Mod Posts: 3,063 mod
    https://community.native-instruments.com/discussion/comment/199451#Comment_199451

    Yes, what you wrote is true, at least for the most part and you did well to post here.

    But what i'm telling you is that:

    -your problem is unique (even if 100 posts talks about slow scans, there are thousands others without that problem)

    -posting here, does not guarantee that a NI employee can see your post, or, even if he sees it, that he will have the technical skills to provide a solution. Most probably he will forward it to NI Support

    -NI Support is not the best, we know it. Not because of lack of good will or knowledge but because of limited personnel (this is strictly my opinion). But if the owners don't hire more people, its their fault, not NI support's personnel. That said, NI Support remains the most reliable source to fix problems (and on many cases, the only source). 🙏

  • Vocalpoint
    Vocalpoint Member Posts: 2,667 Expert
    edited 1:59PM
    https://community.native-instruments.com/discussion/comment/199475#Comment_199475

    The real bottom line issue with this specific problem is payload.

    There is simply no way for NI to test this scanner against every plugin known to man. There are plugins that are well written, standard and professional grade and then there are a whole slew that are not.

    Without a full inventory of every plugin that every user is ever going to scan - it is impossible to troubleshoot.

    From my chair - I was one of these folks that had to sit thru this scan for 20-30-40 secs - sometimes a minute last year with my old DAW. BUT - that was when I thought having 1267 plugins in line was cool.

    When I built my new DAW with today's much more reasonable 411 plugins (as of this morning) - with exactly one remaining VST2 (Absynth) - KK v2.9.6 opens in 5 secs.

    And has opened for 5 seconds since I built the DAW in Jan of 2024.

    So unless someone wants to post up a full list of ALL their stuff - all their plugin paths and whatever else might be part of this - there will be no immediate solution.

    I firmly believe that the actual NI "scanapp.exe" simply cannot navigate poorly written (seemingly modern) plugins. Poorly designed old plugins. Plugins that suddenly need to reach out to their "mothership" as soon as any computing process comes near them or a number of other obscure issues - all of which unfortunately - NI cannot be responsible for.

    It is VERY telling that most us of have zero issues and a very tiny contingent of others have seemingly insurmountable issues - all while we all use the same versions of KK.

    One thing is for certain - KK and it's scanapp.exe are never going to win any awards for efficiency - but if this truly was a rampant problem - this forum (and many others) would be chock full of chaos filled posts as large swaths of users suddenly are waiting minutes to hours for scans to complete.

    That is not happening to my knowledge. So something else must be at play.

    VP

  • trusampler
    trusampler Member Posts: 244 Advisor

    Well thanks guys, I appreciate your help.

  • Sunborn
    Sunborn NKS User Library Mod Posts: 3,063 mod
    edited 2:28PM
    https://community.native-instruments.com/discussion/comment/199483#Comment_199483

    Agree

    https://community.native-instruments.com/discussion/comment/199485#Comment_199485

    There is something else you can do if you have a bit patience. Trial and error.

    Remove everything from your VST folders except NI plugins. Do not delete them or uninstall them! Just move them temporarily in another folder. Scan.

    Then start to add few developers each time. Start with the most reliable. NI partners and plugins with good reputation. Scan

    Leave out anything that interacts with the internet, such as Roland cloud and also "cheap" plugins and old plugins. Put back everything else. Scan. I bet it will be fast!

    Finally, start to add the rest. One developer at a time. Scan each time.

    With this method you can easily identify which plugins take too long to be scanned!

    What you will do next, its up to you. Personally i would throw in the rubbish bin (and i have done this many times!) every old, badly written and problematic plugin (except of the expensive ones of course! 😊)

    Start with the VST2. You do not need them if you have a VST3 version! Unless if you have old projects that still use them and they do not automatically migrated (VST2 to VST3).

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,449 mod
    https://community.native-instruments.com/discussion/comment/199219#Comment_199219

    Maschine 3 just added parallel plug-in scanning. I'd expect that to come to Komplete Kontrol soon-ish. But I defer to @Martin_NI and @Chris_NI as I am now on the Kontakt team and cannot speak directly to the Kontrol team's plans for 2025.

  • Kymeia
    Kymeia NKS User Library Mod Posts: 4,972 mod
    edited 3:03PM

    Parallelising the scan process and distributing it between multiple cores will speed things up for sure but I think what KK and Maschine also need is a plugin manager that can enable users to identify the plugins that have failed, exclude badly behaving plugins from being scanned as well as selectively rescan blacklisted plugins - Logic’s almost perfect plugin manager would be the example to follow imho

    The current plugin ‘manager’ doesn’t really count - it’s really just a plugin menu manager and has no effect on plugin scanning

  • trusampler
    trusampler Member Posts: 244 Advisor
    https://community.native-instruments.com/discussion/comment/199494#Comment_199494

    I'll give this a shot, thanks Sunborn !

  • trusampler
    trusampler Member Posts: 244 Advisor

    Hi Matthew_NI ,

    That's excellent news,yeah I'm on the Maschine beta team, and they work perfectly in Maschine official release as well as beta. So this is great news to hear it's coming to Komplete Kontrol !

  • trusampler
    trusampler Member Posts: 244 Advisor
    edited 5:11PM

    Yes kymeia, that, as well as an option to select plugins by vendor, and not the current plugin list. The current option is not very user friendly at all, and a major Pain to deselect plugins when troubleshooting!

  • trusampler
    trusampler Member Posts: 244 Advisor
    edited 7:07PM

    Ok so here's what I just tried I uninstalled Komplete Kontrol 3.3.4 . I then moved ALL of my plugins out of their respective folders VST3/VST2. I then deleted the Komplete Kontrol database.

    I then reinstalled Komplete Kontrol 3.3.4, had it scan only Native Instrument plugins and rebuild the database.

    I then added my sound toys plugins + NKS to Komplete Kontrol. Rescanned plugins and database.

    It's still not finding the images so I cannot select them inside Komplete Kontrol. It finds the plugins both VST 2/VST3 Soundtoys plugins I can select in the drop down VST folder, but no images are showing up at all, not even blank UI's.

    I then removed all my NKS User Content folder,as well as NI Resources, deleted the database let it do a fresh rescan.

    I then added only the sound toys NKS files back in the User Content folder + my NI Resources

    Still nothing but Native Instruments photo's showing up and Arturia ( these are natively supported ) even though the plugins aren't being scanned somehow, idk ?

    ANYWAYS my point is, UNLESS you can tell me something else I'm doing wrong here. KK 3.3.4 is completely broken here.

    I've tested both freelance and kymeia's sound toys NKS , which I know these NKS files work perfectly, as they're working just fine in Maschine 3x

    NO Clue what to think now as before ! Is there some other trick to completely deleting the database, is there a secret database somewhere ?? Other than the one that NI recommends we trash n rebuild ?

Back To Top

Categories