[gmpi] Re: Topic 6: Time representation
- From: "Angus F. Hewlett" <amulet@xxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Tue, 29 Apr 2003 14:18:10 -0400 (EDT)
On Tue, 29 Apr 2003 RonKuper@xxxxxxxxxxxx wrote:
> 32-bit unsigned isn't even enough. Video post guys are used to working on a
> 24 hour timeline that wraps around. You can *just* squeeze 24 hours into 32
> bits @ 44kHz, but no higher rate.
OK, thanks for the info... absolute time will have to be 64-bit; to Tim
Hockin: it may be that some simpler plugins can safely ignore the high
word for speed reasons.
> OTOH, plugins will be hosted in apps that have timelines and conductor
> tracks. There might be some benefit in this context to allow for conversion
> anywhere along the timeline (for tempo sync effects, generative effects,
> etc).
> So to restrict the model to say "there is no future" seems, well,
> perhaps too restrictive.
I think the main reason to have this idea of "the future" is to allow
certain classes of plug-ins to generate events in to "the future" (rather
than buffering internally and watching and waiting for the future to
arrive, taking any changes in status in to account along the way). This
opens up a whole can o' worms and I'm inclined to agree with the XAP (and
VST) model here.
----------------------------------------------------------------------
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:
