Comment 2 for bug 618091

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
>