I searched for a post discussing this topic and, to my surprise, I didn’t find any.
I’d like to ask about the behavior of the plugin manager in Ardour (and Mixbus) for Linux.
Initially, this only happened with plugins converted by Yabridge, but recently it happened with a native Linux plugin:
For directories plugin-directory-name.vst3, the scanner detects the same plugin twice: once in the folder itself and again in a binary .so file in the Contents/x86_64-linux/ subdirectory.
The list always shows one plugin that installs correctly and another with an error (the one in the binary file in the subdirectory).
This doesn’t prevent the plugin from working correctly, but it pollutes the plugin list in the manager.
Is there any parameter I can change to avoid this?
No. There wasn’t a file there. And while I was searching, I realized I was wrong before.
Actually, there are two subdirectories, one for Windows and one for Linux, within the same plugin.vst3 directory, even though it was downloaded as a native Linux plugin.
The GH releases page doesn’t say that it’s linux only…
anyways, you can simply delete the x86_64-win/ subdir (and also move WetReverb.vst3/ up into ~/.vst3 and delete “Wet VST/” if you like. the ~/.vst3 dir is scanned recursively, so further nesting doesn’t really matter.
Which version of Ardour are you using? I believe that issue was fixed in Ardour 9.2
Then again a multi-arch bundle may indeed still be an issue in some cases…
Until VST 3.6.10, the SDK allowed VST3 plugins on Windows as a single dll file with the .vst3 file extension. Since the folder is scanned recursively this leads to an ambiguity (bundle and file):