Re: Application Behaviour when AU returns kAudioUnitErr_Unauthorized
Re: Application Behaviour when AU returns kAudioUnitErr_Unauthorized
- Subject: Re: Application Behaviour when AU returns kAudioUnitErr_Unauthorized
- From: Stefan Gretscher <email@hidden>
- Date: Fri, 6 Jan 2006 01:34:10 +0100
Hi Andrew,
Logic interprets kAudioUnitErr_Unauthorized as "I won't render any
meaningful audio, but you can open my UI so the user can manage
authorization".
The problem is that if no UI for the AU can be opened, how is the
user supposed to enter an authorization code etc.?
Best,
Stefan
Am 06.01.2006 um 01:22 schrieb Andrew Kimpton:
If our AU is not authorized we return kAudioUnitErr_Unauthorized
from the Unit Initialize() method.
However some hosts seem to either 'ignore' this error or at the
least continue on and try to open the Unit's view component even if
the above error is returned.
For example SoundTrack Pro will attempt to change the stream format
even if the above error is returned. Logic 7.0 actually works
properly and stops doing anything with AU after this error, however
Logic 7.1 displays it's own 'plugin unauthorized' dialog but then
persists in opening the Units view component.
Digital Performer and AULab also attempt to open the view component
in spite of the Unauthorized error.
It seems to me that if the process component returns any sort of
error from Initialize then 'all bets are off' and the unit is not
usable, and that includes not attempting to open it's UI (after all
what's the UI going to control ? There's no process component). Or
am I missing something here ?
Andrew 8-)
_______________________________________________
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