Had a good search around the forum and it seems there have been various issues with the GUI in the past, but I cannot see anything recently that shows this issue… As soon as I create a track, then select drumkv1, Ardour crashes out to the desktop…
I am aware of some the plugins that cannot be used through their gui at this time, I can normally choose ‘Edit with generic controls’, but with Ardour crashing out entirely, I am unable to do this… Have just tried to also open tracks with samplv1 and padthv1 and get the same result, ardour crashes out.
Saw one post earlier where it was suggested that editing the drumkv1.tff file would get around the gui problem, but that post was 3 years ago and I doubt it is the same issue (might be tho…).
The GUI issue with newer versions of the official Ardour download has to do with GTK-plugins.
Rui’s *v1-plugins are using QT, so they should supposedly work.
I have a self compiled ardour-8.11 and just compiled the latest git version of padthv1 and have no problem using it.
What’s the version of your *v1-plugins?
I have padthv1-1.3.0 with QT 5.15.3
Also: what, if any, errors do you get at crash-time if you start Ardour from the command line?
Ardour does not crash at startup, so no errors when starting from the command line…
Am using drumkv1, samplv1 etc ver 0.9.24-1 (straight out of the repo), am still with Ardour 8.10… OS is AV Linux 21…
I was asking what errors you get at crash time.
Usually when Ardour crashes it prints out some kind of error message and the easiest way to see them is if you start the program from the command line.
drumkv1 LV2 GUI shows well here too in Ardour 8.11. This is on openSUSE Tumbleweed, distro packages from GeekosDaw project. The plugin is compiled against Qt 6.8 and linked statically.
Rui, the author of drumkv1, has an area in OBS where he maintains his own software’s packages, and builds binaries for several distros, so you could try and see if yours is included and try them. drumkv1 download link for Arch, Fedora and SUSE Same as web directory, also listing Debian/*ubuntu package areas
The notice about Auburn Sounds not being a valid VST3 bundle shouldn’t be the issue but just to make sure you can try and move /usr/lib/vst3/AuburnSounds to /tmp and then try again.
If that doesn’t help and Edgar’s suggestion about finding newer versions of the *v1 plugins doesn’t either you may have to try and debug the issue :
Thanks Peder, but I think I may have a play with Qtractor for a while, all gui’s seem to be working with it and I have spent way too much time chasing down errors, really want to spend time making music and am in serious danger of learning how to trouble-shoot Linux, not Plan A…!
Will no doubt come back to Ardour in time…
Thanks again…
Yes that could be the issue, this must be quite an old version of AVL 21 because there were improper permissions on Lens on one release only which was later fixed. @fasteddy if you don’t use that Plugin uninstall the Auburn Sounds Demos package or update it with this one:
Hey Glen…
I removed it, rebooted, Ardour still crashes on opening a drumkv1 track…
Am going to leave Ardour alone for a wee while Glen, I tried opening these plugins in Qtractor and they all work, including the GUI for all the calf plugins… Thanks for your previous efforts to get AV 23 to work with xfce, but I spent several days chasing down errors and eventually gave up… AV 21 is absolutely rock solid but I continue to find issues with Ardour.
I had not realized how many issues I had just ‘learned’ to get around until last weekend when some friends came over to have a look at Ardour on my system. After a while someone asked me “you had to learn all those little tricks to get around the glitches?”. It put them all off it…
But with Qtractor I have yet to find a single fault, everything just works and AV21 is just as rock solid with it.
So am off to adventure with Qtractor for a spell, will come back to Ardour in a while…
Things work in QTractor because that program uses a different GUI toolkit than Ardour (QTractors uses Qt, Ardour uses GTK). The CALF plugins that you’re having problems with use GTK for their GUIs.
We’ve told plugin developers for decades that they should not use any desktop GUI toolkit for their plugins, because all it takes is a version mismatch between the plugin and the host, and the plugins GUIs will stop working. This applies to Qt as much as GTK: you cannot have, for example, Qt5 and Qt3 being used in the same program. If you ever tried to use a plugin that uses a different version of Qt than the one QTractor is built with, you will find similar problems.
This is just another reminder about this. I’m glad you’ve found a way to use them, but the underlying issue remains and will remain until all plugin developers stop doing this.
It works just fine here with Ardour 8.11, and 8.10 and the current development version. This is on Debian 11, using drumkv1 from the debian packaging system. As Edgar hinted above, this is almost certainly a plugin and/or Ardour packaging problem.
I have loading issues with drumkv1 because I use the official binary on opensuse tumbleweed/geekos.
After uninstalling the geekos package. I went to the link that Edgar posted and downloaded the deb file for debian 11, opened it in Ark archive manager and copy pasted the drumkv1.lv2 folder into ~/.lv2 Restart of and rescan in ardour, It now works.
Can you explain this better please? Which official binaries do you refer to, those linked from Rui’s website are the same I mentioned in my above post, AFAIK.
Also this thread initially was about deb packages in AV Linux 21, so I really find it confusing what you write about geekos/openSUSE, there are no “official” openSUSE packages except the GeekosDaw ones which is a “semi-official” user driven project.
So I checked in Tumbleweed, and all the vee-one GeekosDaw packages install without hassle and work well with our Ardour rpm package or a self compiled Ardour9 pre from current git, but not with a current nightly build from ardour.org (failing to load when trying to add them to a track).
Hi Edgar, I can confirm that the packages from our repo are ok. I just tested drumkv1 and I use samplv1 a lot. This with our Ardour 8.11 but with 9.0preXXX
2025-02-21T17:16:19 [ERROR]: LV2: Failed to instantiate plugin http://drumkv1.sourceforge.net/lv2
2025-02-21T17:16:19 [WARNING]: Failed to add Synth Plugin to newly created track.
2025-02-21T17:17:11 [ERROR]: LV2: Failed to instantiate plugin http://samplv1.sourceforge.net/lv2
I meant I use the official Ardour binary from this website, whilst using tumbleweed. That doesn’t work with the v1 packages from geekos but does with the debian build binaries (bar one) on on Rui’s website.
I neither package nor ship the V1 Plugins in any AVL version because I ship the ardour.org Ardour binaries and try to avoid shipping more ‘toolkit’ Plugins than I need to (I only continue with Calf for User continuity). MX Linux (the wheels and chassis of AVL) also doesn’t package the V1 stuff (although they do Qtractor and most other common Rui things).
Outside of whatever is in the official Debian Repos or self-compiling I don’t really have a recommended source for V1 in AVL. I know Rui has his own Repo but I avoid generic ‘Debuntu’ style PPA’s and Repos as much as possible and leave that stuff to the User.
