On Fri, May 02, 2003 at 01:45:22PM -0400, RonKuper@xxxxxxxxxxxx wrote: > >>> > Does this means MUSTIME, tempo, & meter can't be stapled to the > timeslice struct, since they come in as a param from some other > arbitrary source that the host shouldn't need to peek into? > <<< > > Part of the MUSTIME struct could an ID that indicates the musical timeline > context. Then the host could refer to this ID when making conversions. > > How would this work if a plugin wanted to convert from ABSTIME to MUSTIME. > It would need to ask for the conversion in the context of some specific > tempo context. How would the plugin know which one? In this design I dont think you can convert from ABSTIME to MUSTIME, without some serious hoop jumping. > Finally, is support for multiple tempo maps so vital that it belongs in > version 1.0? (I mean, you all felt that offline processing wasn't even > worth of a 1.0 spec, but c'mon... <g>) Not, multiple tempo maps, just multiple tempos. I've lost track of what the current thinking was about how to represent musical time, events or position data? - Steve ---------------------------------------------------------------------- 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