-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On PipeWire, getting "snd_aloop" error message unless capture method is explicitely set to pipewire/pulse #518
Comments
Uncommenting the input source from the config fixed it for me, its:
|
It's fixed, tks. |
Yeah but it worked in older versions without having to explicitly set it, and the config comment/documentation says that it should default to pulse and pipewire before the problematic alsa:
|
thanks for the bug report @FeralHedgehog! actually two bugs are at play here:
|
Everything's working after b05f829. |
When/where was the bug introduced?
Yes - using the cava package from the AUR (also tested with cava-git).
No.
Bug introduced in pipewire support #493
Describe the bug
After upgrading to v0.9.0 and running cava the following error appears:
However, everything works as expected when setting the
method
setting in the config to eitherpipewire
orpulse
.I noticed that setting it to
alsa
throws the same error, so maybe the capture method detection logic/order is broken?To Reproduce
Steps to reproduce the behavior:
method
config parameter unset.Expected behavior
Expected cava to run normally without having to configure the capture method.
Desktop (please complete the following information):
Terminal emulator
The text was updated successfully, but these errors were encountered: