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.
[ 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?
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.
[ 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?
Statistics: Posted by MrJubbly — Mon Nov 04, 2024 12:08 am — Replies 1 — Views 25