Key Text corrupts after Traktor plays track

I use Mixed in Key to analyze key of my tracks.
After track is played it Traktor, its Key Text corrupts.
Why? Any solutions?

http://take.ms/t1lTi

 

Anyone?

 

There are two key columns in traktor. KEY and KEY TEXT.
If you made the right settings in the preferences, traktor should show the mik-detected key (camelot) in the field KEY and the traktor-detected KEY (openkey) in the field KEY TEXT.

Right mouse click on the columns.

Greetz
J

 

Jayrock79,

1. I have these settings
http://take.ms/YkgVH

It changes way to display existing sey in Traktor. My problem is change in text after initial play, not style of display.

2. I use Mixed In Key to analyze keys. You can see on my screenshot:
— green / correct key from Mixed in Key
— red / corrupt key from unknown source with unknown notation (1m and 12d??? its not Camelot notation)

http://take.ms/lqW48

3. Maybe Traktor re-analyze my tracks when I play them? How can I prevent this?

 

Yes. Traktor corrupts the key notation from MIK. One work around is to make MIK add the key result at the beginning of the Comments field. You can use that in Traktor instead of the Key field.

 

i am seeing this as well, but i wouldn't say it is being "corrupted", but its value being (annoyingly) overwritten by traktor, due to:

A) the file has been analyzed, key among the analyzed items - traktor writes key text acording to its analysis results.

B) traktor overwrites key text with an old value, stored maybe on the track collection or a diferent version of the id3.

case B is happening to me, randomly, in when performing actions such as:
- loading a track from the itunes node.
- browsing through history playlists.
- importing a playlist from the itunes node.

it is not clear where are you getting your tracks from, in the traktor tree on the left (your first screenshot is cut) but i'd bet you're either using the file explorer or the itunes node. loading tracks to decks from these locations may trigger a re-analysis of the file, which will result in key text overwritten. if you load them from the track collection instead, you'll probably avoid most of these undesired tag modifications.