Mousewheel EQ
-
I would like to have a problem - as we say in germany
the following:
In the GUI of the parametric EQ the Q value can be changed by mousewheel
But there is no possibility for the user to change it without mousewheel.It would be nice to have an alternative then e.g. option key and mouse
or shift-key and mouseNow I could just put a Q-knob in my GUI where the user can change the Q-value.
But he can't select the band in the gui which will be controlled with this knob. -
I think this would be better:
When clicking a node, a pop up window will be opened and Type, Gain, Q, Frequency options controls will be appeared. Also this pop up window layout can be edited with LAF.
I think with this way, everyone will be happy since the all controls are available and also customizable :)
-
@MikeB you can control the values by scripting. Try these in a knob callback:
ParametriqEQ1.setAttribute(ParametriqEQ1.Q + 1 * ParametriqEQ1.BandOffset, value);
ParametriqEQ1.setAttribute(ParametriqEQ1.Gain + 0 * ParametriqEQ1.BandOffset, value);
You'll have to figure out a nice way of changing which band is selected but it can be done
-
Yes that sounds good - but my question is HOW do I get the band that the user clicks in the GUI?
He clicks on band (1) and I would like to get the position of band 1 via get
or at least that the user has now clicked on band (1).
Does this exist? -
@MikeB You could probably do it with a scriptPanel but it would take a lot of coding.
The TLDR version would be "cloning" the display, then allowing specific mouse events to adjust the EQ. The EQ itself would be hidden and doing stuff in the background, and the user would interact with the Panel.
-
I don't quite understand ?
I can already interact with the panel - anyone can do thatIt's just about the callback for clicking on the 1 or 2 or 3
That is not given in the GUI ?! -
@MikeB You can get individual attributes with getAttribute but I don't think there's a way to "detect" which node the user is clicking on.
-
@iamlamprey said in Mousewheel EQ:
@MikeB You can get individual attributes with getAttribute but I don't think there's a way to "detect" which node the user is clicking on.
Yes - that is the problem unfortunately
Why?
Too bad - All attributes I can change - this important one not! -
@MikeB I'm working on a snippet, I'll post it here if I finish it (but don't hold your breath) :)
-
Ok thank you
I will continue to breathe in the meantime :-)