#Mixed in key windows download software

And in some of these cases, after listening closely and for quite some time, I find myself agreeing with Engine DJ in the end. The major/minor decision is often a matter of asking: does this sound happy or sad … happy or sad ? … happy or sad ? … but in electronic music it may not sound like either, but like or … mysterious, sinister, otherworldly, garbage, really-fluffy-colourful-in-a-weird-way, experimental …įor some tracks I find it really hard to even find the harmonic center, the note which feels mostly at home. In that case I still leave the Camelot key at F minor, but I put a note in the description field that something else is going on in the track.

#Mixed in key windows download software

Especially acid tracks often have some squelchy psychedelic weirdness in them, the software may say it is F minor, but if you play along the melody you may find it to be F phrygian. And here I also see how limited the Camelot system is, because I often find that other scales are used in a track which are not covered by the Camelot system. Engine DJ is quite good at identifying the harmonic center note, but often it seems to classify a fast high-energy techno track as major rather than minor. I use a keyboard synth and a piano to play along a track. The BPM analysis is usually spot on, only every now and then I have to adjust the beat grid. Now I start with organizing files first, renaming files in a consistent way, I use mp3tag to fill in all the details that I like. I often do not agree with the results in either Mixed in Key or Engine DJ. In the beginning I used Mixed in Key, but its BPM analysis was off in about 50% of the tracks that I analysed - I used this mainly for techno tracks and the genre of music will certainly influence the analysability of the tracks, especially in terms of the Camelot system. I do a lot of key analysis at the moment. I think that the claim Engine DJ badly analyses tracks is too general. If it sounds out, shift the key up or down and try to match it. Of course tracks can also change key, but software tends to only assign one (the average), so if one of the tracks you used has more than one key, that could explain the clash.Īt the end of the day, use your ears. Other things can enter into it too, like the track being between keys or using an unusual scale. The fewer notes used, the harder it is to detect accurately, as notes often fit into more than one key. Even trained musicians do, because there has to be enough note pitch info in the track for the ear (or algorithm) to work out the key. This way the keys should (in theory) be compatible regardless of whether they match another software’s analysis.Įven MIK gets it wrong. The recommended thing is to analyse all tracks in the same software so that the algorithm used is identical for each track. It’s also not wise to assume the key is “wrong” because it’s not the same as. Without knowing what the tracks are (and therefore what they sound like) it’s difficult to put a finger on why they didn’t work together. I was shocked to find that more than a half (around 150) had an incorrect key (I will go through all the tracks in order to give you a precise statistic to Denon this means going through more than 1400 tracks, ouch).ĭid you have the same issues? if yes, where does the problem come from? I reviewed 200-220 tracks that did or didn’t contain a key in their MP3 file. I finally decided to go through some tracks manually and compare their key with beatport and tunebat. I then found myself in the same situation with several tracks, more and more.Īfter reanalyzing all the tracks, nothing changed. After searching on beatport and tunebat, I found that both keys determined by Engine DJ were incorrect. I was testing two tracks in 8A (camelot key), but they didn’t matched at all: it sounded bizarre, even if they were supposed to match perfectly in terms of key. To give you the hole context : I was searching for new ideas of associations. So lately, I had issues with the key analyser on Engine DJ.