PipeWire 0.3.31 Released With Better JACK Support, More Crash Fixes

[jacob]

I gave up trying to use the "native" Teams app. Just sign in via Chromium. Way better, and no Microsoft crap running locally.

You realise that the web app you run on Chromium runs locally and is, for the most part, the same JS code as the standalone client (which is based on Electron)?

[jacob]

I'll dogpile as well, PipeWire works for me on Teams. Maybe its your version of PipeWire? I'm running latest rolling Arch, happens to be what's mentioned in this article.

I'm running Fedora Silverblue, atm it has pipewire 0.3.30.

[aorth]

The only problem I've had is that MS Teams doesn't work with PipeWire. I know the problem is apparently on Teams' side rather than PipeWire's but it's still a big bummer.

I gave up trying to use the "native" Teams app. Just sign in via Chromium. Way better, and no Microsoft crap running locally.

[oiaohm]

I'll dogpile as well, PipeWire works for me on Teams. Maybe its your version of PipeWire? I'm running latest rolling Arch, happens to be what's mentioned in this article.

If you read over the pipewire bug report for teams its quite a few layers of complexity. https://gitlab.freedesktop.org/pipew...e/-/issues/838 One is if pipewire says here teams here is a 24 bit sound output and teams go bugger you I only support 16 bit audio out that one can be got around using apulse on top of pipewire but that requires pipewire with-alsa support enabled.

The reality here is MS Teams on Linux with Pulseaudio at times is a pain i the but to get working. Lot of cases it MS teams limit audio support of course pipewire exposes some things differently so a system that works with MS Teams before putting pipewire on does not but if you alter different configurations in Pulseaudio lot of cases MS Teams would fail as well.

MS Teams is really a pain on but program on Linux caused by limit audio support and very quirky detection. Yes very quirky detection as in claiming no speakers or microphone just because its the wrong bit or speed or MS Teams is just having I be stupid this start up. Yes MS Teams is fun like that on Linux run it one everything works no updates run it again and detection can fail then run it again it working again. Yes MS Teams on Linux at times can be a game of coin flip.

There was always going to be a handful of programs that would be harder than the other to get working.

[damentz]

Then you're lucky, here it worked with PulseAudio but since the switch to PipeWire sound in Teams doesn't work for me

I'll dogpile as well, PipeWire works for me on Teams. Maybe its your version of PipeWire? I'm running latest rolling Arch, happens to be what's mentioned in this article.

[ChristianSchaller]

Unplug headphones and plug it back in and it isn't found. Its great. I see no problem here.

Maybe this one will fix that. Could pull it down now and find out but will wait for now.

I have the same issue, looked into it with Wim Taymans and from what we can tell it is likely to be an ALSA driver bug, where the correct event is not fired when you plug back in again and thus PIpeWire doesn't know that it has been re-plugged. Filed a bug against ALSA, but no response to the bug report yet.

[zxy_thf]

As a light user I haven't noticed any difference since F34 switched to PipeWire.
The only exception is I have to manually restart its daemon after "dnf update -y", which is not needed by PulseAudio server.

[lethalwp]

The only problem I've had is that MS Teams doesn't work with PipeWire.

I use Teams with pipewire everyday for my work. There were some early issues (crackling microphone), but it's all fixed now.
I still have to adapt the in/out device settings in Teams after almost every suspend/resume of my pc.

Another tool that works great with pipewire is pavucontrol, which lets you set what application connects to what device.
If you have teams problems, try to check if you can fix it with pavucontrol ?

The last teams big problem is the sharetray that is empty when native in wayland. And MS doesn't care i guess...

[Alexmitter]

At the beginning I got quite a few pops and crackles, quite similar sounding to a dirty vinyl but its gone since a few versions and otherwise it is rock solid.
I especially fancy the latency, playing the rhythm game osu!lazer in native wayland and with pipewire is to my extend a better experience then the game ever had on Windows.

[jacob]

Looking on PipeWire's GitLab, there seems to actually be an open issue regarding Teams.
Seems like it's indeed an issue on Teams itself, I can only hope that Microsoft fixes it once more distros start switching to PipeWire by default, but seeing as they've been neglecting and even downgrading the Linux client (in terms of features) that may or may not happen any time soon.

I've used PipeWire + Teams on at least 3 devices and so far I've never personally encountered this.
Have you tried any of the workarounds posted in the issue thread?

The only workaround that works (somewhat) reliably is to open Teams, *then* pair with a Bluetooth headset. At that point Teams detects the audio device and I can either use Bluetooth or even switch to my laptop's speaker and microphone.