SampleHardwareDriver bug?
SampleHardwareDriver bug?
- Subject: SampleHardwareDriver bug?
- From: "Mike Kluev" <email@hidden>
- Date: Thu, 18 Dec 2008 16:43:41 +0300
My HAL plugin is based on SampleHardwareDriver sample code. It has
more
than one sample rate, and while the rates are shown in HALLab and AMS,
I can't change them. I traced it down to the following:
When my client app calls
AudioDeviceGetProperty(device, channel, isInput,
kAudioDevicePropertyNominalSampleRate ...)
the channel parameter is getting translated into the the
AudioObjectPropertyAddress's
inAddress.mElement and the isInput parameter is getting translated
into the
inAddress.mScope ('inpt' or 'outp') inside SampleHardwareDriver
plugin.
However, the SampleHardwareDriver's
HP_DeviceFormatList::GetPropertyData
completely ignores mScope (it has logic that tries input first, then
output).
Also, HP_DeviceFormatList::SetPropertyData completely ignores the
scope
(it has different logic in its kAudioDevicePropertyNominalSampleRate
handler
that not only ignores the scope but is completely incompatible with
the
GetPropertyData logic).
Is that not a bug in SampleHardwareDriver?
Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden