audio: Prefer PipeWire over PulseAudio #5268
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
.