[gmpi] Re: Topic 6: Time representation
- From: Chris Grigg <gmpi-public@xxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Fri, 2 May 2003 12:46:59 -0700
I said...
I would see your scenario as a plug with a music even in pin and a
music event out pin, and would say that the same events are -not-
flowing through the plug-in. It's receiving a stream of events, and
producing a separate (almost always denser, by definition of
'arpegiator') stream of events.
...and re-reading that made me think that there's a problem with this
scheme. Time travel.
If all event queues contain ABSTIME-stamped events, how (assuming a
MUSTIME-driven arpeggiation clock) can an arpeggiator post correctly
timed events for the future? It can't, because tempo might change in
the meantime. Really, it can only post MUSTIME-stamped events and
leave them around for something else to convert them to ABSTIME based
on what actually happens with the tempo, timebase modulation, etc.
Now these -could- go into a special kind of MUSTIME-stamped output
queue destined for the downstream plug(s), and leave it to the host
(or pkg) to skim the queue per timeslice, converting just-in-time
(right before the downstream plug's process() is called) to
ABSTIME-stamped events and moving the events to the regular BASTIME
queue... but that's kind of ugly, eh?
--- Chris
----------------------------------------------------------------------
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:
