In my case disc 1, track 1 file would start as "101 - rest of filename.ext" . However you roll your own, having the means to add the disc number is a must for me.

Jim!

Sure, I understand. Some albums have different cover art for each disk, plus you might just prefer it that way.

Discnumber would be just another token, so you could ignore it, use it on its own for its own folder, or use it with other tokens for a track name. e.g:

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

Would be your way @RBoatright while

<album_artist>/<album name>/<discnumber>-<tracknumber>-...

Would be another.

Another question would be... what to do in the event of no discnumber being available?

on the other hand, I -strongly- prefer that multi-disk albums be sorted into folders which are for EACH disk, and I prefer to see the cover with a tag for disk 1, 2 and 3.

In my MANUAL arrangement of my files, I typically do

I prefer this to the D1-01-song1 , D1-02-Song2, D2-01-Song1 scheme. I find it confusing to read. :-(

so, if you choose to implement this, please allow for a good bit of flexibility.

Nat_King_Cole /
... Unforgettable /
... ... Disk 1 / - - - songs
... ... Disk 2 / - - - songs
... ... Disk 3 / - - - songs

S

This is very important for multi-disc albums, I hate to see the cover art twice when I scroll albums, it's a two disc album not two separate albums.

Yes, the case when these tags don't exist can be tricky. A quick fix would be to use "<disknumber><tracknumber> - <tracktitle>", and <disknumber> would expand to an empty string when not present. That way the files would be sorted correctly, which is what I want.

My opinion is that if one uses different album tags, the tracks should go to separate folders, so no special handling should be needed in this case. If one uses separate folders *and* disknumber tags, then one could just opt to not use the <disknumber> in the file name template.

In any case I would leave all the defaults as they are. Just add the <disknumber> tag so that people who like to store multiple CDs in one directory can use it in the file name template.

As stated above, it would be good if <disknumber> expanded to an empty string if the tag is not present.

Yes, the case when these tags don't exist can be tricky. A quick fix would be to use "<disknumber><tracknumber> - <tracktitle>", and <disknumber> would expand to an empty string when not present. That way the files would be sorted correctly, which is what I want.

My opinion is that if one uses different album tags, the tracks should go to separate folders, so no special handling should be needed in this case. If one uses separate folders *and* disknumber tags, then one could just opt to not use the <disknumber> in the file name template.

In any case I would leave all the defaults as they are. Just add the <disknumber> tag so that people who like to store multiple CDs in one directory can use it in the file name template.

As stated above, it would be good if <disknumber> expanded to an empty string if the tag is not present.

Gotcha. bliss could work off the 'discnumber' tag. However, these tags aren't always available. Sometimes, people have the disc number in the album tag, e.g. "All Things Must Pass (Disk II)". So, in that case, the album name would have to be correctly interpreted too.

I think the first step would be to implement with the disknumber tag, is this acceptable to you?

On a related note, I think that bliss determines the number of leading zeros for <tracknumber> from the number of files in the directory and not from the maximum track number in the ID3 Tags. I think this should also be changed.

Forgot to note that this info should be easy to get from the ID3-Tags. And of course, if the CD number is empty, <cdnumber> should expand to an empty string. Thus, a format like this would be feasible <cdnumber><tracknumber> - <track name>