On Tuesday 13 May 2003 00.42, Tim Hockin wrote: > > Either way, the *real* question is still whether anyone needs it. > > a) Does anyone need it, and if so, define it as host-defined or as > fixed point? Well, the second part of that question depends on the first part. If it's just a way of getting better than sample accurate timing, I'm not sure there is a reason not to use a hard-coded resolution. It's definitely easier and faster. Fixed point values don't even have problems with wrapping. Values based on arbitrary quanta do. > I believe that leaving it to be host-defined means that we can add > it later and not break anything. Yeah, but I'm worried about how plugin authors will ensure that their plugins do the right thing. It's easy to get it "right" when you divide and multiply by 1 all the time. :-) //David Olofson - Programmer, Composer, Open Source Advocate .- The Return of Audiality! --------------------------------. | Free/Open Source Audio Engine for use in Games or Studio. | | RT and off-line synth. Scripting. Sample accurate timing. | `-----------------------------------> http://audiality.org -' --- http://olofson.net --- http://www.reologica.se --- ---------------------------------------------------------------------- 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