[FIXED] Tracks clock division slightly out of sync

[LostForWords]

Hi. I've noticed where a track clock is a division of the main clock if I stop a track and restart it at a quantized point or at the start of the next 64 steps it can (most times) be slightly out of sync. It's late by a noticeable fraction of a step.

I'm testing with track 1 out to an oscillator with notes on normal clock and track 7 is on /2 time with the factory kick drum sample. I thought first it was the kick sample out of sync but swapping track 7 to normal clock and track 1 to the /2 track has the same effect with track 1 becoming slightly out of sync against the main clock (and steady kick drum).

Let me know if a video would help.

[XORadmin]

I’m going to check it tomorrow. It should start always fine at the zero cross.

[XORadmin]

I checked it out and indeed if the older clock settings have been different than the 1/1 once then it seems like to skip the first tick. Mostly noticeable with low BPM.
That is not correct of course and it looks like it have been like this forever ( i checked older versions for this and they show the same behaviour).

It works well when you switch the clocks while sequencing.

I will see whats going on and fix it.

[LostForWords]

Great. Not me going mad then.

I've just come back to using Nerdseq and it was only my second project when I noticed it - indeed a low 62 bpm.

[theotteryears]

any news on this fix? Not sure if it was fixed in v1.23 but I still have the problem with any track that has a clock division on it...

[XORadmin]

I am busy with the last ends of a new firmware and it is in there.

[theotteryears]

perfect! thank you