Is it possible to get the new GUI to work in older versions of ardour possibly mixbus version 5
The EQ, yes.
You could copy /opt/Ardour-6.3.0/lib/LV2/Harrison.lv2/a-EQ_* to ~/.lv2/a-eq-ui.lv2/
However the delay plugin changed from v5 to v6 (support for dotted notes was added), so the plugin ports don’t match. Also the port-ranges for the compressor were relaxed.
For those to work you’d also have to get the new a-* plugins and replace them.
If @zamaudio is not up for adding one of his limiters in generic disguise (i.e. ZaMaximX2), perhaps I could put in a “plug” for a version of your x42-dpl or asking @SadKo for something from the LSP stable (with true peak option given the new loudness workflow).
+1 for an a- convolution reverb. I love the look of your convo.lv2 but I guess at low buffer sizes it is designed only for very short cabinet IRs? I can’t use it for adding halls and churches while playing live like I can with Klangfalter…
Also, I really love the new UIs for EQ and compressor 
Wow, excellent. The author does warn not to install it though 
About the IR bundles you have listed, I have started converting some B-format ones to stereo from the openair library (https://openairlib.net/) using a GNU Octave script if you want to list them at some point…
I copied the ardour 6.3 plugins into my mixbus and it works fine and I got the new GUI to show up. But I do fine at times the GUI locks up the system. Even on ardour 6.3 on Linux but at times I notice it’s fine and no issue.
Would that not imply or invite all manner of potential licensing ambiguity and / or conflicts? (And possibly make it difficult for the end-user to be sure of what it is they are using, and under what license or attribution? )
It’s the same as loading a proprietary VST plugin into a free-software DAW, or vice versa.
The LV2 DSP / GUI interface is literally just that: an interface. Any software can use the interface, regardless of the software’s license.
This is also possible for VST, the host can provide a custom view and controller and one can create custom UIs for 3rd party plugins too. VST3 makes this even easier since the Vst::IEditController interface is publicly exposed.
Yes I understand all that, and that’s not really (in fact, not at all) what I was referring to - your original comment appeared to suggest that someone could just take any existing LV2 and put a different GUI on it - technically possible, yes, but… the ambiguity, in that case, might be that you could have ‘a plugin’ (e.g. an ‘LV2’ ) potentially composed of a proprietary part and an open source part, and that it might not be clear to the user what the licensing of ‘the plugin’ is or even e.g. the attribution of an open source plug-in to which a proprietary UI may have been attached.
On a slightly different topic, when I tried the a* EQ GUI, the ‘Q’ control behaviour appeared incorrect. For example, dragging the Q control to the left, decreases the Q value, but, makes the filter appear sharper which is not what I would expect.
‘Q’ commonly denotes the ‘quality factor’ of the filter e.g. how good at filtering it is, therefore a high Q implies a more selective e.g. narrower passband not a wider one. Q is related to bandwidth, but not equivalent.
Last I checked Q was generally considered the inverse of bandwidth.
Seabladefractional bandwidth - to be pedantic (but under that definition you would expect a narrow bandwidth filter to have the higher Q, and that is not what the a* EQ GUI is doing, at least, not when I tried it. The plug-in itself e.g. the DSP appears to be exposing bandwidth as a parameter, so I suspect something has gone wrong in the translation between the GUI and the DSP parts of the plug-in)
1 Like
I completely agree with @mike3 (so does Presonus: https://www.presonus.com/learn/technical-articles/What-Is-a-Parametric-Eq)
Higher Q = narrower cut/boost in my book however simplistic or technically wrong my verbiage might be. a-eq with new GUI definitely has it backwards. Still looks pretty though
Yikes that is a really embarrassing oversight.
Will fix the label and scaling in the next release. I copy/pasted from our own EQs which typically use Q not bw.
Thanks for bringing this to my attention.
-Ben
1 Like
Ah, that explains the spite-crash when opening the plugins with X11 forwarding. Harrison does the same thing.
‘GLXBadContext’ 1477 Segmentation fault Ardour6
They still work with generic controls so it’s not much of an issue.
Might be related to indirect GLX contexts? - https://askubuntu.com/questions/745135/how-to-enable-indirect-glx-contexts-iglx-in-ubuntu-14-04-lts-with-nvidia-gfx
That seems to have sorted things, thanks.
Section “ServerFlags”
Option “AllowIndirectGLX” “on”
Option “IndirectGLX” “on”
EndSection
Was the bit added to xorg.conf
Or try ssh -Y ... That way remote apps are trusted and can use the local graphics card’s hardware acceleration.
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.