Key Detection PLEASE!

+10000

 

Any tips on how best to process tracks? My tracks don't seem to keep the tags written to them for starters.

 

Can you elaborate? My current workflow is as follows:

1) I drag my "music to be imported" folder to KeyFinder.

2) Run Batch Analysis.

3) Right-Click "Write Tags to files".

4) Import to iTunes.

Now that I think about it I did have a few tracks where the Tags didn't stick. I've been working with the developer and I will bring this up. Can you give me some more information regarding which tracks are having issues? Bitrate? Format?

 

I would very much love this option!

it sucks to analyse tracks outside of traktor
so i am analysing 2 times per track, would really appreciate merging the two

 

Well fellas, it's been a couple years and no word from the NI team on this. I gave up and gave Mixed In Key $50 to have key detection. It's a shame I couldt use that money to further support NI in using a product I love. Oh well.

 

how about you do your homework.

Id bet you would want NI to wipe your ass on stage too..



be a ****ing dj, and do some homework.... lazy assholes! :angry:

 

I use RapidEvolution3 just for key detection.
The Software writes the detected keys right into the key field.
And Traktor shows it - of course even if tracks are analized and beatgrited.

So - for me its no more necessary, that NI integrates key detection into Traktor.

 

"Id bet you would want NI to wipe your ass on stage too..
be a ****ing dj, and do some homework.... lazy assholes!"

---so tired of these type of comments!
Native Instruments make cutting edge music technology so there's not really any room for luddites who hate clever technology

lazy DJs will always be lazy - whether or not they have key detection or beat syncing! but using clever technology definitely does not make you into a "lazy asshole" - it's usually just a matter of diverting the time you spend from one thing into another

personally, I don't think key detection is all that relevant - it's pretty quick to judge it by ear. and two tracks playing in the same key does not always sound good. and often tracks will harmonize even when not in the right key - it depends very much on the actual melodies being played

I try and mix in key most of the time - but I will avoid shifting the key by more than 2 or 3 semitones because it warps the sound too much. I'm not convinced that key detection would make this much easier - as you can test different key shifts pretty quickly and I think you're more likely to identify what sounds good by ear

 

I completely agree with Matt's comments above, I see key detection as just another useful tool which you can choose to use, abuse or ignore depending on the situation. Yes, you can tell pretty quickly by shifting the keylock whether a track is going to go or not, but having a hint as to how much you need to move the keylock can be pretty helpful, just like knowing the bpm of a track.

I would rather spend my time doing other more constructive things than "homework".

 

You know its a great feature to implement when people start arguing over it

 

http://www.native-instruments.com/forum/showthread.php?t=150806

and you are served.

works like a charme, is freeware...

 

This is not the place to speak to people like that. You will never address someone in a manner like that again, ok..?

Cool..?

 

100% agree. the only "lazy" guy is himself. google fixes his issue...the community here (! see my link !) has a solution....

 

key detection in 2.5? i only get about 60percent of songs.

 

as for me i use Virtual DJ to get the keycode. Then I edit all tracks to write the keycode and bpm straight in the title.

I reckon it takes hours.

 

Since the current version of Traktor Pro 2 has the option of adding the Key field in the browser, could NI add the Keycode field as well?

 

Pretty please? Just one more field option in the browser for the Camelot Keycode?

 

totaly agree!

this post 2010...

i was post again in 2013

 

now that we have key detection it gives me great pleasure in closing this thread.

[closed]