www.mixshare.com

"rapid evolution" is an advanced harmonic music library tool for dj's, designed to be used while you mix. it helps profile your songs by saving important properties, such as the bpm, key, time signature, styles, comments, etc. you can then instantly see which songs are within bpm range, in key harmonically and in similar styles. more importantly, it lets you save comments and information about each individual mix you come up with. use it to enhance your knowledge of your music and remember the important details of what you do. you will quickly take your mixing to new levels! the software includes automatic bpm and key detection, as well as tools to determine this information yourself--a bpm tapper and a midi keyboard. it also lets you share all song and mix information with other dj's. use it and start evolving! :-)



I've been playing with it for a little bit now, seems pretty accurate and is helpful even if you aren't using ableton or traktor yet and still use CDJs or Vinyl because it will detect from an analog signal and you can mark it as analog in the database...

I found out that an error is occurring. I didn't get any hits when I search the RE forums, so I posted about my problem. Hopefully, Qualia will be able to give me some sage advice.

wow! I LOVE stuff like this. Thanks for the heads up!

Now that I've got it working, I've played with it some. It agreed with MixedInKey on the keys of tracks that I tried. It did seem to consistently detect a slightly lower BPM than I arrived at when adjusting the beat grids in Traktor. It was almost always within 1-1.5 BPM of the value I got, so it does give you a good starting point for doing finetuning. I guess I just thought it'd come in closer to the value I found. (I had the accuracy sliders all the way to the right--most accurate. Boy, did that take a while. ) Of course, maybe my ears are just off and the tool got the BPM right.

That's good to know about Traktor 3.2. I analyzed all the tracks I've got in Traktor's Collection before I upgraded from 3.0. You're right about 3.0's BPM detection. For me, it was anywhere from slightly to wildly off.

I'll have to start using your approach.