It's amusing that you couldn't chase down this information, because it is all clearly documented. The ioctl code is IOCTL_KS_PROPERTY, which is documented. The buffer contains a KSPROPERTY and a KSDATAFORMAT. The property GUID is "1D58C920-...", which is KSPROPSETID_Connection. The property number is 2, which is KSPROPERTY_CONNECTION_DATAFORMAT, also well documented. The flags word is KSPROPERTY_TYPE_SET, which means the caller is trying to set the data format. The rest of this should be a KSDATAFORMAT.A bit embarrassing, I had a bug in the output where I was looping for the buffer with i++ and p++ meaning i missed every 2nd line which was why I was baffled why the guid didn't match. I have since learn how to debug in kernel mode :-D and in a ureaka moment I released what KSPROPERTY.id is for from your statement above.
The IO codes are all making scene now. Thanks again for your help. ****************** 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/