-Brading Software Message Board
+--Forum: Mp3/Tag Studio Support and Bug Reports
+---Topic: Access Violation started by Vern Erickson
Posted by: Vern Erickson on Nov. 18 2002,12:20
verickson@sympatico.ca
Every time I try to use "mp3 tag studio" to auto-write tags
based on filnenames in a certain directory, the software gets
to 59% of the way through the directory then stops cold. A
box with the following message comes up "Access violation at
address 00474459 in module mp3tag_s.exe Read of address
582ACAD8". This message might as well have been in Greek!
Assuming that the "offending" mp3 file was the last one on the
list (where it stopped) I deleted that file from the directory
and tried again. The software still stopped at 59% but at the
next file it came to. It did so even after I deleted 4 or 5 files.
What can I do to complete the auto-writing of that directory?verickson@sympatico.ca
Posted by: Magnus Brading on Nov. 18 2002,15:06
The offending file would be the one processed after the last one listed in the status window.
But if you use the "Custom file selection mode" it is very easy to see which file that is, because in this mode the files are processed in the order listed in the custom file selection list. Simply select all the files and press execute, and when it crashes, look what file is listed in the custom file selection list after the last one that was mentioned in the status window.
When you have isolated the offending file, you can mail it to me, and I will analyze the problem.
Posted by: Magnus Brading on Nov. 22 2002,15:34
I have analyzed the files you sent me. They contained corrupt ID3v2 headers, having the "extended header" flag set, but no extended header was present. This caused arbitrary data to be interpreted as pointers, which in turn caused the crash.
Even though these files are clearly corrupt, I have now modified Mp3/Tag Studio to handle such tags gracefully (no crash, but no ID3v2 tag data will be shown for it). It will no longer crash in the next update.
Posted by: thei on Nov. 25 2002,12:31
Hello, this might be related...
I have found certain (very common) ripping and encoding programs add corrupt ID3v2 data, which will display and play in Winamp, but says no ID3v2 tag present in tag studio and "This file is not a valid mp3 audio file" in many other non-Winamp players. Totally removing all ID3v2 tags fixes the problem. I have had tag studio and certain players crash attempting to write to these files.
Also, tag studio will freeze if attempting to write to a drive which is full during repair mp3 mode, or updating tags and coming across a file which is read-only (i.e. being played at the time).
Just in case that's any help
Posted by: Magnus Brading on Nov. 25 2002,14:22
Thei, you are very welcome to mail me a sample of such an mp3 file (with the corrupt ID3v2 tag problem), and I'll analyze it and see what I can do.
Posted by: thei on Nov. 25 2002,14:37
I think I fixed them all
You're program made it too easy for me to fix them.... sorry.
Posted by: Magnus Brading on Nov. 25 2002,14:42
I hate when that happens...
end