hdaudio.sys supports KSPROPERTY_PIN_PROPOSEDATAFORMAT (GET) on HDMI outputs. There was a known test bug in GAudiT where the KSPROPERTY_PIN_PROPOSEDATAFORMAT test cases would incorrectly call the wrong test functions, and end up testing KSPROPERTY_PIN_CONSTRAINEDDATARANGES instead. This was fixed in July 2009. But it doesn't seem to match your symptoms. Can you post (or send me privately) the full log for the failing test case? -----Original Message----- From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Eugene Muzychenko Sent: Sunday, May 19, 2013 3:53 AM To: wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] GAudit and KSPROPERTY_PIN_PROPOSEDATAFORMAT (GET) Hello! Recently I have implemented KSPROPERTY_TYPE_GET in KSPROPERTY_PIN_PROPOSEDATAFORMAT handling (KSPROPERTY_TYPE_SET was implemented earlier and works normally). Testing my driver with GAudit, I always get failures on all 16.200:400.13.x cases (KS properties\KSPROPSETID_Pin\KSPROPERTY_PIN_PROPOSEDATAFORMAT\xxx). On log level 10, each case reports only follwing messages: Property SET is supported Property GET is supported Failed to retrieve pin property I set breakpoints on the property handler and saw that it called exactly two times for each case. Each time the handler is called with KSPROPERTY_TYPE_BASICSUPPORT flag and output buffer size 4. As required, my driver returns only access flags (KSPROPERTY_TYPE_GET | KSPROPERTY_TYPE_SET) and STATUS_SUCCESS. No calls with flags other than KSPROPERTY_TYPE_BASICSUPPORT are made. The handler never fails PROPOSEDATAFORMAT requests received from GAudit. If I disable GET support by removing KSPROPERTY_TYPE_GET from AccessFlags, all these cases are passes successfully. Tried x86 GAudit from WLKs 1.6.8367 and 1.2.6475, both from wlk and wlk\xp subdirectories. All four behave exactly the same way. Tried with other audio drivers but none of them support PROPOSEDATAFORMAT/GET so these cases are passes successfully. Is there the same GAudit bug in different WLK releases or such BASICSUPPORT requests must be processed a special way? Regards, Eugene ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/ ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/