Music library management blog

Release 20120201 - auto tagging untagged files

2012-02-07T00:00:00+00:00

It's been the top rated idea on the bliss feedback forum for a while and now it's released: introducing auto tagging for untagged files!

This is the first of a series of releases to automatically tag your untagged music files. Music files without tags are routed to an acoustic fingerprinter called Chromaprint which identifies music on the MusicBrainz online database. bliss then shows the matched files and releases. Here's a sample of the new untagged page:

The untagged files you own may match to multiple releases. bliss (currently) shows all of these releases in this list format. Scroll through the different suggestions for each folder, clicking show tags to inspect how the files will be tagged.

When you are happy, click Tag files to apply the tags into the files.

I stated above: this is the first of a series of releases. This means there's more to come in this area. I am making the tag table editable, so you can override tag values. I am collapsing the rows into one row per folder so that you are not confronted with a large number of rows for the same folder. I'll also put extra work into making sure the default (top) suggestion for each folder is the one with the most matched files.

Other suggestions are gratefully received, please post them in the ideas forum!

Any other stuff?

One other minor item: a bug in the UI where, for fixing file paths, multiple 'fix file path' buttons would be presented is now fixed so there is just one button. Sorry about that.

The new release can be downloaded from the downloads page. Your existing fixes will apply!

The case of the disappearing Folder.jpg files

2012-02-01T00:00:00+00:00

Generally, Folder.jpg files are image files created to represent or visualise the contents of a folder on Windows computers. Applied to music, album artwork is named Folder.jpg and is stored alongside the tracks for the given album. Music players, when playing the music from a given album, are able to lookup the Folder.jpg file inside the source folder of the music files and display this as the artwork (although other means of storing artwork exist)

Recent versions of the Windows operating system have seen the lookup and creation of Folder.jpg happen automatically, often without even listening to music. This sounds ok in principle; it may save you some work. But the subject of this blog post is not what Windows does, it's the way that Windows does it.

Windows Media Player version 11 and later introduced a new feature that finds and downloads album artwork as Folder.jpg automatically. Unfortunately, there are a number of problems in exactly what it does, such as download inferior (lower resolution) art, overwriting anything that already exists. Less obvious is the fact that it then marks these Folder.jpg files as 'system' read-only files, hiding them from Windows Explorer and preventing them from being updated by other applications with saner allowances for different album art resolutions.

Worse, recent versions of the Windows operating system itself ("WMP") now perform this function without you even starting up WMP. Step forward the Media Streaming Metadata Synchronizer, installed within Windows Home Server 2011. Unless you live in a soley Microsoft world and are happy with low resolution album art, it's best to disable this, at least until Microsoft release an update so that you are able to configure it to work as you like. HINT HINT, BILL

Help, my Folder.jpgs have disappeared!

Folder.jpgs that have been changed to system and/or hidden files will disappear from Explorer and software will have trouble updating the files. bliss, for example, will give this message:

If Windows Media Player or the Media Streaming Metadata Synchronizer have already done their dastardly deed, it's time to fix your Folder.jpgs. Thankfully, Windows comes with the powerful command line tool attrib which can be used to set your system and hidden attributes in bulk.

Here are the steps:

Open a command window
Change directory to the root of your music library
Issue the attrib command

There, you go, sorted! Oh, you wanted more detail...?

Start by opening a command window. Click the Windows button or Start Menu, click Run or Search programs and files and type cmd. It should look a little like this:

Press return. Your command window opens.

Type cd [your music library] where [your music library] is the path to the root of your library, as supplied to bliss. Here's how it appears for me:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\gravelld>cd C:\Users\gravelld\Music

C:\Users\gravelld\Music>

Now you can issue the attrib command. Here's what the command you should issue looks like:

attrib -s -h Folder.jpg /s

The attrib command is used for adding and removing file attributes. The -s -h arguments mean "remove the system and hidden attributes" from whatever files match the next statement. This next statement is Folder.jpg /s which means every file named Folder.jpg in this folder and child folders. This means every single Folder.jpg in your library will be changed.

Now let's type that in...

C:\Users\gravelld\Music>attrib -s -h Folder.jpg /s

C:\Users\gravelld\Music>

There's no feedback as to whether the command was successful, but if you check using Explorer you should now be able to see all of your Folder.jpgs, and the files will be writeable by other software, including bliss.

I hope this fixes your Folder.jpg woes!

Thanks to benklocek for the image above.

New release - 20120119 - cover art alternatives

2012-01-24T00:00:00+00:00

This new build contains a new user interface to make choosing cover art alternatives easier and fixes some minor bugs.

It's long been suggested that choosing cover art alternatives can be laborious. The Change art page can be used to choose from alternatives to current art that bliss finds or upload your own art. The trouble is you have to click into each page for each album, then click back to the previous page to work on the next album and so on.

The new user interface combines several albums' alternative art on one page. Albums are shown as a list, with cover alternatives to the right. Here's how it looks with alternatives loaded:

These alternatives are shown in the album page. There's a new option in the filter bar, 'Show'. Click that and you get the link to show cover art alternatives. The alternatives can be filtered by start character and compliance, and you can display 12, 48 or 96 albums, like when viewing albums in the traditional 'grid' view.

Bugs and other

A few bugs and other items have also been cleared up in this release.

The new clear and rescan feature was not working correctly on Windows computers. This has been fixed.

Track numbers is ID3v1.1 tags are now supported. Previously these tags were ignored because they were erroneously lumped in with ID3v1 tags, which did not support track numbers.

Still on the subject of track numbers, bliss was previously having trouble with file organisation where some tracks in an album have track numbers and others in the same album don't. This is fixed.

On the subject of file organisation, if file names ever have double extensions, e.g. "01-Thriller.mp3.mp3", bliss would previously have ignored the double extension. Now, it correctly assesses the double extension against your file organisation pattern. In these cases, the filename will only be compliant if a suitable pattern is used, e.g. .<fileextension>.<fileextension>. Note that the settings user interface automatically adds a final .<fileextension> to all patterns. Thanks to Martin at VortexBox UK for spotting that one.

Finally I added in a couple of safeguards to stop errant art or activity causing bliss to fail. Images over 5MB in size are now ignored, and clicks to fix items from the user interface are now throttled so only five can run at once.

Get the new release from the downloads page. Existing fixes apply!

Thanks to loop_oh for the image above.

Organising multi-disc album files

2012-01-13T00:00:00+00:00

Organising music files consistently is a smart thing to do. It means music is easier to find for synchronising your home collection with your smartphone and legacy music players that don't support tagging can still display basic information about your music.

Multi-disc albums present a problem though. Default organisational schemes such as a simple artist/album layout don't cut it - the disc number is not preserved. This means, when you're playing an album such as All Things Must Pass or Speakerboxxx/The Love Below, the tracks may play back in the wrong order.

So, multi disc numbering should be reflected in your music file structure. But how? Here are a couple of ways.

In one folder, prefix to track number. Normally, in an album folder, the first part of a file name is the track number. This orders the tracks in an album so they play back in album order. To retain the order of the multi disc album, you can prefix the disc number to the track number. For instance:

1-01-I'd Have You Anytime.mp3
1-02-My Sweet Lord.mp3
...
2-01-Beware of Darkness.mp3

The advantages of this approach are that all files are in one folder, which may make it easier to play the album on certain devices. The disadvantage is that the album is a little more difficult to separate if desired.

The other approach is to store separate folders for each disc. Here, you have a different folder structure for each multi disc album:

All Things Must Pass/
    Disc 1/
        01-I'd Have You Anytime.mp3
        02-My Sweet Lord.mp3
        ...
    Disc 2/ 
        01-Beware of Darkness.mp3

This tends to be my own preference but it's a fairly cosmetic consideration.

bliss's <discnumber> token and file organisation conditionals

All this theory is great, but how do you put it into practice? bliss added the ability to use disc numbers in file organisation patterns a month or so ago. In the same release it also added a powerful new feature that can be used elsewhere in file organisation patterns: conditionals. Conditionals provide a way of adding a piece of file organisation structure, but only if a given tag exists.

Conditionals are important for tags which might not exist in your music. If you were to use the <discnumber> tag without a conditional you would likely find a lot of your music cannot be assessed for file organisation compliance because most non-multi disc albums do not have a DISCNUMBER tag.

So, how do the file organisation rules appear? Following the two examples of how to organise multi disc album files above, the first approach, one folder, looks like this:

<artist name>/<album name>/<discnumber>?|<discnumber>-|<tracknumber:nn>-<track name>

The interesting <discnumber> bit basically means: if the album has a <discnumber>, include "<discnumber>-" in the target file name.

The second, separate folders, appears as so:

<artist name>/<album name>/<discnumber>?|Disc <discnumber>/|<tracknumber:nn>-<track name>

Notice how a literal "Disc " is added to the folder name. This makes it easier to understand what the folder represents. You could do this in the first approach too. In addition, note how an extra folder is also added when a <discnumber> is present, by means of the trailing "/". Remember, when a <discnumber> is not present, the pattern in between the "|" characters is ignored, so the trailing "/" is not evaluated and there are no extra folders created.

A quick caveat: use of <discnumber> (currently) only applies to where the DISCNUMBER tag is actually used and present in your music files. It does not interpret 'disc number artifacts' in album names, for instance "All Things Must Pass (Disk 1)". Such albums will not be interpreted by the <discnumber> token and will be treated as 'normal' albums if the DISCNUMBER tag is not present.

Walkthrough: using bliss to organise multi disc albums

Let's walk through how bliss can organise multi disc albums. We'll start with the album we've discussed in this blog post, All Things Must Pass. It's the two CD, early 2000s re-issue, but the same can be applied to the original three record version. We'll aim to split the album folder into two folders, one for each disc.

Here's the current file and folder structure. Currently there are separate folders for the two discs, but these folder names are inconsistent and they are located in the artist directory rather than an album directory:

Assuming bliss is already installed, we start it up, open the settings panel, and click Organise music files:

In the resulting panel, we choose a Custom folder and file structure and place our file organisation pattern <album artist>/<album name>/<discnumber>?|Disc <discnumber>/|<tracknumber:nn>-<track name> inside the supplied text field:

Below this, we'll keep the rule on 'manual' operation while we check where bliss wants to move files to. With our pattern set we can then click 'Apply'.

Once the rule is applied, bliss assesses all my albums for adherence to the pattern. The files that make up All Things Must Pass don't adhere so it's marked 'Uncompliant'.

Clicking the File path link takes us to the file detail page, where we can see the expected and actual file locations:

You can just about see the target file locations bliss wants to move files to. Notice these locations have the "Disc n" folder as part of their structure, inside the parent album folder. Clicking Fix all file paths moves all the files. We can then do the same for the second album in the overview screen.

The albums now show up as compliant.

And the most important test is how this appears in Explorer:

Perfect! Of course, if I put the other, single folder pattern in as my file organisation pattern, I would have a different structure.

Good luck in your organising you multi-disc album files!

Thanks to john_a_ward for the image above.

New release - 20111221 - clear and rescan

2012-01-03T00:00:00+00:00

Over the past few months, the cause of most problems related to running bliss has been database corruption. Strange messages such as double get for block and page header magic for block not OK mean bliss's internal database has become corrupt. It is caused most commonly by an abrupt shutdown of the bliss process, perhaps because the computer hosting it has been switched off or reset without a 'shutdown'.

This new build contains multiple ways of alleviating these problems. First, extra care is taken to avoid corruption in the first place, even if the host computer is switched off abruptly. In addition, when bliss detects a corrupted database on startup it deletes it and starts over. Finally, the same delete-and-start-over code is available for invocation manually using the clear and rescan button.

The button can be reached by clicking the down pointing triangle next to the existing rescan button. The clear and rescan button will be displayed. Clicking it deletes the existing database and starts from the beginning, re-assessing all of your music against your rules.

Improvements to acoustic fingerprinting

The acoustic fingerprinting code introduced in the last build has been polished up a little. As a recap, acoustic fingerprinting is a way of identifying music by the audio within a music file, rather than its tags, which may be incorrect (often subtly) or non-existent. This is useful when looking up information or album art for some music online.

For starters there's now a 64 bit version of the Linux acoustic fingerprinter. The existing 32 bit version would still work on a 64 bit Linux box if you had the correct libraries installed, but without them the fingerprinter would fail.

The main improvement though is a big increase in the accuracy and coverage of the fingerprinter. On the bliss test machines the fingerprinter now outperforms 'legacy' tag based lookup.

Other stuff

More stuff in this release includes:

Fixed a memory problem when viewing 100s of album detail pages.
Linux start script now uses JAVA_HOME, if set, as a default for the location of 'java'. Otherwise, just 'java' as before. This makes using the start script more hackable as it's possible to point the script to a different version of Java.

Get the new release from the downloads page. Existing fixes apply!

Thanks to Sebastian Anthony for the image above.

Tags and case

2011-12-18T00:00:00+00:00

Let's go back to when bliss was a forming, still amorphous idea of some software to fix inconsistencies in a music collection. The first time I explained it to my wife she responded quite differently to what I expected. Instead of eyes glazing over her first response was "great, will it fix the inconsistent capitalisation in our music?".

We all have our different pain points which arouse the inner OCD within us. For her, and quite a few other people, inconsistent or plain incorrect letter case can be a real annoyance when browsing your music library.

Indeed, if you've ever wondered about capitalisation, you're not alone. All the major online databases take the subject seriously!

Let's take the case (sorry) of track names as we consider what types of case inconsistency exist.

Before I continue, I am aware of the irony of discussing correct capitalisation when my own product name, "bliss", breaks standard capitalisation rules. All I can say is: it's about having a choice!

Intra-tag

Taking any one track name in isolation, it can be easy to spot case inconsistencies. For example:

Like a rolling Stone

For some inexplicable reason the 'r' in 'rolling' is not capitalised, whereas all of the other initial letters are. This doesn't follow any standard capitalisation styles.

Case styles vary, but there are a number of standard styles. Taking these as inspiration gives us:

LIKE A ROLLING STONE

Like A Rolling Stone

Like a Rolling Stone

Like a rolling stone

ALL CAPS makes my eyes bleed, so that's a bad idea. The last one, sentence case, feels wrong for a title of a song. Personally, given this is a title, I vouch for the consistency of the second option, where all initial letters are in upper case. I know many that would opt for the penultimate option, however.

The same goes for album names, artist names and any other tags, of course. Depending on the nature of the tag, some tags may require different case styles.

Inter-tag

Creating inter-tag case style consistency is making sure that the case style you decide for one tag is applied to the other tags of the same type.

Taking the Highware 61 Revisited example further, consider the potential track name inconsistencies:

Like a rolling Stone

Tombstone blues

It Takes A Lot To Laugh, It Takes A Train To Cry

Keeping your case styles consistent is a matter of applying your case rules throughout your music library. This takes a lot more work than just deciding what your preferred style is and fixing it for one tag. This might mean hundreds of changes.

Consider the artist

While it's fine idea to impose custom case styles to titles in your music collection, it's also worth considering whether you are meant to. I speak, of course, of musical artists and their sometimes liberal approach to case rules.

Artists like OutKast or eels, album titles like CrazySexyCool and tracks like tourette's (from In Utero) prove that artists have an infinite capacity to break your title case conventions.

Arguably, you should defer to artistic intent.

How to fix

Naturally, this is an ideal feature for bliss, and one that's already been suggested. If you want to see it implemented, please vote for it!

It's possible to use manual taggers like MP3Tag and others too. These allow you to edit the tags, which is obviously the first step, but they also tend to have a semi-automatic 'action' capability to convert a batch of tags. Here's how to change case with MP3Tag and here's how to do it in puddletag.

I hope these thoughts and tips help keep the OCD monster at bay!

Thanks to cogdogblog for the image above.

New release - 20111206 - track number padding and acoustic fingerprinting

2011-12-14T00:00:00+00:00

There are two main new features in this release. The first offers control over how zero padding is used in track filenames. The second uses acoustic fingerprinting technology to identify music when finding cover art, genre or year information.

Zero padding in file names

Zero padding is the addition of leading zeros to track numbers, in this case applied to file names. Why is this needed? Consider the following three files:

1-Devils Haircut.flac
2-Hotwax.flac
10-Sissyneck.flac

Now, in any sane human's head the ordering of files would be as above: 1, 2, then 10. This is called natural ordering. The trouble is, computers aren't sane, and instead they often impose an ordering based on the character codes for the strings. In this case:

1-Devils Haircut.flac
10-Sissyneck.flac
2-Hotwax.flac

This is because the first character of 10-Sissyneck.flac is considered before the first character of 2-Hotwax.flac.

The workaround is to pad our string with zeros, as follows:

01-Devils Haircut.flac
02-Hotwax.flac
10-Sissyneck.flac

By forcing the number of digits for each track number, we can assure that each order of magnitude in the number is compared like with like. Therefore, 0s are ordered before 1s.

So how does this apply to bliss, and this release? Well, before, bliss would pad track numbers according to the highest numbered track in the album. For instance, if the highest numbered track was track 15, bliss would pad tracks 1-9 with one zero. In this new release, and as requested, you can now control the track number padding. Here's how the <tracknumber> token is now used in file organisation patterns:

Token	Use
`<tracknumber>`	The track number as-is in tags
`<tracknumber:nn>`	The track number, minimum two digits
`<tracknumber:nn>`	The track number, minimum three digits (and so on for any number of ns)
`<tracknumber:auto>`	The track number, leading zeros dependent on size of album

Note that the default behaviour of <tracknumber> changes from automatic padding to raw, as-is representation. When you run bliss for the first time with the new code your <tracknumber> will be automatically converted to <tracknumber:auto>

Acoustic fingerprinting

This release also contains the first batch of code surrounding bliss's mooted support for untagged music files. The enabling technology for this is acoustic fingerprinting, a way of representing a piece of music in a short summary. This fingerprint can then be looked up online and the discovered data used for tagging your music library.

There are two broad uses for this. The first, as introduced above, is with untagged music files. The second is in providing corrections for already tagged files. For now, I have introduced the technology into bliss's existing MusicBrainz queries for cover art, year and genre data. They are generally super-accurate and should, with time, provide higher match rates for missing information.

Other stuff:

I fixed some error messages displayed when cover art is corrupt
Any errors when parsing file organisation patterns are now caught and displayed
When albums are deferred from assessment the icon in the activity page changes to a completed one

Get the new release from the downloads page. Existing fixes apply, of course!

Thanks to mpcevat for the image above.

The Synology Diskstation and other platforms

2011-12-09T00:00:00+00:00

One of bliss's users, Nigel, recently wrote a HOWTO for installing bliss on the Synology Diskstation. A prepackaged version of bliss for the Synology Diskstation has been requested before so it was great to see a technically minded user finding the solution themselves.

It's not the first time bliss has been 'ported' to another interesting platform! Because bliss is written for the Java virtual machine it means bliss is likely to work wherever there's a Java VM available.

VortexBox was the first port to a different, interesting platform. VortexBox is a ripping, tagging, networked music jukebox. You buy one for your house, rip your CDs, store all your music on it, then use applications like Squeezebox Server and protocols like DAAP and DNLA to stream the music throughout your home. bliss is a good fit here because it's a server application that can work in the background installed on the VortexBox, fixing all those missing pieces of cover art and reducing inconsistencies.

The ReadyNAS integration was completed by Paul Hardy, who later wrote how to install bliss on the ReadyNAS. The ReadyNAS is a standard NAS but it can also be customised to run choice pieces of software.

I recently blogged Richard Rudd's work on installing bliss on Solaris 11. Solaris is a general purpose operating system with good support for Java. Once I had fixed a restriction which meant bliss wouldn't start on non-Linux, Windows or Mac operating systems (oops) it was fairly straightforward to get bliss working.

Similarly, Geoff Coupe pioneered installing bliss on Windows Home Server. Windows Home server is a server for your home - storing all of your photos, music, documents and everything else you have computerised. Again, because it's a server it fits bliss's always-on, in the background modus operandi.

I've also had contact from people trying to install bliss on Pandaboard and other ARM architectures. These are popular because they are very energy efficient, just right for powering your home server in these energy conscious times!

The common thread through all of these ports are that the target environment is that of a 'server'. What characterises server operation? First, there's no assumption that the user of the server is physically connected to the machine. Next, the server is likely to stay running for long periods at a time. Furthermore, because there's rarely a direct connection between user and machine, operations on the server are not necessarily directly invoked.

bliss was written to satisfy these types of concerns. First, its user interface is web based, which means it can be accessed across the network and you don't have to be connected to the machine it's running on. It works by reacting to changes in your music library, assessing your music to make sure it conforms to your rules. You can connect to it and ask it to perform changes, such as changing cover art, renaming albums, artists or genres, but it also works in the background, automating what is sensible.

I'm always willing to help with projects to port bliss to new and interesting platforms . Get in touch and let's get hacking!

Thanks to frankh and AMagill for the images above.

What's the best album art size?

2011-12-05T00:00:00+00:00

Your music collection's album art can be stored in a variety of sizes. With the new variety of devices with which you can listen to music, from tiny smart phones to enormous wide screen TVs, which size should you choose?

There are two points to consider: the size of your artwork, and its internal quality. These are different things. They are sometimes known together as resolution, but pixel and spatial resolution are separate concepts. This article will concentrate on pixel resolution, i.e. its size.

Historically the most common sizes for artwork have been 300x300 pixels and, laterly, 500x500. These are the sizes most music information databases store album artwork at. However, with newer, larger screen displays these images are beginning to look rather inadequate.

bliss offers the choice of album art size within its album art rule. It can assess all of your albums, to make sure their art is within these minimum and maximum size bounds, and even shrink or find new art automatically that is within these size constraints.

So which size should I choose?

But knowing you can resize your music is of no help in determining which size to aim for! The truth is, your target size should depend on the largest display you play music (and can visualise album art) through. Your target artwork size should be a function of the screen real estate available in your music players. Higher resolution music players mean higher resolution art. Here's a rough guide as to what sizes you should be aiming for:

Personal MP3 players e.g. iPod, smartphones - aim for small/medium size images of around 300x300 pixels. The higher resolution players are around 800 pixels in one dimension, so 300x300 leaves just under half the screen for the artwork.
Tablets e.g. iPad - Aim for medium/large images of 500x500 and larger.
Computer based software e.g. iTunes, Winamp - depending on the size of your player window, aim for medium/large images of 500x500 are larger.
Large TVs - Aim for large images of 900x900 pixels and larger. Again, this depends on the resolution of your TV's software and the screen real estate afforded to your artwork.

But what if you have many of these devices? A TV for browsing at home, a computer in your office and a smart phone for when you are out-and-about? The ideal solution is to aim for the largest resolution you need and use that. Well-behaved music player software should simply scale down any image to the player's size.

There's always a "but...."

Unfortunately, there are a couple of reasons why using the largest art and hoping your player resizes it may not work. First, some music players have constraints that prevent them from displaying any art over or under a given size. If you go for large art in the vain hope your smart phone will resize it, this may not happen. Your-mileage-may-vary, so consult your music player's documentation and online communities (or just give it a try!).

The second reason this might be undesirable is that the larger art will take up more storage space. This is most likely to affect portably devices with less storage space. Sure, storage is cheap, but bear in mind that this image, if embedded, will be duplicated multiplied by the number of tracks in each album. So, you may notice a difference.

If either of these limitations affect your music library one way around it, assuming you have plenty of storage in your home network, is to maintain separate copies of your music library for portable devices (which are more likely to be the players with the issue). You can also take advantage of converting lossless FLAC files to lossy compressed music to save further storage space.

I hope this article has helped you choose a size for your album art!

Thanks to daveynin for the image above.

New release - 20111125 - Disc number file organisation

2011-11-29T00:00:00+00:00

The main new feature this week is a new disc number token in file organisation patterns plus the ability to add conditional statements to file organisation patterns.

<discnumber> and file organisation conditionals

First up, if you like, you can just use the <discnumber> tag in a basic way:

 
<album name>/<discnumber>/...

In most cases though you probably only want to use <discnumber> when there is a DISCNUMBER tag. So you can use a new feature for file organisation patterns, a conditional:

<album name>/<discnumber>?|<discnumber>/|...

Which means: if <discnumber> is set, evaluate the subsequent pattern within the pipe ‘|’ characters. Meaning you get either All Things Music Pass/1/... or Thriller/...

You can put further tokens within the pipe characters if you like:

<album name>/<discnumber>?|Disc <discnumber>/|...

Would give All Things Music Pass/Disc 1/...

The conditional can be used with any token, not just <discnumber>. More generally, the conditional is evaluated such that when the preceeding token is set, the subsequent token is output. The tokens within the pipe characters are essentially grouped in one token.

Other stuff:

When using the track artist consolidation rule, if the track artist is inconsistent offer the album artist (e.g. 'Various') as an optional response
Fixed how some responses appeared in the Inbox
Fixed memory usage when rescanning
Fixed potential memory usage when losing connection to a music library (e.g. network connection lost)
Lowered memory use of the activity page UI
Fixed a couple of areas in the change art and album detail screen where you could get a 'no responder' error

Get the new release from the downloads page. Existing fixes apply, of course!

Thanks to _sarchi for the image above.