Comment 3 for bug 618091

I still can't reproduce. Here are the exact steps I'm taking:

1) Delete ~/.mixxx/mixxxdb.sqlite (if you have spent time on your library
this will delete it -- save a backup instead of deleting it)
2) Restart Mixxx, my library is re-scanned
3) Nothing shows up in Analyze view (this is another bug apparently), reboot
Mixxx
4) Go to Analyze view, highlight and analyze a BPM 0.0 track.
5) BPM analysis completes, BPM is populated in Analyze View table.
6) Drag and drop analyzed track to Player 1, BPM shows up immediately, BPM
analysis is not run by Mixxx (can tell via console)
7) Switch back to 'Library' view, the BPM that was detected is shown in the
library table
8) Drag and drop the analyzed track from Library View to Player 2, BPM is
immediately populated to the right value. BPM analysis is not run by Mixxx
(can tell via console)

So I was totally wrong about there not being BPM-related fixes since 1.8.0
beta2 was released. If those exact steps reproduce the bug for you, then I
think this is fixed in the latest 1.8 revision in the repositories. Until a
beta3, a 1.8.0 RC, or 1.8.0 comes out, I would suggest compiling from
source. It's pretty easy to get setup for Debian, just apt-get build-dep
mixxx, install bzr, `bzr branch lp:mixxx/1.8 ./mixxx-1.8' will get you the
code, and then just type 'scons' in the 'mixxx-1.8/mixxx' subfolder. More
details here:

http://mixxx.org/wiki/doku.php/compiling_on_linux

Thanks!
RJ

On Sun, Aug 15, 2010 at 12:47 PM, Jeremy Salwen
<email address hidden>wrote:

> Hi,
>
> I realized it does work if I drag from the library. However, if I drag
> from
> the analyze view, I get the bug. And then, even if I go back to library
> view, I still get the bug. As in the BPM temporarily changes to 0 and then
> get set back to the analyzed value.
>
> and as a note, this will override manually set BPM (like when I clicked
> /2)
>
> Jeremy
>
> On Sun, Aug 15, 2010 at 3:06 PM, RJ Ryan <email address hidden>
> wrote:
>
> > Hi Jeremy, thanks for the report.
> >
> > I can't seem to reproduce this in our latest repository version of 1.8,
> > though I don't think any bugs related to BPM were fixed since we
> > released beta2. Are there any extra details you think might be relevant
> > to reproducing the problem?
> >
> > Best regards,
> > RJ Ryan
> >
> > ** Changed in: mixxx
> > Milestone: None => 1.8.0
> >
> > --
> > Reanalyzes BPMs every time a song is dragged to a player.
> > https://bugs.launchpad.net/bugs/618091
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
> > Status in Mixxx: New
> >
> > Bug description:
> > This is on Debian linux, with mixxx 1.8.0 beta 2.
> >
> > I went to the analyze view and analyzed all of my songs. Most of them
> > worked. However, when I double click on a song, it gets loaded in player
> 1
> > and the BPMS gets reset to 0. After a bit, it gets re-analyzed to the
> > correct value.
> >
> > If I load any song in any way, it's BPMs gets reset, and it tries to
> > re-analyze it. This is *REALLY* annoying when trying to sync songs.
> >
> > To unsubscribe from this bug, go to:
> > https://bugs.launchpad.net/mixxx/+bug/618091/+subscribe
> >
>
> --
> Reanalyzes BPMs every time a song is dragged to a player.
> https://bugs.launchpad.net/bugs/618091
> You received this bug notification because you are subscribed to Mixxx.
>