Can Engine DJ 2.0 replace Traktor & MiK analysis?

[Rips]

I have done some testing of a workflow directly from Mixed in Key to DJ Engine.

I can confirm that if the BPM and Initial Key exist as MP3 tags they will be retained by DJ Engine even after ‘Analysis’. I think this is a good thing, however, retaining the BPM may cause trouble for people who are unaware.

Here is how I tested…

1. Start with some tracks that have no BPM or KEY

   

2. Analyse the tracks with Mixed in Key and tag the BPM and Initial Key fields

   

3. Manually edit a few tracks and change the BPM to 100 and Key to 1A

   

4. Analyse the tracks in DJ Engine

   

Note: The manually edited tracks have not been corrected!

6. Load tracks into SC6000
   

The issue with retaining the BPM is that it is stored as an integer by Mixed in Key in the MP3 tag, as required by the ID3 tag specifications. This will cause issues for tracks that have a BPM like 123.5 because the .5 will never be known to DJ Engine.

DJ Engine appears to be capable of storing the BPM to at least 1 decimal place so it is more accurate than what can be stored in an MP3 tag.

People who use a direct workflow from Mixed in Key to DJ Engine should ensure the BPM is not stored to the tag or they will run into trouble with sync and quantize.

I have not done any testing of the Traktor import process, but I would hope that DJ Engine uses Traktors more accurate BPM and not the integer present in the MP3 tag.