So, i analyze all of my tracks through MIK, this, allows me to use Camelot Keys in Traktor, if i don’t analyze the Key through Traktor when i import new Tracks in it’s collection. Traktor automatically translates the Key text into it’s form of key, in Key column.
Importing Traktor’s Collection in Lexicon, overwrites the Key with Traktor’s open key or any other selected key format within Traktor’s settings.
Unfortunately, this means that all of my previously MIK analyzed tracks, have been overwritten by Lexicon and their key is now in open key format, although i choose to retain the original values when i imported my Traktor collection to Lexicon.
It would be better if we had an option to choose if we want to retain or prioritize the Key text “tag” as our key preference or keep the original key that is already written in the file tags and not the one that Traktor saves in the collection.
In the example below, you can see that the key text changed after i chose to check the consistency of the track to force Traktor to re-read the tags on the marked track.
Key is a bit weird in Traktor, since it allows 2 different values. It’s best to let MIK write to the common Key tag, then reload Key tag in Lexicon. After a sync to Traktor, it should show whatever it shows in Lexicon. If you want Camelot keys, you can set up Custom Keys in the Lexicon settings.
Hi, I’m trying to take my Traktor over to Rekordbox and getting a similar issue with key and just wanted to add on to this topic having done a few tests to back up a request to simply not take key over from Lexicon to Rekordbox.
I run my files through Mixed In Key to get it’s version of key, which I prefer to use opposed to RB or Traktor version. MIK stores it in Comments, (Camelot KEY - BPM) and Initial Key ID3 field which comes in Traktor as Key Text.
Taking the tracks into Lexicon the custom mapping is not relevant because it’s not a one-to-one mapping in all cases if the key is detected differently in the softwares. If I use the custom mappings to generalise this, the Custom option takes those to Rekordbox, but if I update tags in Rekordbox it reloads the Initial key version.
So to avoid having to reload all the tags again in Rekordbox to retain the one detected by MIK at the outset, can there be an option to just not update RB with the key at all, because at the moment it always overwrites and if there’s no custom mapping they go blank in RB, leaving me having to reload tags again.
ok Traktor has Initial Key as the camelot and Key as the other Open format. Lexicon & RB on reloading the ‘Key’ load the Initial Key ID3 value, so why not just load Initial Key upfront from Traktor import? I guess you’re saying the ‘Key’ in Traktor trumps Initial Key from ID3 in your Import. Just a pain to reload all Key data again to get the Camelot style from Initial Key which both Lexicon & RB grab on reload.
hmm techincally yes it has it’s own Key if analysed there, but also has Initial Key. For those with MIK workflow, would be good to have an option to take Initial Key over as Key to Lexicon instead.
