Analyzing a song with manually modified BPM does nothing in 1.8.0 beta 2

Bug #618099 reported by Jeremy Salwen on 2010-08-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Low
Unassigned

Bug Description

When you click analyze, it should override the previous BPM, but it wont if you have manually edited it.

This is in 1.8.0 beta 2 under debian linux.

RJ Skerry-Ryan (rryan) wrote :

Hi Jeremy,

Thanks for the report. This is actually intentional because we didn't want to manually over-ride what the user entered b/c, for example they might have spent a bunch of time hand-tagging their BPMs and we'd rather not destroy their data if possible. If you set the BPM to 0.0 then it will re-detect it via manual analysis. What would be better here is if via the analyze GUI you could say which analyzers you'd like to run on the song.

Best regards,
RJ Ryan

RJ Skerry-Ryan (rryan) on 2010-08-15
Changed in mixxx:
milestone: none → 1.8.0
status: New → Invalid
importance: Undecided → Low

On Sun, Aug 15, 2010 at 7:58 AM, RJ Ryan <email address hidden> wrote:
> What would be better here is if via the analyze GUI you could say which
> analyzers you'd like to run on
> the song.

This would be rather interesting and useful to do with the aubio
support and tonal analyzers.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers