Beat detection slow for 48 k and 96 k tracks
Bug #1879588 reported by
Daniel Schürmann
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Released
|
Medium
|
Daniel Schürmann |
Bug Description
The beat detection in 2.3 for 48 k tracks and is significant slower that before.
I may case it has raised from 4 to 14 sec.
I did a bisect and the first failing commit is.
https:/
I did not investigate this further to check the results.
At least the BPM values are different.
It looks like 44.2 k tracks are not affected.
We need to investigate this more.
summary: |
- 2.3 Regression: Beat detection slow for 48 k tracks + Beat detection slow for 48 k and 96 k tracks |
Changed in mixxx: | |
importance: | Undecided → Medium |
status: | New → In Progress |
assignee: | nobody → Daniel Schürmann (daschuer) |
milestone: | none → 2.3.0 |
Changed in mixxx: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It looks like this is a symptom of a deeper issue.
With 2.2.4 the analysis of 48 k Tracks is also significant longer than for 44.2k tracks.
However the result is looking reasonable.
In 2.3 the result looks random, before and after the commit of question.
We have also fixed a buffer overflow later in the code.
So maybe we see here a QM bug?