Private Parameters
Private Parameters
- Subject: Private Parameters
- From: Bill Stewart <email@hidden>
- Date: Tue, 15 Jul 2003 12:52:01 -0700
At the request of some host app developers...
If you are using private parameters to facilitate the communication
between your UI and your AU, please don't publish these.
If you do publish parameters, you should give them names, set their
flags appropriately, etc...
The problem for the Host Apps, is that they query the AU for its list
of parameters, then turn around and get information about those
parameters. If the AU is publishing parameter ID's but then refuses to
give any information about them (like their name, whether they are
readable, etc...), then the host really can't work out what to do with
them, can't build a good "generic" UI for the AU, can't sort out which
parameters it needs to listen to, which paramters it can automate,
etc...
You UI, as it is released with the AU, doesn't need to know the
paramID's it is using through this mechanism... It is after all, both
your AU and your UI, and so you don't need to publish these.
The intention of the published parameter information is to allow a host
app to:
(1) Build Generic UI
(2) determine which Params a host should listen to changes
(3) determine which parms can be automated (including ramped)
Thanks
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
________________________________________________________________________
__
_______________________________________________
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.