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: William Stewart <email@hidden>
- Date: Thu, 5 Jan 2006 16:49:59 -0800
On 05/01/2006, at 4:22 PM, Andrew Kimpton wrote:
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.
This is both desirable and possibly even expected behaviour - for
instance, the AU might use its view to provide UI for the user to
register the AU.
For example SoundTrack Pro will attempt to change the stream format
even if the above error is returned.
That would be an ST bug and should be filed appropriately
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.
As I said, that is ok - you can always fail to open the view if this
is a concern for you.
Digital Performer and AULab also attempt to open the view component
in spite of the Unauthorized error.
right - though AULab won't add your AU to its document if it returns
an unauthorised error AND the document is running and Initialised
(which is the normal case). However, looking through the code I can
see how it is trying to open a view on some AU!! but I don't think it
will be yours (because your AU isn't actually there!) - this is
something we need to fix.
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 ?
There has *never* been any coorelation between an AU's general
usability and its initialised state. In fact, this has been a
constant and ongoing problem for us (and why we added the Init state
menus in the Debug menu in AULab) that AU writers assume that their
AUs have to be initialised before their views could be open. We would
really, really like developers to at least have UIs that do not crash
if their AU is *not* initialised.
All that Initialise means is that after that succeeds the AU can then
be used to render.
Bill
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
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