Which extended field should I use?


#1

Hi!

Here's the situation: I edited all tags for my mp3 collection, and added song key info (based on Mixed In Key results, but manually) into the Comments field. I somehow hoped that Traktor Pro would "understand" it, and put the info into its own 'Key' field.
Obviously, it didn't. Comments are in the comments field.

If I could transfer these "comments" into a field called "Key" (via Convert Tag to Tag), all my problems would disappear.
The question is: which extended field should I use to put the key info in, that Traktor will recognise, and handle properly?
There is no 'Key', and I don't know what to choose. :frowning:
Maybe 'initialkey' is the one? Or am I wrong?

Any help would be appreciated!

All the best,
Laszlo


#2

Why not just try INITALKEY on a few files and see if it works?

If it doesn't, then try KEY and see if that works. INITIALKEY will create a native 4-character ID3v2 field named TKEY, while using "KEY" would create a user-defined TXXX field with a description of "KEY". Any time you write a field with a name that Mp3tag doesn't map to an ID3v2 frame, it creates a user-defined TXXX field for it.


#3

What does MP3tag have to do with a very particular function of that Traktor program?

Is it possible to save the key setting from that Traktor program in one of your files?
If so, you could inspect it after saving with mp3tag and you have the field name.

But it could be just as well that the Traktor stores these values in a database of its own... please turn to the traktor forum for clearification.


#4

Why do this when MIK fills either the comment tag and/or the INITALKEY tag and it does this automatically also. I think you need to read up on MIK software manual.

EDIT: MIK Version 4 (Newest version is 5)




#5

Thanks, guys, I understand some of your comments...

JJ Johnson: this is exactly what I will do.

ohrenkino: Traktor handles the files when I add them to the Collection. The question was what to do before importing, in order to have handled properly.

stevehero: I know what MIK does (and found out that it writes into initial key tag), but in this case, I analyzed my original wav files, and then saved them as mp3s, so MIK had nothing to do with them. As I wrote: "added song key info ... manually."

Anyway, thanks for the suggestions, I will try to mess around with "initialkey".


#6

Well, it would not have done a lot of harm to add ONE file to traktor, do the keying stuff and then check with MP3tag what has changed. You then probably would have found the place where the programs stores the information: either in the file (= new field in the file) or in its database (=no new field in the file).
You check fields in the extended tags dialogue (Alt-T)


#7

Guys, 'initialkey' is the solution. I added MIK info (e.g.: 1A) to a file, imported itno Traktor, and... bang! Key is in the Key field!

Thanks for all your efforts! :wink:


#8

Let me get this right. You run the wavs through MIK yet you decide to do this manually for mp3s when all you do is load your mp3 files into MIK and set it up to go to the comment tag. I sense you don't know how MIK works otherwise you won't have asked such a simple Q.


#9

No, it's a little bit more complicated, and would be off topic to describe here. Trust me, I'm not that dumb that you think I am. :w00t:

Plus, my original problem has been successfully solved. :rolleyes: