saving presets works when using Ardour and the Vee One Suite on Arch with KDE, but it does not work with Qtractor.
what exactly doesn't work? how are you saving presets on the vee-ones and qtractor that doesn't work but does in ardour?
Arch version of Ardour, opening a plugin from the Vee One Suite...
you're probably using the Arch supplied packages to both ardour and the vee-ones lv2 plugins...
it happens that these Arch's packages of the plugins are not built to Qt6-static and thus are not self-contained and depending on system provided shared libraries which is a big issue for plugins, most specially in Ardour: all bad and strange things might happen then, if it doesn't crash on show or barely work at all.
hth.
thanks
ps. for the vee-ones, in any case or distro, you're recommended to source the repos for the safe, static builds for the lv2 plugins.
pps. on those cases (Arch) where it's showing bizarre GUI things, most probably due to wayland, try to launch with this command line prefix if you can: QT_QPA_PLATFORM=xcb ardour9
and maybe things behave a little better on the vee-one's.lv2 front;
what exactly doesn't work? how are you saving presets on the vee-ones and qtractor that doesn't work but does in ardour?
you're probably using the Arch supplied packages to both ardour and the vee-ones lv2 plugins...
it happens that these Arch's packages of the plugins are not built to Qt6-static and thus are not self-contained and depending on system provided shared libraries which is a big issue for plugins, most specially in Ardour: all bad and strange things might happen then, if it doesn't crash on show or barely work at all.
hth.
thanks
ps. for the vee-ones, in any case or distro, you're recommended to source the repos for the safe, static builds for the lv2 plugins.
pps. on those cases (Arch) where it's showing bizarre GUI things, most probably due to wayland, try to launch with this command line prefix if you can:
QT_QPA_PLATFORM=xcb ardour9and maybe things behave a little better on the vee-one's.lv2 front;