>>> - The host defines a int64 ticks per sample which is guaranteed to be constant during runtime. <<< Can this be true across a tempo change? Or is your notion of "tick" not actually a musical tick. > 1. Absolute sample clock - int64 in samples > 2. Transport (media) sample clock - int64 in samples > 3. Absolute UST clock - UST clock structure > 4. Transport UST clock(?) - UST clock structure > 5. Musical clock in ticks and fractions of ticks Is (4) really necesssary? You could just pass in the current absolute UST clock at the start of streaming, and then subsequent process() calls could subtract it if they need an transport time from the start. Also, which of these time values are passed in as args to the process() function, and which are available for query by plugin? ---------------------------------------------------------------------- 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