(Looks at code)
Yup, you’re right. Windows will query (say) 192 kHz for 16-bit, 24-bit,
24-in-32-bit, and 32-in-32-bit, but will query 176.4 kHz for 16-bit only.
Can you report the problem via the Feedback Hub and send me a direct link?
From: John Kraft<mailto:johnfkraft@xxxxxxxxx>
Sent: Thursday, September 29, 2016 4:51 PM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] 176400 sample rate support in Windows 10 build 14393
sound device properties
I'm seeing some odd behavior with the 176400 sample rate when our device is
being queried for its supported audio formats. Our device exposes the
KSDATARANGE_AUDIO format on its WaveRT miniport pin:
{
{
sizeof(KSDATARANGE_AUDIO),
0,
0,
0,
STATICGUIDOF(KSDATAFORMAT_TYPE_AUDIO),
STATICGUIDOF(KSDATAFORMAT_SUBTYPE_PCM),
STATICGUIDOF(KSDATAFORMAT_SPECIFIER_WAVEFORMATEX)
},
2, // Max number of channels
32, // Min bits per sample
32, // Max bits per sample
44100, // Min sample rate
192000 // Max sample rate
},
When I open the list of support formats on the advanced tab of the device
properties window in the Sounds control panel, I see 44100, 48000, 88200,
96000, and 192000 formats. What I don't see is 176400. I set a breakpoint in
the driver's ProposedFormat property handler, but I'm only seeing
KSPROPERTY_TYPE_SET calls for 176400 with a bit depth of 16.
Has anyone else observed issues with this, or is it something specific to our
implementation?
Thanks.
-John
