Re: Meta Param Flag
Re: Meta Param Flag
- Subject: Re: Meta Param Flag
- From: Brian Willoughby <email@hidden>
- Date: Fri, 29 Feb 2008 05:00:55 -0800
Paul,
Why not just group all the "solo" buttons into a single parameter,
with Off (no solo) and each signal path as its list of options? You
can create a parameter with custom naming if you want automatic GUI
representations to be readable, or you can simply rely on your own
custom GUI to map the radio buttons in your interface to this one
parameter.
To answer your question, the Meta Param Flag refers to parameters
where value changes affect other parameters. In your case, turning
on a solo will necessarily turn off all others.
On Feb 29, 2008, at 04:03, Paul Tapper wrote:
I'm working on an AudioUnit plugin which has a number of signal
paths which the user can select to "solo". Whether a path is
solo'd or not is a parameter (for each path) and I've coded it so
that only one path can be solo'd at a time. The way I've done this
is, whenever a solo parameter is set on, I'm also automatically
switching off all the other solo parameters.
My problem is that, when I run auval, the plugin fails validation
and I'm told that it doesn't like the solo parameters and says they
should have the "Meta Param Flag" set on them.
Please, can anyone tell me what this flag means, and how I'd go
about setting it?
Thanks for any help.
_______________________________________________
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