Hardware control surfaces (was Re: Private Parameters)
Hardware control surfaces (was Re: Private Parameters)
- Subject: Hardware control surfaces (was Re: Private Parameters)
- From: Chris Reed <email@hidden>
- Date: Thu, 17 Jul 2003 16:53:14 -0500
On Thursday, Jul 17, 2003, at 15:42 US/Central, Marc Poirier wrote:
Also, remember that generic UIs are more than just things like custom
AUCarbonViews vs. GenericAUViews. Other sorts of interfaces might be
things like interfaces to parameter automation, which might just be
menu/list based or something like that (like in Logic, for example).
So
providing parameter information correctly really is important. Also,
some
hardware control surfaces are able to use this information to give
proper
display of information and proper response to slider/knob/button
changes.
Hardware control surfaces are another reason that Urs' idea (it was
you, right Urs?) for parameter groups is important to consider.
On a control surface, you have only a very limited number of controls
that you can edit at once (a "page" of controls). It is quite
important--if only for user experience--that related controls be
grouped together, so you don't have to flip back and forth between
pages all the time.
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.)
-chris
_______________________________________________
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.