-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
pipewire support #3212
Comments
It doesn't look ready to support our use-case: It's not clear to me how clients locate the socket or how we could have multiple daemons for a single user without running each session with a different |
FYI : More bad news: *buntu 22.10 will make this "change" :( :( :( Don't know if this will back channel up to Debian..... |
@ScanCaster On Fedora you can just |
We have some initial pipewire support: #3750 (comment) |
Does this one work for the latest version of xpra? I am running on Debian 12, and when I tried to enable audio forwarding by installing xpra-audio it asked me to install pulseaudio. But if I try to install pulseaudio it asks me to uninstall pulseaudio as well as gnome-core, which I of course hesitates to do for the fear of actually breaking my existing audio and desktop... Is there a way to forward audio from a remote desktop on debian without breaking things? It used to work so easily when everything was simply pulse audio! |
Audio forwarding can only work with It used to be a simple case of installing |
Fedora 34 switched to pipewire and the
pulseaudio
command is no longer installed.This obviously breaks our audio forwarding plumbing.
It looks like we can tell the pipewire deamon where to look for its configuration using
PIPEWIRE_CONFIG_NAME
:https://docs.pipewire.org/page_daemon.html
It's not clear at this point how easy it will be to allow multiple daemon instances per user. If that's even possible.
As for API, there is pipewire_python - not sure how complete it is.
The text was updated successfully, but these errors were encountered: