Sorry for double posting, but I didn’t get any replies on the other thread at “Platform specific”, and I’m really hoping to get some insight into this:
When calling PluginDirectoryScanner::scanNextFile on Apple Silicon, if there’s a VST3 installed that doesn’t have
arm64 architecture, the error (with s(M)exoscope being the plugin in this case)
'/Library/Audio/Plug-Ins/VST3/s(M)exoscope.vst3/Contents/MacOS/s(M)exoscope' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')) The bundle doesn’t contain a version for the current architecture.
is reported when the plugin is encountered. After that, in a debug build,
assert (factory != nullptr) is triggered in juce_VST3PluginFormat.cpp:1050. If I just continue under the debugger, nothing bad seems to happen (I haven’t tried actually loading the plugin, I suppose that wouldn’t work but that’s fine).
I believe it should be possible to list faulty plugins even in debug, without hitting an assert. Is there a way to do this? If not, I’d consider this a bug.