[Bug]: Forced misses on extreme low rates when pitch change is off

[foxfire667]

Is there an existing issue for this?

• I have searched the existing issues

Contact Details

Reply to issue.

Version Info

Latest available release

What operating system are you seeing the problem on?

Linux (any distro)

Bug Behavior

If you have pitch rates off, choose a song which starts on beat 0, and use a super low rate (e.g. 0.05x), the song will warp past the first note during fade in. This results in forced misses every time.

This is an exceptionally minor bug I ran into while attempting to do a silly challenge. It appears to only impact songs which start immediately beat wise, but there may be some leeway for further triggering I didn't find while trying to reproduce this bug on other songs.

Expected Behavior

Like with pitch rates on, I would expect the song to play without warping the player past the first note, resulting in a forced miss every time.

Reproduction Steps

To reproduce:

1. Disable pitch on rates
2. Navigate to a song which starts on beat 0.00
3. Select an exceptionally low rate, such as 0.1x or 0.05x
4. The song begins after the first note(s), resulting in forced misses.

Anything else?

I happened to be recording, so you can see a few minute video of the bug discovery here.

[StarbotArc]

Could it be grace period is also scaled by rate?

[StarbotArc]

I've decided to do some further testing, and it definitely goes further, as it breaks the first beat on Polyloop GAMMA (x3 for brevity) at 0.05x, which is most definitely unintended behavior, and also skips seconds ahead when trying to select a certain point to play at.

It's most definitely a bug with how the new system works, and might just be due to it not going back to where it's supposed to be once done.