System audio output incorrectly changed to app virtual device in >= 0.4.4
Ignore most of this, see this comment.
0.4.4 has a bug where after launching easyeffects, system sound output might be set to "easyeffects sink" (a virtual device) instead of the normal headphones or system speakers. This results in easyeffects' switches to disable processing for an app seemingly not working, when the actual issue is the incorrect output being set.
- From fresh reboot
- Launch firefox and play audio (I did youtube)
- Launch easyeffects (I used stable Flathub build)
- Notice how in gnome settings (possibly also other tools) easyeffects sink becomes the default system audio output.
- Now the easyeffects app switch (next to the app name) no longer works, you seemingly can't disable easyeffects' processing.
Note: If you launch easyeffects before firefox, it might behave differently.
I could not reproduce this on
wireplumber-0.4.3-3.fc35.x86_64). I was using
pipewire-0.3.40-1.fc35.x86_64 for my testing.
Is this incorrect wireplumber or easyeffects behaviour?
Originally reported: https://github.com/wwmm/easyeffects/issues/1251