>> Now, for your rolling transport counter code...
I've been looking back over at those source codes...
Using a low ppqn such as 24 in my timebase code (based on
non-sequencer) utterly fails. Using a ppqn of 100 in non-sequencer
fails too. As does using a low ppqn in Dino.
(I see you've used a low ppqn of 48 in Tritium/Composite, and are
In other words, you're right about it sticking when nframes <
frames_per_tick and needing bbt_offset. Until now I did not realize
this is worked-around by using a high ppqn such as 1920 or 2520 (which
give integer results when divided by integers up to values 8 and 9
respectively (ie what the magic number means)).
So with low ppqn values, the bbt_offset integer will be ok, but what
about for high ppqn values?
Even high ppqn won't be perfect, but might not a floating point
bbt_offset improve the timing?*
*not in my case, it's some more serious problem in my code.