PipeWire 0.3.22 Released With Many Improvements

[finalzone]

You can tell Pipewire is a serious project when they implement in a few months stuff that took years for Poettering to fix.

Pulseaudio did the heavy lifting on audio for the Linux desktop environment when the Linux audio world was a complete mess back to 2000. Pipewire fast development from which one of developers also contribute to GStreamer took on an existing foundation set by Pulseaudio and make it better with further unification of audio (with JACK) and video.

[tornado99]

For anyone have problems with headsets not appearing or not having mic functionality you have to play around with disabling hsp_ag or hfp_ag in the .config file

[ix900]

You can tell Pipewire is a serious project when they implement in a few months stuff that took years for Poettering to fix.

Seriously full of bugs probably. With all the sound configurations that exist, would be surprised if it isn't swiss cheese. But like most things from Fedora, they will release it before its polished and well tested. Sadly, it could work better. There's been a lot of audio breakage past years.

[oleid]

You can tell Pipewire is a serious project when they implement in a few months stuff that took years for Poettering to fix.

Like what?

[angrypie]

You can tell Pipewire is a serious project when they implement in a few months stuff that took years for Poettering to fix.

[Toggleton]

Interesting. How does one switch to Pipewire? Does it depend on a specific desktop environment? What about desktop environments that require PulseAudio? Does PulseAudio need to be uninstalled or disabled first?

For me on Arch it was just install pipewire + pipewire-pulse (that should uninstall Pulseaudio https://wiki.archlinux.org/index.php...e#Installation I think that was all maybe restart the Device and
"pactl info" should then show -> Server Name: PulseAudio (on PipeWire 0.3.22)
Did only test it with sway and a bit with KDE

Here is a other guide for Gentoo with sway https://www.reddit.com/r/linux/comme...le_using_sway/

[pal666]

/sarcasm mode on
is it just me, or does it appear, that though the developer has funding to code sound driver, wasn't funded to buy sound hardware to test it with . . . maybe michael has some spare sound cards lying around. (I bet they didn't even know they could buy one of those, the probably think a sound card is that thing that comes with the motherboard.

/sarcasm mode off

it's not sound driver. alsa is sound driver. and yes, developer has sound hardware, you can't find computer without one. your sarcasm doesn't look sarcastic at all

[pal666]

Well, Pulseaudio was as well, wasn't it?

no, it was developed by non-redhat employee

[sb56637]

Interesting. How does one switch to Pipewire? Does it depend on a specific desktop environment? What about desktop environments that require PulseAudio? Does PulseAudio need to be uninstalled or disabled first?

[pal666]

it's pretty seamless overall. Nothing like wayland.

could it have something to do with the fact that wayland is new protocol requiring every application change while pipewire is new implementation of same protocol(s) requiring no application changes?