Any messages in the ardour log? There may also be informative messages if you start ardour from a terminal and look for messages in the terminal after trying to load the plugin.
I see that the plugins are compiled to use dynamically loaded system libraries, which has the possibility of conflicting with Ardour libraries, and there is apparently a library needed which my system does not have (and I would say I have all the common application libraries installed on my system).
The reference to libglib-2.0 is GTK 2, and that is known to cause problems with Ardour.
Plugins should not use heavy weight GUI toolkits such as GTK or QT. If that is actually required it seems likely that these plugins will not work with recent Ardour builds. You might get them to work using a distribution built plugin and distribution built Ardour, but it will always be a brittle setup (and may not work even then, I think Ardour has removed the ability to build with system GTK and only builds with the fork included in the Ardour source tree).
Actually, glib is not intrinsically part of GTK, a plugin may have entirely legitimate reasons to use it, and we have not “vendored” it into our own source tree. It is still a bad idea for a plugin to be dynamically linked to libglib, for the same reason that it is a bad reason for it to be dynamically linked to most libraries. But libglib is not, by itself, a desktop toolkit (it’s more of a portability library, plus a highly evolved event loop).
The libsaf… linkage, however, is entirely and completely wrong. The plugin has been built inappropriately, and should be using static linkage with that library, so that users do not have to have it installed in order to use the plugin.
In this case, if I try to put my plugin in a track, this message appears:
lilv_lib_open(): error: Failed to open library /usr/lib/lv2/sparta_binauraliser.lv2/libsparta_binauraliser.so (/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /usr/lib/lv2/sparta_binauraliser.lv2/libsparta_binauraliser.so))
Notwithstanding the other issues mentioned above, there have been a couple of topics on Linux Musicians forums with the same issue - plugins requiring GLIBC later than what is provided in Debian 12. Notably Kazrog plugins - Kazrog plugins are coming on Linux - LinuxMusicians which is well worth reading, and recently DDMF plugins, both of which are recently ported to Linux and require GLIBC ≥ 2.38.
If you don’t want to read, the discussion centres around the fact that most plugins don’t need the latest shiny GLIBC and it would be advantageous to compile with an older version to ensure more broad compatibility.
It does indeed. There is another collection of (commercial) plugins by ToneBoosters I tried several demos of which work in Trixie but not Bookworm. Some very nice plugins in these and the other 2 I mentioned above, but my budget doesn’t extend very far for buying plugins.
