-Brading Software Message Board
+--Forum: Mp3/Tag Studio Support and Bug Reports
+---Topic: Track # tags v. Filenames started by tHiNkBoNe
Posted by: tHiNkBoNe on Mar. 21 2005,16:52
Dilemma:
Track number tags are basically numeric tags (although stored as text). They are set in my MP3TS setup as Zero-pad to length: 0. Works great for the tags, so all of my media players show the tags correctly
However, this one global setting also affects how files are renamed, so when I use the rename capability all of my files, which include track numbers get the same setting. Naturally Windows gets confused by something as trivial as numbers in filenames and places tracks 10,11, and 12 etc. next to track 1 and before track 2 etc. 
Changing the global setting to provide decent Zero padding for the filenames, b0rks the track # tags whenever a tag operation is performd How can I set no padding for the track tag operations, yet set zero padding for the filename operations. Switching back to global settings every time, is making my head spin... There has to be a better way. What is it?
Posted by: devNull on Mar. 22 2005,10:00
Record a separate macro for each of the operations. Macros
have their own settings, so you can add zero-padding to the
file rename macro, and keep the padding at 0 for the retagging
macro.
Of course, the best solution is to stop using Windoze Exploder,
install Total Commander, and in the settings make it sort filenames
with numbers as they should be sorted - numerically.
devNull
Posted by: Magnus Brading on Mar. 28 2005,11:38
First of all, Windows XP (SP1 and above) uses numerical sorting for filenames with numbers in them, so if you use this operating system version you won't have this problem at all.
And thanks for the reply devNull, but global settings are actually not stored in the macros, only filter and casefix/replace settings are, so this macro solution will not work in this case.
In any case, separate zero padding settings for renaming and tagging have already been suggested here on the board recently, and it is already on the todo list for implementation, so stay tuned.
end