[gmpi] Re: 3.9 (draft) use cases and stuff
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Fri, 20 Feb 2004 17:59:13 -0800
On Fri, Feb 20, 2004 at 07:52:32PM -0500, Michael Stauffer wrote:
> Just to clarify, the plugin must be able to generate tempo and meter
> changes for the host too? ("realtime" events, that is, not "offline").
What does the host use tempo for? To control plugins. The host itself
doesn't care about tempo, really.
> I have only one argument in favor of having this somehow in the API.
> There's been a little bit of discussion about allowing tempo/meter
> lookahead for plugs. This of course would only be relevant when the
> host/tempo-controller were playing from a static tempo map. It doesn't
> sound like this capability will be added, and I agree that it probably
> isn't worth the extra complications. But *if* this capaiblity is added to
> GMPI, I suggest that a corresponding API call be included to push static
> tempo map events back to the host/tempo-controller. This could use the
I'll agree to that. IFF we decide to have a static-map
mode/option/model/whatever, then passing map data around is porbably
useful.
----------------------------------------------------------------------
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
- Follow-Ups:
- [gmpi] Re: 3.9 (draft) use cases and stuff
- From: Michael Stauffer
- References:
- [gmpi] 3.9 (draft) use cases and stuff
- From: Tim Hockin
- [gmpi] Re: 3.9 (draft) use cases and stuff
- From: Michael Stauffer
Other related posts:
- » [gmpi] 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- » [gmpi] Re: 3.9 (draft) use cases and stuff
- [gmpi] Re: 3.9 (draft) use cases and stuff
- From: Michael Stauffer
- [gmpi] 3.9 (draft) use cases and stuff
- From: Tim Hockin
- [gmpi] Re: 3.9 (draft) use cases and stuff
- From: Michael Stauffer