The waveform comparison display doesn't always count beat snaps correctly

[Gabixel]

Type

Game behaviour

Bug description

Apparently, the waveform comparison display in the editor doesn't enumerate the lines correctly in some cases. Not sure how it works under the hood, could it be something related to rounding errors? (See details in the video section.)

I first noticed it in a local beatmap while checking the tempo, then I tried again on a ranked beatmap (which is the one in the video).

(I'm not sure if "beat snap" is the correct term here.)

Screenshots or videos

The video shows the beat snap starting around 00:15:751.

Pay attention to the last row/number/waveform in the bottom-right:

• In the first "main" snap, the number shifts from 26 to 27 (normal behavior)
• In the next snap, the waveform shifts, but the number is still 27 (while it should be 28)
• In the third snap, the number "fixes" itself by increasing by two (27 → 29, which is the correct number for it)
• ...the issue cycles back, 29 stays 29, then goes from 29 to 31

2023-12-30.14-46-43.-.Trim.mp4

Version

2023.1229.1-lazer

Logs

N/A