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.
I found a fix for my system
under sound settings > Microphone Properties > Advanced Tab uncheck the "Allow Application to take exclusive control of this device"
mbaker-wv
- CastyMcBoozerFeb 08, 2021Copper Contributor
mbaker-wv Settings in the app? Settings in Windows? Settings in macOS?
There is no "Microphone Properties" in either Windows 10 Settings or in the Teams application. I don't have my Macbook with me at the moment.
- NilsReichertJan 05, 2021Copper Contributor
Incorrect. Exclusive access setting is *ignored*.
Let me explain the problematic behavior and how it happens.
Mic volume stays as it is, but as soon as you open the menu Device Settings to select Mic and Speaker, then it is active and stays active, the Mic volume auto adjust.
So if you plan to never touch Mic and Speaker selection, *never open* device settings menu, and you are good, however, if you need to check or switch, then it will happen.
Only workaround that prevents Teams from auto adjust volume (if I need to change device settings) is to install vb cable (but then there is a delay because of listen to device) or to install voicemeeter (virtual mixer, currently using this as solution)
- Kevin296Jan 05, 2021Copper Contributor
NilsReichert Thank you! This is the exact issue I have been seeing for one of our users. I thought I had fixed it, but just received an email stating it is doing the same thing. If anyone has a real fix for this problem that would be ideal.