George Kiagiadakis
November 02, 2021
Share this post:
Reading time:
Today marks an exciting day as Fedora 35 has now been released, with WirePlumber as the default session manager for PipeWire! Under development by Collabora since 2019, and previously adopted in the automotive space by Automotive Grade Linux, WirePlumber has now officially entered the linux desktop space and is the recommended session manager to accompany PipeWire, with other distributions expected to follow very soon.
WirePlumber brings some new and interesting things to the desktop. Most notably, it introduces the ability to easily modify the overall behavior of PipeWire for different use cases, using Lua scripts. This allows power users as well as developers of use-case specific distributions or desktop environments to customize their multimedia experience and get the most out of PipeWire. Recently I gave a talk about how this Lua scripting mechanism works, which you can watch here.
Additionally, WirePlumber comes with a library that provides a high level object model to interface with objects in PipeWire, enabling application developers to more easily integrate PipeWire control functionality into their applications. This can help in transitioning away from the PulseAudio API in the forthcoming future, as most graphical applications like desktop environment sound settings dialogs and mixer applications are still using the PulseAudio API to interface with PipeWire.
If you are trying WirePlumber in Fedora 35 (or in any other distribution) and have suggestions to make or issues to report, please let us know in the issue tracker and/or drop by the PipeWire discussion channel (matrix: #pipewire:matrix.org / oftc irc: #pipewire) to discuss. Contributions are also more than welcome. And to all of you who have already been using WirePlumber, testing it, submitting issues and patches... thank you!
20/12/2024
The Rockchip RK3588 upstream support has progressed a lot over the last few years. As 2024 comes to a close, it is a great time to have…
09/12/2024
Collabora will be at NeurIPs this week to dive into the latest academic findings in machine learning and research advancements that are…
05/12/2024
Now based on Debian Bookworm, Apertis is a collaborative OS platform that includes an operating system, but also tools and cloud services…
Whether writing a line of code or shaping a longer-term strategic software development plan, we'll help you navigate the ever-evolving world of Open Source.
한국어 버전의 Collabora.com 보기
Acesse Collabora.com em Português
Comments (5)
Lu:
Nov 03, 2021 at 10:32 AM
Awesome, kudos to everyone involved!
Reply to this comment
Reply to this comment
Fedora user:
Nov 03, 2021 at 03:47 PM
Like the idea but sadly didn't work for me... Had to:
sudo dnf swap wireplumber pipewire-media-session
Sound came back. Maybe it's time for a system upgrade!
Reply to this comment
Reply to this comment
mfilion:
Nov 04, 2021 at 02:27 PM
Sorry to hear that! Please provide some feedback on the issue tracker so that we can help resolve this issue. https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues
Reply to this comment
Reply to this comment
Mauricio:
Mar 28, 2022 at 05:25 PM
I installed fedora 35, fresh install on a intel based laptop and it shows as Multimedia audio controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster (rev 0b), but there is no sound coming out from the build in speakers and headphones, detects when I'm connecting but no sound either , searching online seems like theres more than a few ones that having this same issue
Reply to this comment
Reply to this comment
George Kiagiadakis:
Mar 29, 2022 at 02:21 PM
Hi,
I am not sure what the issue might be with this specific card, but searching online seems to indicate that others have encountered issues as well, but not with PipeWire / WirePlumber. There seem to be driver issues. It may be worth asking in a Fedora-specific support forum for assistance to debug this problem.
If you still think this is a PipeWire or WirePlumber specific issue, please open a ticket on our ticket tracker: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues
Reply to this comment
Reply to this comment
Add a Comment