[gmpi] Re: lost-n-found #3 parameter stuff

On Fri, Nov 05, 2004 at 08:35:32AM -0700, Mike Berry wrote:
>       I don't think it is a corner case if we can show a host (Premiere) 
> which needs it 100% of the time for all plugins, custom UI or not.

I meant that its a corner case the the current API will not support that
well.
 
>       The issue is not just for parsing the string that is typed. Hot text 
> controls in Premiere are also draggable. For that, I need to know what 
> the natural unit of increment is. Lets say that I have a parameter that 
> is frequency in linear units in a float. In the plugin's custom UI, it 
> is free to put a log-based control onto that parameter. But the host has 
> no idea. So how does the host pick a useful unit for incrementing and 
> decrementing the value? This is exacerbated by the normalization in VST, 
> but just getting rid of the normalization does not fix the problem.

I disagree. Until recently LADSPA only had hsot generated UIs, and many of
them offer these options (with spinbuttons or draggable or click
incrementable textboxes), and I'm not aware of any problems with it.

- Steve

----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules:  Please stay on topic.  You are responsible for your own
words.  Please respect your fellow subscribers.  Please do not
redistribute anyone else's words without their permission.

Archive: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: