Kilohearts plugins lost then found issue

[MrJubbly]

The KSM v0.2.0.0 correctly identified that v.2.2.4 of installed Kilohearts plugins (VST3) were outdated.

However, after updating Kilohearts plugins to that latest version, this current version of KSM has failed to scan in most of the v2.2.5 Kilohearts' plugins (only 2 were correctly scanned from the complete Kilohearts suite).

First time this has happened for Kilohearts in KSM. Usually, KSM has no problems with Kilohearts' plugin updates.

Most Kilohearts v2.2.5 plugins failed to scan.png

[ Edit ] - After the above result, I decided to run a subsequent scan with KSM v2.0.0 just in case, which somehow? managed to then correctly scan the updated Kilohearts v2.2.5 plugins. Not sure why it couldn't do so with the initial scan and had to be run twice in succession? Any ideas why this would be?

Subsequent KSM v0.2.0.0. Scan then correctly scanned Kilohearts v2.2.5 plugins.png

[Ben [KVR]]

We had seen this issue intermittently with some NI and Plugin Alliance plugins in pre-release testing - the scan timeout (should be 10) and an automatic retry function was catching them consistently - not here though

I've flagged the issue for further investigation.

Anyone else that experiences similar please let us know.

[bjm4tt]

We had seen this issue intermittently with some NI and Plugin Alliance plugins
...
Anyone else that experiences similar please let us know.

I'm also getting "File failed to scan." errors for the following NI plugins:

Bite, Choral, Dirt, Driver, Flair, FM8, Freak, Guitar Rig 7, Phasis, Raum, RC 48, Reaktor 6, Replika XT, Transient Master

I tried increasing the timeout setting and running the Manager app as admin without any effect.

I have 2 other NI plugins which were scanned without any issues: Battery 4 and Kontakt 8.

In the log file these are the errors for the above listed plugins:

VSTScanner: Scanning file: C:\Program Files\Common Files\VST3\Driver.vst3
VSTScanner: Failed to parse XML output for C:\Program Files\Common Files\VST3\Driver.vst3:
VSTScanner: Timeout scanning file: C:\Program Files\Common Files\VST3\Driver.vst3
VSTScanner: Failed to scan file C:\Program Files\Common Files\VST3\Driver.vst3 on try 1. Retrying.

VSTScanner: Scanning file: C:\Program Files\Common Files\VST3\Driver.vst3
VSTScanner: Failed to parse XML output for C:\Program Files\Common Files\VST3\Driver.vst3:
VSTScanner: Timeout scanning file: C:\Program Files\Common Files\VST3\Driver.vst3
VSTScanner: Failed to scan file C:\Program Files\Common Files\VST3\Driver.vst3 after 2 tries. Giving up.

All the plugins are up to date based on NI Access. Happy to do some debugging if needed.

Edit: the version number is 0.2.0.0 and am on Windows 11. Subsequent scans don't affect the results.

[bjm4tt]

That's weird: didn't change anything, no Windows updates, no plugin updates, no KSM updates, but after scanning again it found all those plugins as new.

[MrJubbly]

Just another update regarding the KSM v0.2.0.0 and Kilohearts.

This time the Kilohearts update was between v.2.2.5 and v2.3.0.

KSM did not exhibit the partial detection scan described above for this update. It instead correctly scanned and identified that all v.2.3.0 plugins had been updated.

Must just have been an intermittent glitch as stated.