# \[X\] Problem with leading zeros in the TRACK tag

**URL:** https://community.mp3tag.de/t/x-problem-with-leading-zeros-in-the-track-tag/12964
**Category:** No Bugs
**Created:** [January 20, 2012, 12:07am UTC](https://community.mp3tag.de/t/x-problem-with-leading-zeros-in-the-track-tag/12964 "2012-01-20T00:07:59Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![DetlevD](https://community.mp3tag.de/user_avatar/community.mp3tag.de/detlevd/32/123_2.png) [@DetlevD](https://community.mp3tag.de/u/DetlevD)
#### Post date: [January 20, 2012, 12:43pm UTC](https://community.mp3tag.de/t/x-problem-with-leading-zeros-in-the-track-tag/12964/4 "2012-01-20T12:43:59Z")

</div>

> [@LikeYourStyle](#):
>
> ... This was producing a 3 digit track with leading zeros and Windows explorer was misinterpreting most numbers between 010 to 077 as hex (as you said). ...

No, I did not say hexadecimal, but **octal**.  
[http://en.wikipedia.org/wiki/Octal](http://en.wikipedia.org/wiki/Octal)

> [@LikeYourStyle](#):
>
> ... The simple solution was to set up a new transformation for use with numbers 010 to 099.  
> %artist% - %album% . **0** %track%.%title%  
> This transformation generates 2 digit track numbers by ignoring the leading zero and so avoids the problem with Hex numbers (which I have also seen in some Android apps).

Ok, this is one way to go, but needs to do it by two filtered steps.  
Another way to go would be to modify the tag-field TRACK, after importing the number string having the leading zero, by an action "Format value" using the format string: $num(%TRACK%,1).

DD.20120120.1444.CET

---

_[View the full topic](https://community.mp3tag.de/t/x-problem-with-leading-zeros-in-the-track-tag/12964)._