Control zero padding for track number in file names
The <tracknumber> token currently reads the track number tag for a music file, and uses it verbatim for the expected file path. This means if the tag says '1' it will use '1', or if '01' it will use '01'.
Additionally, if the tracks in an album number greater than nine, then bliss will also add an automatic padding of one zero to all single digit tracks.
This idea would allow users to specify they always want a minimum number of zeroes padding in their filenames, so even if there's, say, an EP of six tracks the numbering would be 01, 02, 03 and so on.
This feature is now released, as per http://www.blisshq.com/music-library-management-blog/2011/12/14/new-release-20111206-padding-file-org-acoustic-fingerprints/index.html
The <tracknumber> token changes to behave as follows:
<tracknumber> : The track number as-is
<tracknumber:n> : The track number, minimum one digit
<tracknumber:nn> : The track number, minimum two digits (etc for any number of "n"s)
<tracknumber:auto> : The track number, leading zeros dependent on size of album
Because the old behaviour of <tracknumber> was the same as <tracknumber:auto>, your settings will be updated to the latter.
-
Derek Smith commented
Yep, no problem to merge this.
-
The problem is that zero padding cannot be controlled for the file organisation yet. See http://ideas.blisshq.com/forums/21939-bliss/suggestions/1848929-control-zero-padding-for-track-number-in-file-name
Note the point about zero padding - currently in the file org rule it determines its own zero padding depending on how many tracks are in the album. This is why it tries to remove padding for albums with < 10 tracks.
Is it ok if I merge this idea into the idea above? This will add a vote and make it more likely to get fixed quicker.
-
Gregor commented
I think this important. On some CD's I didn't store all tracks and I want to keep the correct track numbering
01 .......10, 11, etc. If I delete some tracks an the total amount of files is less than 10 the numbering is not correct anymore....