Beatgrid is 0.02 s off

Bug #1832995 reported by Daniel Schürmann
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mixxx
In Progress
High
Daniel Schürmann

Bug Description

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:
https://github.com/mixxxdj/mixxx/pull/926

Changed in mixxx:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Daniel Schürmann (daschuer)
milestone: none → 2.3.0
Revision history for this message
kek001 (kek001) wrote :

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.

Revision history for this message
Be (be.ing) wrote :

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

Revision history for this message
Be (be.ing) wrote :

Is this a duplicate of Bug #1837092?

Revision history for this message
Daniel Schürmann (daschuer) wrote :

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.

Changed in mixxx:
milestone: 2.3.0 → none
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/9678

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.