OS Level Mute Failure
This support article is for both macOS and Windows users that are experiencing issues in which their microphone is not being controlled by the MuteMe application.
We learned a short while ago that there are a handful of products out on the market that do not conform to normal standards and OS level mute functionality is not working. Both macOS and windows have functionality in which a microphone should be able to be muted based on the operating system sending certain commands. Some devices however fail to conform to the standards and persist to remain activated even if the operating system sends a mute command. This issue persists and exists with the drivers of those microphones and the operating system itself.
Temporary solutions:
There are a handful solutions users could rely on based on their configuration and applications. These solutions although not as elegant as desired could still work for a majority of users and use cases.
Application Level Sync:
Application level sync continues to function across all the platforms that we support regardless of OS level mute functionality. By setting level two and level threes sync in the MuteMe application you will still be muted in your conferencing applications.
Using a Different Microphone
Change the default microphone from one that is not supported to a version that is supported.
Long Term Solutions
We have added this problem as something that we have a plan to solve. We are exploring changes that will allow our software to sit in the middle between the product and software to allow us to control the microphone even if the hardware does not support it. This is something that we have on our product roadmap.
Devices With Known Issues:
- Realtek Microphone on some Gateway Computers - Windows 11 Tested
- RODE NT Microphone on macOS
- SHURE Microphone on macOS
- Bang and Olfsen Beosounds A1 Gen2 Bluetooth Mic
- HyperX Cloud Headset