[agreeing with Tim, and taking issue with Frederick's statement that
"There is no need to carry this kind of annoyance forward into a new
standard."]
> The straightforward thing to do is to represent musical time, which is a real number, with one of the builtin data types that C/C++ provides for real numbers, i.e. float or double. Doubles should probably be used to guarantee enough precision. The unit should be a traditional one, either beats or measures, rather than an artifical technical construct like the tick. I would vote for beats.
Disagree - this is not the sort of thing the end musician cares about, but it IS the sort of thing that impacts the code.
A tick is the hosts finest level of granularity. This abstraction allows for hosts to have very fine or very coarse accuracy, depending on the needs of the situation.
---------------------------------------------------------------------- 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