-Brading Software Message Board
+--Forum: Mp3/Tag Studio Support and Bug Reports
+---Topic: Bug in "Auto Rename (from Tags)"? started by Jens Vogel
Posted by: Jens Vogel on June 06 2004,14:30
Hi!
I don't know whether this is a bug or whether I just overlooked a setting.
When doing "Auto Rename (from Tags)" and using the <Album> tag as a source, Mp3TagStudio just drops one zero if there are numbers like "001" in the string.
Example: An Album is named "Symphony No. 009" (three numbers are necessary for reasons of sorting because there are more than 99 symphonies). Now, if I'm doing an auto rename from tags, Mp3TagStudio names the Files "Symphony No. 09" instead of "Symphony No. 009". To my knowledge this doesn't happen when "Symphony No. 009" is stored in the <title> tag and the <title> tag is used for renaming.
Is this a bug or is this a feature? :-)
Bye,
Jens
Posted by: Jens Vogel on June 06 2004,14:33
Sorry, I made a mistake in the Topic description - it must read "drops one zero when using <album> field", of course.
Jens
Posted by: just on June 06 2004,14:46
Oh my.
I guess I must seem like an idiot right now - I can't reproduce the problem. It's just gone. Maybe I just made some stupid mistake while tagging the files. Embarrassing!
Sorry for the confusion and the inconvenience and for wasting your time!! What do they say... "errare humanum est".
Bye,
Jens
Posted by: Magnus Brading on June 06 2004,17:40
Ok, I'm glad it worked out anyway.
Just so you know, you can use the "Zero-pad track numbers to length" feature in the "General tagging and renaming" section of the global settings to force a certain number of digits to all track numbers you handle.
Posted by: Number 6 on June 27 2004,03:35
I encountered a different problem. My tags are clean in both V1 and V2 fields, I have the settings set to ignore padding, my field chosen was <Title>, and every file renamed with an extra "T" at the end--e.g., CCR's "Fortunate Son" became Fortunate SonT.mp3 -- very odd. Any thoughts anyone?
Posted by: Magnus Brading on June 27 2004,20:00
Yes, this bug has been submitted before, and it will be fixed. It has to do with the fact that the tags for which this happens are Unicode-encoded, which has been very uncommon in tags this far, seems like there has been a little increase in this lately though. It would be great if you could send me a sample file for which this happens, just to be sure (in the state it is before Mp3/Tag Studio has tagged it).
end