Same song showing up with different key value?

[djliquidice]

I’ve got this situation where some songs on my decks are showing up with a different key value and i’m wondering what I’m missing about how the database track table is setup. From my understanding the key value (integer) is the only value that is used by the decks.

I’m currently using 4.0 and have done pragma integrity_check on my DBs and they don’t show up with errors.

Here’s one example: This one track shows up with key 9A (while sorting by key) in the playlist.

Long Press the track in the playlist and the detail view shows 9A also.

Load the track in to the player and it shows 4A.

Other troubleshooting i’ve done:

• Reanalyze ALL tracks in the library
• Reimport track data on ALL tracks in my entire library

Still can’t fix this issue.

Anyone else experience this?

[Kwarkgebak]

Your pitch is almost 4% up. Do you have keylock enabled or disabled?

[djliquidice]

@Kwarkgebak you are a fookin genius man! <3 Thank you

You hit the nail on the head – i somehow disabled key lock.

Here I am thinking it’s a data integrity issue.

[Kwarkgebak]

Haha, great that it is solved!

[djliquidice]

yes indeed! I ended up writing tools to check data validity and it all came out good, which confused TF out of me.

[PKtheDJ]

A 4% difference shouldn’t change the key. 6% is generally accepted to be a semitone (difference between Em & Fm).

I guess the track could be slightly sharp to start with…

[Kwarkgebak]

Then again, +4% is closer to +6% than +0%, so this makes perfectly sense. It would be even better if we could also see cents, but currently we cannot.

[Parysatis]

In Engine DJ, it flips from 9A to 4A between +2.9 and +3.0, so +4 is definitely in the 4A range, … slightly out of tune.

If you deactivate key lock in Engine DJ, it shows the distance from the actual key as a small bar above the key symbol that increases or decreases in length … a pretty nice feature.