Option/Setting to completely disable Key Detection (Usefull for Mixed in Key users)

Some of us are using Mixed in key (The most accurate Key detection program by the time) to analyze our files.
Traktor is giving us the option to disable key detection only if we analyze our file in "ASync Mode" (which is a pain in the A$$ de-selecting it every time) but is not giving us the option to disable key detection while we load tracks on deck for example. It would be nice to have that feature as soon as possible because as i can understand it won't be difficult to implement this.
Just a setting to completely disable key detection.

Also i would be nice and usefull for everyone if Traktor will be able to sort Camelot keys by the right way, right now if you want to sort by Camelot keys the only way is to add a 0 (Zero) at the beginning.

 

Or, even better, give us full control about how metadata is handled (mapped & displayed) and what fields Traktor is allowed to write into & how (i.e. fully automatic - after user confirmation only - or not at all).
c.

 

Traktor Always changes the MIK back into Traktor key(in key text ),which is annoying and lots of Work retyping it again by hand.

 

C.L.Audio it won't do that if you go to Preferences > Analyze Options and set Written to File Tags to Key Text.

 

Exactly...

 

Thanks !
And(as i cant pm you ) thanks a loot for your d2 Mod - ur a HERO !

 

Yes it does, randomly. It's a bug that's been in Traktor ever since key detection was introduced and it's been completely dismissed by NI.

 

To be clear, are we talking about the Key field or the Key Text field? There is an undocumented feature where if the Key Text is changed by another program, Traktor will try to update the Key with the corresponding Musical or Open Key notation. I agree that should be made more clear.

 

It updates the traktor specific key field at analysis, but also randomly updates the field that mixed in key after a track has been loaded to a deck.

It's been complained about repeatedly and unbelievably dismissed as user error.

 

This is something it's not happening to me...

 

This is not happening to me now but did happen in the past. There are steps to get around it but we shouldn’t need to do that. I can understand how frustrating this is, and we do need more control over meta data so I’m supporting this as well.

 

What are they?

 

+1 to this!

 

actually i don't remember how but i managed to have my traktor key and mixed in key tags side to side. i'm sure that the right one (keytext) is mixed in key and the leftone is tracktor. I have it like that in the uncommon case that i get a track that wasn't going trough mixed in key. Here you can see what i mean.

 

This is what I'm doing too as you can see in the image.
What i understand is that Traktor is able to translate the camelot keys to open key format without the need to analyze them through traktor and because many times I've seen that when traktor is analyzing my track it gives wrong keys i would prefer to disable this function.
In the end as i told before traktor is already translating the Camelot keys (Key Text Column) to Open Keys (Key Column).

 

Still randomly changes the key in key text which sucks ASS !!!!!
such an annoying bug !

 

Bump. This is STILL happening in TSP3.

Anyone know the “steps” it takes to stop it? It still happens (randomly?), but not on every track I play or import to the collection.