beaTunes News

Thursday, August 21, 2014

Built-in Scrobbler :: Getting Moody

Today I want to tell you about two new beaTunes 4 features I have not mentioned extensively yet. Both have to do with

Let's start with scrobbling. That's what calls the process of logging the music you play in your account. The data is used by to recommend songs and artists to you. But more interestingly, it builds a listening history you can check out later. To configure beaTunes to scrobble to your account, open the Preferences, then the Playback tab, and click on the Authorize button. This will open a webpage in your default browser that lets you authorize beaTunes to send scrobbles to your account.

On you can contribute by tagging songs, i.e. assigning keywords like "sad" or "danceable" to individual songs. And this brings us to the other feature. Previously only available as plugin for beaTunes 3.5, version 4 allows you to import exactly those tags into beaTunes, which in turn helps you find songs and determine similarities. But that's not all. A number of commonly used tags have clear mood-related meanings. Good examples are "sad", "happy", or "depressing". beaTunes can take these tags and infer a mood value. Currently, this is the best way to automatically fill beaTunes' mood field. Which naturally can help you to build better playlists or find a certain kind of song.

Labels: ,

Tuesday, August 19, 2014

beaTunes 4.0.4: Configurable key formats

beaTunes3 logo It's been requested many times, but so far there just wasn't time. Now it's finally built-in: Configurable key formats. This means, that beaTunes can now display the tonal key in several different formats (traditional, OK-Notation, Wall Clock, etc). And for those, who are still unhappy with the built-in formats, there is an API that allows you to create custom renderers.

For those of you, who use the KeyToComment-plugin, please note that there is an update available via the beaTunes plugins preference pane. The plugin now features the ability to choose a key format.

To avoid misunderstandings: beaTunes still writes the same standard information to Id3 tags—exactly as it is defined in the specification. But it is now capable of displaying this information in multiple different ways. In other words, the Id3 TKEY frame will not suddenly contain information formatted in OK-Notation, just because it is rendered as such in the beaTunes user interface. This is to ensure interoperability between different applications.

Besides this addition, v4.0.4 contains some important bug fixes for Windows users who keep their music on network shares. Interesting for everybody is a fix for a bug that led to missing BPM values in iTunes when analyzing with Use online resources turned on.

As always, you can download the software from the download section of the website.

Most important changes in 4.0.4

  • Fixed use online resources for BPM (0 values).
  • Fixed ignore solution for acoustic. duplicates.
  • Fixed UNC path support.
  • Moved to FFSampledSP 0.9.7.
  • Moved to MFSampledSP 0.9.4.
  • Added interface for custom key text renderers.
  • Segment analysis of songs longer than 30min now skipped.

Labels: , , , , , ,

Tuesday, August 5, 2014

Much, much faster search: beaTunes 4.0.3

beaTunes3 logo It's been a turbulent couple of weeks since the original release of beaTunes 4. I have received lots of praise for the new UI and the new features—existing customers seem to love it and they do let me know. Thank you! I really appreciate it. Without this kind of feedback, I'd probably soon go and get myself a cushy job at some insurance company.

But admittedly not everything has been great. A couple of nasty bugs have forced me to push bug fix releases. While these releases fix problems and make things better, they also annoy everyone. They cause work for me and I simply cannot imagine re-downloading the same piece of software every week is fun for users. And while I'm glad that my little one-man-show is actually capable of releasing maintenance updates quickly, I'd rather ship the perfect product right away. So please accept my apologies for this not quite so smooth launch.

Today's release first and foremost fixes one big issue: user interface responsiveness.

In particular, a bunch of people complained that search is way too slow, especially in large lists like the main Music list. I'm happy to say that this should now be fixed and results should appear pretty instantaneously, unless your computer is busy with something else e.g. analysis. A welcome side-effect of the corresponding fixes are other performance improvements throughout the application.

Another important fix in this release deals with the duplicates finder. 4.0.2 introduced a possible hang. This is also now fixed.

As always, you can download the software from the download section of the website.

Most important changes in 4.0.3

  • Fixed slow search in libraries with > 10k items.
  • Fixed hang in duplicates introduced in 4.0.2.
  • Fixed application names in OS X application menu.
  • Fixed non-detection in duplicates caused by empty fingerprints.
  • Fixed external change detection for folder-based libraries.
  • Fixed validity test for audio identifiers.
  • Improved audio device recognition robustness.
  • Improved normalization of ISRC codes.


Friday, August 1, 2014

beaTunes 4.0.2

beaTunes3 logo I'm happy to announce that I just released beaTunes 4.0.2. Like 4.0.1, this is a maintenance release, aimed at fixing the kind of little bugs that pop up right after a major release. For details, please see the list below or the release notes.

As always, you can download the software from the download section of the website.

Most important changes in 4.0.2

  • Fixed sync failure of songs with fingerprints.
  • Fixed diacritic-related unicode file name problem on Windows.
  • Fixed AIFF decoding failure.
  • Fixed playback start on Enter in textfields.
  • Fixed excessive file attribute reads.
  • Fixed potential analysis deadlock.
  • Fixed database access in EDT during analysis.
  • Improved formatting of AppleScript errors.
  • Improved Schema Evolution resumability.
  • Improved genre list loading.
  • Improved TitleStartsWithTrackNumber inspection to remove repeated track numbers.
  • Improved segmentation performance.
  • Added ability to repair or rebuild database via the Tools menu.


Friday, July 25, 2014

Visualizing Playlist Flow

beaTunes2 logo Playlists are basically songs put into a specific order, sometimes for a particular occasion. So much is clear. But what makes a playlist good? A recent paper by Thor Kell and George Tzanetakis suggests, that good EDM playlists or DJ sets are usually made up of songs that match sonically: "Our transition analysis has shown timbre to be an important attribute used by DJs".

But while timbre (related to beaTunes color) apparently is a very important choice for EDM DJs, it may be less so for the madly in love teenager who works on his graduation mix, or the oldies show DJ, who is restricted to songs from the 50ies. But in any of these scenarios it can be helpful to get some visual feedback for how the list, not the song, sounds and what the transitions are like. beaTunes 4 addresses this by displaying a playlist image above the textual list and also showing a transition column in the main table.

The playlist image represents each song in three dimensions: height, width, and color. Each of these dimensions can be assigned to a song property, e.g. duration, BPM, or key. To change the current setting, simply right-click on the image and re-define what is being displayed. To listen to a given song, double-click on it to start playback.

While the playlist image is a positive, descriptive approach, i.e. it tells what you have, the transition column is a somewhat negative approach. Like a little brother it nags, it tells you with little icons what may be wrong with your playlist. Among the things it indicates are tempo, key, and language changes (all of these require prior analysis). If you are keen on avoiding certain transitions, like a harsh tempo change, the corresponding icon will make you aware of it (a tooltip shows more info), and might help you to avoid it.

Without a doubt, automatic playlist generation has come a long way and certainly has its (very convenient) place. But it does not replace manual set-building, as it cannot know your goals and interests or the given occasion. Automatic playlist algorithms simply cannot detect intent. What's left is trying to support playlist creators. That's where beaTunes shines. It's meant to support you in building excellent playlists—giving you a little more feedback than just the song names.

Labels: , , ,

Monday, July 21, 2014

beaTunes 4 is out!

beaTunes3 logo I'm very happy to announce that after a year filled with lots of work beaTunes 4 finally saw the light of day today. Compared to version 3.5 there are a bunch of changes—most are improvements of existing features. Please note, that after multiple years of free updates for 3.x, the upgrade from 3.x to 4.x is not free. However, owners of beaTunes 2 and 3 licenses can count on significant discounts.

When updating, please let the database re-organization run through to the end to avoid database corruption. Even if this takes a while. Should you run into any problem, please let me know.

You can download the release from the brand new website.

Most important changes in 4.0.0

  • Semantic music player
  • Completely rewritten BPM, key, and color algorithms
  • Acoustic dupe detection (requires prior calculation of fingerprints)
  • Configurable playlist visualization
  • scrobbling, tag import, and mood inference
  • Playlist import
  • Completely overhauled UI
  • Find and replace in textual metadata
  • Improved scalability
  • 64-bit support for Windows

Thank you for your continued support!


Friday, July 18, 2014

Featuring: Fancy Find and Replace

beaTunes2 logo Most beaTunes users love its inspection feature. It's probably the best way to manage a large library, cleaning metadata, keeping it all consistent. But for some things inspections aren't specific enough—especially because they cannot be configured (by design). A good example is: "featuring". How do you write it in your library? "feat.", "ft.", "featuring"?

To tackle this kind of problem, beaTunes 4 (to be released soon!) has Find and Replace functionality built-in. It treats the visible text fields in the current playlist like one big document and allows you to search it. Naturally you can also replace stuff. But how does this help with the "featuring" problem?

Glad you ask! Obviously you can run multiple searches. But using regular expressions, you can also use just one. It gets a little tricky, but bear with me for a second. In regular expressions a vertical line | means or. So to search for "feat", "ft", or "featuring" you could write "feat|ft|featuring". But this will also find all instances where "ft" is just part of a word as in "left". So we need to add spaces like this " feat | ft | featuring ". That's better. But now we are missing all the cases where there is a dot after the word. So we need to add something to the expression that says: Oh, and perhaps there is a dot, too. In regular expressions this is done with a question mark. Now before we simply add a dot and a question mark, I have to mention one thing: just like vertical lines and questions marks, dots have a special meaning. They act pretty much like a joker, meaning any character. That's certainly not what we want, which is why we have to escape the dot character; meaning, tell the program to use the dot literally. This is done with a backslash. In the end our regular expression looks like this: " ft\.? | feat\.? | featuring "


beaTunes highlights all visible matches, and when searching with regular expressions even displays an overlay with the potential replacement. This is especially handy when working with capturing groups.

If you'd like to try out an Early Access release, please go to the Early Access Page and download the latest version. And if you do so, please provide feedback.