Re: AU Properties and Initialization
Re: AU Properties and Initialization
- Subject: Re: AU Properties and Initialization
- From: Urs Heckmann <email@hidden>
- Date: Sun, 30 Mar 2003 12:11:05 +0200
Am Sonntag, 30.03.03, um 00:33 Uhr (Europe/Berlin) schrieb Glenn O:
If it is true that almost all properties could
be supported in an uninitialized state, then it seems to me
that it is also true that those properties could be externalized
into a resource or code object (as Angus suggested).
The advantage of the externalized approach is that there is
a design artifact which enforces the behavior you desire.
Otherwise, you will only get the desired results if developers
politely learn, understand, and follow your recommendation :-).
- Glenn
I think it really depends. I would like to know what the hosts do need
except supported channel configurations, some name strings, some basic
type info...
Otherwise I would prefer having the chance to run some code before, for
some reasons. Some stuff may result from internal investigation _after_
initializing some objects. These could from the AU perspective be
treated like data (VST-AU wrapper, "SynthEdit" patches). There could
also be "Preferences" made from user or an external application that
might affect properties (i.e. Inter Application Communication between
plugin and external application or authorization schemes). And of
course crossplatform concerns would possibly require extra work for AU
support.
However, if the info host's need can be broken down to some small
need-to-knows, I have no objection.
Cheers,
;) Urs
_______________________________________________
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.