Update Pipewire backend to use latest pipewire-rs release #884
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dorindabassey
requested review from
epilys,
stefano-garzarella,
stsquad and
vireshk
as code owners
dorindabassey
force-pushed
the
update
branch
2 times, most recently
from
364b94a to
3fc042c
Compare
MatiasVara
approved these changes
Oct 3, 2025
stefano-garzarella
approved these changes
Oct 6, 2025
added 2 commits
October 6, 2025 12:09
migrate to pipewire-rs 0.9.2 rc API introduced in 0.9.x Signed-off-by: Dorinda Bassey <[email protected]>
after pipewire update fix the hardcoded audio format to use the audio format in the new release Fixes: rust-vmm#856 Signed-off-by: Dorinda Bassey <[email protected]>
epilys
approved these changes
Oct 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary of the PR
Update Pipewire backend to use latest pipewire-rs release
fixes #856
Requirements
Before submitting your PR, please make sure you addressed the following
requirements:
git commit -s), and the commit message has max 60 characters for thesummary and max 75 characters for each description line.
test.
Release" section of CHANGELOG.md (if no such section exists, please create one).
unsafecode is properly documented.