Re: Private Parameters
Re: Private Parameters
- Subject: Re: Private Parameters
- From: Glenn Olander <email@hidden>
- Date: Tue, 15 Jul 2003 16:05:00 -0700
James Coker wrote:
On Tuesday, July 15, 2003, at 03:34 PM, Glenn Olander wrote:
I can live with that, but it seems like a narrow definition
of parameter, especially since only #3 will apply to the
majority of plugins. (can anyone seriously see a generic UI
for any major plugins which have been released in the past
year?)
In FinalCut you can. I think some other hosts (LIVE) allow
plugins (VST in that case) to be used w/ a generic UI.
:-). Trust me, a generic GUI has never and will never be used
for plugins like all the recent releases (Absynth, OhmBoyz,
Crystal, Zoyd, Mach 5, Kontakt, etc.)
Alternatively, we could add a flag to
parameter info that says whether a parameter is automatable
or not. That would seem like a useful thing to have in the
long run.
I assume that if the parameter is readable and writeable,
I can (and will) send it automation data. I also use those
flags to determine which parameters to listen to for changes
so that I can capture 'scene' data separate from the normal
AU preset mechanism.
That's my point, we currently have to assume. But, if everyone
is happy with the narrow definition of parameter, then that
assumption is a safe one.
- Glenn
_______________________________________________
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.