On 14.02.2023 00:15, Will Godfrey wrote:
This is something I've mentioned before that really bothers me. Apart from
anything else, we have no hope of being able to properly separate the GUI
while we are dipping into the main code in an uncontrolled manner.
The area the graph is reading from is our old fiend (not a typo)
analog filter. However, the graphics doesn't require anything like the
accuracy and just throws it away. It only needs pixel density and even
the wide 4k screens are only 3840 pixels wide!
Therefore, is it possible to devise a 'good enough' approximation that
reads from the actual GUI controls and keeps it entirely in the GUI?
On 14.02.23 16:05, Kristian Amlie wrote:
I'm not sure I completely understood all of that, but it's common
in UIs to simply recreate some filter structures inside the UI code.
They are not used for audio, but their properties can be queried
and used for display, since they share the same code.
One of my equalizer plugins does this.
Hehe ... I just stumbled over this old thread.
In fact we introduced precisely this change in Autumn 2024,
as part of a first prototype for a new Core -> UI connection.
The core now sends a pre-rendered EQ graph via push update.
For generating this graph, the Core uses a separate instance of the
filter, which is parametrised with the current target values of the
active filters and only used to computed the filter response function.
-- Hermann
_______________________________________________
Yoshimi-devel mailing list
Yoshimi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
