TRAKTOR 4 AND MIX IN KEY

The only thing that helps is to write to the manufacturer of the tool and ask for an update if they absolutely want to set the cues with a third-party tool.

Harald Walker

https://community.native-instruments.com/discussion/comment/166656#Comment_166656

@Marco67 did you hear back from them by now?

leesinthemix

https://community.native-instruments.com/discussion/comment/171092#Comment_171092

They can't do it flawlessly though, that's completely wrong

It's been known for a long time that Rekordbox, Engine and Serato are quite behind detection compared to Traktor and MiK.

Virtual DJ is by far the worst.

https://www.digitaldjtips.com/best-dj-key-detection-2020/

saradis

I have noticed inconsistent behavior when it comes to cue points, grid markers and everything that traktor stores in the mp3 tag as well as it's database. For example, before TP4, I used to edit songs or replace them with higher quality versions, first I did the prep on the new file on my desktop, cues grid and all, and (because I have my music on dropbox) just did a consistency check on the laptop and relocated the missing files (I was erasing the old versions on the desktop) with the new ones.
Before TP4, every time I relocated a file, the program first read cues BPM grids etc from the tag, and so I ended up with a ready-to-go new file in the place of the old one. If I do that now, I end up with the sound from the new file but the cue points and grid markers of the old one. Now, I have to first import the new file from a new location, so it reads the cues and stuff, puts them in the .nml corresponding to the new file, AND THEN do the relocation of the old ones, and essentially merge the two collection entries.
Having used MIK heavily in the past, it writes key values in the mp3 tag but also uses the .nml file for the automatic cue points. Something has changed in the way Traktor handles updating of those stuff and conflicts between the collection and the mp3 tags, and basically the program ignores cue points that are changed externally, either in another computer or from a program.

It's either MIK's job to find a way to overcome this, or NI's job to re-examine where and how cue points are stored and what happens with conflicts

On a last note, having some ear training over the years, and a keyboard next to my mouse has shown me that no program has a satisfying key detection algorithm and they all have flaws in different types of compositions. But the MIK auto cues are indeed handy if you want to analyze many files that you don't play that often so you wouldn't sit down and prep them one by one, it gets dance stuff usually close enough when it comes to having quick access to sections.

Heisenberg

https://community.native-instruments.com/discussion/comment/171445#Comment_171445

Here is something more current:

Marco67

after a series of checks and tests in tractor 4 the cue point arrived (even if not for all the songs).the sensational difference that immediately catches the eye even for an amateur like me is that in Traktor 4 the accuracy of the mix and key cue points is far less precise than in Traktor 3.I honestly don't know what could have changed but that's how it is.Another thing.The procedure for setting a new cue point in the song in traktor 4 has changed (the support keys have also changed) and is much more complex.

lord-carlos

https://community.native-instruments.com/discussion/comment/171466#Comment_171466

What do you mean by "mix and key cue points" ?

Harald Walker

https://community.native-instruments.com/discussion/comment/166626#Comment_166626

I just got as answer: Yes, Traktor 4 is fully supported.

Haven’t tried it myself yet since I didn’t upgrade yet.

Quick links

Unanswered questions