Re: what would cause QTSetComponentProperty to fail with a kAudioUnitErr_InvalidPropertyValue err?
Re: what would cause QTSetComponentProperty to fail with a kAudioUnitErr_InvalidPropertyValue err?
- Subject: Re: what would cause QTSetComponentProperty to fail with a kAudioUnitErr_InvalidPropertyValue err?
- From: Michael Dautermann <email@hidden>
- Date: Thu, 15 Mar 2007 18:27:23 -0700
Do you mean I should make sure all the selectors for
DeviceGetPropertyInfo and StreamGetPropertyInfo get handled?
I mean adding printf's that display every call into your plug-in
and what those routines returned...
In my debugging output, I print out all selectors that come in
through those two API's.
...which appears to be what you are doing.
The only selectors that my DeviceGetPropertyInfo implementation
doesn't handle are 'pmas' and 'namr' ( I don't see these defined
in any header files under /System/Library/Frameworks, so I am not
sure what to do with them or if they matter ).
The 'pmas' selector is unknown to me. I don't know what that one is
for. The 'namr' selector is an ancient selector that returns the
non-localized (that is, English) name of the device as a C-string.
At any rate, I can't imagine that either of these properties are
what is causing the SG to return that error. One puzzling thing
about this to me is that the HAL always returns error codes that
are 4CC's or are kernel errors. Both of these would look more or
less like very large positive integers. The error you are getting,
kAudioUnitErr_InvalidPropertyValue, is specific to the AudioUnit
stuff. To get that error, I think would involve some problem with
the Sequence Grabber talking to it's instance of the HAL output AU.
If this is something that you can package up and send to us, you
might want to do that in the form of a bug report.
Actually, with the bosses breathing down my neck (and holding a sword
over it, too), I submitted the plug-in source with my dts tsi
yesterday, so it's probably working it's way through the bureaucracy
to you or Brad already.
Another suggestion that was given to me by Chandrasekhar Ramakrishnan
(thanks!) was to chuck my app and try using the HALLabs "play-
through" option, but this won't work as the app instantiates a 'vdig'
for a video stream which also feeds data to the audio plugin at the
same time.
My audio plug-in should be selectable without having live audio
streams (or a device connected) though, right?
thanks again
michael
_______________________________________________
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