[gmpi] Re: 3.11 Parameters

On Wed, Mar 31, 2004 at 03:04:12PM +0100, Steve Harris wrote:
> On Tue, Mar 30, 2004 at 08:00:46 -0800, Tim Hockin wrote:
> > I think we DO need to support the plugin changing a parameter on its own (as
> > a result of another param change, or spontaneously (like an LFO).
> > 
> > In fact, I'd like to add that as a requirement.  Arguments?
> 
> I'm not sure its neccesary, but I'm open to being convinced otherwise.

I'm on the fence about it.  If it were obviously simple I'd argue that as
merit, but it's not.  We've stated that no events are delivered after
process() is called.

Maybe that should state that no external events will be delivered after
process() is called, but the plugin may send itself events (which need to be
handled as if they were external, anyway). ??

Or maybe it's just not worth it..Anyone care strongly?

> > > - Can the parameter list change during runtime (please say no)? Can 
> > > hidden/not hidden change during runtime (also no)?
> > 
> > Well, I don't necessarily think the parameter list needs to change, but I do
> > think there needs to be some dynamics to plugin structure.
> 
> Because?

It always pissed me off to have a 5-band EQ and need 6 bands.  I hate
loading up a separate plugin instance to get that 1 extra EQ band.

> > The plugin could have 16 MONO modules and 1 BUS module.  Or it could have 64
> > STEREO modules, 8 MONO modules, and 4 BUS modules.  All the parameters (and
> > their types, limits, etc) and all the IOs are know at plugin instantiation
> > time, but the actual structure of them is flexible.  Does that make any
> > sense?

> I dont think so - it sounds very compicated when you could just declare it
> as N different plugins, which share common code. It places a lot of
> complexity in the hosts instantiation code and plugins that use it. It
> also looses oportunities for optimisation in the compiler, eg. fixed loop
> unrolling if you use it.

I agree with all this as the flip-side.  I could be talked out of it ;)  We
almost have to support dynamic I/O though.  Too many existing APIs do it to
not handle it, I think.

----------------------------------------------------------------------
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: