A plea for generic interfaces!
A plea for generic interfaces!
- Subject: A plea for generic interfaces!
- From: Bjorn Roche <email@hidden>
- Date: Fri, 25 Aug 2006 13:16:58 -0400 (EDT)
Hey all,
I have an app that builds its own gui for Audio Units by querying
parameters, not unlike generic views built by the OS. (I can't show the
GUI because my GUI and processing code are in separate processes.) What
follows is my comments on the experience and some ideas for making all
Audio Units work better:
My code works well most of the time, but a surprising number of
Audio Units -- even really expensive ones -- publish an incomplete or
useless set of parameters. I don't expect everything to be controllable
from the generic view, but I do think that Audio Unit publishers should be
encouraged to make the set of parameters they do publish more useful. For
example, right now, many audio units publish an array of parameters
with no names or names like "unknown". They are doing themselves a
disservice, but they are doing the audio unit community a *big* disservice.
So here is my plea:
1. Audio Unit publishers: please check your generic interfaces and make
them as useful as possible. This will make your AU more compatible, which
is good for you and good for us.
2. Apple: please consider not allowing people to use the audio unit logo
unless their generic interface is as functional and complete (with
extraneous parameters) as possible. IMHO, if they can't turn their
interface into a few names sliders, then they should hide all their
parameters.
I think our apps could all play more nicely together if this happened.
Okay, thanks for listening!
bjorn
-------------
Bjorn Roche
XO Wave
Audio Production and Post-Production Software for Mac OS X
http://www.xowave.com
_______________________________________________
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