If the device supports only 24-bits-in-24-bit containers, I would expect the driver to fail any request for 24-bit-in-32-bit containers. If the driver is falsely accepting requests for formats that the hardware doesn't support, that would explain why the audio data is corrupted. From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Daniel E. Germann Sent: Friday, October 14, 2011 5:08 PM To: wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] Re: USB audio record problem Just to be 100% sure, I connected a USB analyzer to our USB audio device, and I can confirm that valid audio data is being sent over the USB, and not just 000000's or FFFFFF's. I can see audio on the USB analyzer even when there's only 000000's and FFFFFF's in the capture buffer. I am even more confused than ever. Is there any way a USB audio device could misbehave and cause the USB audio stack in Windows XP to do this, even when there's valid audio being sent over the USB? Thank you, -Dan ****************** 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/