Comment 3 for bug 1645054

This isn't a big problem when the track BPM is 120 and Mixxx
detects it as 129 or 131. But when the track BPM is 130.54
and Mixxx detects it as 130 it is a problem. I used to enter
track properties, guessed a BPM value, saved and looked at
the beatgrid and repeated until I guessed right.

I want the same result when I adjust the beatgrid no matter
where the playposition is in the track when I adjust the
beatgrid. The user-friendly solution is to adjust the
beatgrid one pixel to the left or to the right. That means
dynamic adjustment of the BPM value.

If you adjust the BPM with a constant value by calling
beats_adjust once, you will see the beatgrid move one pixel,
no move at all or more than one pixel depending on where you
are in the track and the number you add or subtract from
the BPM. If the constant is high, you can never get a
perfect beatgrid. If the constant is low you have to call
beats_adjust many times to see any change in the beatgrid
and when one adjustment doesn't result in a change in the
beatgrid there's no way to know if the adjusted BPM is
better than the previous BPM.

I think the dynamic approach is the best and most
user-friendly solution. That's why I changed the existing
functions. Have I missed some use cases? My use case is
getting a perfect beatgrid by playing a track from start
to end and adjust when I see the beat markers are starting
to appear before or after the beat.