I love it. I can run my microphone through noise-canceling when using video call software that doesn’t have its own noise-canceling. I can run an audio compressor over mpv if the movie does that loud explosion/quiet talking thing. You can assign each application a different effect stack.
Tried it on bazzite, seemed to work without issues.
I’m using pipewire with easyeffects and they both work great.
For pipewire I’ve installed all the available compatibility layers: pipewire-pulse, pipewire-alsa, pipewire-jack, as well as every lib32 variant. Without all of these some apps would not work via pipewire.
As for easyeffects, depending on your distro and how you install it, you might need to install the plugins separately. Otherwise the app will open but it won’t be able to actually apply any effects. First time I tried to use it I was confused about this.
Switch from Pulse? No reason not to. Use Wireplumber instead of
pipewire-session-manager, and consider installingpipewire-pulseif any of your scripts rely onpactl(or rewrite them to usewpctl, which does much the same aspactl).As for Easyeffects, use the flatpak package to avoid dependency issues.
I’m not familiar with easyeffects, I use a computer to watch media content and always have to adjust my volume for loud gunfire or soft dialogue. Does easyeffects have a volume normalization setting I could use to smooth out my media volume?
That’s one of the first problems I need solved, so thanks for asking. I used to use pulseEffects to get one place to go for system-wide volume, EQ & compression settings, and want that back.
One of the problems it had was that many FX wouldn’t work without having to install a set of non-default libraries, and the available docs weren’t too clear on that. Will be visiting Ee docs.
Yes, it has both a compressor and a limiter. I don’t know how to set them up though.
I belive you get more effects by using the Flatpak version, too
Yea it just-works, I’ve had zero issues with it, easyeffects too
Unlike Wayland, Pipewire just works as long as you have all needed packages installed. I’m not familiar with any compatibility issues at all. I highly recommend switching.
Idk Wayland has been working for me for years now, my only issue is global keybindings but I just script them with sway, like for push to talk I have alt+x to unmute my mic then mute it again when I take my finger off it
Rant incoming, because I just happened to be dealing with this today.
I tried the push to talk binding method in sway, and found it was extremely fragile because if you press any modifier keys before releasing the button, the release binding won’t trigger and your mic will stay open. This is especially problematic for my use case as I use both my push to talk hotkey and my modifier buttons while gaming.
I just use a toggle mute hotkey instead of push-to-talk though. Just gotta remember to re-mute, and have a visual indicator for your mic status so you don’t accidentally leave it in the wrong state.
Another workaround is binding all possible combinations of modifier keys explicitly, and passing in --device-id so that the binding doesn’t consume the keypress and instead forwards it on to the application. This should perfectly emulate the behavior of an X-style global hotkey. With 4 mods (super, ctrl, shift, alt) and 2 bindings per combination there are 2^5 = 32 total bindings for each such hotkey. However there’s still no telling if the key-release event could be missed somehow and leave your mic open. I don’t know how reliable this method is.
Huh never encountered this, I’ll see if I can think of anything
If your binding is Alt+X, try pressing it down, tapping shift (press and release), then releasing X. The release keybind shouldn’t trigger.
I tried the workaround with all modifier combinations but this still happens, even if you bind Shift+(Your Binding). Pressing “shift” while the a chord is held prevents the release event from being handled.
Huh probably should make an issue on sway, repo
