Comment 1 for bug 1796262

Thank you for the bug.

We have a related visual and usability issue,
but the proposed solution does Imho not work well because there are also tracks without a whole number. So we have no chance to not trust the analyzer. We just can improve it. Just rounding to the nearest integer only linds the symptoms.
So I like to set this bug to "won't fix."

Can you file a new bug that describes the related issue you suffer? like:

"The calculated BPM is imprecise"
Or
"Nothing is found when I search for BPM ..."

A related discussions on Zulip are here:

https://mixxx.zulipchat.com/#narrow/stream/109122-general/subject/Library.20-.20Limit.20view.20to.20mixable.20BPM
And
https://mixxx.zulipchat.com/#narrow/stream/109122-general/subject/BPM.20sorting