David Olofson wrote:
the good thing
about 1920 is it is divisible by both 3 and 4;
this lets both triplets and even sub-beats evaluate to integer
ticks.
...which get rounded to the nearest integer audio sample frame
anyway, as far as events are concerned.
but in any sane system built to be precise, you don't truncate
until really needed, do you?
it is a value
that should be set by the host, or in turn
the user, exercising his right to make the choice.
Yes indeed - but I don't see a reason to force every plugin to keep
track of it. Just make it 1.0, and the sequencer can use whatever it
likes internally and/or in the UI.
who said a plugin needs to care about it? afaik, your plugins
need only audio frame timings. ;)
tim