Windows 10: Headset microphone muted by default

Hello,


I have the "Tronsmart Spunky beat" Bluetooth earphones, which have a mic and can be used as a headset.


Whenever I connect them, the mic appears muted by default, and I have to go to the settings and unmute it so I can use it.


This is what it looks like after connecting them:





Is there any way to make the mic unmuted by default without having to change it every time?


Thanks!

:)

 

microphone mutes itself

When i go into properties the mike is muted. When I unmute it works for less than a minute then mutes again. The only suggestion I have found is set as default device which does not solve problem. I have also read it is a virus but I cannot solve with malware or virus scans. It first became a problem just a few weeks ago while skyping. Never had a problem with mike until then.

Troubleshooter finds the microphone muted and fixes, Within a minute the microphone mutes itself again.

 

USB Headset Microphone Mute Button not Synchronized with System Device Driver Microphone Mute Checkbox in Both Directions

This is a followup on a post I made almost a year ago and I received no explanations here is link to that post: Headset
Microphones Do Not Have Programmatically Detectable Microphone Mute from Headset Mute Button

I have a Dell Inspiron 3650 desktop running Microsoft Windows 10 Pro Version 10.0.18363 Build 18363.

I could be wrong but I believe that this problem needs to solved at the device driver level which would probably involve redesign of device driver specifications effecting all existing drivers/hardware and all manufactures? If this is the case then unfortunately
I guess it will never be resolved until some future version of Windows fixes the problem.

I am trying to use NAudio to mute and unmute my USB headset microphone programmatically using MicrophoneDevice.AudioEndpointVolume.Mute = True or MicrophoneDevice.AudioEndpointVolume.Mute = False

I ran into the problem of the USB device not synchronized to the system device driver. I used to be able to use the Win32 API back in the Windows XP days and don't recall this being a problem. When Windows 7 came out the entire Mixer design for Windows
took a turn for worst, Direct-X Mixer functionality was gone forever and this problem was the result.

THE QUESTION:

Can anyone give an example in Visual Studio 2017 or 2019 C# or VB .net that can make the USB Mic mute button and the OS mute checkbox operate in sync in both directions. Remember, that old VB6 API code related to the microphone does not
work nor does it apply to the Windows 7-10 OS and device driver designs.

THE SYMPTOM:

I have three different brands of USB Headsets with Microphone and Mute Button Wired and Wireless all with the same behavior as follows:

1. If the Mute checkbox shown below is UNCHECKED and the microphone's mute button on the headset is toggled on and off the microphone is muted by the headset's microphone internal circuitry which does successfully mute the sound to the record capture,
   however it does not update the mute checkbox in system settings for the USB microphone device.
2. If the Mute checkbox shown below is CHECKED then the Headset's Microphone Mute button has no effect what so ever.

NOTE: There isn't any Win32 API solution that I can figure out or find to solve this sync problem and apparently NAudio's solution can not address the problem either because the Windows API in it's redesign of the mixer
never considered this scenario of bidirectional syncing between the USB device driver and the OS.

I will try to give an example of how this can be an unsolvable problem the best I can. I am working on a voice driven program for the blind and I can't expect them to be able to turn off a checkbox in settings no more than I can have a visual queue
showing them if the microphone is on or off. The only feedback I can give is sound effects and the computer talking to them.

Functional Example:

I am using System.Speech.Synthesis, System.Speech.Recognition and NAudio.

All of my code works I just need to sync the mute. Consider the code below (simplified).

1. System settings have the mute checkbox unchecked, headset mute button is muted.
2. User un-mutes the microphone with the headset switch.
3. User speaks into the microphone and says "Stop Dictation"
4. The user forgets to quickly mute the microphone with the headset's mute button so that the SpeechRecognition_SpeechRecognized event does not falsely trigger based on the headset's speaker volume being so loud that the microphone picks up the computer
   talking or any background noise in the room.
5. The code wants to mute the microphone while the computer is playing a sound effect and speaking to compensate for the possibility of #4 above.
6. The code wants to keep the microphone muted until the user un-mutes the microphone with the headset switch.
7. The code makes it's sound effect and tells the user that the dictation has stopped.
8. The user no longer has control with the headset's mute button unless he/she manually turns off the mute checkbox in settings.

RELATED IMAGES:

 

Headset Microphones Do Not Have Programmatically Detectable Microphone Mute from Headset Mute Button

I have a couple of gaming headsets both with a mute button. If I go into Windows 10 Sound Manager I can see the headset speakers and microphone and all have a mute checkbox.

I have written a program in C++ that allows me to mute or un-mute the microphone as seen in the Sound Manager and the checkbox is turned on and off successfully coinciding with my C++ program settings.

This setting is overriding the Mute button on the headset and I can see no way to detect the user muting the microphone via the headset's mute button. I am trying to incorporate into an application for the
Visually Impaired or Totally Blind the ability to play a unique sound effect into the headset speakers that would tell the user if the microphone is muted or un-muted when they press the headset's mute button.

See also directly related artical: Microphone AudioEndpointVolume.Mute property not updated when device muted · Issue #337 · naudio/NAudio

I already know that this behavior is "By Design" as of Windows Vista.

Question 1: When Direct-x was retired, why wasn't the ability to have separate volume and mute controls for each device considered in the new Vista design? The decision was apparently made to push that
functionality to become the device driver's responsibility, who's volume and mute properties are not accessible programmatically.

I have a Dell Computer Running Windows 10 1809 with MAXXAUDIOPRO by Waves

I really do miss Direct-X it behaved perfectly for developers.

Please consider adding such functionality to future versions of Windows and to also have as part of the Windows Development Committee a member that represents the Hearing Impaired as well as the Visually Impaired
that will give good input for enhancements to the Ease of Access Technology.

Thank you all for listening.