Komplete Kontrol N - plugin scan crash [Feature Request]

Dooby
Dooby Member Posts: 3 Member
edited February 24 in Komplete Kontrol

I'm aware of the official method of resolving plugin crashes - move the plugin and scan again. I've noticed the new plugin scanner seems to hang on WebView2Loader.dll, which isn't a VST at all, but part of the WebView2 SDK. Universal Audio happens to put this in the same directory as their VSTs, which causes Komplete Kontrol and Maschine's plugin scan to hang.

Moving plugins out of the way is a rather clunky way of dealing with this. It would be better to first check whether a .dll file is indeed a valid VST, then move on if not.

For plugins that are VSTs, but simply do not return quick enough, it would be nice to have the option to at least skip, or even better, have some kind of timeout, and a method for blacklisting the same.

Are there any plans to improve the scanning of plugins?

Tagged:

Answers

  • Jeremy_NI
    Jeremy_NI Administrator, Customer Care Posts: 14,209 admin

    @Dooby So after movig this dll file, everything is functional again?

  • PoorFellow
    PoorFellow Moderator Posts: 6,464 mod
    edited February 24
    https://community.native-instruments.com/discussion/42758/komplete-kontrol-n-plugin-scan-crash-feature-request

    Actually then all Komplete Kontrol needs for that to happen is the ability for users to select and add individual DLL and VST3 to a 'skip when scan' list in the setting interface. @Chris_NI , such a feature sounds as could be relatively easy added ?

  • Dooby
    Dooby Member Posts: 3 Member
    edited March 22

    @Jeremy_NI, so I tried moving all 180 WebView2Loader.dll files, then it started hanging on other VSTs. These WebView2Loader.dll files are part of various plugins' dependencies within the VST folder, and aren't VSTs. They should be skipped as VSTs should be identifiable.

    I moved other DLLs out, but it kept failing, and it'll take me hours to get it working this way, so giving up on the plugin scan.

    The old version of Komplete Kontrol used to spawn a ScanApp child process, but the new version seems to call ni-plugin-info, and handle a lot of the processing internally - I'm guessing as some thread. I used to be able to get Komplete Kontrol working by terminating ScanApp, and then it'd move to the next plugin. A hang now requires manual moving of plugins.

    If I press Escape, it stops the scan, which at least gets me out of the situation.

    The new version of Maschine 3 appears to fix its own plugin hanging issues. This is in the latest changelog. The scan it ran today went without a hitch, whereas before, it would fail in a similar way to Komplete Kontrol. It would be nice to see the fixes made in Maschine 3 added to Komplete Kontrol.

    Just for the record - no other VST host on my machine has issues with VST scans.

  • Jeremy_NI
    Jeremy_NI Administrator, Customer Care Posts: 14,209 admin
    https://community.native-instruments.com/discussion/comment/217726#Comment_217726

    The same fix that came with Maschine 3 is coming to Komplete Kontrol soon. It's already available in the beta. If you wish I can send you this beta version for you to check. Let me know.

Back To Top

Categories