[gmpi] Re: Reqs 3.9. Time - opening arguments.1

  • From: Tim Hockin <thockin@xxxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Mon, 9 Feb 2004 16:31:41 -0800

On Mon, Feb 09, 2004 at 05:20:20PM -0500, Michael Stauffer wrote:
> inventor of our tempo-tracking algorithm if we need to get into this.
> Basically, as I understand it, when shifting tempo in repsonse to a
> realtime input, it's important to also constantly be updating the phase
> of the beat. Midi clocks make this "easy" because the arrival time of the
> clock not only sets tempo but implicitly has phase info too, since
> there's always 24 per beat, evenly spaced. If the tempo events we're
> talking about sending from plug to host(or other plugs) only have tempo
> information, then you need two events to set both phase and tempo, since
> the first one has to do some fancy footwork to correct for phase, and the
> second one sets that actual new tempo. I'm thinking it might be good to
> use something like a modified midi clock event, but perhaps more
> flexible, in which the tempo master would send events that say "at sample
> time S, the exact music is M, and the tempo is T". This allows the host
> (or transport controller) to know tempo and phase. This might be an issue

This has been discussed.  Do you envision this running only while the
transport runs or all the time?

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: