L
Larry G. Robertson
Guest
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
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.
Continue reading...
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
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.
Continue reading...