traditional musical key db corruption?

[Owen Williams]

I am using tradition key display, and I've noticed over time more and more of my tracks are showing up as C?m or D?. This would probably happen if the unicode sharp or flat character were being attempted to be written to the database, which does not support unicode. We should make sure we are converting the unicode back to # and b for compatibility.

[RJ Skerry-Ryan (rryan)]

Hm, we store the key in the database as an integer, not a string so this
shouldn't happen. Unless Mixxx wasn't able to understand your key tags from
the get-go.

How did you get the key annotations? Text entry? Analyser? ID3 tag?

On Mon, Nov 24, 2014 at 10:34 PM, Owen Williams <email address hidden> wrote:

> Public bug reported:
>
> I am using tradition key display, and I've noticed over time more and
> more of my tracks are showing up as C?m or D?. This would probably
> happen if the unicode sharp or flat character were being attempted to be
> written to the database, which does not support unicode. We should make
> sure we are converting the unicode back to # and b for compatibility.
>
> ** Affects: mixxx
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https://bugs.launchpad.net/bugs/1395967
>
> Title:
> traditional musical key db corruption?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1395967/+subscriptions
>

[Owen Williams (ywwg)]

Just the analyzer. It has to be something we're doing, because one of the tracks with a bad key is one that I downloaded from Beatport as WAV and transcoded to FLAC myself, so it never would have had a key originally.

I am trying some things to reproduce the problem.

[Owen Williams (ywwg)]

the oldest track I can find with a bad key is from july, so this might have already been fixed.

[Launchpad Janitor (janitor)]

[Expired for Mixxx because there has been no activity for 60 days.]

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/7677