beaTunes News

Thursday, June 2, 2011

beaTunes 3 out now!

beaTunes2 logoI'm quite happy being able to post that I just turned beaTunes 3 live. The release has been in the making for quite some time, but I think it really kicks ass - not least, thanks to the valuable feedback I got from you guys.

So.. Thank you!

Since I have posted little bits and pieces about what's new in the last couple of weeks, I won't go into too many details here. Let's just say that the UI has gotten a lot better, I added a ReplayGain analysis task, scripting plugins with JRuby/Jython/Groovy is now possible, and I completely rewrote the key detection algorithm - it is now based on Jipes.

Apropos key detection algorithm. Hm.. not sure how to say this humbly.. It rocks! My tests against Christopher Harte's Isopohonics Beatles test set show, that with 'use online resources' turned off it performs significantly better than other software DJs typically use. But more about that in another post.

For now, enjoy this release... I surely will :-)

Upgrading

Upgrade licenses are available for $11.95 for 2->3 and $24.95 for 1->3, respectively. The price for the regular license (for now) stays the same: $31.95.

Note, that when first running beaTunes 3, it changes its internal database layout. This can take a while. Please don't interrupt the process.

Labels: ,

2 Comments:

Blogger mxx said...

How are you handling replaygain? Are you modifying audio data in the file the way mp3gain does it or are you adding tags with replaygain info the way foobar2000 does it? or somehow differently? Do you support both album and train gains? Are you doing anything with iTune's "soundcheck" tags as well?

June 5, 2011 at 5:21:00 PM EST  
Blogger beaTunes said...

beaTunes is not manipulating the audio data at all, instead it's setting the replaygain_track_gain and replaygain_track_peak tags like other apps do, too. Additionally, the iTunNORM tags are adjusted pretty much the same way iVolume probably does it.
beaTunes does not support album gains.

June 5, 2011 at 5:25:00 PM EST  

Post a Comment

<< Home