Comment 8 for bug 1799080

yes, correct.

I think we shouldn't try to work around the problem of the beatmap detection working badly on early beats by trying to guess from the next measure. Beatmaps should be editable, and if the first beats are wrong then the user should delete the incorrect beats and then the extrapolated beats would be correct.

In my glorious beatmap future, it should work like DAWs work where you can create bpm milestones that essentially say "from here on, the bpm is X." This means not every beat needs to be manually placed, they are interpolated from a series of these milestones. (The first marker is the exception, where it also extrapolates backwards). Nobody wants to place individual beat markers for every kick in their track.

(A migration path to this future would be to have the current beatmap detector mark each beat with one of these milestones, and users could delete ranges of beats and mixx would interpolate the results. Interpolated beats could be calculated on the fly, or stored in the beatmap store.)

For now I think we should start with trying to implement extrapolation in a robust way, and then work on beatmap editing.