New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mixxx should recover the BPMs when they are manually set to 0.0 #5445

Closed

mixxxbot opened this issue Aug 22, 2022 · 4 comments

Labels

bug

Milestone

Collaborator

mixxxbot commented Aug 22, 2022

Reported by: hippako
Date: 2010-07-05T19:36:56Z
Status: Fix Released
Importance: Low
Launchpad Issue: lp602019

If I manually set the BPM to 0.0 there is no way to return to the native BPM, with re-analysis the song.

mixxxbot added the bug label

Collaborator Author

mixxxbot commented Aug 22, 2022

Commented by: rryan
Date: 2010-07-05T19:51:38Z

Does the analyze view not allow you to run BPM detection on it? On track load it won't analyze even if the BPM is zero, so maybe we should check for 0 and run detection on track load.

Collaborator Author

mixxxbot commented Aug 22, 2022

Commented by: hippako
Date: 2010-07-05T20:09:21Z

It allows me to run the analyze, but the BPM is unrecoverable, also I try with rescanning and re-adding the song in library, but still no luck. I'm asking because is very easy to reset the BPM to 0.0 by mistake with double click on it.

Collaborator Author

mixxxbot commented Aug 22, 2022

Commented by: rryan
Date: 2010-07-25T18:03:30Z

Hi hiend,

Good catch on this, Albert has added a fix and this will be in 1.8.0 final.

Regards,
RJ

Collaborator Author

mixxxbot commented Aug 22, 2022

Issue closed with status Fix Released.

mixxxbot closed this as completed

mixxxbot transferred this issue from another repository

mixxxbot added this to the 1.8.0 milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment