Note that only the Gx plugins are LV2 GUI ones.
There are plugins like “Guitarix Amp” and “Guitarix Stereo Flanger” that are old LADSPA plugins with generic UIs
Bumping this as there are still problems with the 5.12 64-bit build via ardour.org/download.html
Starting with a fresh install of Ubuntu Studio 17.04 (Ardour 5.5.0 ; guitarix 0.35.2-2 ; glibmm 2.50.0-1) the LV2 GUIs are working.
After completely removing the distro version of Ardour and installing from Ardour-5.12.0-x86_64.run the following error appears:
[ERROR]: failed to instantiate LV2 GUI
Note that this time, I’m not running with the KX-Studio repos.
Any further suggestions on fixing this are welcome, but you might need to explain like i’m 5!
glibmm 2.50.0-1This is the same problem as the one outlined in the bug report above. The distro version of ardour will be build against this version of glibmm but the official ardour binaries use an older version. If this is coming to ubuntu in the future then it looks like the ardour team are going to have to address this problem at some point.
ok - thanks. perhaps a workaround is to emulate the platform that the official binaries were compiled under? or maybe i’m just asking for more trouble?
We won’t address this issue (actually we cannot). Plugins are supposed to be self-contained. There are only a handful which still rely on system-wide libs, unfortunately guitarix is one of them.
see https://linuxmusicians.com/viewtopic.php?t=17503&p=84989#p84986 for an explanation.
So we have to complain at the guitarix team for a solution, if I understand correctly?
The argument seems hardly clear cut to me…
Hi
LV2 supports the use of GTK/GTKMM GUI’s in the LV2 plugin from the beginning on, and still does. And, as some of you already mention, when you use Ardour and guitarix from your distribution, there is no issue.
I’m a linux guy, support open source, support Linux distributions of different colours. So my work on guitarix is meant to be used in/from distributions. I know, that will often be a bit more work then just pushing out binary’s, but it is worse the hazel (for me).
So, clear is, the culprit here comes from the provided ardour binary’s, as those comes with there own environment to run in, bypass the distribution you use.
The argument that plugins have to been self-contained is a bit over the top, as not a single plug I’m aware of, is “really” self-contained. They all use the one or the other system library.
There is just a split in the “good” and the “bad” made here by X42.
This said, there are no plans to rewrite the guitarix plugs with a other GUI toolkit.
We could now pushing the joker from on project to the other, like ping pong, but that wont help us here.
So, there are solutions beside that guitarix needs to be rewritten or ardour didn’t provide binary’s any more.
On the guitarix side we provide now binary’s as well, which is, by the way usually out of scope for me), which were build against a similar library set then ardour, those will run on most distributions (they wont work on arch linux).
regards
hermann (guitarix maintainer)
This is an unfortunate issue as it will certainly affect many people who depend on this plugin, myself included. I am not having problems presently, but if this dilemma persists, how does one build it from source to be “compatible” with future releases of Ardour/Mixbus?
There are a new solution for this issue. It’s Carla by falkTX.
- http://kxstudio.linuxaudio.org/News/?action=view&url=carla-20-beta6-is-here
It allow now the export of jack-applications as LV2 plugs, so even guitarix main app could be used as plugin in Ardour and Mixbus.
Even LV2 plugins could be exported as LV2 plugs.
This way also the guitarix LV2 plugins could be used with there UI’s. The UI will be “Sandboxed” by Carla in a way you wont notice it.
Thanks for the cogent explanation. I am one of the unfortunates on Arch. It took a fair amount of time and effort as I am primarily a musician and only secondarily a Linux guy. Is there anything I can do other than change distributions? My goal in using Arch was configurability and putting together a system light on unnecessary resources. Any suggestions?
We currently do a rewrite of the plugin interfaces to X11/cairo. A couple of them been already done, like the GxAmplifier’s
That’s how it looks now.
When you are on Arch, you could use the guitarix-git package and you’ll have them.
1 Like
could we get some realistic TORX bolt head rendering for the corners?
3 Likes
Ups, sorry, it’s a hex bolt.
1 Like
Thanks Brummer. Here’s where I show my musician-first-linux-guy-second ignorance in two ways!
- I’m assuming from your answer that I need to install cairo. Just cairo or are there support pieces I need to install. I did a package search on Arch and found many cairo-related packages.
- I searched for a guitarix-git package and could not find it. So I assume you must mean something that I simply don’t know.
Yours,
-Paul
I mean the one from AUR:
https://aur.archlinux.org/packages/guitarix-git/
for cairo, this one should do it:
https://www.archlinux.org/packages/extra/x86_64/cairo/
but note, cairo is used anyway in guitarix for drawing, just with gtk underlying, now, for the new LV2 interfaces it’s cairo with X11 underlying. That’s said, when you’ve guitarix running on ARCH, you properly have cairo and X11 anyway installed.
But, I’m not a arch user, so I only guess that’s the one, I can’t promise.
You’ll find out when the pkgbuild fail on configure.
Oh, right. In my haste, I forgot AUR is a separate search. Should’ve checked before bothering you. Sigh.
I will check to see if cairo is already installed. Probably is, as many of the guitarix plugins I use have their GUIs. Thanks again.
UPDATE: cairo was already installed. I got guitarix-git from the AUR, built and installed it and can instantiate the plug-ins with their GUI. THANK YOU!
You are welcome.
As it is a work in progress, you may want to update the build from time to time, as a couple of plugs haven’t been ported yet, but will properly follow.