I made the switch from Kubuntu 24.04 (KDE Plasma 5.x) to Arch (KDE Plasma 6.6.4).
I took the .vst3 folder, which I backuped from the Kubuntu system, copied it 1:1 into my home directory on the new Arch system. Of cource I expected it to just work exactly like before. On both systems I was using Ardour 9.2, both were KDE Plasma, only difference beeing Plasma 5 (Qt5) vs Plasma 6 (Qt6).
Now I got one plugin that is not recognised anymore on the new system.
Could that be because of Plasma 6 (Qt6) colliding with the plugins GUI framework or is there something else I’m missing?
How can I debug and confirm that it’s the GUI?
The Plugin Manager shows this error:
VST3 module-path '/home/foo/.vst3/XCTR v3.vst3/Contents/x86_64-linux/XCTR v3.so'
[Info]: Scanning: /home/foo/.vst3/XCTR v3.vst3
[ERROR]: Could not load VST3 plugin '/home/foo/.vst3/XCTR v3.vst3/Contents/x86_64-linux/XCTR v3.so': libcurl-gnutls.so.4: cannot open shared object file: No such file or directory
Cannot load VST3 module: '/home/foo/.vst3/XCTR v3.vst3/Contents/x86_64-linux/XCTR v3.so'
Scan Failed.
Actually the developer should re-compile and statically link the plugin to not use any external system-wide dependencies. Plugins should be self-contained (like on other OS).
Ah great, it works again but I don’t understand what curl has to do with an audio plugin. Probably for communicating to the manufacturers server when activating the license, or something, now that I think about it. But at first I didn’t consider curl to be an issue, so I thought it’s gotta be something else. Especially because I had curl installed, just not libcurl-gnutls. Very interesting.
It’s also true that this plugin is unfortunatelly not maintained anymore, so I have to take it for what it is but as long it’s just a dependency for curl, that’s fine for me.