Closed zynmuse closed 2 years ago
Hm. Looks like a regression on mruby's side. d0b5096781d41e0362a6658ab870daee6ef8eb5a in mruby-zest-build should provide a workaround.
I don't understand how to implement the workaround. It hasn't been commited to mruby-zest-build archive and this issue has been closed.
Thanks. Don't know what I was looking at!
I see. I was looking at zynaddsubfx/zyn-fusion-build. Your changes were to mruby_zest/mruby-zest-build.
Yep. Ideally zyn-fusion-build should be changed exceptionally rarely with all the real changes going into the backend (zynaddsubfx/zynaddsubfx) or the fairly poorly named GUI repo (mruby-zest/mruby-zest-build)
I'm OK with that. Still learning! The change works fine!
I will say that there is still some quirkyness unrelated to this regression in the view. Mostly in that the fltk UI appears to assume fixed Q values, where the fusion GUI uses whatever Q value comes from the current filter, but doesn't update when the Q value is changed.
When using any of the formant filters the frequency graphs show nothing. Using the old (fltk) interface they work correctly.