|
Printable Version of Topic
-Brading Software Message Board +--Forum: Mp3/Tag Studio Support and Bug Reports +---Topic: Rare problem with mass set started by calberga Posted by: calberga on Sep. 11 2003,03:16 On two or three occasions when I use mass-set all or most of the tags not selected for setting are blanked out. As I say, this has only happened a few times, and "undo" as saved me, but it is a bit disconcerting. I haven't figured out any pattern to this (it is too rare), so I can't help in isolating the bug. Has anyone else seen this? Posted by: Magnus Brading on Sep. 12 2003,00:27 I have never had anything like this reported before anyway. Does it happen every time on the same file, or if you have two copies of a certain file, can it work on one of the copies but not the other (very unlikely)? Otherwise please send me a file for which this happens (in the states both before and after it happens) and I will analyze it. It might also be some problem with the original tag of the file causing such a thing. also, be sure to check that it's not just some kind of ID3v1/v2 sync problem. Posted by: calberga on Sep. 12 2003,03:10 I'll try, but it may be a month or more before it manifests again. The only bother is having to keep copies of everything, in order to have before and after examples! Posted by: calberga on Sep. 15 2003,16:22 Okay, I've got an example. Download: < http://members.bellatlantic.net/~calberga/Example.zip > Then do a Mass-Set of the composer. All the other fields go blank, at least on my machine. I'm running 3.05 on Win98SE Let me know when you download so I can delete the zip file from my space. Cyril Cyril Posted by: Magnus Brading on Sep. 16 2003,17:29 Just as I expected, this file contains unsynced v1/v2 tags, and the v2 tag info is almost blank. The problem with this is that when the program is set to write to both tag versions (default), data will be read from the primary tag version (v2 is default), which in this case is almost empty, then modify it with the new data (the composer field in this case) and then write it back to both tags. This will cause some of the non-blank v1 fields to be overwritten by the equivalent blank fields of the v2 tag, all according to settings. To prevent unwanted effects like this, always try to sync the tags of mp3:s with largely different data between its tag versions, before performing tagging operations on them. Posted by: calberga on Sep. 16 2003,22:57 Thank you. I must say I never noticed the little warning at the top of the display. So, what is the best way of handling this? (Note, it isn't my mp3 file, so I must start with that I have.) Is the "Direct manipulation" machinery best? Or is there a simple operation which will do a reasonable job of distributing the information around? Posted by: Magnus Brading on Sep. 17 2003,01:08 The problem is that when there is info in both the v1 and the v2 tag, but only one of them is correct, there is no way for the program to know which information is correct and which one is not, so you can practically only fix this manually with the browse tool (just make sure it is set to write to both tag versions, and there should be no problem). If several files have the same pattern of correct and incorrect information in their tags, you can use the Direct tag manipulation tool on all of them, that is correct. But remember, it is only when there is both a v1 tag and v2 tag containing different info (i.e. unsynced) that this is a problem, not when only one of them exist, or when they are in sync, which is mostly the case. end |