Ah sure, echoing woggle to say thanks for your really comprehensive explanations of what you're doing, they are very useful for the rest of us!cturner wrote: ↑Thu Jan 10, 2019 1:25 pmThanks. I went a ways down the [get clock] route, but rejected it because of the time discontinuity you mention when looping (which I'm doing most of the time when developing these presets). I believe that [nth tick] performs some kind of modulo operation, and so if the end of your loop is 3840, and the beginning is 740, [nth tick 960] will trigger on the 220th tick of your loop, instead of the 960th. But I should go back and verify this. Obviously, you could have [get clock] trigger a [data 1] object to iron things out, but I wanted to be clear about the function of what I wrote.
I think there's actually a bug with on nth tick at the moment - see my post in the main thread here (unless it was fixed in the latest beta but I didn't see anything in the patch notes).