I should note that I am by no way planning that this will be part of production code - I'm looking for an easy way to debug an issue in the sound processing, which could be related to a hardware setting (suspected) or could be related to post processing in the chain after my GFX APO. Kind Regards - Preston On Tue, May 14, 2013 at 11:30 AM, Tim Roberts <timr@xxxxxxxxx> wrote: > Preston Fick wrote: > > > > Does anyone have experience with the following IOCTL: > > > > IOCTL_AZALIABUS_SENDVERBS > > ( > http://msdn.microsoft.com/en-us/library/windows/hardware/ff536233(v=vs.85).aspx > > < > http://msdn.microsoft.com/en-us/library/windows/hardware/ff536233%28v=vs.85%29.aspx > >) > > There's an interesting cut-and-paste failure in the example on that page: > > To initiate communication with the audio codec, the class driver > calls the DeviceIoControl function with the > following parameters: > BOOL DeviceIoControl( > (HANDLE) hDevice, > IOCTL_STORAGE_GET_MEDIA_SERIAL_NUMBER, > > I'm pretty sure you aren't ever going to be sending IOCTL_STORAGE ioctls > to an audio codec. I'll send a doc update about this. > > -- > Tim Roberts, timr@xxxxxxxxx > Providenza & Boekelheide, Inc. > > ****************** > > 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/ > >