1. I have to modify my audio settings every time I start a call in Teams on Linux because it keeps losing my audio device.
2. In my audio settings UI, half the time I switch my devices the speaker test doesn't work.
3. In my audio settings UI, whenever I switch my mic I hear myself. The mic feedback only disappears 30 seconds after I close the settings UI.
4. My work headsets have a robotic sound (likely caused by an incorrect bitrate or buffer size). I can only use work bluetooth headsets via their dedicated dongle.
This was my default experience on a popular debian based distro. And it mirrors the general experience I see online. Things are unstable and a mess.
I started reading this article and it's embelished with phrases like: "is a professional-grade audio server", "widely used in professional audio production environments", and general language that sounds like a sales pitch. This does not fit with anything I'm familiar with.
I would have preferred a neutral and semi technical approach, with 10% of the buzzwords. As written, I trust nothing.
That would be your headset being in headset mode. I'm on Debian Testing, and I'm finally able to exit headset mode and use a high quality audio codec instead. I hope that's the direction Linux is heading.
Oh no, it's not. I've swapped modes more than imaginable. And even if it were in headset mode the quality would be inacceptable compared to what I was getting on windows. I even manually tried to change pulseaudio settinga for that device with no luck. And I don't feel like turning this thread into a debugging session. But, like, correctly figuring out reasonable bitrates should work by default.
The Teams web app works very well in Chrome. I only miss being able to set a custom background to my video and popping out presentations into their own window. It seems much lighter on resources too, maybe because Chrome does more of the video encoding or decoding using hardware.
1. I have to modify my audio settings every time I start a call in Teams on Linux because it keeps losing my audio device.
2. In my audio settings UI, half the time I switch my devices the speaker test doesn't work.
3. In my audio settings UI, whenever I switch my mic I hear myself. The mic feedback only disappears 30 seconds after I close the settings UI.
4. My work headsets have a robotic sound (likely caused by an incorrect bitrate or buffer size). I can only use work bluetooth headsets via their dedicated dongle.
This was my default experience on a popular debian based distro. And it mirrors the general experience I see online. Things are unstable and a mess.
I started reading this article and it's embelished with phrases like: "is a professional-grade audio server", "widely used in professional audio production environments", and general language that sounds like a sales pitch. This does not fit with anything I'm familiar with.
I would have preferred a neutral and semi technical approach, with 10% of the buzzwords. As written, I trust nothing.