[gmpi] Re: 3.11 topic: Dynamic plugin structure
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Mon, 19 Apr 2004 20:37:46 -0700
On Tue, Apr 20, 2004 at 03:23:45PM +1200, Jeff McClintock wrote:
> > Well, custom UIs already show/hide the parameters. But the parameter list
> > is enormously long and mostly inapplicable. It is very hard to find the
> > parameter when you need to traverse the list. That's the problem.
>
> Not sure i understand.
> "show/hide" also applies to host-generated UI's. If the host presents a
> list of parameters to the user, only the relevant ones are shown.
In existing synths (under VST, anyway) the parameter list is constant, but
the (custom) GUI shows only the active parameters. The host would not
know how to differentiate active vs. inactive parameters.
> > Yes, a modular synth gets to be a lot of fun. ;)
> > ... but the API has to suppot modularity to do this (while still being
> > GMPI-native parameters).
>
> modularity?, well, support parameter add / remove. That's the 'guts' of it.
And that's more-or-less what the modular approach provides, except at a
coarser granularity.
----------------------------------------------------------------------
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: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
Other related posts:
