|
Printable Version of Topic
-Brading Software Message Board +--Forum: Mp3/Tag Studio Support and Bug Reports +---Topic: Access Violation (3.5 Beta 16) started by BenignVanilla Posted by: BenignVanilla on Dec. 13 2005,18:23 I've had this problem for some time, but cannot narrow it down. I periodically run MTS against my library to clean up tags. I use the Auto Rename (from tags) for this. I receive the access violation in mp3tag_s.exe. If I navigate to the specific sub-folder and try the Auto Rename again, it'll work. If I got to the file and under Browse/Edit tags & flags, I can right click the file and it works. I am beginning to think this is a buffer size issue. It only seems to occur when I am working on a large directory structure. Anyone seen this? Posted by: Magnus Brading on Dec. 13 2005,22:00 You say "If I got to the file", but how do you know which exact file is causing it? Are you sure you are testing the right file? These are typical symptoms for corrupted ID3v2 tags anyway. Posted by: BenignVanilla on Dec. 13 2005,23:11 When running the rename, the status window is showing me the files it is working on. So for this error, no matter how many times, i run the rename, it fails on the same file every time. Does that make sense? What can I look for in the tag that may cause the problem? Is there a configuration in the application that I can set to have it ignore such issues and avoid crashing? Posted by: Magnus Brading on Dec. 13 2005,23:27 The problem is that the status display shows those messages after the files have been successfully processed, which means you will never see the actual crashing file in the status window, only the file being processed before it. Hence, try to find the offending file another way, for example by first processing half of the files in the folder, and if it doesn't crash then, you know that the file is in the other half. Now process half of the files in that half, and repeat. This way you will find the offending file quite quickly. Once found, note down the contents of its tag (it it's readable at all) and then completely remove the tag (e.g. with the mass set tool, only having this file in a the working dir), and then create a new tag for the file. This should solve the problem. Please let us know how it went, and maybe we can assist you more if there are further problems. Posted by: BenignVanilla on Dec. 14 2005,01:13 You are correct. I was misdiagnosing the bad file. I belive the problem had to do with an image in the tag, in an extended frame. I use iTunes to listen to music, so I wonder if it's writing something that mp3 Tag Studio cannot recognize or handle? Posted by: BenignVanilla on Dec. 14 2005,01:21 I just found another one. This time it was an additional frame that contained only a comment, so it's not the picture but something about the frame. I believe both frames were put there by iTunes. So it seems there is some incompatibility between iTunes and MP3 Tag Studio. Posted by: Magnus Brading on Dec. 14 2005,10:55 Mp3/Tag Studio is fully compatible with iTunes, so this should not be it. In situations like this the problem is most often not bound to a certain frame, but rather to abnormal corruption in some of the headers in the ID3v2 tag, either the frame headers or the main header. Please try my recommended method above for fixing the tag, and let me know how it goes. Posted by: calberga on Dec. 14 2005,13:49 Forgive me for jumping in here, but lately I have been having tagging failures on many files which are marked as having been encoded by iTunes. Usually there will be image tags in the files which Tag Studio doesn't like, and I go through the files and delete the oddball frames. It seems to be very common in iTunes files. [There are not (as far as I know) files FROM iTunes, but rather files created using iTunes, if that makes sense.] Posted by: BenignVanilla on Dec. 14 2005,15:50 Yes, I agree. The crashes of MP3 Studio are on the rise for me as I use iTunes more and more. Every crash I've had since posting this original thread, has been caused by an iTunes frame. I think maybe iTunes is doing something MP3 Studio is not expecting. For better or worse, iTunes is huge, so even if they are doing something wrong, we'll have to conform. Posted by: calberga on Dec. 14 2005,18:46 In fact, I rarely get a crash, just a refusal by Tag Studio to set a tag. As conforming, perhaps simply tolarating would be a better path, either ignoring the iTunes errors, or quietly (or with a request for permission) auto-magiclly deleating them. Posted by: BenignVanilla on Dec. 14 2005,19:08 Yes, sorry that is what I meant. I'd prefer if it MTS just ignored and reported the issue, but did not die when it hit the item. My library is gigantic, and I have become dependant on this tool. LOL. The crashes make it difficult to use. Posted by: Magnus Brading on Dec. 14 2005,20:03 Could you both please send a sample file to me that causes this problem, and I will take a closer look at it. Posted by: Cyril N. Alberga on Dec. 16 2005,23:01 This may not be quite the same, it doesn't seem to be an iTunes encoding, but it has the property that when I try to set, say the Genre tag Mp3/tap Studio simply closes. I found the original files still on a server, I had, as I've had to do more often of late, dumped all the tag values that I thought were useful into a list file, along with the file names. I then removed all the tags from the files and retagged them from the list. I'll look farther for a real iTunes case. File being sent seperately Cyril end |