Re: GetParameterValueStrings
Re: GetParameterValueStrings
- Subject: Re: GetParameterValueStrings
- From: Jim Wintermyre <email@hidden>
- Date: Thu, 21 Aug 2003 16:06:03 -0700
At 9:24 PM -0500 8/20/03, Marc Poirier wrote:
On Wed, 20 Aug 2003, Jim Wintermyre wrote:
>If it were up to me, I would say don't use VST as the "neutral" interface,
>or use it with some supplementation (your own hooks or data or whatever to
>provide some additional necessary info). VST is definitely not a neutral
>platform. It's the dumbest and most deficient of all of the interfaces,
>so as a result, you're starving the rest of them.
Well, I guess we're just going to have to agree to disagree here.
Our current method works perfectly well for all the other platforms
we currently support (but thanks for explaining how dumb it is :-),
and it's just not going to happen that we're going to do any major
redesigning right now just to work with AU.
Also remember that I said above that you might want to use VST "with some
supplementation." Is that not possible? Could you not just add some
hooks to your internal format to retrieve min and max parameter values in
literal terms, and then map them down to 0-1 when setting from the AU
interface and expanding from 0-1 when getting for the AU interface? Just
another idea... Then you'd get meaningful generic parameter value
displays and the user will get the expected AU behavior.
We already do have most of the information we need to do this via
getParameterProperties() in VST land, and yes we already have
numerous extra hooks etc. and we could add more if we need to.
Still, the one thing I'm asking for that currently isn't addressed is
better support in the generic editor for generic parameters.
Jim
_______________________________________________
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.