Re: Hardware control surfaces (was Re: Private Parameters)
Re: Hardware control surfaces (was Re: Private Parameters)
- Subject: Re: Hardware control surfaces (was Re: Private Parameters)
- From: Urs Heckmann <email@hidden>
- Date: Fri, 18 Jul 2003 23:04:35 +0200
Am Freitag, 18.07.03, um 22:04 Uhr (Europe/Berlin) schrieb Marc Poirier:
I'm new to AU, so I don't know this, but I would assume that AU has
some similar functionality? If not, it's definitely something to
think about adding.
In AU, parameters are handled properly period. There's no extra
optional
stuff to give the necessary information about parameters. So yes,
it's no
problem in AU. :)
Marc,
now you get me curious 8-)
You mentioned in an older incarnation of the topic that the
AUParameterInfo struct can easily be extended. Have you tested it?
For now, these extensions make only sense inside the particular AU (and
its View), because only the AU developer knows about them.
As this struct is something that the world beyond plugin borders
(host...) is also aware of, shouldn't we set that couple of useful
extensions we might agree on in stone?
However, to chime in on VST flaws, it looks like the "category" names
appear redundantly in each parameter. If we agree that grouping
parameters make sense, we should also agree on a ParameterGroupInfo
struct that would be queried like the Parameter list. (And of course,
it needs Scope and Element stuff)
For the short names, I could also imagine we find something simple like
an optional "short_name:full_name" convention for the existing
Parameter name.
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.