RE: Bug in CoreAudio, Channel Names property?
RE: Bug in CoreAudio, Channel Names property?
- Subject: RE: Bug in CoreAudio, Channel Names property?
- From: "Alex Sheh" <email@hidden>
- Date: Tue, 28 Nov 2006 10:39:53 -0800
- Thread-topic: Bug in CoreAudio, Channel Names property?
You might conceptually consider them one "property", but
they are actually 2 different properties. If you've ever implemented an
Audio HALplugin, you'll know that there are 2 code paths that the 3rd party
writes - one that returns a CFString and the other a C-string. Notice that
kAudioDevicePropertyDeviceName and kAudioDevicePropertyDeviceNameCFString
are 2 *distinct* AudioDevicePropertyIDs ('name', 'lnam'), NOT a single
AudioDevicePropertyID with a separate return type flag. If anything you
would want to contact the 3rd party and see whether they are indeed missing the
C-string implementation, as well as double check your own code. Note that
CFStrings are better for localization so it's not inconceivable that the
C-strings were missed or even purposely omitted.
Hi Alex,
You are right, providing names is
optional. I'm not concerned about drivers that do not implement these
properties.
Please read my note carefully.
What I'm talking about
is the situation in which the driver *does* implement the property, yet
CoreAudio does not let an application access it using one of the documented
mechanisms.
BTW, the driver does not implement two properties - it's the
same property, which can be accessed in two ways. Either by retrieving pointer
to a CFString object or by retrieving a null terminated string.
Now, In
cases where the driver *does* provide the property, CoreAudio allows retrieving
it as a CFString, but not as a null terminated string. And that's what I
consider a bug in CoreAudio.
Thanks.
Devendra.
At 11:47 PM
11/27/2006, Alex Sheh wrote:
Hi Devendra,
3rd party CoreAudio drivers are not
required to implement either of the below properties, and many do not - it's
not a CoreAudio bug, rather a driver deficiency. AFAIK, it is something
that you can't rely on being implemented when you query the
driver.
- Alex
From:
coreaudio-api-bounces+asheh=email@hidden [
mailto:coreaudio-api-bounces+asheh=email@hidden] On
Behalf Of BlazeAudio Developer
Sent: Saturday, November 25, 2006
3:02 AM
To: email@hidden
Subject: Bug in
CoreAudio, Channel Names property?
Hi,
I
have run across a situation which might be a bug in the CoreAudio
(framework?).
This has to do with the audio device property for channel
names.
If I try to retrieve the property using kAudioDevicePropertyChannelName it
will not work.
However, if I use kAudioDevicePropertyChannelNameCFString, it works
just fine!
Should I file a bug report, or am I missing something
here?
Thanks.
Devendra.
_______________________________________________
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