[gmpi] Re: 3.9 (draft) use cases and stuff

  • From: Tim Hockin <thockin@xxxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Wed, 25 Feb 2004 16:20:33 -0800

On Wed, Feb 25, 2004 at 11:41:38PM +0100, Koen Tanghe wrote:
> If I were the one to decide, I'd say "required".
> But *of course* I'm not (and wouldn't want to be, this is a group discussion
> after all) so that's why I said "preferably yes".

I'm with you - I'd like to see it be required, but it's not my call :)  Then
again, Requireing the host to enact meter changes is going to be a LOT of
headache for very little gain.

> But if tempo changing is not supported, I have no interest in GMPI.

I never meant to suggest tempo changing could be not supported.  I think
EVERYONE agrees that tempo changes are a must.  The questions are how deeply
those things affect everything.

On the one hand, we have been talking about tempo-master plugins, and things
like that.  That's a nice model, but it is starting to introduce a lot of
things that the host has to do.

On the other hand we can build a simpler model that isn't as flexible.  For

* Every plugin has a tempo-controller and a meter-controller.  These
controllers are accessed via the host callbacks.

* Hosts may provide more than one tempo and meter controller.  If they do,
they must be responsible for assigning plugins to a controller.

* Plugins reeive info about tempo and meter from their tempo and meter
controllers (whether it is maps or JIT events or other).

* Plugins may control tempo and meter by sending tempo and meter change
events to their controllers.

* The controllers may ignore or enact any plugin-generated events.

This implies that the tempo and meter are controlled BY THE HOST, and that
plugins may request changes to those things.  This eliminates the need to
support multiple tempo controller plugins, and any associated complexity.
Is this model good enough?

If we disallow sequencer plugins (or only allow one) we can eliminate some
more complexities.  Is that model good enough?

Maybe so...

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: