[wdmaudiodev] Re: Yet more jack sense questions
- From: Matthew van Eerde <mateer@xxxxxxxxxxxxx>
- To: "wdmaudiodev@xxxxxxxxxxxxx" <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Wed, 8 Sep 2010 16:23:34 +0000
The driver may not be bubbling up the jack sense state to the
KSJACK_DESCRIPTION structure. Try installing hdaudio.sys and rerunning your
sample code.
http://blogs.msdn.com/b/matthew_van_eerde/archive/2010/08/23/troubleshooting-how-to-install-the-microsoft-hd-audio-class-driver.aspx
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of
Edward_Averill@xxxxxxxxxxxx
Sent: Wednesday, September 08, 2010 9:18 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Yet more jack sense questions
Ok, running Vista, I have some sample code that goes out, enumerates
endpoints, gets a KSJACK_DESCRIPTION for each jack, and prints IsConnected.
That was the easy part..
What I'm seeing is that EVERY endpoint says it's connected. Ok, fine, this is
a Dell laptop and it's possible the onboard audio doesn't support jack sense
(in which case it'd always return connected, according to the docs). BUT (you
knew there was a BUT, right?)..
..when I stick a jack in to LINE IN, the little applet that shows jacks etc.
pops right up and knows I just shoved it into LINE IN. The status my program
prints doesn't change, but somehow the applet knows. Ok...
So, is it possible that there's something device-specific in the applet that
lets it get the info reliably OUTSIDE of the standard API? Or does registering
for status changes somehow interfere with other apps ability to reach out and
look at the current state of the jacks?
Comments, suggetions, MSDN pages? All info appreciated.
..ed..
Other related posts:
