Main Counter early by 1 Tick in Grid Mode in 2023.3 [PT-299731]

[Siegfried Meier]

Noticing some grid issues in latest update. My curser is on beat 1, but look at the counter...is this a new feature I'm not aware of? I'm guessing not haha.

Every beat is on 959 instead of to the whole number. Session is at 48k, tempo at 169BPM. I made a brand new session to test, set tempo again and imported all tracks...same thing. Checked tempo at 120, grid is fine...change the tempo, it's not...and, I opened the session in HD10 Accel, and the grid issue does not exist and works as expected.

Anyone else or am I missing something?

Thanks,
Sig

[Dizzi45Z]

Interesting. I'm seeing this too. I'm currently in a project that is 3/4 at 87 BPM. Some beats show right on the beat and others show to be the previous beat at 959 like you are showing in your picture.

[_JJ_]

Same 23.3 oddness here (intel Mac) with the bar/beat counter running "short" against the grid in seemingly random ways, not every bar. I've rolled back to 22.10 and the same session I was looking at (44.1k) does not show the same counting errors. Following this story...

[Baze Music]

I just noticed this as well. Tried starting a session from scratch and having the seeing the same thing.

[jeffro]

Escalated to Engineering, thread stickied and bug# PT-299731 added.

[massivekerry]

Originally Posted by jeffro

Escalated to Engineering, thread stickied and bug# PT-299731 added.

Thanks. Hopefully this is an easy fix. I don't relish working with a shifty ruler.

[OliverH]

confirming one more here experiencing the issue with ruler displaying incorrect grid/beat position

[moogboy100]

confirming one more here experiencing the issue with ruler displaying incorrect grid/beat position

[gthm]

A new low.

[audiogamble]

Would love it if there could be a .1 update for this particular bug. The new version is terrific but this is a showstopper for any music workflows. Running it back to the previous version of PT in the meantime.