Skip to content

Replace PulseAudio with PipeWire/WirePlumber audio stack in WSLg#1418

Open
linghengqian wants to merge 1 commit into
microsoft:mainfrom
linghengqian:pa-remove
Open

Replace PulseAudio with PipeWire/WirePlumber audio stack in WSLg#1418
linghengqian wants to merge 1 commit into
microsoft:mainfrom
linghengqian:pa-remove

Conversation

@linghengqian
Copy link
Copy Markdown

@linghengqian
Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

@benhillis benhillis added audio-redirection enhancement New feature or request labels May 17, 2026
@benhillis
Copy link
Copy Markdown
Member

Triage note (2026-05): Thanks for the substantial work — replacing PulseAudio with PipeWire/WirePlumber is squarely on the roadmap (tracked in #290, with 40+ reactions) and we want to land this. A few things will hold the merge button:

  1. We need to validate audio behavior end-to-end against current RDP audio playback and capture paths. The pipewire-wslg-rdp.patch and pipewire-rdp-module.c carry the equivalent of the existing PulseAudio RDP module — verifying parity (sample rates, latency, capture devices, mute/volume integration with Windows) is the bulk of the review.
  2. cgmanifest.json will need entries for PipeWire / WirePlumber so Component Governance is happy.
  3. An internal buddy build through the full Azure Pipelines flow before merge.

Not asking for changes yet — just setting expectations. If you want to chip away at (1) and (2) preemptively that would help.

Copy link
Copy Markdown
Author

@linghengqian linghengqian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm glad Microsoft is willing to take on this work, especially since I don't actually have an Azure account to test the corresponding CI files. Should I close this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

audio-redirection enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

use Pipewire instead of PA

2 participants