beaTunes News

Tuesday, March 24, 2015


Heads up! On 3/25/2015 we're having a sale over at MUPromo.

Labels: ,

Monday, March 16, 2015

beaTunes 4.0.21—Now with Java 8u40

beaTunes4 logo

As already mentioned a little while ago, I'm excited to release an official version of beaTunes with a bundled Java 8u40. Well, today is the day.

You can download the software from the download section of the website.

Most important changes in 4.0.21

Labels: ,

Wednesday, March 4, 2015

Faster graphics, fewer crashes: Java 8u40 is finally out!

beaTunes4 logo

Yesterday, Oracle finally released Java 8 update 40. Usually, these updates are minor affairs, but this one is a bit special for me. Buried in the list of fixes, 8u40 addresses the single largest source of beaTunes crashes on OS X. And just because it is surprisingly unclear to what a crash constitutes—let's just say a beaTunes crash is an event during which beaTunes suddenly disappears, OS X offers to send a crash log, and beaTunes also offers to send logs the next time it's started.

After reporting the bug in early September 2014 it was first ignored by the Oracle bug report evaluation team, until a little digging and poking provided more information and suggestions for a fix. Eventually the bug was fixed in late October 2014, but because of the standard release process didn't make it into an official release until now.

Though this is the most important fix for me personally, 8u40 certainly has a couple more things to offer (complete list). Here are my favorites specifically for OS X:


It will take a little while until an official beaTunes release with this updated Java version is published. But if you want to try it out right now, you can use the current development snapshot for OS X.

Labels: , , , ,

Friday, February 27, 2015

beaTunes 4.0.20 —taking diagonal mixes into account

beaTunes4 logo

More or less as a consequence of some unannounced Discogs API changes from 2/20/2015, beaTunes 4.0.20 was released today. Primary purpose of this update is to re-enable cover art import from Discogs via the Import metadata analysis task and the Get Info dialog pane. Another minor change in this release is an improved Similar Key rule, which now takes the "diagonal" mix as well as several energy boost mixes into account. This should help finding a good transition order, when using a match ruleset with emphasis on key, as additional transitions become feasible. For a good overview of harmonic mixing techniques, take a look at this article by Radley Marx. Diagonal key transitions are now also considered, i.e. there is no warning for them in the transition column anymore.

You can download the software from the download section of the website.

Most important changes in 4.0.20

  • Fixed Discogs cover fetching caused by Discogs API change.
  • Added diagonal mix (Xd <-> X+1m) to valid key transitions.
  • Improved similar key rule to support diagonal mix and energy boost.
  • Improved 'Open in MusicBrainz'.
  • Moved to CASampledSP 0.9.9.
  • Moved to japlscript 3.1.1.


There was a minor mess-up with the OS X version of this release, related to dylib dependencies, which is now fixed. If you see a related error message, please simply download again.

Labels: , , , , ,

Wednesday, February 18, 2015

beaTunes 4.0.19

beaTunes4 logo

beaTunes 4.0.19 was released today. As always, the release contains some more or less important fixes, improvements, and updates. For those of you interested in seeing partial artwork in the main table, please check out this discussion.

You can download the software from the download section of the website.

Most important changes in 4.0.19

  • Fixed display of progress dialog on initial import.
  • Reversed mousewheel direction on volume knob on Windows.
  • Improved automatic BPM range detection for EDM.
  • Improved repair/rebuild logic and dialogs.
  • Improved performance of adding selected songs to queue.
  • Improved caching of auto-completion.


Monday, February 9, 2015

Creating great Playlists

So, now that I have bored you enough with overview, libraries, analysis options, and inspection, finally I'm getting to the point of it all: Building better Playlists.

At the core of playlist creation stands a concept. Something that is supposed to make the list tick. Something that ties it all together. This can be something as common as "Best Rock of the 80ies", "Love Songs of 68", as personal as "Songs you made out to as Teenager" or as specialized as "Songs influenced by Nirvana's Nevermind". Or, if you're into working out "Driving Beats for Aerobics", "Steady Steps for Marathon Trance", and "Up and Down on two Wheels". You get the idea.

The point here is, every one of these concepts follows different rules and therefore requires different data.

Regarding data we're in luck. Analysis and Inspection should have whipped your collection in shape. But how do you find the right songs? How do you make beaTunes understand the rules?

Song Matching

Naturally, you can simply browse your library or use the filter field to search, build your lists completely manually. Another approach is called query by example. The idea is, that you choose a song and ask beaTunes to find a similar one. The $100.000 question is: What exactly is similar?

beaTunes sidesteps this question by letting you define what's important to you. This happens in the Song Matching preferences. There you can set up sets of rules that emphasize certain aspects of similarity, like tempo, mood, or color.

Creating Matchlists

Once you have created a ruleset appropriate for the playlist you want to create, select a song that the other songs are supposed to be similar to. This song is called a seed song. Then choose New Matchlist from the File menu (or use the corresponding toolbar button). beaTunes will then display the dialog shown below. Once you click OK, it will automatically create a new playlist according to the configured rules.

Building Playlists Iteratively

Matchlist are a great tool for building playlists with the click of a button. But they also take all the fun out of the creative process. beaTunes supports another way to create playlists, one that works song-by-song.

To get started, again select a song that you want to use as the first song of your list—your opener. Then click on New Playlist from Selection in the File menu. beaTunes will create a new playlist and you might want to change the default name to something better. Then select that very first, lonely song, open the View menu, and make sure that Show Matching Songs is turned on. Below the main playlist table, a panel with matching songs should appear.

To build your playlist, check out the matching songs. Once you've found a good candidate for song #2, simply drag it into the main playlist table above. You will find that beaTunes automatically selects the newly added song, triggering the match process again. So now, beaTunes shows you potential candidates for song #3. And so on... The process is also nicely demonstrated in this video. If you're unhappy with the current match ruleset, you can select another or modify the current one in the preferences. And for those people interested in harmonic mixing, I'd like to point out the key filters. They let you hide songs that are not in a defined harmonic relationship to the selected song.


I hope this articles helped you getting the most out of beaTunes when creating playlists. If you have further questions, please comment below or start a discussion in the support forum.

This article is part of a small series under the heading "HowDoesItAllWork".

  • Part 1 explains the overarching idea behind beaTunes.
  • Part 2 explains what kind of libraries beaTunes supports.
  • Part 3 takes a closer look at analysis and analysis options.
  • Part 4 takes you step-by-step through the inspection process.

Labels: , ,

Wednesday, February 4, 2015

DigitalDJTips features beaTunes

beaTunes4 logo

Phil Morse from just featured beaTunes in his article 5 Ways To Create Better DJ Sets With beaTunes. The article contains a great video walkthrough that I can highly recommend to anyone using beaTunes. Especially the bit about manually building a set using the match table (5:20) is awesome advice.

Today I also released a minor update. As always, the release contains some more or less important fixes and improvements. You can download the software from the download section of the website.

Most important changes in 4.0.18

  • Fixed read-only check on Windows.
  • Fixed issue with tuning rule.
  • Fixed additional matchlist filters.
  • Improved timeout handling on inspection commit.

Labels: ,