Many VST2 and VST3 plugins that work perfectly fine with Reaper, OpenMPT, etc. are wrongly reported as "unscannable"

[c0d3h4x0r]

One such example are the KSHMR Chain Leader and Follower VST3 plugins from Excite Audio.

This is on Windows 11.

[DropSnorz]

Hi @c0d3h4x0r,

A couple of quick things to help narrow this down:

• Are you using the OwlPlug Scanner (default) or the OwlPlug JNI Legacy scanner? You can check this in Settings.

• When you click on the "unscannable" plugin in the UI, does OwlPlug show an error message? (crash, timeout, exit code, ...) ?

These issues are often hard to pin down. There are hundreds of contributing factors, and most of them come down to DRM. When the full set of a vendor is not working, like all Arturia plugins, most of the time the DRM is blocking the execution, waiting for user input, network calls, iLock, or doing weird system I/O...

Also, the KSHMR Chain Leader/Follower use inter-process communication, which might be disrupting the scan. Just an hypothesis at this point; I never used this plugin.

I'm relying on JUCE for native plugin scanning, so an update in the next major release might resolve some of these crashes.

• Update Juce dependency to v9 #514

[c0d3h4x0r]

I'm using the "OwlPlug Scanner", not the JNI scanner.

The unscannable plugins just have a red error that says the scanner exited with code -1. No other info.

DRM shouldn't be an issue, as most of the unscannable plugins are free VSTs not requiring any purchase, registration, activation key, or iLok.

[DropSnorz]

Thanks for the details.

Can you list some of the free plugins impacted? I should be able to download them and reproduce the crash on my side.