Re: AU Properties and Initialization
Re: AU Properties and Initialization
- Subject: Re: AU Properties and Initialization
- From: "Angus F. Hewlett" <email@hidden>
- Date: Mon, 31 Mar 2003 10:46:18 +0100
OK, so in fact Initialize() is really almost equivalent to the first
resume() call in VST... in other words, the host is saying to the plug,
"I've told you everything you need in order to begin streaming (connection
formats, sample rates, ...), now go away and set up all the expensive stuff
you'll need in order to stream". The difference being in this case that
with AU, the goal of any implementation is to delay as much initialization
and setup as possible until it is actually needed, so as to make
enumeration fast.
I have to admit, I think a centralised registry of sorts would be a better
solution (though either approach is better than VST's where every app has
to implement its own plug-in info cache)... just that the current AU
approach seems like a "big" solution for a "small" problem. Having to split
off anything with library dependencies from the main code module just to
keep the load time short seems like a bit of a pain.
Regards,
Angus.
At 12:31 PM 3/29/2003 -0800, Bill Stewart wrote:
>
From our code (and I must admit that this may have different
>
ramifications for a ported VST unit) - there are very few if any
>
properties that cannot be called in an AU in an uninitialized state...
>
>
Now I'll qualify this:)
>
>
Properties are really aimed at both retrieving and specifying state
>
criteria
>
Initialization is aimed at establishing that state
>
>
=======================================================
Angus F. Hewlett, Technical Director
FXpansion Audio UK Ltd -
http://www.fxpansion.com
=======================================================
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.