[gmpi] Re: Topic 6: Time representation

  • From: Paul Davis <paul@xxxxxxxxxxxxxxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Wed, 30 Apr 2003 12:15:21 -0400

>> 4. Transport UST clock(?) - UST clock structure
>Is (4) really necesssary?  You could just pass in the current absolute UST

actually, (4) is a non-sequitur. the UST clock is monotonic and
system-wide. it is not influenced in any way by transport position.

>> 5. Musical clock in ticks and fractions of ticks

no fractions of ticks. the tick is the "atomic" unit of musical
time. there is no smaller unit. if you want to be more precise than
that, you use samples or nanoseconds. (i prefer either 1420 or 2520
ticks per beat, which maximises the available factors so that
divisions of the beat can be expressed in ticks without loss of
accuracy. 2520 is particularly good, as tim noted yesterday).

>Also, which of these time values are passed in as args to the process()
>function, and which are available for query by plugin?

all of the above would be passed by reference (i.e. pointer in C) to
the process() function. other times (e.g. time since last bar start,
time to next bar, etc. would be accessed via a callback to the host.


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