# Native Instrument TRAKTOR PRO 4 (v4.1.1.23) tag compatibility with Mp3tag

**URL:** https://community.mp3tag.de/t/native-instrument-traktor-pro-4-v4-1-1-23-tag-compatibility-with-mp3tag/67494
**Category:** Off-Topic
**Created:** [February 13, 2025, 3:21pm UTC](https://community.mp3tag.de/t/native-instrument-traktor-pro-4-v4-1-1-23-tag-compatibility-with-mp3tag/67494 "2025-02-13T15:21:46Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [February 13, 2025, 3:21pm UTC](https://community.mp3tag.de/t/native-instrument-traktor-pro-4-v4-1-1-23-tag-compatibility-with-mp3tag/67494/1 "2025-02-13T15:21:46Z")

</div>

[Some years ago](https://community.mp3tag.de/t/decoding-the-traktor-4-binary-data-inside-a-priv-tag/54352) I wrote about my findings about the PRIV frame written from Native Instrument Traktor.

PRIV frame content is not displayed up to Mp3tag v3.28c for `*.mp3` files.

 ![image](https://community.mp3tag.de/uploads/default/original/3X/b/f/bf2b985f60d4538b60771943c95d96ae416ba82a.png)

Traktor 4 writes data in a PRIV frame (after all the ID3 fields) that looks like this:

 ![PRIV field content Traktor 4](https://community.mp3tag.de/uploads/default/original/3X/1/b/1bfdeb35adff290a4648c9defe4e9b3e1daf9ca8.png)

Some content entered in Traktor 4 input fields are written into the expected ID3 tags for a mp3 track like this:

 ![Comparison Traktor 4 ID3 tags and Mp3tag](https://community.mp3tag.de/uploads/default/original/3X/0/3/035f9d950c331a890c69218810da6c1a6312bd99.png)

In the tested Traktor Pro 4 v4.1.1.23 there are at least 7 fields that are not written as ID3 tags into the mp3 track (yellow highlighted in the above screenshot):  
a) Comment 2  
b) Mix  
c) Play Count  
d) Imported  
e) Autogain  
f) Key Text  
g) Cat. No.

The [mentioned online tool](https://hellricer.github.io/2021/05/05/decoding-traktor4-field.html) is still able to decode the PRIV frame from v4.1.1.23 like this:

 ![image](https://community.mp3tag.de/uploads/default/original/3X/f/c/fc178e959e42480ef8e21075a7984e276742e6ce.png)

In the PRIV frame you find the above  
a) as `COM2`  
b) as `TMIX`  
c) not sure, maybe `BPMQ` or `CUEP`?  
d) as `IPTD`  
e) not sure, maybe `PCDB` and/or `PKDB`?  
f) as `TKEY`  
g) as `CTLG`

Some remarks to the used tag like names:  
a) `COM2` is not a valid ID3 tag  
b) `TMIX` is not a valid ID3 tag  
c) Neither `BPMQ` nor `CUEP` are valid ID3 tags  
d) `IPTD` is not a valid ID3 tag  
e) Neither `PCDB` nor `PKDB` are valid ID3 tags  
f) [TKEY](https://docs.mp3tag.de/mapping/#initialkey) is a valid ID3 tag and contains the value for INITIALKEY.  
Mp3tag reads **12d** correclty in above example song.  
It remains unclear why Native Instruments write "Key Text" in the same TKEY name but in the PRIV frame.  
g) `CTLG` is not a valid ID3 tag  
There is a [CATALOGNUMBER](https://docs.mp3tag.de/mapping/#catalognumber) (TXXX:CATALOGNUMBER) that could be used for that content.

For the cover art I could not find a way that the cover will be embedded in the mp3 track.  
Traktor let you import a cover art picture and show it in a very small table view:

 ![image](https://community.mp3tag.de/uploads/default/original/3X/a/3/a3d9499c11fccfc7b324faa9c788d51da5b87163.jpeg)  
Such a cover picture seems not to be saved back into the track.  
(I do not rule out that this could be a limitation of the used demo version.)

* * *

If you try to import a mp3 track into Traktor with prefilled ID3 tags, most of them will be imported.  
But please carefully check special tags like BPM or INITIALKEY.  
In my tests Traktor silently changed the content in the mp3 track for this fields and wrote its Traktor values back in the track.

These are the fields and content BEFORE I dropped it into Traktor:

 ![image](https://community.mp3tag.de/uploads/default/original/3X/9/a/9abd6894d4ae7fc578beee5fcaf82dda5b6ff236.png)

These are the values - silently changed from Traktor after the import:

 ![image](https://community.mp3tag.de/uploads/default/original/3X/1/6/16a44245e28b597f0501d43992b50dedcc5a997c.png)  
Have special look at BPM and INITIALKEY. 😉

If you don't want Traktor to change the BPM and INITIALKEY content silently, you have to manually deselect them in the import window “Analyze”:

 ![image](https://community.mp3tag.de/uploads/default/original/3X/7/1/716ba679275fb96a6179e994b04e6648147d06a4.png)

I hope that this information can help users of Mp3tag and Traktor to see the current compatibility and limitations.

* * *

Small addition:  
In `*.flac` files the equivalent of the ID3-PRIV content is written as `TRAKTOR4` field. This field can be read from Mp3tag.

 ![image](https://community.mp3tag.de/uploads/default/original/3X/d/e/de0f101c058a0f334ec185b2fd57778069729756.png)

Due to its binary content, however, it is almost impossible to change specific values and save them back as valid changes.