Re: kAudioUnitErr_Unauthorized and auval
Re: kAudioUnitErr_Unauthorized and auval
- Subject: Re: kAudioUnitErr_Unauthorized and auval
- From: Marc Poirier <email@hidden>
- Date: Wed, 8 Feb 2006 09:48:42 -0500
On Feb 8, 2006, at 1:27 AM, Andrew Kimpton wrote:
Stefan Gretscher wrote:
Hi Andrew,
we're aware of this problem, and I've recently talked to Bill
Stewart about it.
The current idea is that Bill's team could change auval so that it
handles kAudioUnitErr_Unauthorized with a separate return code
which is indicating that validation wasn't performed because of
authorization failure, and our team could then adopt Logic so that
it evaluates this new return code and presents corresponding
warning dialogs etc.
This sounds good to me, too.
This is how things would be handled if kAudioUnitErr_Unauthorized
is returned from Initialize(), in case it's returned from
OpenAComponent() the behaviour would be slightly different because
then Logic could not open any UI for such an AU, so such an AU
must provide some other way of handling authorization.
This looks good too. However at this (late) hour I'm not sure how
an AU would get OpenAComponent() to return the unauthorized error ?
If you're using the AU SDK doesn't OpenAComponent 'turn into' the
AU's constructor ? And there's no return value there (just the
possibility of throwing an exception).
Right, you can throw an exception, and then in the AU SDK, the
exception is caught and returned as an error code from the handler
for kComponentOpenSelect.
And of course you can modify the AU SDK, or not use it, etc.
The way PACE wrapped plugs work, whatever PACE adds into them, it
results in them returning this error from OpenAComponent() when they
are not authorized.
Marc
_______________________________________________
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