Re: GetParameterValueStrings
Re: GetParameterValueStrings
- Subject: Re: GetParameterValueStrings
- From: Marc Poirier <email@hidden>
- Date: Wed, 20 Aug 2003 07:37:38 -0500 (CDT)
On Tue, 19 Aug 2003, Jim Wintermyre wrote:
>
One of the plugins in question is the VST_AU wrapper. In an ideal
>
world, which is what I am looking for, the VST API could be mapped
>
well enough to the AU API that the generic view for AU-wrapped VST
>
plugins would work correctly. As it stands currently this is not
>
possible for the reasons I've been mentioning.
No, in an ideal world, no one would be wrapping VST and everyone instead
would be utilizing AU to gain the advantages that it provides. :)
>
>parameter's value is until you've set it. The only way to know is after
>
>setParameter and then getParameterDisplay have both returned, after the
>
>fact. So this only works in the context when you are "finding" the value
>
>that you want by gradually adjusting some continuous control. But if you
>
>have a parameter value in mind and want to set it right now, you are sore
>
>out of luck with VST, but it is no problem with AU since it presents its
>
>parameter value ranges as what they actually are.
>
>
I guess I can see that being a problem in the generic editor. In our
>
custom editors we handle this with editable text boxes for things.
>
It will accept appropriate text for the given control.
>
Parsing/translation happens inside the plugin code.
Of course, but a generic interface is still always used in some contexts.
>
However, I still stand by my requests as useful. Here's a key point
>
for me. All of the plugins I'm working on basically use VST as the
>
primary "platform-neutral" interface to the plugin. We have these
>
plugins running in VST (Mac/Win), MAS (Mac), DX (Win), and TDM (Mac).
>
All of the non-VST versions actually talk to the VST API and
>
translate appropriately. It works fine. I want it to work fine in
>
AU too. It already does work fine using the custom editor which is
>
what people will use 95% of the time. I just want it to work fine in
>
the generic editor as well.
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.
Marc
_______________________________________________
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.