BPM info shows 0.0 in BROWSE mode

Bug #1020438 reported by daniel
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Low
RJ Skerry-Ryan

Bug Description

even if the tracks were analized before and the correct bmp is shown in file-properties.
thank you!

mixxx 1.11 beta 1 R3285

Tags: library
Max Linke (max-linke)
Changed in mixxx:
status: New → Confirmed
jus (jus)
tags: added: library
Changed in mixxx:
importance: Undecided → Low
jus (jus)
summary: - bpm shows 0.0 in browse mode
+ BPM info shows 0.0 in BROWSE mode
Revision history for this message
Tomasz Kowalkowski (coval-pl) wrote : Re: [Bug 1020438] Re: BPM info shows 0.0 in BROWSE mode

Thank You. I tried to find similar problem, and I did not, so added this one. Sorry for duplicating.

best regards

W dniu 2012-11-27 08:37:18 użytkownik jus <email address hidden> napisał:
> ** Summary changed:
>
> - bpm shows 0.0 in browse mode
> + BPM info shows 0.0 in BROWSE mode
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1083465).
> https://bugs.launchpad.net/bugs/1020438
>
> Title:
> BPM info shows 0.0 in BROWSE mode
>
> Status in Mixxx:
> Confirmed
>
> Bug description:
> even if the tracks were analized before and the correct bmp is shown in file-properties.
> thank you!
>
> mixxx 1.11 beta 1 R3285
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1020438/+subscriptions
>

Revision history for this message
Leo Combes (combesl) wrote :

Now (1.12.0-alpha (build master r4460)) in properties shows correct BPM data, but in the list shows 0.0

Revision history for this message
Raf Van De Meirssche (rafvdm) wrote :

If you need more information, perhaps see http://www.mixxx.org/forums/viewtopic.php?f=3&t=6728

RJ Skerry-Ryan (rryan)
Changed in mixxx:
assignee: nobody → RJ Ryan (rryan)
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Thanks for pinging the bug -- I was able to reproduce. Fixed in:
https://github.com/mixxxdj/mixxx/commit/b07bdf2dfb09ddd5623babd9b0afe0697e870a3d

Changed in mixxx:
status: Confirmed → Fix Committed
milestone: none → 1.12.0
Revision history for this message
Raf Van De Meirssche (rafvdm) wrote :

Approved
Thank you

RJ Skerry-Ryan (rryan)
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
kartoffelsalat (silberzwiebel) wrote :

I'm using Mixxx 2.0.0 (build 1.12 r5772) on Fedora 23 and still see this bug. Since I'm more likely to find my music in my own folders than via the library, I like to use the "Browse" function but it's a pity that the BPM is not shown there. BPM is correctly shown in the properties of the file, but in the column it's always 0.0. Right-Click > BPM options also does not show anything (but I suggest this is another problem...)

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

The browse feature shows the bpm value stored in the track metadata.
If there is nothing stored 0 is correct. So this bug is actually fixed.
The browse feature shows the raw track data by design.

I think your request is to show the Mixxx Bpm value instead, if the track is already in the Mixxx library.

It is something similar to https://bugs.launchpad.net/mixxx/+bug/1179318

You may file a new bug, to request a change or proposes a better solution.

Revision history for this message
kartoffelsalat (silberzwiebel) wrote :

Thanks for the quick reply.
Ah, okay, I see. Maybe it's possible to add two columns to the browse view? Metadata BPM and Mixxx BPM?
I read somewhere that Mixxx also can store the BPM value in the metadata but I didn't find the option to do this. My music library is kind of big and I'd rather not re-compute all BPMs with an external program again.

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/6559

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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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