Chris, thank you for an excellent summary!
Seeing it all spelled out like this, I'm starting to think that all event
timestamps should be in MUSTIME. MUSTIME can be generally defined to
encompass both absolute times and musical times. Absolute times result when
the tempo doesn't change, so provided the definitions for MUSTIME and tempo
are sufficiently accurate, I don't see any disadvantage to using MUSTIME
for all event timestamping. It seems really messy to stamp outgoing events
with absolute times that need to be recalculated when the tempo changes.
Event queue sorting/management is a lot easier if everything is stamped
with MUSTIME.
MUSTIME to me has a connotation of being inaccurate, that is of having
musically pertinent resolution that may be insufficient for
sub-sample-period synchronization. If I start to think of it as being
extremely accurate and scalable, then it starts to make more sense as a
timestamp.
Also, for ABSTIME, how's about a 64-bit fixed point representation, seconds
scaled by 2^32? The wall clock can start from year 2000.
Bill
---------------------------------------------------------------------- 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
