Inconsistency in what file path gets recognized as a valid VST3 plugin between platforms

[HRudyPlayZ]

Also happens on the effects that have been tested for compatibility, like RoughRider3.

VST3Plugin: Unable to scan plugin C:/Program Files/Common Files/VST3/RoughRider3.vst3: unsupported plugin format or scan failure.

This is a new Windows 10 install, with the pedalboard pip package. All VC++ runtimes are there. I'm running Python 3.12.10.
Also confirmed to happen on Mverb 2020 and Graillon 3.

Doesn't happen on the linux release, everything runs fine there.

The error occurs on this line within my code: self.effect: VST3Plugin = load_plugin(fileName)
With fileName just being the effect path as a string provided by the rest of my codebase. As you can see, the usage is simple and nothing's fancy going on.

[HRudyPlayZ]

Ok for some reason there seems to be an inconsistency in whats to be loaded depending on the platform.

I need to do further testing to be fully sure but it seems like:

• Pedalboard on Windows expects to be provided the plugin file (VST3/plugin.vst3/Contents/x86_64-win/plugin.vst3)
• Pedalboard on Linux expects to be provided the plugin folder (VST3/plugin.vst3)