Re: Coreaudio-api Digest, Vol 2, Issue 142
Re: Coreaudio-api Digest, Vol 2, Issue 142
- Subject: Re: Coreaudio-api Digest, Vol 2, Issue 142
- From: "Glenn Hughes" <email@hidden>
- Date: Tue, 10 May 2005 14:34:23 -0400
Hi Jim,
DP's model is that all parameters are announced up-front, but exactly
which show up at a given point (in the Insert menu, and other places
where an instance of the effect is known) is dependant upon the IO
configuration. In other words, there are sort of two views that the
user can have on the params of an effect, one where the particular IO
config is not known (that includes all parameters) and another view
which is for a specific instance of the AU (which includes only the
params for that IO config.)
What we'd like to see is a way to test whether a given param is used
by an IO config, rather than having them "come and go" as IO configs
change. One big reason for this is: what to do about automation that
is in tracks that does not 'go with' the current IO config... It
should still display correctly, and not appear as orphaned, and the
AU would just ignore it during playback.
This way of doing things also makes sense, because you are supposed
to be able to query the parameter info on an AU before it has even
been initialized, or had an IO config set into it.
Best wishes
Glenn
We have a "braindead" mono version of one of our AU's. The reason
for this is it only exposes half of the parameters vs. the regular
version of the plugin. This makes it a lot easier to use the mono
version on a control surface because you don't have to wade through a
bunch of unused params (this was more of an issue in this particular
plugin). The regular version will run in mono as well, but half the
params aren't actually used (the right channel params). Is there a
better way? If you dynamically decide which params to expose based
on the I/O config, will this work properly in all current AU hosts?
Jim
_______________________________________________
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