Forum Discussion
Disable Microphone Auto Adjustment
- Jul 06, 2020
Workaround on macOS: create an aggregate device to "mask" the gain settings from Teams.
Steps:
1. Open 'Audio MIDI Setup' application
2. In the left pane, click + symbol and choose Create Aggregate Device
3. Ensure that the new aggregate device is selected in the left pane
4. In the main window area, select the 'Use' checkbox for your real input device
5. Select the real input device from the left pane and set the Master Stream input gain correctly
5. Optionally rename the newly created aggregate device by clicking its entry in the left pane
6. Quit & restart Teams application
7. In Teams, choose the newly created aggregate device as the microphone deviceBecause the aggregate device does not have a gain setting, Teams cannot f* it up.
Settings -> Devices -> Automatically adjust mic sensitivity (disable)
- Michael TroelsenJul 19, 2021Copper Contributor
This should be fixed in the latest version of teams 1.4.00.16575 with the introduction of automatically adjust mic sensitivity.
- Chopo127Aug 26, 2023Copper Contributor
- tjhallumFeb 16, 2024Copper Contributor
Chopo127, like you, I also do not have that toggle.
Apparently, back in 2021, Microsoft added a helpful toggle for disabling automatic volume sensitivity adjustment...and it seems they've since deleted that toggle from the UI 🤷.
What some people say is supposed to be in MS Teams' device settings:
What's actually available in my device settings within MS Teams:
As you can, I don't have a toggle to disable "Automatically adjust mic sensitivity."
I'm using the latest version of MS Teams available:
This is absolutely infuriating!!! I have a studio-grade XLR mic and USB audio interface that sounds great in every other app, but MS Teams makes me sound like trash on work calls. At the beginning of a call, it always jacks the sensitivity of my mic up to almost 100%, and then for the first ~5-10 seconds when I start to speak it blows out the eardrums of everyone else on the call. This is completely crazy and fixing it needs to be elevated to priority #1 for the MS Teams developers.