--- Jeff McClintock wrote: > > Making timestamps relative to block-start may be easier for plugins to > > handle, emphasizes the "there is no future" model, and saves 4 bytes > > per event (as well as saving 64 bit math). > > Well..... the host has to maintain the timestamps at 64 bit accuracy, so > you're actually imposing a conversion step on the host (a 64 bit math > subtraction). So I'm not sure there's any overall saving by using 32bit > timestamps. Either the host does it, or the plugin does it (converts > timestamps to block-relative). > > Not too worried either way to tell the truth though. Yeah, it seems pretty silly to be discussing performance costs of 32 vs. 64 bit for event timestamps. If there's any reason to say that 64-bit timestamps would be useful (which I think has already been shown), then we should just use them. The amount of CPU time that goes to handling timestamp values is totally trivial anyway. If, by choosing 32-bit rather than 64-bit now, we screw ourselves over at all down the road, then that would just be so ridiculous because the performance issue doesn't even matter at all today, and it surely will only continue to not matter more and more to the point of ultra-not-mattering at homeopathic type levels... Marc __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ ---------------------------------------------------------------------- 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