Re: Audio Units - newbie questions
Re: Audio Units - newbie questions
- Subject: Re: Audio Units - newbie questions
- From: Marc Poirier <email@hidden>
- Date: Tue, 11 Oct 2005 23:33:47 -0400
On Oct 11, 2005, at 6:20 PM, Muon Software Ltd - Dave wrote:
You should fix this. In fact, I think auval might even try to test
this case - if it doesn't it will be soon :-)
Well hang on a minute - why would a host need to call methods on
AUs that
aren't initialised? what we do in our code isn't absurd, it just
assumes a
logical sequence:
1. Construction (do nothing much)
2. Initialisation (do the heavy stuff)
3. Be ready for anything :-)
That is definitely not how Initialized vs. Uninitialized states are
defined in the AU specification. The short version of that is:
Uninitialized = ready for anything except audio rendering
Initialized = ready for anything
????
Why are you initializing (and crashing) here.
I'm not crashing there, because I've detected that the host hasn't
called
Initialize yet and for reasons unknown it is trying to call methods
on my
plugin before it has had chance to set up. By calling Initialize there
myself I'm working around Intialize not being called in what I
would say is
the right order of thigns.
You really shouldn't be overrunning the host's determination of the
AUs Initialization state. It is the host's choice, and the host
needs to be able to know and depend on the state being as it has set it.
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