allowing single digit tracks to be stored as two digits
I would like my track numbers stored in two digits. For example I would prefer track #2 to be renamed and stored as track #02.
This applies to tags, not filenames.
 Matthew
    
 shared this idea
Matthew
    
 shared this idea
      
    This feature has now been released:
The rule is called ‘Track number length at least’ and there are four settings: ignore, auto, two digits and three digits.
‘Auto’ will work the same as the file compliance stuff – it will depend on the number of tracks in an album already. If more than nine and less than one hundred, it will be one leading zero, for instance.
- 
      Great, well I'll be waiting for your further feedback then! :-) 
- 
       Miles Willcod
    
 commented Miles Willcod
    
 commentedI like this lots, nice one Dan. 
- 
       Miles Willcod
    
 commented Miles Willcod
    
 commentedAwesome! Yes for tags - Squeezserver reads the tags and is rubbish when you have 10 tracks and single digit tags for 0-9. Thank you! 
- 
      Ahhh... I think I misunderstood before. This is for _tags_ not filenames. This all makes more sense now... 
- 
       Miles Willcod
    
 commented Miles Willcod
    
 commentedIf we could set this up as a rule that would be ace, as unfortunately I find Squeezeserver puts track 11 after track 1 (i.e. behind 2, but not behind 02). 
- 
      No, not yet, that would be the new feature I think. 
- 
       Philippe
    
 commented Philippe
    
 commentedAnd can't we specify another syntax to force starting with 0 even if there is less than 10 tracks? 
- 
      Ok, bliss should already store in two digits, if there are between ten and ninety-nine tracks in the album. Maybe this album has fewer than ten tracks, and we need bliss to have a blanket minimum number of 'padding' zeroes regardless of the number of tracks in an album? 
