Organising multi-disc album files

Old media 2

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:

<album artist>/<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:

<album artist>/<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:

Explorer, before

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

Organize 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:

File pattern setting

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'.

Apply rules

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'.

Non-compliant file path assessment

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

Non-compliant file path detail

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.

Fix all files button

The albums now show up as compliant.

Compliant file path after moving files

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

Explorer, after

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.
tags: files and folders files multi disc

The Music Library Management blog

Dan Gravell

I'm Dan, the founder and programmer of bliss. I write bliss to solve my own problems with my digital music collection.