-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Mention a workaround for the PipeWire #63
Comments
This works with bluetooth too? |
Nope, it does not. ALSA is crap. And you'll have to set your Bluetooth output as your default sink with Bluealsa-tools |
Yes, but alsa is not used in this case, pipewire works with bluez directly. No workaround required for that. |
Bluetooth would work, except not with this workaround, it will if he uses the patch instead of the cfg workaround. |
It works for me with the workaround and without it (without the patch in both cases). |
Oh, when did it start working? I should probably start using libudev-zero again then it seems. I had issues with it in the past, but I kept this project in my watchlist in case such issues were resolved... |
For me bluetooth worked without an issue on multiple machines from since the day I got pipewire installed ...until recently I should say. A year ago or so I had to finally switch to wireplumber and I had to disable couple of plugins (like |
If not wireplumber, then what are you using? |
Previously it was |
Ah. I see. The workaround did nothing then, since it is for Wireplumber, not pipewire-media-session. Which is a deprecated reference implementation. I'm guessing you are on Debian or some other distro like that? |
The alsa workaround is for |
The readme states that PipeWire doesn't work without the patch, but there's another workaround.
Defining alsa sinks and sources manually allows you to use the PipeWire.
In
pipewire.conf
there's an example for source:So you can have a sink (and hence some sound) by adding a few lines beside it:
Unmuting the device every reboot is also a thing that is required. You can nicely do it in the same config just below in the
context.exec
section:Not the prettiest workaround, but I think it's worth mentioning.
The text was updated successfully, but these errors were encountered: