-Brading Software Message Board
+--Forum: Mp3/Tag Studio Support and Bug Reports
+---Topic: Adding Frame <TEXT> Corrupts Tag started by Skeezix
Posted by: Skeezix on July 04 2007,06:54
IIRC, mp3ts does not currently support <TEXT>. However, it is still included in the Browse/Edit Tags > Add New Frame list, and attempts to use it will corrupt the entire ID3v2 tag. Shouldn't it be removed from that list so the user won't blow away the tag if he (like me) tries to use that frame anyway?
Also, I see that clicking OKAY in the Add New Frame DB results in an immediate tag edit. Not sure that is the best way, since it allows the user to unknowingly corrupt the tag, resulting in a bad hair day.
Posted by: Magnus Brading on July 05 2007,11:01
Thanks for this bug report regarding the text tag, I will look into it further.
Does this mean that Mp3/Tag Studio cannot read the tag at all after you have tried to add a TEXT tag, or exactly how does this corruption manifest itself?
Posted by: Skeezix on July 07 2007,03:59
The War Dept. is on the rampage again, hafta run...
The error manifests itself... hmmm... don't know. However, MP3TS displays an error that the tag is corrupt. IIRC, the V2 tag is wiped out but the V1 tag remains.
Bye
Posted by: Skeezix on July 07 2007,07:36
Had a chance to work with this a bit and reproduced the problem this evening. It appears to be file-related, as I cannot reproduce it on all mp3s. The error is followed by an Invalid Pointer Operation message when I dismiss the original error message.
After verifying the problem, I copied the problem file to d: (it was on e: (2 different spindles). When I tried to verify the problem on the copy of the file, I added the BPM frame. The screen accepted my value input, then froze, then MP3TS died. No error message, just died as though I closed it. I opened MP3TS again and repeated the problem. You should be able to download it from the following link:
< http://home.bresnan.net/~pipsisiwah/various/ >
The file is a 4 MB file. Please let me know if you cannot access the file.
Posted by: Magnus Brading on July 10 2007,13:43
If it only happens for one file, it's 99% sure to be a pre-existing corruption in the ID2v2 tag of the specific file. I will try to still take an extra look at it when I've got some time later though.
end