Request of confirmation in regard to a bug in easyeffects (7.2.5-1) #4153
Unanswered
Godzilla1965
asked this question in
Q&A
Replies: 1 comment 2 replies
-
That is weird. I do not remember a single occasion where a crash in EasyEffects made pipewire crash. Strange... I also not do not remember having ever seen the other problems. But now that we moved our development branch from gtk4 to Qt debugging the last stable release |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm on Debian "testing" and use the version of easyeffects as mentioned above. I also use pipewire 1.4.8-1, qpwgraph (occasionally... and when something in the routing got messed up).
A comparably new issue is as follows:
The equalizer (set to 32 bands) crashes (the ui hangs) easyeffects when changing per band settings (the tooth wheel above each band) like enable solo mode or switching band mode (low-/high cut, bell, notch... etc). Such a setting can be made once, what makes the whole UI irresponsible to any switching / parameter change attempt. The only way out I found is to kill easyeffects, what also crashes pipewire and forces to restart pipewire (I assume, because unless I find the corresponding services - as a Linux NON-professional... 🙄 - I log off - and on, what btw. may be not much slower all in all).
Interestingly there's another strange effect meanwhile visible:
The first and last band (so to speak band 1 and 32 when numbered from 1 to 32) are greyed out and are inaccessible for any changes (not even the frequency can be changed although both bands are enabled). This only concerns the first and last band.
Could someone please verify these effects?
Beta Was this translation helpful? Give feedback.
All reactions