Forum Discussion
Allow muting a person only for me
- Daniel BlumentrittSep 02, 2022Brass Contributor
Even with headsets, if some users are remote and others are sitting a few feet from you, you'll hear them both in person AND through your headset, which is highly unsatisfactory. Other voice chat programs figured this out years ago.
- crackerEVJul 07, 2022Brass Contributoreven if wearing headsets, the non electronic audio and subsequent electronic audio some milliseconds later is wildly annoying and distracting
- crackerEVJul 07, 2022Brass Contributor
headphones, as a hardware solution, is not what OP asked for, they clearly asked for software solution
- peterrrattewMar 10, 2022Brass Contributor
It's not always possible to go to a conference room if they are already booked or you are in a shared workspace. So it would be pretty useful to be able to mute a specific participant.
- KLeDematicAUMar 14, 2022Iron Contributor
This is a feature which I see will be more useful as parts of the workforce start returning to the office and parts continue working remotely. People in the office will always be using their desk stations to join Teams meetings due to the need for sharing personal work content, often with other office people mixed with remote people so the effect of hearing office voices both live and through Teams will become more of an annoyance.
I also imagine that the way Teams takes multiple input streams of audio and video and combines them into a single stream of mixed audio and video to multiple participants is the main stumbling block to implementing this feature. It would need the Teams server to also have the ability to customise the mixed audio output stream for each participant, so instead of a single mixed stream there would potentially be as many output streams as there are participants in the Teams meeting.
Regardless, it would be an awesome feature enhancement if Microsoft could get it working.
- g4nzgMay 09, 2023Copper ContributorAs it's a local 'thing', where you're just muting the audio from a specific user/s on your own application for that specific meeting (I assume), this could be a simple application-level feature that didn't hit the servers at all.
So, an easy fix, most likely.