-Brading Software Message Board
+--Forum: Mp3/Tag Studio Support and Bug Reports
+---Topic: access violation error started by Disposable Hero
Posted by: Disposable Hero on Dec. 02 2003,21:40
OK, every now and then I have run into access violations with mp3tag_s.exe, but never figured out the exact problem. Usually I'm in a hurry and not paying attention, and the files which cause it get modified despite the error, so I never figured out why it occurred. But I think I am closer, after having seen the pattern.
The errors always occur when applying changes in Browse/Edit mode to files which only have ID3 v1 tags. If I quit and restart MP3TS, then sync v1 and v2 tags manually on the offending file, everything works fine for all tagging ops to that file. So it appears to be something about certain v1-only files that disagrees with MP3TS.
I wish I knew the commonality between v1-only files which do not work, and what distinguishes them from v1-only files which process with no problem. If I run into the issue again, I will make copies of the problem files for your comparison and examination, Magnus. That will be my Christmas present to you
Posted by: Magnus Brading on Dec. 03 2003,01:05
I just tried the files you sent me, but could not reproduce it.
I first tried to edit the tags (the title field, but it should not make any difference which field it is anyway) and then write the tag to the file. I did it with all the files, in order, and nothing went wrong. This was with the "Write to both" setting.I then tried the same thing with the all the other write settings (v1/v2/existent) and still everything went just fine.
Any ideas for other methods to reproduce it?
Posted by: Disposable Hero on Dec. 03 2003,02:36
Weird. When I had problems, I was also using Write To Both, Detailed Info, and Advanced v2 Info. With those files, errors occured when I tried to set a new genre (Techno). Dunno what to say
Posted by: Magnus Brading on Dec. 03 2003,03:52
Ah, it was the "Advanced ID3v2 info" combined with the v1-only tag files (combined with a forgotten line of code during an earlier update
) that did it!It's fixed now, and hence, the problem will be gone in the next release.
Thanks for the report, as always!
Posted by: Disposable Hero on Dec. 03 2003,04:22
Sweet! Glad I could help out a bit.
end