For now, I will be happy if Ron Kuper's rewording of my suggestions for improving the tempo map requirement is adopted. There are various reasons why plugins may wish to create or modify tempo maps. One that springs to mind is a plugin that applies "feel" to existing sequences. Another is one that generates arrangements and orchestrations given a "lead sheet" type score. Both kinds of software already exist (RUBATO with Rubette plugins in the first case, OpenMusic plugins for Finale 2002 or the Band in the Box plugin for Finale 2004 in the second case). I am sure there are other applications. In my view, GMPI should open up as much musical power as possible to plugins, not limit that power or prescind from it, at least as long as the engineering is reasonably straightforward. I don't see that these requirements are that difficult to implement. In other words, the more GMPI is doing (or allows control of) and the less the host is doing (or withholds control of), the more powerful and desirable GMPI is. Original Message: ----------------- From: Tim Hockin thockin@xxxxxxxxxx Date: Tue, 23 Dec 2003 10:35:17 -0800 To: gmpi@xxxxxxxxxxxxx Subject: [gmpi] Re: New Reqs 3.8 - Events On Tue, Dec 23, 2003 at 09:11:18AM -0500, gogins@xxxxxxxxxxxx wrote: > Thanks for your response, now we're getting real. I propose some new > requirements: For the record - we're WAY OT. :) > GMPI shall support tempo maps, to be provided to plugins as one polynomial > spline per sample buffer, one such tempo map per channel or group of > channels. I think a spline is a bad approximation at the buffer level. See David's well spoken email. I still think simple ramps and point values are sufficient and more accurate. > GMPI shall provide an API to plugins for converting from music time on a > tempo map to sample frame position, and vice versa. Absolutely. A req like that exists already, but I'll make sure it is worded better, when we get there. > GMPI shall provide an API to plugins for creating and destroying tempo > maps, getting and setting tempo maps by identifier, and getting and setting > the elements of tempo maps. Whoah, hold on. Why does any plugin need to create and destroy or access any tempo map but the one it is subscribed to? Even assuming that timeline controllers are plugins themselves, this requirement makes it seems like plugins can wantonly change their own (and others') tempos at will. Tim ---------------------------------------------------------------------- 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 -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . ---------------------------------------------------------------------- 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