Re: GetParameterValueStrings
Re: GetParameterValueStrings
- Subject: Re: GetParameterValueStrings
- From: Jim Wintermyre <email@hidden>
- Date: Thu, 21 Aug 2003 16:06:03 -0700
At 9:07 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 :-),
No, I called VST dumb, not your methods. But by using a VST foundation,
you are losing out on the advantages of handling parameter values the AU
way (not normalized), as I described. It's up to you whether you think
that's dumb or whatever, but it is true, so no need to shoot (or
sarcastically complain to) the messanger...
Marc, did you miss the smiley? :-) I'm not trying to shoot the
messenger. To be honest, I did feel your last reply did had a bit of
a "AU is great, everything else sucks" (which may be true! :-) kind
of tone without necessarily considering the constraints I have, and
if my response was a bit sarcastic, I was probably reacting to that.
I apologize. I'm just trying to do the best that I can within the
constraints that I have.
> and it's just not going to happen that we're going to do any major
redesigning right now just to work with AU. We're already most of
the way there, in fact the main issue currently is just this generic
UI stuff. I don't understand why adding the things I suggested seems
like such a bad thing. It only helps improve the AU functionality
for generic params as far as I can tell.
I didn't say it was such a bad thing (that's exaggerated again), but more
importantly, it's definitely not up to me anyway. ;) I was just giving my
thoughts, mostly because your first message demonstrated that you didn't
understand how AU parameters are used, so I've been trying to help you
determine whether AU parameters as they are now would be a good enough
possibility for you.
I do appreciate your explanations. But from everything you've said
so far, I haven't really gleaned anything new about the way AU
parameters work, as what you've described basically matches what I
got out of the docs. I guess what I was trying to say is that for
me, AU params work fine *except* for ones that AU doesn't know about
(generic params), and in that case only in the generic UI.
Look, I'm not trying to piss anyone off, I'm just trying to make our
plugins work. No hard feelings.
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.