Skip to content
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

audio: Prefer PipeWire over PulseAudio #5268

Closed

Conversation

flibitijibibo
Copy link
Collaborator

Since we had a Wayland tracker, makes sense to have a PipeWire tracker as well... main difference is, we only have one issue and it happens to be the blocker:

https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1835

Once PipeWire exposes a way for us to detect that a session is actually running (vs. someone using Pulse but with the PW libs installed) this should be a perfectly safe change; we can fall back to Pulse when the session isn't started or the system doesn't expose the metadata described in the linked issue.

Like with Wayland this branch is for internal testing only; end user testing should use SDL_AUDIODRIVER=pipewire.

@flibitijibibo
Copy link
Collaborator Author

Adding this to 2.28 - I have someone working on implementing PipeWire session detection right now, and expect this to be upstreamed into PW/WP by the end of the year, which should make it feasible to make the switch for the release after 2.26.

@flibitijibibo flibitijibibo changed the title [DONOTMERGE] audio: Prefer PipeWire over PulseAudio audio: Prefer PipeWire over PulseAudio Oct 10, 2022
@slouken slouken modified the milestones: 2.28.0, 3.0 Nov 23, 2022
@flibitijibibo
Copy link
Collaborator Author

Obsoleted by #9473

@flibitijibibo flibitijibibo deleted the pipewire-by-default branch April 27, 2024 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants