|
Printable Version of Topic
-Brading Software Message Board +--Forum: Mp3/Tag Studio Support and Bug Reports +---Topic: Non-convertable frames -- How do I identify? started by calberga Posted by: calberga on Aug. 04 2004,03:32 I have a number (serveral hundred) mp3 files which mp3/tag studio will no write to. The error message I receive is: ID3v2 tag is of non-directly-supported version and contains frames that cannot be converted. You must remove these frames before being able to write to this tag (you can do this from the "Advanced ID3v2 info" window). I see a number of frames in that window including (not the same on every file) Custom text frame Part of a set Attached picture and additional "Comment" frames which do not display in the main window. I am assuming that one or more of these are the frames which must be removed, but short of experimenting, how do I tell which are which? Additionally, the files contain ONLY ID3v2 frames. Must I explicitly set each v1 frame using the "Direct Tap Manupulation" tool? Cyril Posted by: Magnus Brading on Aug. 05 2004,00:04 There is currently no direct way of getting the program to tell you which frame is the problem, but just try and remove one at them time, and once you find which one it is it will most likely be the same for most of the files. About your last question, ID3v1 tags do not contain frames, my guess is that the problematic tags contain ID3v2.2 or ID3v2.4 tags, whose frames must be converted before they are written with Mp3/Tag Studio, and that some of these are the problem. In that case you can transfer the info to other working frames with the "Direct tag manipulation" tool, yes. Posted by: calberga on Aug. 05 2004,04:33 Thanks, I'll make copies and play with them. Cyril Posted by: calberga on Aug. 05 2004,04:48 Well, it seems to be the frame for the "Picture" tag that is giving the trouble. Another program, Mp3 Tag Tools v1.2, will display the picture, and I've had other files with pictures which haven't caused any problems. The files were created and tagged by iTunes v 4.6, if that is of any interest. They were posted from Japan. Any further ideas? Cyril Posted by: calberga on Aug. 05 2004,04:51 One final (well, don't bet on it) datum. One set of the files in question was posted on the second, so it should be still on most servers. The subject line starts "A Century of Song - ", and it was cross posted to alt.binaries.sounds.mp3.folk, a.b.s.m.celtic and a.b.s.m.world-music. CNA Posted by: calberga on Aug. 05 2004,04:54 Told you not to bet! File number 4 is an example with the tag, picture, in question. CNA Posted by: Magnus Brading on Aug. 06 2004,01:12 I currently don't have access to those newsgroups, but could you check what version the v2 tags are (from the "Advanced ID3v2 info" window of the Browse tool in Mp3/Tag Studio)? I would guess that they are 2.4? Could you mail me a sample of those files, so that I can analyze it? Posted by: calberga on Aug. 06 2004,14:30 I would swear that I posted this last night -- but here it is (again?). The version 2.2.0, and I have an example of just over 1 meg. Do you want it e-mailed as a single chunk, or should I split it up (using hjsplit)? Cyril Posted by: Magnus Brading on Aug. 06 2004,20:15 You can mail it in one chunk, but the 2.2 version number confirms my suspicions too. This is an older tag version that's practically not used anymore, and all frame types of it cannot be directly converted to ID3v2.3 tags. Are you really sure that iTunes wrote those old type tags? Sounds quite strange... Posted by: calberga on Aug. 06 2004,21:40 The files are tagged "Encoded by" with value "iTunes v4.6", and I exchangened notes on the newsgroup with the poster (to see if I could clear this up without bothering you), who repeated the claim. As I said, he is in Japan, if that sheds any light on the issue. Also, you will note that only the v2 tags are set. Cyril PS, I'll mail the file in a short while. CNA Posted by: Magnus Brading on Aug. 06 2004,22:34 Thanks for the file. I've taken a look at it, and as we earlier concluded, it was the picture frame of the ID3v2.2 tag that was the problem. Removing it solves the problem. And it might be the case that whatever program wrote that tag did it after iTunes encoded it, but kept the encoding information, although downgrading the ID3v2 tag version. Please encourage all software vendors you find using the old ID3v2.2 standard to upgrade to using at least ID3v2.3. Posted by: calberga on Aug. 07 2004,01:22 Thank you very much. It isn't as if the contents of all those odd-looking (to me) tags were anything which seemed useful, I was basicly trying to figure out what was going on. Cyril end |