Beatgrid is 0.02 s off

[mixxxbot]

Reported by: daschuer
Date: 2019-06-16T15:49:59Z
Status: In Progress
Importance: High
Launchpad Issue: lp1832995

---

The Beatgrid is 0.02 s off using the QM Beat detector.

Beat detection is 0.04 s off using the SoundTouch Beat detector.

Not sure when this was introduced.
I am Investigating this:
#926

[mixxxbot]

Commented by: kek001
Date: 2019-07-07T19:06:32Z

---

This has been long time in mixxx 32 windows,
I remember when was big update, and had to analyse every track again.

It would be very very helpfull if this will be fixed soon as possible. :)
i know there are other priorities too.

not want adjust rest of my life every track, or allmost 90% of them. it takes some time if count together. and it really annoying, if you had adjusted and then mixxx think it has to analyse and adjust beatgrid again, not want lock every song.

[mixxxbot]

Commented by: Be-ing
Date: 2019-09-14T18:03:17Z

---

What is the status of this? It is marked as In Progress but no pull request fixing this has been linked here.

[mixxxbot]

Commented by: Be-ing
Date: 2019-09-14T18:04:51Z

---

Is this a duplicate of Bug #⁠1837092?

[mixxxbot]

Commented by: daschuer
Date: 2019-09-14T23:06:32Z

---

This is a pending issue in the beat detector that sometimes it sets the beat on the falling edge, because it is slightly more significant. I am working on a solution that values the rising edge more.

We may also value the base beats more than the high head beats. I have some tracks where the beat makers are placed wrong on the high heads or even worse is jumping between. .. another issue.