hc Posted Feb 15, 2012, 6:56 pm	If the command line is used to set some tags, then TLEN is erased, COMM assumes English language, and TRCK is stripped from any leading zero. After installing ID3Editor in Windows x64, if the track number (TRCK) had a leading zero (e.g. 07) then windows explorer displays only zero (instead of "7" as before the installation).
jamesrae Posted Feb 16, 2012, 8:58 am	The TLEN field was considered depreciated and thus we do not support it. If you would like it to be supported, please contact support and it could be added to the next update or release. As only one COMM is currently supported the language is of little use, but we are intending to offer multi-comment support which will then require the need to specify the language. ID3 Editor uses a number for the track and thus no leading zero. This is certainly an option we could add though. With regards to the Windows issue, could you contact support with an image of this so that we can investigate. Could you also state if the shell extension is used.
hc Posted Feb 16, 2012, 9:30 am	jamesrae said: With regards to the Windows issue, could you contact support with an image of this so that we can investigate. Could you also state if the shell extension is used. Yes, the shell extension was used. As for a picture showing the Windows issue, it will just show a zero for files that were tagged (by another program) with a leading zero in the track-number column. Files tagged by ID3Editor will show just fine. Except for the Windows issue, none of the other issues are deal breakers. Even the Windows issue is not a big deal for me since I plan to use ID3Editor in a batch file to re-tag all of my library (that is the reason I am testing carefully before I commit).
jamesrae Posted Feb 16, 2012, 12:11 pm	The leading zero is not an issue we have had reported before so we will need to investigate why the extension is showing a zero. Would it be possible to send a copy of the track so that we can be sure it is not an issue in the tag.
hc Posted Feb 17, 2012, 2:09 pm	I used the tagging switches of lame 3.99.4 (64 bit version). Encode any tag with the latest lame and use the shell extension in Windows 7 64 bits to reproduce the behavior.
jamesrae Posted Feb 17, 2012, 5:41 pm	Does this always happen as we have been testing tracks with one or more leading zeros with and without the track count and even tracks created with Lame, but we always get the correct track number in the shell extension under Windows 7 x64.