One of the most irritating (and slightly painful) parts of joining a Microsoft Teams call could soon be fixed by a new update.
The video conferencing service is a popular choice for many companies, meaning calls with large numbers of participants joining at the same time, and from the same location (such as a meeting room) are a common occurrence.
However, often when multiple people join a meeting in the same room, a feedback loop is created, which causes echo, which in most cases quickly escalates to howling - with Microsoft likening the noise to when a musician holds the mic too close to a loudspeaker.
Teams' howling
Fortunately, a new fix is coming for Microsoft Teams users. In its entry in the official Microsoft 365 roadmap, the new "Ultrasound Howling Detection" describes how it aims to prevent this noise for users on Windows and Mac across the world.
Microsoft says that the update should mean if multiple users on laptops join from the same location, it will share with the user that another Teams Device is detected in their vicinity and is already joined with audio to the current meeting.
If a user has already joined with their audio on, Microsoft Teams will automatically mute the mic and speakers of any new the person who then joins the call, hopefully putting an end to the howling and screeching feedback.
Thankfully, the update is already listed as being in development, with an expected general availability date of March 2023, so users shouldn't have to wait too long to enjoy.
The news follows a number of recent updates largely aimed around improving the audio quality on Microsoft Teams calls using AI and machine learning.
The new updates are the result of using a machine learning model trained on 30,000 hours of speech samples, and include echo cancellation, better adjusting audio in poor acoustic environments, and allowing users to speak and hear at the same time without interruptions.
- Here’s our list of the best productivity tools right now
from TechRadar - All the latest technology news https://ift.tt/IiPfQYy
via IFTTT
Comments
Post a Comment