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: Marc Poirier <email@hidden>
- Date: Fri, 18 Jul 2003 15:04:17 -0500 (CDT)
On Fri, 18 Jul 2003, Jim Wintermyre wrote:
>
>The only plugin API that I know of that handles this is RTAS.
>
>Developers explicitly map parameters to hardware knobs and define what
>
>parameters appear on what pages. You can even provide a page table for
>
>a specific piece of hardware, to provide the absolute best mapping
>
>possible. Very, very nice. (There are definitely reasons that people
>
>stick with ProTools.)
>
>
Actually, VST does have a routine that allows you to specify the
>
ordering of parameters for "display" purposes (where "display" could
>
be either a generic UI, or external hardware controller). That
>
routine is called getParameterProperties(). It allows you to specify
>
a number of other useful things which would be useful for a hardware
>
controller to know, such as a "shortened" param name, whether a param
>
is a switch/discrete/continuous, display "categories" (which would be
>
like the related control groups you mention above) etc.
>
Unfortunately most hosts don't support this routine, or only
>
partially support it. One host which does support it in part is
>
Logic, and it is very helpful for making Logic Control work well with
>
with VST plugs.
Well, the other big "unfortunately" is that it's not documented at all in
the VST docs or headers. The details are very very fuzzy. It's always
seemed like something that could be useful, except that practically no
host supports it (no surprise, it's all undefined) and it's really only
useful on the plugin side if you can rely on the host supporting that
stuff, so even if that stuff was well defined, it's just kind of a hack
piled on top of the existing VST API, and not as useful as it should be.
>
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
_______________________________________________
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.