Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jgourd]

I complained about this once before. If you have an album with more than 100 tracks (Audiobook, sound effects, etc...) and you use the rename files from properties feature it only pads the zeros as if there was no such a thing as a three digit track number.

For instance, an audiobook with 150 files needs to pad two zeros in the track number. 001, 002, ... 011, 012 etc.

[Alex B]

The problem is not limited to audio files. For example, image collections may need more numbers than 100.

A previous discussion:

http://yabb.jriver.com/interact/index.php?topic=27807.0

Besides the add "n" number zero padding option I requested in that thread I would like to be able to add user defined fields that work exactly like the Track Number field including the automatic numbering. Then it would be possible to use alternative numbering systems without changing the existing track numbers.

[Matt]

We need to make this easier, but you can workaround this now by using an expression:

This will show the track number always using three digits:
If(IsEqual([Track #], 10, 3), 00[Track #], If(IsEqual([Track #], 100, 3), 0[Track #], [Track #]))

A simple function like PadNumber([Track #], 3) or something would help.

[Matt]

Build 164 and later adds this:

NEW: Added a function PadNumber(...) to allow forcing numbers to a certain number of digits. (for example, when renaming, use PadNumber([Track #], 3) to get 001, 002, 003, etc.)