I am a huge fan of mp3tag, so first off many thanks! I think I have found a bug in the renumbering of a large set of tracks. I attempted to renumber a set of 121 tracks (from 001 to 121) and it appeared to have worked fine in mp3tag. However, when I closed mp3tag and looked at the files in File E…

From a MS forum (I can't directly link to it): It is the 7th reply in this thread [image] See also: [image] track numbers differ between mp3tag and w7 Support For some reason, Windows Explorer interprets track numbers with leading zeros as octal numbers instead of deci…

[image] HarrisMan: I think I have found a bug in the renumbering of a large set of tracks. If the files show correctly in MP3tag but the [image] HarrisMan: File Explorer (Windows 11) does not treat them correctly, I would think it is a bug in the Windows Explorer. See here: …

I don't think the problem is in Explorer, because when I renumber only 99 tracks in mp3tag they do appear correctly in Explorer. Therefore I suspect that when I renumbered all 121 in a single pass the new numbers (001 to 121) were not being written correctly to the mp3 files even though they appear…

[image] HarrisMan: I don't think the problem is in Explorer, Apparently, you did not go through the linked thread as that already describes your observation and the cause for it: WIndows Explorers interpretation of values with 3 digits and leading zeros as octal values. If you take care that…

The CD Redbook stipulates that no disc can have more than 99 distinct tracks. So the idea of going beyond that when recognizing track numbers shouldn't typically be a problem. But as far as creating digital albums of some sort, this could be an issue for some interfaces. Windows has a documented is…

That is not the issue. The track numbers reported by Explorer appear to be simply wrong. If I create track numbers from 001 to 121 in batches then they come out correct, but if I try to create them in a single operation they are wrong. This cannot surely be an issue to do with octal representation:…

Do you have any proof execpt the display in the Windows Explorer? Have you checked a file that appears out of order with a hex editor to see what is stored in TRCK? A simple test: [grafik] and the same files with 3-digit-numbers and leading zeros, [grafik] where the second dump shows 2x8 and 2…

Maybe this is too complex for me to understand, but I would point out that I don't think this is to do with sorting - the track numbers shown by Explorer are not the same as those shown in mp3tag. I simply want to be able to select all my 131 tracks in mp3tag and give them track numbers 001 to 131…

Leave ot the leading zeros and you should be fine.

Thanks, I'll try that but I'm definitely baffled as to why there is a problem. I always use leading zeros in my track numbers and have never had a problem before, but in fairness I've never had more than 100 tracks before. And it does work fine with 99 tracks, so I'm baffled!

Please address your astonishment at Microsoft. What you see is a Microsoft problem, no MP3tag problem. You do not need leading zeros in a decent player - if you want to create filenames with leading zeros, you can use $num(%track%,3) instead of the plain %track%. The Windows Explorer has not proble…