violetmage

It looks like you're on cachyOS, is that right? If so, please ensure all your packages are up to date, as there was a somewhat recently released update to ananicy...

If easyeffects is completely closed, and then restarted, everything works normally? Is the easyeffects option `Shutdown on Window Closing` turned on?

Maybe your window manager is trying to be in control of hardware volume? Does your audio work normally if easyeffects isn't autostarted at all?

For displaying the bypass/active state of the effects, I think that instead of dimming bits of the UI, we should simply have a different icon in place of the flow...

Can you provide the full debug log, from program start to crash? It's difficult to understand the full context with just the information one provided.

To get debug logs for easyeffects on a flatpak installation, you'll need to run easyeffects from the command line like this: `flatpak run --env=G_MESSAGES_DEBUG=easyeffects com.github.wwmm.easyeffects` Before running this command, remember...

IMHO, for such an integral and stateful control the use of a emphasized switch type widget is warranted. A switch type will take more space but will avoid completely any...

Can you try the [flatpak version](https://flathub.org/apps/com.github.wwmm.easyeffects) and see if the behavior is the same there?

In order to find the issue, we will need some more information: What input and output devices are selected in zoom? What are the settings on the pipewire tab of...

To be sure, you are using the zoom flatpak, correct? Also, does the audio work correctly if you manually select easyeffects sink/source in zoom? Edit: Just found this issue on...