I can't seem to get past a particular point in the VST scanning process.
It scans most of my plugins, but when it hits 81% it starts to scan Stereo Pusher by CARP Audio and hangs forever. Even after canceling the scan and closing the KSM window, a KVR Studio Manager process remains running in the background until I kill it.
If I don't kill the process, then each time the scan hangs, it adds a new process that never exits on its own. If I try scanning 3 times and then close KSM, there are 3 background processes hung forever until I kill them.
It seems like deleting the offending plugin entirely from my filesystem might be the only way around the issue currently, but I'd rather not do that since I use the plugin.
When I do delete or change the extension of Stereo Pusher, it then hangs on a different CARP Audio plugin (Mono Pusher), so it seems like an issue with CARP Audio plugins in general.
KSM hangs while scanning CARP Audio plugins
-
replicaobscura replicaobscura https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=174469
- KVRist
- 45 posts since 24 Feb, 2008 from WV
Replica Obscura
-
replicaobscura replicaobscura https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=174469
- KVRist
- Topic Starter
- 45 posts since 24 Feb, 2008 from WV
Since Bitwig lets you add multiple VST3 directories, I ended up just moving each plugin that KSM hangs on to a separate folder that KSM doesn't scan. This isn't ideal, but at least it lets me use KSM for my other plugins for now.
Perhaps KSM needs some kind of feature that checks for a hung scan and moves on to the next VST after a timeout period, to account for any unsupported plugins that might not scan correctly?
Perhaps KSM needs some kind of feature that checks for a hung scan and moves on to the next VST after a timeout period, to account for any unsupported plugins that might not scan correctly?
Replica Obscura
-
- Mr KVR
- 1580 posts since 23 Oct, 2000 from UK
- KVR Audio
I can replicate this on Windows 10.
However, on my system, if I cancel the VST scanner by clicking the X and then do another scan for changes it DOES detect all the plugins fine. I wonder if the first time they are scanned they do some initial setup that causes the hang.
I've logged the issue for investigation.
However, on my system, if I cancel the VST scanner by clicking the X and then do another scan for changes it DOES detect all the plugins fine. I wonder if the first time they are scanned they do some initial setup that causes the hang.
I've logged the issue for investigation.