I mostly do not check whether the numbering created by MP3Tag also shows correctly in the Windows folder but accidently I stumbled on a difference.
First I thought just clear the numbers and redo them but the problem persists.
The numbering set by MP3Tag displays correct in the tool itself but when looking at the folder content the Number is sometimes different. They are all MP3.
I added screen prints of it. Any idea what is happening here?
I use version 3.33.1
Yes: it is the leading zeros that upset the WIndows explorer which interpret the numbers now as octal values - a problem that has not been corrected for ages, see e.g. here:
So you are saying this is a Windows problem?
In this folder there are 2000 mp3s so that is why it becomes four digits when using Auto-numbering option with leading zeros switched on.
Is there a way to get around this?
I’ve tested it too and it’s definitely a Windows problem, basically unavoidable for any official releases with 100 tracks or more.
Only other way around it is sub-dividing releases into other folders, like CD’s or Part 1-10 or for folders with less organisation, more folders with specific genres, artists etc.
Keep in mind the CD Redbook standard limits the number of separate tracks on a CD to 99. So in theory the 3+ digits that Windows interprets as Octal should not typically occur in a typical album folder.
Ultimately it is only a Windows display issue. If that doesn't affect your library or player software then just ignore it.
Yes. You have to omit leading zeros.
Do not use leading zeros at all.
The TRACk field is supposed to be numeric anyway (with the exception of the separating slash) so any decent player should sort TRACK as a number.
If you like to see the leading numbers in the filename, then use $num(%track%,4) instead of a simple %track% when writing new filenames with Convert>Tag-Filename.
Using $num(%track%,4) is a good suggestion! In that way I will still get a proper file name/
Windows having this problem you wonder why the option of leading zeros is there?
Because Windows is not the navel of the world?
BTW: MP4 tags do not accept leading zeros at all.
No I meant why MP3tag has this option? If you can set the track number in the file name in the $num(%track%,4) way I do not see why MP3tag offers this option? Just out of curiosity.
Many do not care what Windows shows as it doesn't affect how their library manager or player programs work.
A feature request?, See e.g. here:
and as it is not forbidden and most other players can cope with it and only Microsoft has refused to iron out the strange interpretation of track numbers being octal values, I see no harm.
Yes MS has a mind of its own……… 
I have switched the option off and now everything displays fine.
