![]() This MAY be extended with a "/" character and a numeric The 'Track number/Position in set' frame is a numeric stringĬontaining the order number of the audio-file on its original The ID3 standard for ID3v2.3 and ID3v2.4 says: number strings (!), which contain only digits from 0 to 7 and begin with 0, are interpreted as octal numbers by the other software. The problem seems not related to Mp3tag but to other software on the target system. ![]() It is clear to me that this leading zero in the actual tagged field is causing problems with the algorithm that windows uses to "calculate" the track numbers.For info, I am running Windows 7 Ultimate 64 bit. If I remove the leading zero by editing the file name, it solves the problem but that will cause my files to be displayed in the wrong order. So, Windows is interpreting tag 030 as 24 and tag 031 as 25. However, when I view these resulting tagged files in Windows Explorer and Windows Media Player the above track numbers are shown as 28, 29, 24, 25. mp3tag creates ID3v2.3 tags with a track of 028, 029, 030, 031 etc. I am creating a set of audio files with 3 digit track numbers in the file names. Is it possible for you to strip leading blanks when converting the track number in the file name into the TRACK tag so that they are actually stored as 28, 29, 30 and 31.įor info, I am running Windows 7 Ultimate 64 bit. It is clear to me that this leading zero in the actual tagged field is causing problems with the algorithm that windows uses to "calculate" the track numbers. I can also solve the problem by manually removing the leading zero in mp3tag after the filename has been converted into tags but that does away with a lot of the benefit of your very good Filename to Tag utility. ![]() So far I have files with track numbers in the range 001 to 053 and it appears that 001 to 009 work fine but after that the only track tags that Windows interprets correctly are 018, 019, 028, 029, 038, 039 & 048, 049. ![]() So, Windows is interpreting tag 030 as 24 and tag 031 as 25 Mp3tag creates ID3v2.3 tags with a track of 028, 029, 030, 031 etc. FIX: installer did not default to English for unsupported languages.ĭownload: Mp3tag 2.82 | 3.Firstly.FIX: preserving the file modification date on write operations resulted in an 1h offset of the file creation date if daylight saving time status was different.FIX: renaming directories via action 'Format value' also affected files where the folder path contained the renamed directory string.FIX: removed DATE from list of default tag field names.CHG: updated Opus to version 1.1.4 and Opusfile to 0.7.FIX: scripting functions $meta(x), $meta(x,n) and $meta_sep(x,sep) did not create matches in square bracket notion.FIX: unicode characters in filenames where not supported when exporting configuration to zip file.CHG: removed associate tag from web sources.FIX: some actions allowed to create empty tag fields for certain tag formats.FIX: removed text-length limitation from track number field at tag panel.FIX: auto-numbering wizard did not consider track-number offset when determining amount of leading zeros.FIX: after closing the filter window via the x symbol, focus was still on the now invisible filter window.FIX: mp4 atoms with errorneous data size descriptors were not detected.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |