fractional 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.