Finding the Key

In the past two weeks a bunch of things have changed on the analysis front. I got to test the new key analysis algorithm from EA10 and as a result completely rewrote it. Accuracy of the results should be much better now. I also introduced a second BPM detection algorithm called SimpleSoundEnergy, which is generally faster than the original one, but not quite as accurate. This is hopefully great for folks who quickly want to scan huge collections and don't care as much about accuracy.

Of course I fixed a bunch of little things that are too tedious to list here. But you might want to know, that I added a couple of new inspectors. The amazon album version inspector lets you easily remove the (Album Version) suffix that Amazon likes to append to their mp3 titles. The rarely used genre inspector let's you find genres that are hardly used and maybe should be replaced by other genres. Lastly, I added an inspection that finds dupes with different ratings and lets you adjust them.

And here's the obligatory warning: Before downloading and installing this, please make sure you understand what Early Access means:

• Absolutely no warranty for whatever
• Features may or may not work, appear, and disappear
• It may not be possible to migrate data to future versions (even though we make a reasonable effort)
• This version will cease to function 2 weeks after its release
• You cannot buy this version

Just so that there is no doubt about it: EA11 isn't even a beta version.

And here are the download links:

• beaTunes-2-0-0-EA11 (OS X)
• beaTunes-2-0-0-EA11 (Windows)

Note for EA10 users

There will be some updates to the database. Make sure the analysis queue is empty before starting EA11 for the first time. If that is not possible, please note that BPM tasks that are still in the queue will probably fail.

Fixes, Fixes, Fixes

Wow - EA9 brought a couple of issues to light, which I hopefully have addressed in today's EA10. So expect a bunch of more or less obvious fixes. OutOfMemoryErrors are hopefully a thing of the past...

The biggest new item is the spanking new tonal key analysis. Finally, beaTunes now knows how to fill that key field it already supported for quite a while. However, the algorithm still needs some testing and tuning, so results may vary.

And here's the obligatory warning: Before downloading and installing this, please make sure you understand what Early Access means:

• Absolutely no warranty for whatever
• Features may or may not work, appear, and disappear
• It may not be possible to migrate data to future versions (even though we make a reasonable effort)
• This version will cease to function 2 weeks after its release
• You cannot buy this version

Just so that there is no doubt about it: EA10 isn't even a beta version.

And here are the download links:

• beaTunes-2-0-0-EA10 (OS X)
• beaTunes-2-0-0-EA10 (Windows)

Note for EA9 users

There will be some updates to the database.

Explaining Rulesets

The other day a customer sent us an email with a couple of questions that are asked again and again. I would like to take a few minutes and try to clarify a number of things.

What determines the color?

beaTunes looks at a part of each track and performs a frequency analysis of that part. The result is then projected into the RGB (color) space. In essence, it is a measure for whether different songs are using the same acoustic frequencies. The idea is that songs that share similar frequencies are more likely to sound alike. So two acoustic guitar singer/songwriter tracks are more likely to have a similar color than an acoustic guitar song and some AC/DC anthem.

But same color definitely doesn't mean that two songs sound the same. They only share some acoustical properties. It is meant as one of multiple factors that can be used to find matching songs. It is by no means the all determining factor.

Which leads us directly to the next question:

How do I configure rulesets?

Let's look at an example. Say you have three rules, a), b) and c):

• a) set to 1
• b) set to 4
• c) set to 2

If one song matches another song for all three rules 100%, then this song will be awarded 1+4+2=7 points. So in this case 7 points equal 100%.

If a song only matches rule a) and b), that would be 1+4+0=5, and that would be 71.4% (5/7).

So in essence you weigh the rules. In our example, rule a) has very little weight (1) - so it's really not that important. Rule b) on the other hand determines most of the outcome. It alone can score more than 50% (i.e. 4/7).

Note that matching rules isn't necessarily binary. That is, a song can match a song partially. So if a song matches rule b) somewhat, it might be awarded 2 out of 4 points. A good example for this is key matching.

How does key matching work?

Let's assume the key rule's weight has been set to 1. If it's a 100% match, i.e. a song has the same key as the one you would like to match, then beaTunes awards 1 point. If a song is in the dominant or subdominant of the song you would like to match, beaTunes awards 0.75 points. If it's in the tonic parallel, beaTunes awards 0.5 points. If it's neither of these three, beaTunes awards 0 points.

Please note that for key matching to make any sense you first have to set the key for a significant number of songs. beaTunes is capable of reading existing key values from id3 tags, but is not yet able to automatically determine the key.

What about negative values for rules?

Again, say you have three rules:

• a) set to 1
• b) set to -4
• c) set to 2

In this case the total number of points a song can score is 1+0+2=3 (the negative weight is ignored for this).

The values for the matching rules are added up. So, if a song matches all three rules the score it reaches is 1-4+2=-1.

In essence, with this setting you want to make sure that a song that matches rule b) is ranked really low.

What kind of similarity does the rule “similar tags” mean?

beaTunes lets you tag tracks with keywords (both in the Get Info dialog and in the table view tags column).

Again the -5 to 5 slider determines how important this rule is relative to the other rules. Assuming it's set to 1, if two songs have the exact same tags, 1 point is awarded. If two songs have two tags and one of the two tags is the same, 0.5 points are awarded. etc.

What is the difference between the “match quality” slider in the preferences and the one in the matchlist dialog?

The slider in the preferences applies only to the the "matching songs" panel (Edit > Show Matching Songs). The one shown when creating matchlists applies just to the matchlist you are creating. Check out our demo video for creating playlists using the matching songs panel.

I hope this post explained one of the core features of beaTunes a little better and helps you build some great playlists.

Key Ingredients

The bad news first: beaTunes 1.1 will not feature automatic tonal key detection.

However, we have made an effort to provide better support for harmonic mixing. Whenever you analyze an mp3 file, beaTunes 1.1 will check whether the ID3 tags contain any key data. If the key tag is present, it is read and copied into beaTunes' database. This means, it is also shown in the playlist views. This at least lets you take advantage of other tools' key detection.

Additionally, to allow DJ's to instantaneously see whether two keys match, beaTunes now renders keys in the colors defined by the Camelot Easymix system. In fact, when you hover with the mouse over a key, the tooltip even shows you the Camelot keycode (e.g. C Major = 8B).