From py.thoulon at gmail.com Wed Nov 9 01:21:45 2005 From: py.thoulon at gmail.com (Pyt) Date: Wed, 9 Nov 2005 10:21:45 +0100 Subject: [ID3 Dev] SEEK frame semantics Message-ID: From the V2.4 specification, regarding the SEEK frame: This frame indicates where other tags in a file/stream can be found. The 'minimum offset to next tag' is calculated from the end of this tag to the beginning of the next. There may only be one 'seek frame' in a tag.
Minimum offset to next tag $xx xx xx xx The wording "Minimum offset" seems misleading. What does "Minimum" mean in this case ? The next tag is anywhere *after* the offset (e.g., offset+1 or offset+5 would be valid positions) ? or is it supposed to be exactly *at* the offset, as the text seems to imply ? Insights welcome. By the way, has anybody encountered a file using SEEK frames and multiple tags ? If so, I'd be interested in getting my hands on one, for test purposes. Thanks, Pyt. -------------- next part -------------- An HTML attachment was scrubbed... URL: From py.thoulon at gmail.com Mon Nov 21 22:12:35 2005 From: py.thoulon at gmail.com (Pyt) Date: Tue, 22 Nov 2005 07:12:35 +0100 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: <003801c5ef19$143c3c80$4a046c6b@sisodomain.com> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <30155.195.91.64.54.1132612773.squirrel@195.91.64.54> <003801c5ef19$143c3c80$4a046c6b@sisodomain.com> Message-ID: I've had initially the same problem with the new frames, but a very small modification of my library (which in not able to fully parse all frames, anyway) allowed me to take them in as binary (unparsed) frames, as long as the header is well-formed. As far as the "sync" goes, in case of a corrupt frame, you can always: 1. Check that the size of the frame is correct (there is another valid frame header or padding right after the frame) 2. If not, go into detailed analysis of the file right after the corrupt frame, looking for a valid header pattern. It's not fool-proof, but it will work in most cases. Pyt. On 11/22/05, Shiv Charan Panjeta wrote: > > I am also facing the similar problem . if any of the frame is not > understood > .. I have to quite parsing. > Is it make sense to introduce some sync mechanism like (MP3 frame) in > future specs to recover the corrupted frames.? > > Regards, > -Shiv > ----- Original Message ----- > From: "Michal Vician" > To: > Sent: Tuesday, November 22, 2005 4:09 AM > Subject: Re: [ID3 Dev] Moving forward on Chapter Frames > > > > > - should there be a new version of the ID3v2 specification which > > > incorporates Chapter Frames or an addendum which describes Chapter > Frames > > > and nothing else? > > > > Hi. > > > > My first ID3v2 library was built in supposition that there can be only > > frames which are defined in ID3v2 specification. Therefore if there had > > been an "unknown" frame found in ID3v2 tag, my application would have > > ignored the whole tag. Why? Because there was suspicion that tag is > > broken. This was the way of protection against broken tags -> whenever > > something was assumed to be wrong/something unexpected was found, the > > application simply ignored whole ID3v2 tag rather then risk the > > RuntimeException... > > > > Nobody can guarantee that all applications will run properly! Therefore > I > > would rather a new version of ID3v2 specification was released. > > > > Regards > > Miso > > > > > > -- > > Michal Vician > > id3v2 at audiott.com > > http://www.audiott.com/ > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > > For additional commands, e-mail: id3v2-help at id3.org > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul_t100 at fastmail.fm Thu Nov 3 13:48:46 2005 From: paul_t100 at fastmail.fm (Paul Taylor) Date: Thu, 03 Nov 2005 21:48:46 +0000 Subject: [ID3 Dev] Labels And Release Number In-Reply-To: <43698AB0.5060409@northpb.com> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> Message-ID: <436A85BE.7010006@fastmail.fm> Dan O'Neill wrote: > > b. Which library out there do people feel is the *best* example of > an ID3 tag editor that supports v1, v2.3 and v2.4 tags correctly? > https://jaudiotagger.dev.java.net/ is a fairly complete Java API which also allows conversion between tag formats (e.g 2.2 -> 2.4) . --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From shivcharan.p at samsung.com Mon Nov 21 19:59:02 2005 From: shivcharan.p at samsung.com (Shiv Charan Panjeta) Date: Tue, 22 Nov 2005 09:29:02 +0530 Subject: [ID3 Dev] Moving forward on Chapter Frames References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <30155.195.91.64.54.1132612773.squirrel@195.91.64.54> Message-ID: <003801c5ef19$143c3c80$4a046c6b@sisodomain.com> I am also facing the similar problem . if any of the frame is not understood .. I have to quite parsing. Is it make sense to introduce some sync mechanism like (MP3 frame) in future specs to recover the corrupted frames.? Regards, -Shiv ----- Original Message ----- From: "Michal Vician" To: Sent: Tuesday, November 22, 2005 4:09 AM Subject: Re: [ID3 Dev] Moving forward on Chapter Frames > > - should there be a new version of the ID3v2 specification which > > incorporates Chapter Frames or an addendum which describes Chapter Frames > > and nothing else? > > Hi. > > My first ID3v2 library was built in supposition that there can be only > frames which are defined in ID3v2 specification. Therefore if there had > been an "unknown" frame found in ID3v2 tag, my application would have > ignored the whole tag. Why? Because there was suspicion that tag is > broken. This was the way of protection against broken tags -> whenever > something was assumed to be wrong/something unexpected was found, the > application simply ignored whole ID3v2 tag rather then risk the > RuntimeException... > > Nobody can guarantee that all applications will run properly! Therefore I > would rather a new version of ID3v2 specification was released. > > Regards > Miso > > > -- > Michal Vician > id3v2 at audiott.com > http://www.audiott.com/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at audiott.com Mon Nov 14 12:17:09 2005 From: id3v2 at audiott.com (Michal Vician) Date: Mon, 14 Nov 2005 21:17:09 +0100 (CET) Subject: [ID3 Dev] Suggestion - uniform 'Element ID' creation In-Reply-To: <6.1.2.0.2.20051114115507.02ea9190@pop3> References: <48758.195.91.64.54.1131648555.squirrel@195.91.64.54> <6.1.2.0.2.20051111093213.02e0f178@pop3> <7329.195.91.64.54.1131731492.squirrel@195.91.64.54> <6.1.2.0.2.20051114115507.02ea9190@pop3> Message-ID: <27373.195.91.64.54.1131999429.squirrel@195.91.64.54> > At 17:51 11/11/2005, you wrote: >>> Thanks also for the example content. I'm having problems with this >>> because >>> my chapter tool application is based on the Jens Vonderheide API and >>> this >>> doesn't currently support ID3v2.4. Does anyone have a fix for this? >> >>Just tell me and I can generate ID3 tag in whatever version. >>See attachment. There is example content in ID3v2.3. > > Michal, > > I've found that you're using sync safe integer values for the Frame Size > field in Frame Headers. This is correct in 2.4 but incorrect in 2.3. If > you can fix this problem I'll have another try. Thanks for the "bug report". I have fixed it.. - see attachment > Attached is an example file created from ID3v2ChapterTool using a 2.3 tag. > It has the following sequence of frames: > > APIC > TCOP > ... I don't know where is the problem, but I didn't receive any example content. Please try send it again. Best regards Miso -- Michal Vician id3v2 at audiott.com http://www.audiott.com/ -------------- next part -------------- A non-text attachment was scrubbed... Name: example_content.zip Type: application/zip Size: 1851 bytes Desc: not available URL: -------------- next part -------------- --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From jid3 at blinkenlights.org Wed Nov 2 20:08:51 2005 From: jid3 at blinkenlights.org (Paul Grebenc) Date: Wed, 2 Nov 2005 23:08:51 -0500 (EST) Subject: [ID3 Dev] Labels And Release Number Message-ID: On Wed, 2 Nov 2005, Brian Mearns wrote: > The ID3v2.4.0 spec has been around since late 2000, but as far as I know most > major digital media players still base their parsing and writing of tags on > the 2.3 standard. Even there, they do not support most of the frames clearly My take on the major reasons for this are: 1. There is no perceived need for v2.4.0, when v2.3.0 already includes so many frame types that are never used. 2. The v2 standard is not developer friendly. 3. The lack of a test suite for v2.4.0. Until a test suite is available, v2.4.0 should be downgraded to a proposed specification only. Paul --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at northpb.com Tue Nov 22 09:58:52 2005 From: id3v2 at northpb.com (Dan O'Neill) Date: Tue, 22 Nov 2005 09:58:52 -0800 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <30155.195.91.64.54.1132612773.squirrel@195.91.64.54> <003801c5ef19$143c3c80$4a046c6b@sisodomain.com> Message-ID: <43835C5C.2080607@northpb.com> Hi everyone, I've been quite busy with my "real" job over the past few weeks and therefore have lagged on some of your requests to update the implementations pages and the like. The last two days of this week are a holiday in the US so I'll spend some of my free time catching up on the requests. Regards, dano --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From birkirb at stoicviking.net Tue Nov 8 18:00:20 2005 From: birkirb at stoicviking.net (Birkir A. Barkarson) Date: Wed, 09 Nov 2005 11:00:20 +0900 Subject: [ID3 Dev] Worst cases of "ID3 offenders"? In-Reply-To: <27905705A869164CBE58B96BA8547557269EB7@mail.internal.cddb.com> References: <27905705A869164CBE58B96BA8547557269EB7@mail.internal.cddb.com> Message-ID: <43715834.9010507@stoicviking.net> Exactly! Since the standard (2.3) specificies only ISO8859-1 and Unicode as valid character sets then all non ISO8859-1 text SHOULD be converted to unicode and stored as such. How about dropping ISO8859-1 all together in the next version since so many libraries use windows ANSI instead of ISO8859-1. BAB Robert Manson wrote: >>I often work with non english character sets so it's a big issue to get > > >>them displayed correctly. I noted some ID3 editors write any character > > >>sets to the tags, spoofing them as ISO8859-1, usually opting for the >>system default character set. Others will break unicode tags if they >>contain non english characters. > > > ID3 tag libraries should not write text encoded in ISO8859-1 due to the > fact that so many files have been tagged as being IS08859-1 when in fact > the text was encoded in whatever the windows "ANSI" code page was. Try > converting shift-jis to iso latin 1 and see what happens. > > -----Original Message----- > From: Birkir A. Barkarson [mailto:birkirb at stoicviking.net] > Sent: Tuesday, November 08, 2005 5:46 PM > To: id3v2 at id3.org > Subject: Re: [ID3 Dev] Worst cases of "ID3 offenders"? > > I made these notes a few weeks back when working on a ID3 library. > > iTunes > Generally will play any MP3 even if it fails to parse the tag. > > Windows Media Player > Does not seem to support extended headers. > Does not seem to support unsynchronization. > Very sensitive to ill formatted tags and won't play an MP3 if > such a > tag is detected. > > Quicktime Player > Similar to iTunes but doesn't correctly display unicode > characters. > > VLC Media Player > Sensitive to ill formatted tags and will crash with a memory > read error. > > WinAmp 5 Lite > General compatability, but will not display unicode characters > in > default mode. > > > I often work with non english character sets so it's a big issue to get > them displayed correctly. I noted some ID3 editors write any character > sets to the tags, spoofing them as ISO8859-1, usually opting for the > system default character set. Others will break unicode tags if they > contain non english characters. > > BAB > > Mitchell S. Honnert wrote: > >>In testing out my ID3 tag library, I've come across dozens of cases of > > >>mangled v2.3 tags. If there's some way that a tag can be screwed up, >>I've probably seen it. I've done my best to have my lib gracefully >>handle these exceptions, but they're frustrating none-the-less. It's >>not so bad when the offending file looks like it's just the victim of >>simple file corruption, but when it's obvious that the author of the >>app/lib/encoder that wrote the frame decided to just reformat a > > standard > >>frame or make up their own frame, I really cringe. >> >> >> >>What's even more frustrating it to get a bug report from a user of my >>library only to have it turn out that it's one of these renegade >>frames. I've posted the common offenders I know about to my library's > > >>page, but I'm curious to see if any of you know of any more. Here are > > >>the bigger ones I know about. >> >> >> >>- WinAmp will record apparently gibberish bytes in the Language field > > of > >>the Comments (COMM) frame. I don't see any pattern to the bytes, so > > I'm > >>guessing that it's just some uninitialized variable that's getting >>written the Language bytes. >> >> >> >>- WinAmp ignores the Description field of the Comments (COMM) frame. > > It > >>displays whichever COMM frame happens to be read last. (So your >>Comments frame written in another app may "disappear" in WinAmp.) >> >> >> >>- iTunes adds an extra nullchar to the end of the Comments frame. >> >> >> >>- iTunes uses a non-standard frame (TCMP) to record the "Part of a >>compilation" flag. >> >> >> >>- Some app/lib/encoder adds a non-standard NCON frame to the ID3 v2.3 >>tag. I've seen the errant frame hundreds of times, but I've never been > > >>able to track down its source. (Man, I wish I could find the culprit > > who > >>is writing NCON frames. Gah!) >> >> >> >> >> >> >>So, does anyone know of any other popular applications, libraries, or >>encoders that write non-standard, corrupted ID3 tags? >> >> >> >>(Part of me just wanted to vent about applications that break the >>standard I work so hard to adhere to, but I do still think it would > > help > >>reduce some of the support requests I get or at least lessen the >>perception of people that use my lib that it's broken when it's really > > >>the tag that's broken.) >> >> >> >>Thanks, >> >> >> >>Mitchell S. Honnert >> >>UltraID3Lib - http://home.fuse.net/honnert/hundred/?UltraID3Lib >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: id3v2-unsubscribe at id3.org >>For additional commands, e-mail: id3v2-help at id3.org >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From py.thoulon at gmail.com Mon Nov 21 22:04:57 2005 From: py.thoulon at gmail.com (Pyt) Date: Tue, 22 Nov 2005 07:04:57 +0100 Subject: [ID3 Dev] Whole Album Tags In-Reply-To: <438291CD.4080301@coe.neu.edu> References: <438291CD.4080301@coe.neu.edu> Message-ID: Looks like a job fit for the newly define CHAP and CTOC frames. Check http://www.id3.org/develop.html, under "Work in progress". Pyt. On 11/22/05, Brian Mearns wrote: > > I'm interested in constructing a data base of my record collection using > ID3 format. My plan is to just create a file for each album, the only > contents of the file would be an ID3 tag with the album's meta data. I > want to set it up so that the entire tag contains all the data for the > album, plus a frame for each track which contains any necessary meta > data for that track, including possible "overrides" of the data in the > album (parent) tag (For instance, the album may have a certain composer, > but one particular track has a different composer.) > > I was just curious if there was any existing structure for something > like this, or if anyone's came across anything like it before. > > Thanks > > -Brian Mearns > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From py.thoulon at gmail.com Tue Nov 8 09:32:01 2005 From: py.thoulon at gmail.com (Pyt) Date: Tue, 8 Nov 2005 18:32:01 +0100 Subject: [ID3 Dev] New member In-Reply-To: <6.1.2.0.2.20051108143503.02fdfdf8@pop3> References: <45601.195.91.64.54.1131402561.squirrel@195.91.64.54> <6.1.2.0.2.20051108143503.02fdfdf8@pop3> Message-ID: > > Alternatively, you could try exchanging content with my authoring tool: > http://sourceforge.net/projects/id3v2-chap-tool > > Let me know if you have any problems. Chris, I've been playing with the ChapterTool, but it seems that you can't set chapter start and end times just by typing the time into the text entry boxes, but only by using the media player and clicking on Set Start or Set End on the fly (or am I doing something wrong ? the times don't seem to be saved to the file unless the buttons are used). This is kind of cumbersome and does not allow for precise, to-the-frame, setting of the start and end times. I posted a bug request to the tracker page, but I was just wondering whether you were monitoring that. Thanks, Pyt. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mitch at honnert.com Wed Nov 30 09:54:32 2005 From: mitch at honnert.com (Mitchell S. Honnert) Date: Wed, 30 Nov 2005 12:54:32 -0500 Subject: [ID3 Dev] Moving forward on Chapter Frames References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <6.1.2.0.2.20051125161419.02cf2418@pop3> <4da424620511251914o43262f92pc19117c8cf3241a2@mail.gmail.com> <14398.195.91.64.52.1133020015.squirrel@195.91.64.52> <6.1.2.0.2.20051128165838.02da7b70@pop3> <57148.195.91.64.54.1133283276.squirrel@195.91.64.54> <6.1.2.0.2.20051130095722.02f37a90@pop3> <438DD9DF.1070403@northpb.com> <002701c5f5d2$e9f4a9b0$87000105@kendle.com> <55198.195.91.64.54.1133372563.squirrel@195.91.64.54> Message-ID: <005c01c5f5d7$1e891040$87000105@kendle.com> >Is your library also written in C# ? No, it's written in VB.NET. (What can I say? I started out using C-64 Basic and QuickBasic.) But that shouldn't have any affect on using the library from a .NET language. > If yes, is your library open source? It's not open source, but it is free. For more information, check out the link in my sig. Mitchell S. Honnert UltraID3Lib - http://home.fuse.net/honnert/hundred?UltraID3Lib ----- Original Message ----- From: "Michal Vician" To: Sent: Wednesday, November 30, 2005 12:42 PM Subject: Re: [ID3 Dev] Moving forward on Chapter Frames >> ...I was running a scan of a friend's music library as a test of my >> .NET ID3 tag library when hundreds or errors were reported. >> I've run several of... > > I'm a bit interested in .NET. I work with Java but I have also tried to > write some code in C#. Is your library also written in C# ? If yes, is > your library open source? > > Many thanks > Miso > > -- > Michal Vician > id3v2 at audiott.com > http://www.audiott.com/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From vician at audiott.com Fri Nov 4 12:22:08 2005 From: vician at audiott.com (Michal Vician) Date: Fri, 4 Nov 2005 21:22:08 +0100 (CET) Subject: ID3.org - other implementations notice Message-ID: <62615.195.91.64.55.1131135728.squirrel@195.91.64.55> Hi. I don't know what's going on, but "CDDB-MP3-Tagger v2.0" (the link in other implementations list of id3.org) seems to be canceled. I've just noticed it ... (maybe you don't know about it) -- Michal Vician www.audiott.com vician at audiott.com From chris.newell at rd.bbc.co.uk Mon Nov 28 10:06:00 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Mon, 28 Nov 2005 18:06:00 +0000 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: <14398.195.91.64.52.1133020015.squirrel@195.91.64.52> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <6.1.2.0.2.20051125161419.02cf2418@pop3> <4da424620511251914o43262f92pc19117c8cf3241a2@mail.gmail.com> <14398.195.91.64.52.1133020015.squirrel@195.91.64.52> Message-ID: <6.1.2.0.2.20051128165838.02da7b70@pop3> At 15:46 26/11/2005, you wrote: >> Any MP3 reader/library that doesn't handle unknown tags is poorly >> implemented *****and breaks the standard***** (at least v2.3 and v2.4 -- I >> haven't read prior standards). > >What? Breaks the standard? I don't agree with you. There is nothing stated >in ID3v2 specification that tag may contain other frames. There is only >allowance in custom frames (X,Y,Z), but nothing stated that my application >should handle frames like "HAHA" or "TOOT". Michal, I'm not sure I agree. This is what it says in ID3 version 2.3.0: "Identifiers beginning with "X", "Y" and "Z" are for experimental use and free for everyone to use, without the need to set the experimental bit in the tag header. Have in mind that someone else might have used the same identifier as you. All other identifiers are either used or reserved for future use." Where it says that all other identifiers are "reserved for future use" it must mean they are reserved within the context of ID3 version 2.3. This means that you might expect to find them in a future revision to version 2.3. In my experience I've found the following version 2.4 frames types inside version 2.3 tags e.g: TDRL And I've found some frames that aren't defined in any ID3v2 specification: WFED TCMP TGID TDES PCST If this is typical of what ID3 parsers will accept then it may be acceptable to allow Chapter frames in ID3 v2.3 and v2.4. Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr J.C. Newell Digital Media Group, BBC Research & Development Kingswood Warren, Woodland Way, Tadworth, Surrey KT20 6NP UK mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd Tel: +44 (0)1737 839659 Switchboard: +44 1737 839500 Fax: +44 (0)1737 839665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From chris.newell at rd.bbc.co.uk Mon Nov 28 03:39:36 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Mon, 28 Nov 2005 11:39:36 +0000 Subject: [ID3 Dev] Moving forward on Chapter Frames Message-ID: <6.1.2.0.2.20051128103138.02da0970@pop3> At 16:11 25/11/2005, I wrote: >I've tried files tagged with Chapter Frames carried in version 2.3 tags with a number of media players running on Windows. > >The following played the files without problems and could decode the standard tags: > QuickTime > VLC > iTunes > >However, although Windows Media Player 6.4 played the file it appeared unable to read any information from the tag when the Chapter Frames were present. I've discovered that the problem with Windows Media Player is related to the de.vdheide.mp3 Java API rather than the presence of Chapter Frames. Therefore I don't have any evidence to suggest that there would be a problem with Chapter Frames in version 2.3 tags. If anyone knows what the problem may be with the Java API can they please let me know. Cheers, Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr J.C. Newell Digital Media Group, BBC Research & Development Kingswood Warren, Woodland Way, Tadworth, Surrey KT20 6NP UK mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd Tel: +44 (0)1737 839659 Switchboard: +44 1737 839500 Fax: +44 (0)1737 839665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From bmearns at coe.neu.edu Wed Nov 2 16:50:55 2005 From: bmearns at coe.neu.edu (Brian Mearns) Date: Wed, 02 Nov 2005 19:50:55 -0500 Subject: [ID3 Dev] Labels And Release Number In-Reply-To: <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> Message-ID: <43695EEF.7040705@coe.neu.edu> I don't have any particular opinion for or against adding these frames to the spec, but I do have some other comments: The ID3v2.4.0 spec has been around since late 2000, but as far as I know most major digital media players still base their parsing and writing of tags on the 2.3 standard. Even there, they do not support most of the frames clearly and precisely defined in the 2.3 standard. My point is this: the id3 crew seems to get stuff going pretty quick so lets even say every done decides to add these frames to the spec, and they complete the revised standard to include these tags by the new year. My guess is, you wouldn't see these changes in too many media players till 2008 easy. Even by then, especially if these are tags as you said which are primarily of import to independent musicians/labels, you probably aren't going to find too many folks as Microsoft (for example) eager to dredge up so old code out of CVS to implement the changes in the standard. I don't mean that to be a discouragement, because by that logic, nothing would ever get done. But it is something for you to consider if you're looking at this as a short term solution to something. If it's a relatively private issue, like you want to catalog your own collection by these tags, you might consider using the User defined text information frame: [http://www.id3.org/id3v2.3.0.html#sec4.2.2] or (probably better) the private information frame: [http://www.id3.org/id3v2.3.0.html#sec4.28] -Brian Robot Gunslinger wrote: > I am currently using the genre field for storing label information, so > I can browse > them within iTunes. > > TPUB and TSRC are not really what I meant. The TSRC is an ISO standard > while catalog numbers > are handled by Labels themselves. Here are some examples. > > Ghostly International (Electronic Music) uses GI-xx for Ghostly > International releases and SPC-XX > (for Spectral Sound) for their more technoid music releases. > > http://www.ghostly.com/1.0/ (click on Catalog). > > same with Moor Music > http://www.morrmusic.com/ (under releases) > > and also heavily put do use by netlabels > http://www.netlabels.org (list of netlabels) > > Almost every small label (that is everyone not owned by Sony and Co.) > is heavily relying on > catalog numbers. Some releases / catalog numbers that are out of print > are highly valuable > something that is the case with some early Warp Records > (www.warprecords.co.uk). > > Also publishers and labels aren't really the same, with many indie > labels using publishing / distributing channels > of bigger labels, since they can't afford to do it themselves. > > This might all sound very niche like, but it really isn't. Those small > independent labels represent > the musicians that redefine what music is and highly influence the > cultural aspect of > music in general and almost every good music publication (print or > online) are concentrating on > those "good" records. > > Again, I really think that this should be added to the ID3 > specifications and I don't think > I am alone here. A lot of people think that this is a feature that is > clearly missing from the > id3 tag specification. > > > > Am 02.11.2005 um 19:39 schrieb James J. Williams: > >> I agree, there should definitely be a standardized Label field, some >> programs (NI Traktor) store a Label field, I'm not sure what the >> field is >> named in the tag but that would be easy enough to find out, anyhow >> for now >> I've resorted to storing label information in the album field... It's >> not >> pretty but it works. >> >> - JW >> >> -----Original Message----- >> From: Robot Gunslinger [mailto:robot.gunslinger at gmail.com] >> Sent: Wednesday, November 02, 2005 8:14 AM >> To: id3v2 at id3.org >> Subject: [ID3 Dev] Labels And Release Number >> >> One thing that always bugged me about id3 is it's inability to provide >> a field for "Label" and "Release Number". >> >> It's especially annoying if you're a fan of electronic or indie >> music, where >> where labels (netlabels or otherwise) still are of importance, >> especially for collectors. >> >> I am not a programmer and I don't know if this feature has already been >> implemented in the latest release, but judging from the most common >> mp3 players, I guess it hasn't. >> >> I am sure this can't be too hard to integrate and would be a very >> useful feature >> for Netlabel releases and adding the possibility to defining the >> Label and the Catalog Number of an id3 tagged music file sure is an >> valid >> addition to the metadata capabilities of the id3 standard, so please >> guys >> just put it in there. >> >> >> cheers >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org >> For additional commands, e-mail: id3v2-help at id3.org >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org >> For additional commands, e-mail: id3v2-help at id3.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From bmearns at coe.neu.edu Mon Nov 21 19:34:37 2005 From: bmearns at coe.neu.edu (Brian Mearns) Date: Mon, 21 Nov 2005 22:34:37 -0500 Subject: [ID3 Dev] Whole Album Tags Message-ID: <438291CD.4080301@coe.neu.edu> I'm interested in constructing a data base of my record collection using ID3 format. My plan is to just create a file for each album, the only contents of the file would be an ID3 tag with the album's meta data. I want to set it up so that the entire tag contains all the data for the album, plus a frame for each track which contains any necessary meta data for that track, including possible "overrides" of the data in the album (parent) tag (For instance, the album may have a certain composer, but one particular track has a different composer.) I was just curious if there was any existing structure for something like this, or if anyone's came across anything like it before. Thanks -Brian Mearns --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From chris.newell at rd.bbc.co.uk Wed Nov 9 02:05:43 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Wed, 09 Nov 2005 10:05:43 +0000 Subject: [ID3 Dev] Embedded frames (COMM or TXXX?) In-Reply-To: <44171.195.91.64.52.1131492297.squirrel@195.91.64.52> References: <44171.195.91.64.52.1131492297.squirrel@195.91.64.52> Message-ID: <6.1.2.0.2.20051109092624.02e2f920@pop3> Michal, At 23:24 08/11/2005, you wrote: >The only problem I have is that I can't find any free java library, which >can play MP3 files (I need it for my Chapter GUI). Your authoring tool is >able to play them - can you help me to gain the library please. I'm using JMF2.1.1e which you can download from: http://java.sun.com/products/java-media/jmf If you're unfamiliar with the JMF API have a look at the bbc.rd.id3.tool.JMFPanel class in ID3v2ChapterTool. >In the latest CHAP/CTOC frame specification is no stated which frame do I >have to use if I want to write more notes related to the Chapter/CTOC. I >think it should be stated there, because the situation can happen that >somebody will use COMM frame and somebody other will use e.g. TXXX frame >for this purpose. >Can anybody tell me which one should I use. I just want to implement the >support for more "notes" into my application... In theory, you should use the same frames to describe chapters that you use for files which don't have chapters. Personally, I would use COMM for a synopsis but I've also seen a frame called TDES used which isn't in the ID3v2 spec. Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr J.C. Newell Digital Media Group, BBC Research & Development Kingswood Warren, Woodland Way, Tadworth, Surrey KT20 6NP UK mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd Tel: +44 (0)1737 839659 Switchboard: +44 1737 839500 Fax: +44 (0)1737 839665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From deathboy2000 at earthlink.net Tue Nov 8 07:11:23 2005 From: deathboy2000 at earthlink.net (darien) Date: Tue, 08 Nov 2005 08:11:23 -0700 Subject: [ID3 Dev] questions regarding TBPM frame. In-Reply-To: <000901c5de76$c4d6b600$0500000a@MARVIN> References: <6.2.5.6.0.20051030223858.02ecdb90@earthlink.net> <6.2.5.6.0.20051031034035.02e9f310@earthlink.net> <000901c5de76$c4d6b600$0500000a@MARVIN> Message-ID: <6.2.5.6.0.20051108075210.02cafa28@earthlink.net> hey there andy. thanks for taking the time to drop a reply to this thread... > the ID3v2.X.0 standard clearly states that the TBPM frame > contains a string representation of an integer, so the values > 132.68 and 95.35 are invalid. >I would not personally recommend changing the current specification >of the TBPM frame to allow for high precision bpm values but instead >I would suggest >you submit a proposal for a new frame (PBPM?). This would allow TBPM >aware applications to prefer the high precision frame over the >standard TBPM frame >whilst also ensuring that existing non-aware applications remain intact. i honestly think it would be better to change the TBPM frame to allow both. the reason why i think that way is that most of the apps i've seen that handle BPM measurement and store it in the TBPM frame all store a non-whole number. i've only seen a couple of apps that adhere to the standard, and the rest ignore it and store a non-whole measurement (ie 13278) in that frame. one of the oldest 'pro' apps that i know of, PCDJ Red, stores that information in the TBPM frame. i haven't seen a version of that app in quite a while, but the last version i saw put a value like '13278' in there. because there are apps that i use to do bpm measurement that probably won't ever be updated (mixmeister bpm analyzer, flatfeetpete's recordboxing app : http://sourceforge.net/project/showfiles.php?group_id=70378 ) to adhere to a standard, i think it would be better to change the standard of that frame to allow both. since apps already stick non-whole numbers in there, i reckon that devices/apps that look at that frame already round off non-whole numbers that they see already if that is necessary. it would be nice though to have newer apps that adhere to the standard not round off the number if they see a non-whole number in the frame. i have several thousand files that have all had their bpm measurements done, and i don't want to have them all rounded off, as it has taken hours of cpu time to analyze them. i am not a programmer, and i can't write an application that would convert the values to a new frame, and don't have the money to hire a programmer to do that either ... and unfortunately, neither one of the apps i use would probably be updated to use the new frame. so again, i ask ... how does one get the standard changed to allow both types of entries? cheers for any advice. --darien! >----- Original Message ----- From: "darien" >To: >Sent: Monday, October 31, 2005 2:07 PM >Subject: Re: [ID3 Dev] questions regarding TBPM frame. > > >> >>hey there Pyt ... >> >>thanks for replying. >> >>>Strictly speaking, TBPM is a text frame, so it is very possible >>>for it to be set to just about anything textual if a program would >>>allow it. However, the v2.4 spec is pretty clear that it is an >>>integer and that it is beats per minute, so you cannot set it to >>>123.45, and even though you could set it to 12345, but that would >>>probably meaningless from a musical standpoint... >>> >>>I guess your programmer must have decided that more than 999 beats >>>per minute is nonsense, which can be understood but is indeed >>>going a bit further than the spec intends. >>> >>>Not sure this helps... >> >>it sort of does ... it's brought a couple of things to light, and i >>have a question... >> >>how does one go about getting the spec for the TBPM frame changed >>to allow for a decimal place and 'non-whole' bpm measurements (ie >>132.68, 95.35, etc) as allowable and legitimate data for the spec? >> >>i feel that it's not right the way it is, i can think of quite a >>few arguments for why the 'standard' should be changed to allow a >>decimal place if desired or needed, and i'd like to push to have it >>changed. it would make my life a bit easier in a few different >>ways, and i reckon it would probably help other people out there as well. >> >>bpm measurement is *never* a solid, honest-to-goodness integer. >>well, not practically, anyway. it's usually measured in averages, >>because there are no recordings out there that are perfectly >>on-beat from start to finish ... there are many obvious reasons >>why... neither midi clocks nor human drummers are ever 100% on the >>money with regard to keeping time, hence having bpm measurements of >>132.68, 95.35, etc. while midi clocks come close, there's always a >>little bit of slide with regard to the accuracy of its' generation. >>human drummers are never 100% -- every human drummer is always off >>the mark by some percentage (usually depending on how drunk they >>are). the only thing that is pretty much right-on is smpte, and a >>large percentage of professional musicians don't use smpte for >>clock generation (though there are a few out there that do, >>especially if they're working in hollywood on film or television projects). >> >>most software applications that measure bpm properly do not end up >>with a bpm measurement that is a whole integer either (here's one i >>know of that's free and writes the value into the id3v2.x tag : >>http://www.mixmeister.com/download_freestuff.html ) ... >> >>i'm a dance music dj and i play a lot of electronically-based >>music. i play house, prog house, hip hop, breaks, and i play some >>mobile dj gigs too if the money's right. years ago, i used to >>exclusively dj with vinyl records and cd's, but now i use traktor >>dj studio to dj with. traktor dj studio has the ability to be able >>to control/manipulate playback of mp3's using a special hardware >>audio interface and vinyl records with a recording of timecode cut >>onto them. the timecode records tell the computer what pitch the >>record is playing back at, where the needle is on the record and so >>forth. the records and hardware are essentially a control >>interface, and a brilliant one at that. >> >>about 80% of the mp3's i generate to dj with are from recordings of >>vinyl records, because that's the medium of choice for dj'ing >>electronic music -- a lot of prime stuff gets released on vinyl >>that never sees a digital release, even in this digital world of >>ours. vinyl, as a rule, is an imperfect medium, which opens up a >>pretty huge can o' worms in itself with regard to bpm and speed in >>general. here are some examples of things that cause timing issues >>with vinyl records: >> >>o - vinyl records are never perfectly flat. every record pressed >>(even a 180 gram audiophile grade record) has a certain degree of >>warp to it. they can be really close to flat, but never perfectly flat >>o - the stamper plates used to press records are made of nickel, >>and a high amount of pressure is placed on them for every record >>pressed -- it takes 120 tons of pressure to press a vinyl record. >>as a result, every pressing degrades the stampers slightly. >>stampers are only good for 1000 pressings. after that, the stampers >>will have degraded enough to create a noticably imperfect product >>and a new set of stampers must be used. >>o - consistency of the vinyl material differs slightly from batch to batch >> >>couple these factors with a midi clock that doesn't generate time >>perfectly and you've got a recording that isn't going to be >>anywhere near perfect, timing and bpm measurement-wise. >> >>this is just one example. another that i could explore is disco or >>funk tracks from the 70's... parliament, the bee gee's, gloria >>gaynor, cheryl lynn, donna summer, etc. all of that stuff was >>recorded onto analog tape, and human drummers were employed. analog >>tape stretches and shrinks with temperature and general use. tape >>machines of the day weren't digitally regulated, and no analog >>motor is perfect. pair those imperfections with a human drummer and >>loads of disco or funk swing, and you've got a recording that isn't >>anywhere near a whole integer bpm-wise. >> >>so yeah ... some good arguments there. ;) >> >>any advice on how to go about getting the spec changed for the TBPM >>field would be greatly appreciated. >> >>cheers. >> >>--darien! >> >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: id3v2-unsubscribe at id3.org >>For additional commands, e-mail: id3v2-help at id3.org >> > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: id3v2-unsubscribe at id3.org >For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at northpb.com Wed Nov 2 19:57:36 2005 From: id3v2 at northpb.com (Dan O'Neill) Date: Wed, 02 Nov 2005 19:57:36 -0800 Subject: [ID3 Dev] Labels And Release Number In-Reply-To: <43695EEF.7040705@coe.neu.edu> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> Message-ID: <43698AB0.5060409@northpb.com> Brian Mearns wrote: > I don't have any particular opinion for or against adding these frames > to the spec, but I do have some other comments: > > The ID3v2.4.0 spec has been around since late 2000, but as far as I know > most major digital media players still base their parsing and writing of > tags on the 2.3 standard. With a little evangelization I think we can get some attention and some forward movement. However, Brian is absolutely right that it's going to take a long time to show up in the marketplace. The vendors require a consumer driven reason to make a change. That driver might be podcasts with CTOC/CHAP frames. A full working reference model would be the ideal thing to have. Anyone want to put all the pieces together? MP3 file w/2.4.0 tags w/CHAP & CTOC frames library + sample code that wrote the above v2.4.0 tags player that can read and use these tags Other thoughts: a. Let's revive the v2.4.0 specification and all the issues that people have with it and get it fixed. I'm willing to serve as typist. b. Which library out there do people feel is the *best* example of an ID3 tag editor that supports v1, v2.3 and v2.4 tags correctly? Thanks, dano --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From andrew.kernahan at btinternet.com Wed Nov 9 11:45:42 2005 From: andrew.kernahan at btinternet.com (Andy Kernahan) Date: Wed, 9 Nov 2005 19:45:42 -0000 Subject: [ID3 Dev] Worst cases of "ID3 offenders"? References: <27905705A869164CBE58B96BA8547557269EB8@mail.internal.cddb.com> Message-ID: <003c01c5e566$2bbc6900$0500000a@MARVIN> Hmmmm, it seems to work ok on my XP machine. Are you sure the BOM is present within the text frame? Andy. ----- Original Message ----- From: "Robert Manson" To: Sent: Wednesday, November 09, 2005 7:39 PM Subject: RE: [ID3 Dev] Worst cases of "ID3 offenders"? You are right that Windows XP does not support v2.4. It does claim to support v2.3, however, and its implementation of the standard is flawed due to the fact that it cannot read "16-Bit Unicode 2.0" strings encoded as big endian. -----Original Message----- From: Andy Kernahan [mailto:andrew.kernahan at btinternet.com] Sent: Wednesday, November 09, 2005 11:13 AM To: id3v2 at id3.org Subject: Re: [ID3 Dev] Worst cases of "ID3 offenders"? XP doesn't actually support V2.4.0 and therefore has no need to support UTF16-BE. ----- Original Message ----- From: "Robert Manson" To: Sent: Wednesday, November 09, 2005 1:38 AM Subject: RE: [ID3 Dev] Worst cases of "ID3 offenders"? Windows XP does not read UTF16-BE encoded text frames -----Original Message----- From: Paul Grebenc [mailto:jid3 at blinkenlights.org] Sent: Tuesday, November 08, 2005 2:51 PM To: id3v2 at id3.org Subject: Re: [ID3 Dev] Worst cases of "ID3 offenders"? The MP3ext Windows explorer extension corrupts all of its ID3 v2 tags by repeatedly writing an advertisement for itself (ie. "MP3ext V3.3.18(unicode)") in the tag padding, which violates the spec. Winamp ignores the last frame in a v2.3.0 tag if there is no padding in the tag. Mixmeister BPM analyzer (among others it seems) writes floating point values to the TBPM frame. Paul --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at audiott.com Tue Nov 8 15:24:57 2005 From: id3v2 at audiott.com (Michal Vician) Date: Wed, 9 Nov 2005 00:24:57 +0100 (CET) Subject: [ID3 Dev] Embedded frames (COMM or TXXX?) Message-ID: <44171.195.91.64.52.1131492297.squirrel@195.91.64.52> ------------------------------------------------------------------------ > At 22:29 07/11/2005, you wrote: >>I'm interested in ID3v2, therefore I hope I will be helpful joining the >>mailing list. I've already made a core for reading and writing CHAP and >>CTOC frames... However, it can be done only from the command line. Now >>it's only a question of time to make an "engaging" GUI for it. > > Michal, > > Great to hear you've looked at Chapter Frames. Perhaps we could exchange > some content to explore interoperability? Oh yes. It's great idea. I will send you some tomorrow (now I don't have time). > Let me know if you have any problems. The only problem I have is that I can't find any free java library, which can play MP3 files (I need it for my Chapter GUI). Your authoring tool is able to play them - can you help me to gain the library please. I would really appreciate. Many thanks ------------------------------------------------------------------------ http://www.id3.org/drafts/id3v2_chapters-2005102501.txt In the latest CHAP/CTOC frame specification is no stated which frame do I have to use if I want to write more notes related to the Chapter/CTOC. I think it should be stated there, because the situation can happen that somebody will use COMM frame and somebody other will use e.g. TXXX frame for this purpose. Can anybody tell me which one should I use. I just want to implement the support for more "notes" into my application... -- Michal Vician id3v2 at audiott.com http://www.audiott.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From tsorensen at gmail.com Fri Nov 25 19:14:09 2005 From: tsorensen at gmail.com (Tom Sorensen) Date: Fri, 25 Nov 2005 21:14:09 -0600 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: <6.1.2.0.2.20051125161419.02cf2418@pop3> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <6.1.2.0.2.20051125161419.02cf2418@pop3> Message-ID: <4da424620511251914o43262f92pc19117c8cf3241a2@mail.gmail.com> Any MP3 reader/library that doesn't handle unknown tags is poorly implemented and breaks the standard (at least v2.3 and v2.4 -- I haven't read prior standards). There is an allowance in both for custom frames (technically "experimental" frames) that start with X, Y, or Z. As long as the frame length in the header is correct, it should be parsed (and ignored if you don't know what to do with it). Tom On 11/25/05, Chris Newell wrote: > At 18:49 21/11/2005, Pyt wrote: > >One question is problably whether existing implementations are lenient enough to accomodate Chapter frames in v2.3 or 2.4 tags, even though they are not part of the original spec (for example, how do the existing public implementations like ID3Lib or the java library behave ?). If so, then I would vote for having just an addendum, and making the frames legal in v2.3 and 2.4. > > > >Otherwise, we have to go up one revision. > > I've tried files tagged with Chapter Frames carried in version 2.3 tags with a number of media players running on Windows. > > The following played the files without problems and could decode the standard tags: > QuickTime > VLC > iTunes > > However, although Windows Media Player 6.4 played the file it appeared unable to read any information from the tag when the Chapter Frames were present. > > It looks like a new version of the standard would probably be the safest option but I'm concerned this might discourage support for Chapter Frames. > > Chris > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From mitch at honnert.com Tue Nov 8 13:31:30 2005 From: mitch at honnert.com (Mitchell S. Honnert) Date: Tue, 8 Nov 2005 16:31:30 -0500 Subject: [ID3 Dev] Worst cases of "ID3 offenders"? References: <6.2.5.6.0.20051030223858.02ecdb90@earthlink.net> <6.2.5.6.0.20051031034035.02e9f310@earthlink.net> <000901c5de76$c4d6b600$0500000a@MARVIN> <6.2.5.6.0.20051108075210.02cafa28@earthlink.net> Message-ID: <000801c5e4ab$c8dd3d10$b1000105@kendle.com> In testing out my ID3 tag library, I've come across dozens of cases of mangled v2.3 tags. If there's some way that a tag can be screwed up, I've probably seen it. I've done my best to have my lib gracefully handle these exceptions, but they're frustrating none-the-less. It's not so bad when the offending file looks like it's just the victim of simple file corruption, but when it's obvious that the author of the app/lib/encoder that wrote the frame decided to just reformat a standard frame or make up their own frame, I really cringe. What's even more frustrating it to get a bug report from a user of my library only to have it turn out that it's one of these renegade frames. I've posted the common offenders I know about to my library's page, but I'm curious to see if any of you know of any more. Here are the bigger ones I know about. - WinAmp will record apparently gibberish bytes in the Language field of the Comments (COMM) frame. I don't see any pattern to the bytes, so I'm guessing that it's just some uninitialized variable that's getting written the Language bytes. - WinAmp ignores the Description field of the Comments (COMM) frame. It displays whichever COMM frame happens to be read last. (So your Comments frame written in another app may "disappear" in WinAmp.) - iTunes adds an extra nullchar to the end of the Comments frame. - iTunes uses a non-standard frame (TCMP) to record the "Part of a compilation" flag. - Some app/lib/encoder adds a non-standard NCON frame to the ID3 v2.3 tag. I've seen the errant frame hundreds of times, but I've never been able to track down its source. (Man, I wish I could find the culprit who is writing NCON frames. Gah!) So, does anyone know of any other popular applications, libraries, or encoders that write non-standard, corrupted ID3 tags? (Part of me just wanted to vent about applications that break the standard I work so hard to adhere to, but I do still think it would help reduce some of the support requests I get or at least lessen the perception of people that use my lib that it's broken when it's really the tag that's broken.) Thanks, Mitchell S. Honnert UltraID3Lib - http://home.fuse.net/honnert/hundred/?UltraID3Lib --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at audiott.com Fri Nov 11 09:53:25 2005 From: id3v2 at audiott.com (Michal Vician) Date: Fri, 11 Nov 2005 18:53:25 +0100 (CET) Subject: [ID3 Dev] Suggestion - uniform 'Element ID' creation] Message-ID: <15689.195.91.64.54.1131731605.squirrel@195.91.64.54> > I can see the merit of your "uniform Element ID" > concept in terms of simplicity for parsers. However, I'm concerned that it would block one of the useful capabilities of the current scheme - the ability to reference chapters from more than one table of contents. > > For example, for the recording of a rock festival you could create a CHAP frame for each song and then index these frames in three ways using different CTOCs to provide: > - a full, temporally ordered table of contents > - a table providing an index of band names or genres > - a table listing highlights > > I think it's important to maintain this kind of flexibility because it opens up all kinds of interesting opportunities for content developers. Oh yes. I had forgotten that there may be more than one table of contents in each tag. Therefore I have adjusted my "uniform Element ID" concept so that there may be more than one table of contents. How? Just by adding the "X#" at the very beggining of each Element ID. X - the unigue number identifier of each table of contents. Here is example of 2 tables of contents written in one ID3 tag (there are also some CHAP frames which are not referenced by any CTOC frame): {THIS IS TABLE OF CONTENTS #1} 1#0 (root - zero level) 1#1 (1st level) 1#2 1#3 1#3.1 (2nd level) 1#3.2 1#3.3 1#3.3.1 (3rd level) 1#3.3.2 1#3.3.3 1#3.3.3.1 (4th level) 1#3.3.3.2 ... 1#4 1#4.1 (2nd level) 1#4.2 1#4.3 1#4.3.1 1#4.3.2 ... {THIS IS TABLE OF CONTENTS #2} 2#0 (root - zero level) 2#1 (1st level) 2#2 2#3 2#3.1 (2nd level) 2#3.2 2#3.3 2#3.3.1 (3rd level) 2#3.3.2 2#3.3.3 2#3.3.3.1 (4th level) 2#3.3.3.2 ... 2#4 2#4.1 (2nd level) 2#4.2 2#4.3 2#4.3.1 2#4.3.2 ... {CHAP FRAMES NOT REFERENCED BY ANY CTOC FRAME} *1 *2 *3 ... I think that now there is nothing what would block the capability of current chap/ctoc scheme. I also think that this way of creating "element ids" will make it much easier for parsers. Consider revising the current chapter scheme in this way please. > Thanks also for the example content. I'm having problems with this because my chapter tool application is based on the Jens Vonderheide API and this doesn't currently support ID3v2.4. Does anyone have a fix for this? Just tell me and I can generate ID3 tag in whatever version. See attachment. There is example content in ID3v2.3. Cau Miso -- Michal Vician id3v2 at audiott.com http://www.audiott.com/ -------------- next part -------------- A non-text attachment was scrubbed... Name: example content.zip Type: application/zip Size: 1853 bytes Desc: not available URL: -------------- next part -------------- --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From rmanson at gracenote.com Tue Nov 8 17:38:39 2005 From: rmanson at gracenote.com (Robert Manson) Date: Tue, 8 Nov 2005 17:38:39 -0800 Subject: [ID3 Dev] Worst cases of "ID3 offenders"? Message-ID: <27905705A869164CBE58B96BA854755703659145@mail.internal.cddb.com> Windows XP does not read UTF16-BE encoded text frames -----Original Message----- From: Paul Grebenc [mailto:jid3 at blinkenlights.org] Sent: Tuesday, November 08, 2005 2:51 PM To: id3v2 at id3.org Subject: Re: [ID3 Dev] Worst cases of "ID3 offenders"? The MP3ext Windows explorer extension corrupts all of its ID3 v2 tags by repeatedly writing an advertisement for itself (ie. "MP3ext V3.3.18(unicode)") in the tag padding, which violates the spec. Winamp ignores the last frame in a v2.3.0 tag if there is no padding in the tag. Mixmeister BPM analyzer (among others it seems) writes floating point values to the TBPM frame. Paul --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From py.thoulon at gmail.com Wed Nov 9 01:14:50 2005 From: py.thoulon at gmail.com (Pyt) Date: Wed, 9 Nov 2005 10:14:50 +0100 Subject: [ID3 Dev] Worst cases of "ID3 offenders"? In-Reply-To: <000801c5e4ab$c8dd3d10$b1000105@kendle.com> References: <6.2.5.6.0.20051030223858.02ecdb90@earthlink.net> <6.2.5.6.0.20051031034035.02e9f310@earthlink.net> <000901c5de76$c4d6b600$0500000a@MARVIN> <6.2.5.6.0.20051108075210.02cafa28@earthlink.net> <000801c5e4ab$c8dd3d10$b1000105@kendle.com> Message-ID: I've seen Windows Media Player write a v2.3 tag to a file that already had a v2.4 tag, resulting in two tags in the same file and thus "disappearance" of the 2.4 tag (as the 2.3 tag is written first, and there is no mechanism in 2.3 for chaining tags). Pyt. -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul_t100 at fastmail.fm Wed Nov 9 00:14:05 2005 From: paul_t100 at fastmail.fm (Paul Taylor) Date: Wed, 09 Nov 2005 08:14:05 +0000 Subject: [ID3 Dev] How do I get my lib on the Implementations page of www.id3.org? In-Reply-To: <436FD7A4.1050102@northpb.com> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> Message-ID: <4371AFCD.5010606@fastmail.fm> Hi I have also emailed Martin in the past with no luck, I would like to recommend jaudiotagger (https://jaudiotagger.dev.java.net/) an open source Java API for ID3 & Jaikoz (www.jaikoz.net) a powerful shareware ID3 Editor that uses the jaudiotagger library Paul >> >> Anyway, does anyone know how I would go about getting a link to my >> library on the Implementations page of www.id3.org >> ? > > > You post it to the mailing list and I edit the HTML and link to your > library. That easy. Look in the implementations section tomorrow. > > There's been a glaring need for a reference test suite, but no one has > taken the charge (yet) to put something together. Martin has not been > responsive to email for quite some time, therefore, I've volunteered > to provide maintenance services for the ID3.org standard and this > interested group of people. > > Again, welcome to the list. > > dano > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From tsorensen at gmail.com Mon Nov 21 10:58:50 2005 From: tsorensen at gmail.com (Tom Sorensen) Date: Mon, 21 Nov 2005 13:58:50 -0500 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> Message-ID: <4da424620511211058j5c733859s35707d8f9f24530a@mail.gmail.com> ID3Lib will happily ignore any frames it's not familiar with (e.g. -- iTunes TCMP frame), at least as long as the frame header is sane. I haven't tested to see what would happen with a broken frame header (e.g. -- bad length), but I'd guess it wouldn't be pretty. As the id3.org specs recommend, be liberal in reading and strict in writing. Not that every library actually manages to do that. On 11/21/05, Pyt wrote: > One question is problably whether existing implementations are lenient > enough to accomodate Chapter frames in v2.3 or 2.4 tags, even though they > are not part of the original spec (for example, how do the existing public > implementations like ID3Lib or the java library behave ?). If so, then I > would vote for having just an addendum, and making the frames legal in v2.3 > and 2.4. > > Otherwise, we have to go up one revision. > > For what it's worth... > Pyt. > > > > On 11/21/05, Chris Newell wrote: > > Colleagues, > > > > The Chapter Frame proposal has been available on the ID3 web site for a > while now and feedback on the reflector has tailed off. I'm wondering how we > could move things forward. One issue not covered by the proposal is how > support for the Chapter Frames might be introduced and this raises a couple > of questions: > > > > - should there be a new version of the ID3v2 specification which > incorporates Chapter Frames or an addendum which describes Chapter Frames > and nothing else? > > > > - should we allow Chapter Frames to be used in ID3v2.3 tags and ID3v2.4 > tags? > > > > Your thoughts on these issues would be very appreciated. > > > > Chris > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Dr J.C. Newell > > Digital Media Group, BBC Research & Development > > Kingswood Warren, Woodland Way, Tadworth, Surrey > > KT20 6NP UK > > mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd > > Tel: +44 (0)1737 839659 > > Switchboard: +44 1737 839500 > > Fax: +44 (0)1737 839665 > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > > For additional commands, e-mail: id3v2-help at id3.org > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at audiott.com Sat Nov 26 07:46:55 2005 From: id3v2 at audiott.com (Michal Vician) Date: Sat, 26 Nov 2005 16:46:55 +0100 (CET) Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: <4da424620511251914o43262f92pc19117c8cf3241a2@mail.gmail.com> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <6.1.2.0.2.20051125161419.02cf2418@pop3> <4da424620511251914o43262f92pc19117c8cf3241a2@mail.gmail.com> Message-ID: <14398.195.91.64.52.1133020015.squirrel@195.91.64.52> > Any MP3 reader/library that doesn't handle unknown tags is poorly > implemented *****and breaks the standard***** (at least v2.3 and v2.4 -- I > haven't read prior standards). What? Breaks the standard? I don't agree with you. There is nothing stated in ID3v2 specification that tag may contain other frames. There is only allowance in custom frames (X,Y,Z), but nothing stated that my application should handle frames like "HAHA" or "TOOT". I think that the only problem is that the previous specifications of ID3v2 don't include a statement that frames with an unrecognised Frame ID should ignored and skipped using the Size field. Regards. Miso -- Michal Vician id3v2 at audiott.com http://www.audiott.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From chris.newell at rd.bbc.co.uk Fri Nov 11 02:02:19 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Fri, 11 Nov 2005 10:02:19 +0000 Subject: [ID3 Dev] Suggestion - uniform "Element ID" creation In-Reply-To: <48758.195.91.64.54.1131648555.squirrel@195.91.64.54> References: <48758.195.91.64.54.1131648555.squirrel@195.91.64.54> Message-ID: <6.1.2.0.2.20051111093213.02e0f178@pop3> At 18:49 10/11/2005, Michal Vician wrote: >I have a suggestion to make the creation of "Element ID" uniform. Michal, Thank you for the input. I can see the merit of your "uniform Element ID" concept in terms of simplicity for parsers. However, I'm concerned that it would block one of the useful capabilities of the current scheme - the ability to reference chapters from more than one table of contents. For example, for the recording of a rock festival you could create a CHAP frame for each song and then index these frames in three ways using different CTOCs to provide: - a full, temporally ordered table of contents - a table providing an index of band names or genres - a table listing highlights I think it's important to maintain this kind of flexibility because it opens up all kinds of interesting opportunities for content developers. Thanks also for the example content. I'm having problems with this because my chapter tool application is based on the Jens Vonderheide API and this doesn't currently support ID3v2.4. Does anyone have a fix for this? Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr J.C. Newell Digital Media Group, BBC Research & Development Kingswood Warren, Woodland Way, Tadworth, Surrey KT20 6NP UK mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd Tel: +44 (0)1737 839659 Switchboard: +44 1737 839500 Fax: +44 (0)1737 839665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From py.thoulon at gmail.com Mon Nov 21 10:49:15 2005 From: py.thoulon at gmail.com (Pyt) Date: Mon, 21 Nov 2005 19:49:15 +0100 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: <6.1.2.0.2.20051121143508.02f2feb8@pop3> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> Message-ID: One question is problably whether existing implementations are lenient enough to accomodate Chapter frames in v2.3 or 2.4 tags, even though they are not part of the original spec (for example, how do the existing public implementations like ID3Lib or the java library behave ?). If so, then I would vote for having just an addendum, and making the frames legal in v2.3and 2.4. Otherwise, we have to go up one revision. For what it's worth... Pyt. On 11/21/05, Chris Newell wrote: > > Colleagues, > > The Chapter Frame proposal has been available on the ID3 web site for a > while now and feedback on the reflector has tailed off. I'm wondering how we > could move things forward. One issue not covered by the proposal is how > support for the Chapter Frames might be introduced and this raises a couple > of questions: > > - should there be a new version of the ID3v2 specification which > incorporates Chapter Frames or an addendum which describes Chapter Frames > and nothing else? > > - should we allow Chapter Frames to be used in ID3v2.3 tags and ID3v2.4tags? > > Your thoughts on these issues would be very appreciated. > > Chris > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Dr J.C. Newell > Digital Media Group, BBC Research & Development > Kingswood Warren, Woodland Way, Tadworth, Surrey > KT20 6NP UK > mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd > Tel: +44 (0)1737 839659 > Switchboard: +44 1737 839500 > Fax: +44 (0)1737 839665 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kochakaden at gmail.com Fri Nov 18 04:12:05 2005 From: kochakaden at gmail.com (Grits Lars) Date: Fri, 18 Nov 2005 21:12:05 +0900 Subject: [ID3 Dev] Some questions on the spec Message-ID: <4ab5c4700511180412v1455c0aco46691f2feaa8a67d@mail.gmail.com> Hi everyone, I'm attempting a java implementation of the id3 tag scheme, but I've run into some difficulties interpreting the specs. Could someone help explain some of the following? id3v2.4.0-structure.txt: Section 3.2: Here, the CRC value is described as "a 35 bit synchsafe integer, leaving the upper four bits always zeroed". Are the bits cleared from the 35-bit result to give a 31 bit value, or are the bits cleared from the encoded (5 byte) value to give a 32-bit result once decoded? id3v2.4.0-frames.txt: Section 4.5 According to the description, the only allowed timing formats are absolute times from the beginning of the file. Later, the following description is given: "The 'Time stamp' is set to zero if directly at the beginning of the sound or after the previous event." Does this mean that the time stamps are not always absolute? Also, what is meant by "the beginning of the sound"? Is that the point that would be marked by $02 (intro start)? Section 4.6: Am I correct in assuming that "Bytes between reference" and "Milliseconds between reference" are both 24-bit values? Are the deviation values to be interpreted as signed or unsigned integers? Section 4.7: This section describes a tag that starts with a time format byte, followed by a series of tempo codes. Each tempo code has a tempo part (1-2 bytes) followed by a time part. The next paragraph talks about a tempo descriptor, which is not defined elsewhere in the document. How is a tempo descriptor composed? How is it stored in the tag? Is a tempo descriptor the collection of all the tempo codes? If so, how do you know when the tempo codes finish and the time stamp starts? Section 4.9: "The 'time stamp' is set to zero or the whole sync is omitted if located directly at the beginning of the sound." I don't really understand this part... Why would you omit a sync if you need to show lyrics at the start of the song? Is the beginning of the sound equivalent to the beginning of the audio stream? If so, then it's self-evident that the timestamp would be 0... Or am I missing something? Section 4.11: What are the units for peak volume? Is it the same fixed point integer format as the volume adjustment, but as unsigned values? Section 4.19: If more than one encryption frame is present in a tag, does that mean that the file has been encrypted with multiple schemes? If so, is there a set order that the decryption must be applied? (for example, if there's an AES encryption frame, and then a Blowfish encryption frame, does this mean that the file has been run through both algorithms and must be run through both decryptors before becoming readable? Which decryptor runs first?) Also, what happens if the encryption frames have different preview windows? Is this considered an error? Best regards, Kochakaden -------------- next part -------------- An HTML attachment was scrubbed... URL: From rmanson at gracenote.com Wed Nov 9 11:39:46 2005 From: rmanson at gracenote.com (Robert Manson) Date: Wed, 9 Nov 2005 11:39:46 -0800 Subject: [ID3 Dev] Worst cases of "ID3 offenders"? Message-ID: <27905705A869164CBE58B96BA8547557269EB8@mail.internal.cddb.com> You are right that Windows XP does not support v2.4. It does claim to support v2.3, however, and its implementation of the standard is flawed due to the fact that it cannot read "16-Bit Unicode 2.0" strings encoded as big endian. -----Original Message----- From: Andy Kernahan [mailto:andrew.kernahan at btinternet.com] Sent: Wednesday, November 09, 2005 11:13 AM To: id3v2 at id3.org Subject: Re: [ID3 Dev] Worst cases of "ID3 offenders"? XP doesn't actually support V2.4.0 and therefore has no need to support UTF16-BE. ----- Original Message ----- From: "Robert Manson" To: Sent: Wednesday, November 09, 2005 1:38 AM Subject: RE: [ID3 Dev] Worst cases of "ID3 offenders"? Windows XP does not read UTF16-BE encoded text frames -----Original Message----- From: Paul Grebenc [mailto:jid3 at blinkenlights.org] Sent: Tuesday, November 08, 2005 2:51 PM To: id3v2 at id3.org Subject: Re: [ID3 Dev] Worst cases of "ID3 offenders"? The MP3ext Windows explorer extension corrupts all of its ID3 v2 tags by repeatedly writing an advertisement for itself (ie. "MP3ext V3.3.18(unicode)") in the tag padding, which violates the spec. Winamp ignores the last frame in a v2.3.0 tag if there is no padding in the tag. Mixmeister BPM analyzer (among others it seems) writes floating point values to the TBPM frame. Paul --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From py.thoulon at gmail.com Wed Nov 2 10:37:09 2005 From: py.thoulon at gmail.com (Pyt) Date: Wed, 2 Nov 2005 19:37:09 +0100 Subject: [ID3 Dev] Labels And Release Number In-Reply-To: <0C0E9486-37AC-4B49-BCB7-898BAC438BA0@gmail.com> References: <0C0E9486-37AC-4B49-BCB7-898BAC438BA0@gmail.com> Message-ID: There are the TPUB (Publisher) and TSRC (International Standard Recording Code) frames which may correspond to what you need. But that does not mean they are used/rendered by common MP3 players... Pyt. On 11/2/05, Robot Gunslinger wrote: > > One thing that always bugged me about id3 is it's inability to provide > a field for "Label" and "Release Number". > > It's especially annoying if you're a fan of electronic or indie > music, where > where labels (netlabels or otherwise) still are of importance, > especially for collectors. > > I am not a programmer and I don't know if this feature has already been > implemented in the latest release, but judging from the most common > mp3 players, I guess it hasn't. > > I am sure this can't be too hard to integrate and would be a very > useful feature > for Netlabel releases and adding the possibility to defining the > Label and the Catalog Number of an id3 tagged music file sure is an > valid > addition to the metadata capabilities of the id3 standard, so please > guys > just put it in there. > > > cheers > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From id3v2 at audiott.com Wed Nov 9 05:10:40 2005 From: id3v2 at audiott.com (Michal Vician) Date: Wed, 9 Nov 2005 14:10:40 +0100 (CET) Subject: [ID3 Dev] Re: Audio TT translation In-Reply-To: <1cd7d6da0511090341k3b583b08m661aee634744849b@mail.gmail.com> References: <1cd7d6da0511090341k3b583b08m661aee634744849b@mail.gmail.com> Message-ID: <9392.195.91.64.54.1131541840.squirrel@195.91.64.54> > I'm OK to help you for translation in french. Hi Manu. I'm lucky now. AudioTT is only a few weeks old - you will be the first translator. > What's the work ? you send me .txt file with text to translate or you've > something else ? Yes, AudioTT uses text files as language packs, but I prefere suffix "lng" rather than "txt". Take a look at this page please: http://www.audiott.com/home/lngpacks.html. You may learn here more about how to. Unfortunately, I haven't translated entire Slovak language pack to the English (I'm Slovak). I will have translated it by the end of this week. Therefore some passages of English lng pack are still in Slovak. Despite that you may begin with the translation. If you allow me I will add your name to the list of "special thanks" - maybe you may write your full name. Many thanks. > Would you be ok to release your source code ? ( eventually , if you don't > envisage to make money , to put him in gpl licence ) , it can be a way to > me to see how resolves some problemes. Sorry, I'm not about to release AudioTT source codes. AudioTT is free to use, copy... but not open source. But if you need some help, just be more concrete about that and I will try to help you. Cau -- Michal Vician id3v2 at audiott.com http://www.audiott.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From chris.newell at rd.bbc.co.uk Fri Nov 25 08:36:15 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Fri, 25 Nov 2005 16:36:15 +0000 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> Message-ID: <6.1.2.0.2.20051125161419.02cf2418@pop3> At 18:49 21/11/2005, Pyt wrote: >One question is problably whether existing implementations are lenient enough to accomodate Chapter frames in v2.3 or 2.4 tags, even though they are not part of the original spec (for example, how do the existing public implementations like ID3Lib or the java library behave ?). If so, then I would vote for having just an addendum, and making the frames legal in v2.3 and 2.4. > >Otherwise, we have to go up one revision. I've tried files tagged with Chapter Frames carried in version 2.3 tags with a number of media players running on Windows. The following played the files without problems and could decode the standard tags: QuickTime VLC iTunes However, although Windows Media Player 6.4 played the file it appeared unable to read any information from the tag when the Chapter Frames were present. It looks like a new version of the standard would probably be the safest option but I'm concerned this might discourage support for Chapter Frames. Chris --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From birkirb at stoicviking.net Tue Nov 8 17:46:18 2005 From: birkirb at stoicviking.net (Birkir A. Barkarson) Date: Wed, 09 Nov 2005 10:46:18 +0900 Subject: [ID3 Dev] Worst cases of "ID3 offenders"? In-Reply-To: <000801c5e4ab$c8dd3d10$b1000105@kendle.com> References: <6.2.5.6.0.20051030223858.02ecdb90@earthlink.net> <6.2.5.6.0.20051031034035.02e9f310@earthlink.net> <000901c5de76$c4d6b600$0500000a@MARVIN> <6.2.5.6.0.20051108075210.02cafa28@earthlink.net> <000801c5e4ab$c8dd3d10$b1000105@kendle.com> Message-ID: <437154EA.9070903@stoicviking.net> I made these notes a few weeks back when working on a ID3 library. iTunes Generally will play any MP3 even if it fails to parse the tag. Windows Media Player Does not seem to support extended headers. Does not seem to support unsynchronization. Very sensitive to ill formatted tags and won't play an MP3 if such a tag is detected. Quicktime Player Similar to iTunes but doesn't correctly display unicode characters. VLC Media Player Sensitive to ill formatted tags and will crash with a memory read error. WinAmp 5 Lite General compatability, but will not display unicode characters in default mode. I often work with non english character sets so it's a big issue to get them displayed correctly. I noted some ID3 editors write any character sets to the tags, spoofing them as ISO8859-1, usually opting for the system default character set. Others will break unicode tags if they contain non english characters. BAB Mitchell S. Honnert wrote: > In testing out my ID3 tag library, I've come across dozens of cases of > mangled v2.3 tags. If there's some way that a tag can be screwed up, > I've probably seen it. I've done my best to have my lib gracefully > handle these exceptions, but they're frustrating none-the-less. It's > not so bad when the offending file looks like it's just the victim of > simple file corruption, but when it's obvious that the author of the > app/lib/encoder that wrote the frame decided to just reformat a standard > frame or make up their own frame, I really cringe. > > > > What's even more frustrating it to get a bug report from a user of my > library only to have it turn out that it's one of these renegade > frames. I've posted the common offenders I know about to my library's > page, but I'm curious to see if any of you know of any more. Here are > the bigger ones I know about. > > > > - WinAmp will record apparently gibberish bytes in the Language field of > the Comments (COMM) frame. I don't see any pattern to the bytes, so I'm > guessing that it's just some uninitialized variable that's getting > written the Language bytes. > > > > - WinAmp ignores the Description field of the Comments (COMM) frame. It > displays whichever COMM frame happens to be read last. (So your > Comments frame written in another app may "disappear" in WinAmp.) > > > > - iTunes adds an extra nullchar to the end of the Comments frame. > > > > - iTunes uses a non-standard frame (TCMP) to record the "Part of a > compilation" flag. > > > > - Some app/lib/encoder adds a non-standard NCON frame to the ID3 v2.3 > tag. I've seen the errant frame hundreds of times, but I've never been > able to track down its source. (Man, I wish I could find the culprit who > is writing NCON frames. Gah!) > > > > > > > So, does anyone know of any other popular applications, libraries, or > encoders that write non-standard, corrupted ID3 tags? > > > > (Part of me just wanted to vent about applications that break the > standard I work so hard to adhere to, but I do still think it would help > reduce some of the support requests I get or at least lessen the > perception of people that use my lib that it's broken when it's really > the tag that's broken.) > > > > Thanks, > > > > Mitchell S. Honnert > > UltraID3Lib - http://home.fuse.net/honnert/hundred/?UltraID3Lib > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at northpb.com Mon Nov 7 14:39:32 2005 From: id3v2 at northpb.com (Dan O'Neill) Date: Mon, 07 Nov 2005 14:39:32 -0800 Subject: [ID3 Dev] How do I get my lib on the Implementations page of www.id3.org? In-Reply-To: <003501c5e3ba$0374dde0$b1000105@kendle.com> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> Message-ID: <436FD7A4.1050102@northpb.com> Mitchell S. Honnert wrote: > I just joined this list a couple of weeks ago and, after reading all of > the messages so far, I'm wondering why I didn't join sooner! It looks > like I finally found a likeminded group of people dedicated to the ID3 > standard. Anyway... You have, and welcome to the group. > (Incidentally, my library is called UltraID3Lib and is a Microsoft .NET > DLL written in VB.NET. It's fully object-oriented and implements all > but a handful of the standard frames as distinct classes. It supports > read and write of v1, v2.3, but not v2.4 yet.) > > Anyway, does anyone know how I would go about getting a link to my > library on the Implementations page of www.id3.org > ? You post it to the mailing list and I edit the HTML and link to your library. That easy. Look in the implementations section tomorrow. Is there some kind of certification process a > library has to go through to get posted on this page? I've e-mailed > Martin Nilsson these same questions over the years that I've been > developing my library, but I've never received a response. There's been a glaring need for a reference test suite, but no one has taken the charge (yet) to put something together. Martin has not been responsive to email for quite some time, therefore, I've volunteered to provide maintenance services for the ID3.org standard and this interested group of people. Again, welcome to the list. dano --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From rmanson at gracenote.com Tue Nov 8 17:53:13 2005 From: rmanson at gracenote.com (Robert Manson) Date: Tue, 8 Nov 2005 17:53:13 -0800 Subject: [ID3 Dev] Worst cases of "ID3 offenders"? Message-ID: <27905705A869164CBE58B96BA8547557269EB7@mail.internal.cddb.com> >I often work with non english character sets so it's a big issue to get >them displayed correctly. I noted some ID3 editors write any character >sets to the tags, spoofing them as ISO8859-1, usually opting for the >system default character set. Others will break unicode tags if they >contain non english characters. ID3 tag libraries should not write text encoded in ISO8859-1 due to the fact that so many files have been tagged as being IS08859-1 when in fact the text was encoded in whatever the windows "ANSI" code page was. Try converting shift-jis to iso latin 1 and see what happens. -----Original Message----- From: Birkir A. Barkarson [mailto:birkirb at stoicviking.net] Sent: Tuesday, November 08, 2005 5:46 PM To: id3v2 at id3.org Subject: Re: [ID3 Dev] Worst cases of "ID3 offenders"? I made these notes a few weeks back when working on a ID3 library. iTunes Generally will play any MP3 even if it fails to parse the tag. Windows Media Player Does not seem to support extended headers. Does not seem to support unsynchronization. Very sensitive to ill formatted tags and won't play an MP3 if such a tag is detected. Quicktime Player Similar to iTunes but doesn't correctly display unicode characters. VLC Media Player Sensitive to ill formatted tags and will crash with a memory read error. WinAmp 5 Lite General compatability, but will not display unicode characters in default mode. I often work with non english character sets so it's a big issue to get them displayed correctly. I noted some ID3 editors write any character sets to the tags, spoofing them as ISO8859-1, usually opting for the system default character set. Others will break unicode tags if they contain non english characters. BAB Mitchell S. Honnert wrote: > In testing out my ID3 tag library, I've come across dozens of cases of > mangled v2.3 tags. If there's some way that a tag can be screwed up, > I've probably seen it. I've done my best to have my lib gracefully > handle these exceptions, but they're frustrating none-the-less. It's > not so bad when the offending file looks like it's just the victim of > simple file corruption, but when it's obvious that the author of the > app/lib/encoder that wrote the frame decided to just reformat a standard > frame or make up their own frame, I really cringe. > > > > What's even more frustrating it to get a bug report from a user of my > library only to have it turn out that it's one of these renegade > frames. I've posted the common offenders I know about to my library's > page, but I'm curious to see if any of you know of any more. Here are > the bigger ones I know about. > > > > - WinAmp will record apparently gibberish bytes in the Language field of > the Comments (COMM) frame. I don't see any pattern to the bytes, so I'm > guessing that it's just some uninitialized variable that's getting > written the Language bytes. > > > > - WinAmp ignores the Description field of the Comments (COMM) frame. It > displays whichever COMM frame happens to be read last. (So your > Comments frame written in another app may "disappear" in WinAmp.) > > > > - iTunes adds an extra nullchar to the end of the Comments frame. > > > > - iTunes uses a non-standard frame (TCMP) to record the "Part of a > compilation" flag. > > > > - Some app/lib/encoder adds a non-standard NCON frame to the ID3 v2.3 > tag. I've seen the errant frame hundreds of times, but I've never been > able to track down its source. (Man, I wish I could find the culprit who > is writing NCON frames. Gah!) > > > > > > > So, does anyone know of any other popular applications, libraries, or > encoders that write non-standard, corrupted ID3 tags? > > > > (Part of me just wanted to vent about applications that break the > standard I work so hard to adhere to, but I do still think it would help > reduce some of the support requests I get or at least lessen the > perception of people that use my lib that it's broken when it's really > the tag that's broken.) > > > > Thanks, > > > > Mitchell S. Honnert > > UltraID3Lib - http://home.fuse.net/honnert/hundred/?UltraID3Lib > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From andrew.kernahan at btinternet.com Wed Nov 9 11:13:19 2005 From: andrew.kernahan at btinternet.com (Andy Kernahan) Date: Wed, 9 Nov 2005 19:13:19 -0000 Subject: [ID3 Dev] Worst cases of "ID3 offenders"? References: <27905705A869164CBE58B96BA854755703659145@mail.internal.cddb.com> Message-ID: <000c01c5e561$a57f29d0$0500000a@MARVIN> XP doesn't actually support V2.4.0 and therefore has no need to support UTF16-BE. ----- Original Message ----- From: "Robert Manson" To: Sent: Wednesday, November 09, 2005 1:38 AM Subject: RE: [ID3 Dev] Worst cases of "ID3 offenders"? Windows XP does not read UTF16-BE encoded text frames -----Original Message----- From: Paul Grebenc [mailto:jid3 at blinkenlights.org] Sent: Tuesday, November 08, 2005 2:51 PM To: id3v2 at id3.org Subject: Re: [ID3 Dev] Worst cases of "ID3 offenders"? The MP3ext Windows explorer extension corrupts all of its ID3 v2 tags by repeatedly writing an advertisement for itself (ie. "MP3ext V3.3.18(unicode)") in the tag padding, which violates the spec. Winamp ignores the last frame in a v2.3.0 tag if there is no padding in the tag. Mixmeister BPM analyzer (among others it seems) writes floating point values to the TBPM frame. Paul --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at audiott.com Mon Nov 21 14:39:33 2005 From: id3v2 at audiott.com (Michal Vician) Date: Mon, 21 Nov 2005 23:39:33 +0100 (CET) Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: <6.1.2.0.2.20051121143508.02f2feb8@pop3> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> Message-ID: <30155.195.91.64.54.1132612773.squirrel@195.91.64.54> > - should there be a new version of the ID3v2 specification which > incorporates Chapter Frames or an addendum which describes Chapter Frames > and nothing else? Hi. My first ID3v2 library was built in supposition that there can be only frames which are defined in ID3v2 specification. Therefore if there had been an "unknown" frame found in ID3v2 tag, my application would have ignored the whole tag. Why? Because there was suspicion that tag is broken. This was the way of protection against broken tags -> whenever something was assumed to be wrong/something unexpected was found, the application simply ignored whole ID3v2 tag rather then risk the RuntimeException... Nobody can guarantee that all applications will run properly! Therefore I would rather a new version of ID3v2 specification was released. Regards Miso -- Michal Vician id3v2 at audiott.com http://www.audiott.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From mitch at honnert.com Mon Nov 7 08:40:50 2005 From: mitch at honnert.com (Mitchell S. Honnert) Date: Mon, 7 Nov 2005 11:40:50 -0500 Subject: [ID3 Dev] How do I get my lib on the Implementations page of www.id3.org? References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> Message-ID: <003501c5e3ba$0374dde0$b1000105@kendle.com> I just joined this list a couple of weeks ago and, after reading all of the messages so far, I'm wondering why I didn't join sooner! It looks like I finally found a likeminded group of people dedicated to the ID3 standard. Anyway... I honestly hope this is the right forum, but I'm looking for some help in "getting the word out" on an ID3 library I've written (and made available online for free.) Based on some of the previous messages to this list, I get the sense that the other people on this list might have some interest in promoting a library that strictly adheres to the ID3 standard. (Incidentally, my library is called UltraID3Lib and is a Microsoft .NET DLL written in VB.NET. It's fully object-oriented and implements all but a handful of the standard frames as distinct classes. It supports read and write of v1, v2.3, but not v2.4 yet.) Anyway, does anyone know how I would go about getting a link to my library on the Implementations page of www.id3.org? Is there some kind of certification process a library has to go through to get posted on this page? I've e-mailed Martin Nilsson these same questions over the years that I've been developing my library, but I've never received a response. I see an ActiveX components section of the list, so I'm assuming it wouldn't be a problem to add a .NET section as well. Again, I apologize if this is not the right venue for this request. I really don't want to come across as "pimping" my library (as those crazy kids these days would say); it's just that I've put a lot of blood, sweat, and tears into the (free) library and it'd be nice to see it used on a wider basis. Getting UltraID3Lib listed on www.id3.org (not to mention making the people on this list aware of the library) seemed like an appropriate way to do this. For those interested, UltraID3Lib can be found here... http://home.fuse.net/honnert/hundred/?UltraID3Lib Regards, - Mitchell S. Honnert -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.newell at rd.bbc.co.uk Tue Nov 8 06:45:08 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Tue, 08 Nov 2005 14:45:08 +0000 Subject: [ID3 Dev] New member In-Reply-To: <45601.195.91.64.54.1131402561.squirrel@195.91.64.54> References: <45601.195.91.64.54.1131402561.squirrel@195.91.64.54> Message-ID: <6.1.2.0.2.20051108143503.02fdfdf8@pop3> At 22:29 07/11/2005, you wrote: >I'm interested in ID3v2, therefore I hope I will be helpful joining the >mailing list. I've already made a core for reading and writing CHAP and >CTOC frames... However, it can be done only from the command line. Now >it's only a question of time to make an "engaging" GUI for it. Michal, Great to hear you've looked at Chapter Frames. Perhaps we could exchange some content to explore interoperability? Alternatively, you could try exchanging content with my authoring tool: http://sourceforge.net/projects/id3v2-chap-tool Let me know if you have any problems. Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr J.C. Newell Digital Media Group, BBC Research & Development Kingswood Warren, Woodland Way, Tadworth, Surrey KT20 6NP UK mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd Tel: +44 (0)1737 839659 Switchboard: +44 1737 839500 Fax: +44 (0)1737 839665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at audiott.com Mon Nov 14 12:11:10 2005 From: id3v2 at audiott.com (Michal Vician) Date: Mon, 14 Nov 2005 21:11:10 +0100 (CET) Subject: [ID3 Dev] Suggestion - uniform 'Element ID' creation In-Reply-To: <6.1.2.0.2.20051114092322.02e86780@pop3> References: <48758.195.91.64.54.1131648555.squirrel@195.91.64.54> <6.1.2.0.2.20051111093213.02e0f178@pop3> <7329.195.91.64.54.1131731492.squirrel@195.91.64.54> <6.1.2.0.2.20051114092322.02e86780@pop3> Message-ID: <50392.195.91.64.54.1131999070.squirrel@195.91.64.54> > At 17:51 11/11/2005, you wrote: >>> I can see the merit of your "uniform Element ID" >>> concept in terms of simplicity for parsers. However, I'm concerned that >>> it >>> would block one of the useful capabilities of the current scheme - the >>> ability to reference chapters from more than one table of contents. >>> >>> For example, for the recording of a rock festival you could create a >>> CHAP >>> frame for each song and then index these frames in three ways using >>> different CTOCs to provide: >>> - a full, temporally ordered table of contents >>> - a table providing an index of band names or genres >>> - a table listing highlights >>> >>> I think it's important to maintain this kind of flexibility because it >>> opens up all kinds of interesting opportunities for content developers. >> >>Oh yes. I had forgotten that there may be more than one table of contents >>in each tag. Therefore I have adjusted my "uniform Element ID" concept so >>that there may be more than one table of contents. How? >>Just by adding the "X#" at the very beggining of each Element ID. >>X - the unigue number identifier of each table of contents. >>Here is example of 2 tables of contents written in one ID3 tag (there are >>also some CHAP frames which are not referenced by any CTOC frame): >> >>{THIS IS TABLE OF CONTENTS #1} >>1#0 (root - zero level) >> 1#1 (1st level) >> 1#2 >> 1#3 >> 1#3.1 (2nd level) >> 1#3.2 >> 1#3.3 >> 1#3.3.1 (3rd level) >> 1#3.3.2 >> 1#3.3.3 >> 1#3.3.3.1 (4th level) >> 1#3.3.3.2 >> ... > > Michal, > > How does this scheme allow the an individual chapter frame to be > referenced by more than one table of contents? In the example scenario > above, the chapters representing individual songs may be referenced three > times. Oh yes. My suggestion seems to be rubbish :-) I was probably quite tired when writing it.... forget it -- Michal Vician id3v2 at audiott.com http://www.audiott.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From chris.newell at rd.bbc.co.uk Thu Nov 3 01:31:51 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Thu, 03 Nov 2005 09:31:51 +0000 Subject: [ID3 Dev] Labels And Release Number In-Reply-To: <43698AB0.5060409@northpb.com> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> Message-ID: <6.1.2.0.2.20051103092817.02e93278@pop3> At 03:57 03/11/2005, you wrote: >A full working reference model would be the ideal thing to have. Anyone want to put all the pieces together? > > MP3 file w/2.4.0 tags w/CHAP & CTOC frames > library + sample code that wrote the above v2.4.0 tags > player that can read and use these tags Dan, I'd would be happy to add chapter tags to this reference content. Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr J.C. Newell Digital Media Group, BBC Research & Development Kingswood Warren, Woodland Way, Tadworth, Surrey KT20 6NP UK mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd Tel: +44 (0)1737 839659 Switchboard: +44 1737 839500 Fax: +44 (0)1737 839665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From chris.newell at rd.bbc.co.uk Mon Nov 21 07:02:55 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Mon, 21 Nov 2005 15:02:55 +0000 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: <436FD7A4.1050102@northpb.com> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> Message-ID: <6.1.2.0.2.20051121143508.02f2feb8@pop3> Colleagues, The Chapter Frame proposal has been available on the ID3 web site for a while now and feedback on the reflector has tailed off. I'm wondering how we could move things forward. One issue not covered by the proposal is how support for the Chapter Frames might be introduced and this raises a couple of questions: - should there be a new version of the ID3v2 specification which incorporates Chapter Frames or an addendum which describes Chapter Frames and nothing else? - should we allow Chapter Frames to be used in ID3v2.3 tags and ID3v2.4 tags? Your thoughts on these issues would be very appreciated. Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr J.C. Newell Digital Media Group, BBC Research & Development Kingswood Warren, Woodland Way, Tadworth, Surrey KT20 6NP UK mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd Tel: +44 (0)1737 839659 Switchboard: +44 1737 839500 Fax: +44 (0)1737 839665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From vician at audiott.com Fri Nov 4 00:37:35 2005 From: vician at audiott.com (Michal Vician) Date: Fri, 4 Nov 2005 09:37:35 +0100 (CET) Subject: AudioTT Message-ID: <8731.195.91.64.55.1131093455.squirrel@195.91.64.55> Hi Dan! Thank you for the mailing list explanation. I have decided to join it next week. Why? First I want to finish my web site (http://audiott.com). Currently it looks to be very shoddy. After improving it I will join the mailing list and present AudioTT and myself to all members. Where can I find the list of current mailing list members? As I said, first I want to improve my site. The problem is, that I don't have much free time for this things. Therefore I'm willing to create new ftp account to anybody, who would like to do the audiott.com service. If you know somebody, just let me know please. > Where are you located in the world? I am in La Jolla, California. Maybe you want to know more about myself. I am in Nove Zamky, Slovakia, EU. I'm going to study nucleonics in Bratislava (the capital of Slavakia) next year. To the future I'm intending to study in technical university of Munchen (Munich... or how is it in english). Programming is just my hobby. I have leart Java for 2 years, but I had learnt many other programming languages before (C++, C#, ActionScript - Macromedia Flash language...). Once I have relized, that I hadn't done any useful program. Thus I had a look through the internet and found www.id3.org. I have found it very useful (I have a big MP3 collection). Now you can see result of my effort in AudioTT... Maybe you can also write more about yourself. Regards. -- Michal Vician www.audiott.com vician at audiott.com From chris.newell at rd.bbc.co.uk Fri Nov 25 08:11:37 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Fri, 25 Nov 2005 16:11:37 +0000 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <30155.195.91.64.54.1132612773.squirrel@195.91.64.54> <003801c5ef19$143c3c80$4a046c6b@sisodomain.com> Message-ID: <6.1.2.0.2.20051125154923.03179e38@pop3> At 06:12 22/11/2005, Pyt wrote: >I've had initially the same problem with the new frames, but a very small modification of my library (which in not able to fully parse all frames, anyway) allowed me to take them in as binary (unparsed) frames, as long as the header is well-formed. > >As far as the "sync" goes, in case of a corrupt frame, you can always: > >1. Check that the size of the frame is correct (there is another valid frame header or padding right after the frame) >2. If not, go into detailed analysis of the file right after the corrupt frame, looking for a valid header pattern. > >It's not fool-proof, but it will work in most cases. > >Pyt. > >On 11/22/05, Shiv Charan Panjeta <shivcharan.p at samsung.com> wrote: >I am also facing the similar problem . if any of the frame is not understood >.. I have to quite parsing. >Is it make sense to introduce some sync mechanism like (MP3 frame) in >future specs to recover the corrupted frames.? I think that any future version of the specification should include a statement that frames with an unrecognised Frame ID should ignored and skipped using the Size field. This would allow new frame types to be introduced in a backwards compatible manner. Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr J.C. Newell Digital Media Group, BBC Research & Development Kingswood Warren, Woodland Way, Tadworth, Surrey KT20 6NP UK mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd Tel: +44 (0)1737 839659 Switchboard: +44 1737 839500 Fax: +44 (0)1737 839665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From tsorensen at gmail.com Thu Nov 3 06:18:40 2005 From: tsorensen at gmail.com (Tom Sorensen) Date: Thu, 3 Nov 2005 09:18:40 -0500 Subject: [ID3 Dev] Labels And Release Number In-Reply-To: <43698AB0.5060409@northpb.com> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> Message-ID: <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> On 11/2/05, Dan O'Neill wrote: > Brian Mearns wrote: > > The ID3v2.4.0 spec has been around since late 2000, but as far as I know > > most major digital media players still base their parsing and writing of > > tags on the 2.3 standard. > > A full working reference model would be the ideal thing to have. Anyone > want to put all the pieces together? > > MP3 file w/2.4.0 tags w/CHAP & CTOC frames > library + sample code that wrote the above v2.4.0 tags > player that can read and use these tags Unless you have a real, working, usable library in a major language (C being the most likely candidate), it won't be widely adopted. I think the reason that 2.3 is still so predominant is because the most widely used library, id3lib, still only does 2.3 (and it hasn't been touched in ~2 years, despite several showstopper bugs). > b. Which library out there do people feel is the *best* example of > an ID3 tag editor that supports v1, v2.3 and v2.4 tags correctly? For C/C++ there isn't one that I've found. id3lib does v1 and v2.3 fairly well, but the API is really quite bad, and the project seems moribund. TagLib does v1 and v2.4, as well as others, but I've found numerous bugs in it -- it's API is decent though. Both have fairly miserable documentation (TagLib being somewhat better). Both read v2.2, and TagLib also reads v2.3, but only write out one version. --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From chris.newell at rd.bbc.co.uk Wed Nov 30 02:14:28 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Wed, 30 Nov 2005 10:14:28 +0000 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <6.1.2.0.2.20051125161419.02cf2418@pop3> <4da424620511251914o43262f92pc19117c8cf3241a2@mail.gmail.com> <14398.195.91.64.52.1133020015.squirrel@195.91.64.52> <6.1.2.0.2.20051128165838.02da7b70@pop3> <57148.195.91.64.54.1133283276.squirrel@195.91.64.54> Message-ID: <6.1.2.0.2.20051130095722.02f37a90@pop3> At 06:27 30/11/2005, py.thoulon at gmail.com wrote: >I would vote for the addendum. I believe it is easier from an implementation standpoint to authorize Chapter frames in existing ID3v2.3/4 implementations (skipping them properly would be enough) than to add support for a new version. > >Moreover, people who will be adding these frames to files will know what they want to do with them, and will most likely test the programs that they want to use them with. Agreed. Having revisited the v2.4 spec I've found that there is support for this approach in the overview section: "ID3v2 is designed to be as flexible and expandable as possible to meet new meta information needs that might arise. To achieve that ID3v2 is constructed as a container for several information blocks, called frames, whose format need not be known to the software that encounters them. At the start of every frame is an unique and predefined identifier, a size descriptor that allows software to skip unknown frames and a flags field." A similar statement is present in v2.2 and v2.3. Apologies for not noticing this earlier! This means we could publish an addendum describing how the Chapter Frames could be used in both v2.3 and v.2.4 tags. Would it also be useful to provide a version of the frames for use with v2.2? I'll try to draft a first stab at an addendum for everyone to review. Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr J.C. Newell Digital Media Group, BBC Research & Development Kingswood Warren, Woodland Way, Tadworth, Surrey KT20 6NP UK mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd Tel: +44 (0)1737 839659 Switchboard: +44 1737 839500 Fax: +44 (0)1737 839665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From py.thoulon at gmail.com Wed Nov 30 05:02:47 2005 From: py.thoulon at gmail.com (Pyt) Date: Wed, 30 Nov 2005 14:02:47 +0100 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: <6.1.2.0.2.20051130095722.02f37a90@pop3> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <6.1.2.0.2.20051125161419.02cf2418@pop3> <4da424620511251914o43262f92pc19117c8cf3241a2@mail.gmail.com> <14398.195.91.64.52.1133020015.squirrel@195.91.64.52> <6.1.2.0.2.20051128165838.02da7b70@pop3> <57148.195.91.64.54.1133283276.squirrel@195.91.64.54> <6.1.2.0.2.20051130095722.02f37a90@pop3> Message-ID: On 11/30/05, Chris Newell wrote: > > Would it also be useful to provide a version of the frames for use with > v2.2? Are there any real implementations of 2.2 out there ? On the other hand, if it's not too much work... Pyt. -------------- next part -------------- An HTML attachment was scrubbed... URL: From id3v2 at audiott.com Tue Nov 29 08:54:36 2005 From: id3v2 at audiott.com (Michal Vician) Date: Tue, 29 Nov 2005 17:54:36 +0100 (CET) Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: <6.1.2.0.2.20051128165838.02da7b70@pop3> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> <43695EEF.7040705@coe.neu.edu> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <6.1.2.0.2.20051125161419.02cf2418@pop3> <4da424620511251914o43262f92pc19117c8cf3241a2@mail.gmail.com> <14398.195.91.64.52.1133020015.squirrel@195.91.64.52> <6.1.2.0.2.20051128165838.02da7b70@pop3> Message-ID: <57148.195.91.64.54.1133283276.squirrel@195.91.64.54> > At 15:46 26/11/2005, you wrote: >>> Any MP3 reader/library that doesn't handle unknown tags is poorly >>> implemented *****and breaks the standard***** (at least v2.3 and v2.4 >>> -- I haven't read prior standards). >> >>What? Breaks the standard? I don't agree with you. There is nothing >> stated >>in ID3v2 specification that tag may contain other frames. There is only >>allowance in custom frames (X,Y,Z), but nothing stated that my >> application >>should handle frames like "HAHA" or "TOOT". > > Michal, > > I'm not sure I agree. This is what it says in ID3 version 2.3.0: > > "Identifiers beginning with "X", "Y" and "Z" are for experimental use > and free for everyone to use, without the need to set the > experimental bit in the tag header. Have in mind that someone else > might have used the same identifier as you. All other identifiers are > either used or reserved for future use." > > Where it says that all other identifiers are "reserved for future use" it > must mean they are reserved within the context of ID3 version 2.3. This > means that you might expect to find them in a future revision to version > 2.3. > > In my experience I've found the following version 2.4 frames types inside > version 2.3 tags e.g: > TDRL > > And I've found some frames that aren't defined in any ID3v2 specification: > WFED > TCMP > TGID > TDES > PCST > > If this is typical of what ID3 parsers will accept then it may be > acceptable to allow Chapter frames in ID3 v2.3 and v2.4. > > Chris > Where it says that all other identifiers are "reserved for future use" it > must mean they are reserved within the context of ID3 version 2.3. If it really means that all the other frames are reserved "within the context of ID3v2.3" there is no reason to hesitate and you should release an addendum which describes only the Chapter frames. But, do bear in mind... Doesn it really mean that I should expect that frames in ID3v2.3 ??? > ... This means that you might expect to find them in a > future revision to version 2.3. As you wrote: it only means that I should expect them in a FUTURE revision to 2.3, but there is nothing stated that I should expect them in ID3v2.3 itself ! Thus I can't agree with the claim that applications which do not expect that frames are "poorly implemented" or whatever and I think that these applications certainly DON'T break the standard. > And I've found some frames that aren't defined in any ID3v2 specification: > WFED > TCMP > TGID > TDES > PCST As far as I'm concerned applications which write these frames to ID3v2.3 break the standard. SUMMARY: Everyone should agree with the following (and this is also what I'm trying to say): There is no guarantee that all applications will behave normally if there is CHAP/CTOC frame present in ID3v2.3 tag (Can anyone quarantee that? NO!). However, I agree that it would be much easier for everyone if the addendum will be realeased rather than new version of ID3v2. Now, what way would YOU choose ("addendum" <- or -> "new version") ??? Please, answer the question above as soon as possible so we can finish this topic. Kind regards Miso -- Michal Vician id3v2 at audiott.com http://www.audiott.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From kirkm at xtra.co.nz Tue Nov 1 19:35:34 2005 From: kirkm at xtra.co.nz (Kirk McMillan) Date: Wed, 02 Nov 2005 16:35:34 +1300 Subject: [ID3 Dev] ID3v2 In-Reply-To: <000901c5de76$c4d6b600$0500000a@MARVIN> References: <6.2.5.6.0.20051030223858.02ecdb90@earthlink.net> <6.2.5.6.0.20051031034035.02e9f310@earthlink.net> <000901c5de76$c4d6b600$0500000a@MARVIN> Message-ID: <43683406.2080908@xtra.co.nz> Many thanks to the couple of folk who answered some questions I had a few days ago. I've reluctantly come to the conclusion there simply isn't an ID3v2 spec as such that's being adhered to. Various programs *write* the header frames differently and other programs interpret then differently. BTW, these are just the basic, common headers as used e.g. in Winamp 5. It seems the only solution is write tags in such a way that your preferred reader shows them all. Cheers - Kirk --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From py.thoulon at gmail.com Tue Nov 29 22:27:28 2005 From: py.thoulon at gmail.com (Pyt) Date: Wed, 30 Nov 2005 07:27:28 +0100 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: <57148.195.91.64.54.1133283276.squirrel@195.91.64.54> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <6.1.2.0.2.20051125161419.02cf2418@pop3> <4da424620511251914o43262f92pc19117c8cf3241a2@mail.gmail.com> <14398.195.91.64.52.1133020015.squirrel@195.91.64.52> <6.1.2.0.2.20051128165838.02da7b70@pop3> <57148.195.91.64.54.1133283276.squirrel@195.91.64.54> Message-ID: I would vote for the addendum. I believe it is easier from an implementation standpoint to authorize Chapter frames in existing ID3v2.3/4 implementations (skipping them properly would be enough) than to add support for a new version. Moreover, people who will be adding these frames to files will know what they want to do with them, and will most likely test the programs that they want to use them with. Those bothered by the frames can always use a tolerant tag editor (I use ID3-TagIt - http://www.id3-tagit.de) to remove them. Pyt. On 11/29/05, Michal Vician wrote: > > Now, what way would YOU choose ("addendum" <- or -> "new version") ??? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From id3v2 at audiott.com Mon Nov 7 14:29:21 2005 From: id3v2 at audiott.com (id3v2 at audiott.com) Date: Mon, 7 Nov 2005 23:29:21 +0100 (CET) Subject: [ID3 Dev] New member Message-ID: <45601.195.91.64.54.1131402561.squirrel@195.91.64.54> Hi! I'm a new member of ID3v2 mailing list. Therefore I want to introduce myself: My name is Michal Vician. I live in Slovakia (central europe) and I'm just 18. I've been programming in Java for 1 year, but I had also tried another languages (javascript, actionscript, pascal, c++, c#...). I have a big collection of MP3s, thus I have decided to make an application which is able to edit ID3 tags. This application is also my biggest programming achievment. It's called AudioTT (Audio Tagging Tool) (http://www.audiott.com/) and is made with Java. I'm interested in ID3v2, therefore I hope I will be helpful joining the mailing list. I've already made a core for reading and writing CHAP and CTOC frames... However, it can be done only from the command line. Now it's only a question of time to make an "engaging" GUI for it. Regards -- Michal Vician id3v2 at audiott.com http://www.audiott.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From bmearns at coe.neu.edu Tue Nov 22 06:26:13 2005 From: bmearns at coe.neu.edu (Brian Mearns) Date: Tue, 22 Nov 2005 09:26:13 -0500 Subject: [ID3 Dev] Whole Album Tags In-Reply-To: <6.1.2.0.2.20051122102800.02e12558@pop3> References: <438291CD.4080301@coe.neu.edu> <6.1.2.0.2.20051122102800.02e12558@pop3> Message-ID: <43832A85.9000806@coe.neu.edu> Thanks to all for the advice, I've been seeing all the traffic for CHAP and CTOC, but for some reason never looked at it (sorry). Now that I have, I'm very excited about the potential for these frames, I think they're going to be very powerful, and especially useful for live recordings. I think they'll also be exactly what I was looking for with my original post about album databasing. After just a quick read through of the most updated published spec (rev 3, 25.10.05), the only thing that really stuck out to me was a question about the heirarchical nature of the CTOC frames: should this structure be a tree, or is a graph feasible? The essential difference (as I'm describing it) is that if a graph is allowed, then a CTOC could reference another CTOC as it's child, which could re-reference the first CTOC as it's own child (actually, "neighbor" if we're talking about graphs). If you're familiar with Categories in Wikipedia, you should know what I mean. These can be mutually nested, but do not actually form a tree. I don't know of a real life situation in music where this would be required, but I do know that in a lot of different tree-based work, I often find the tree restrictions (as opposed to graphs) aggravating. Just a thought, wondering what people think. I probably won't be working on my database (where I'll be using the CTOC and CHAP frames) for a while yet, but when I do, I'll make sure to post any question/comments, etc. on the evolving format. -Brian Mearns Chris Newell wrote: > At 06:04 22/11/2005, py.thoulon at gmail.com wrote: > >>Looks like a job fit for the newly define CHAP and CTOC frames. Check http://www.id3.org/develop.html, under "Work in progress". >> >>Pyt. >> >>On 11/22/05, Brian Mearns <bmearns at coe.neu.edu> wrote: >>I'm interested in constructing a data base of my record collection using >>ID3 format. My plan is to just create a file for each album, the only >>contents of the file would be an ID3 tag with the album's meta data. I >>want to set it up so that the entire tag contains all the data for the >>album, plus a frame for each track which contains any necessary meta >>data for that track, including possible "overrides" of the data in the >>album (parent) tag (For instance, the album may have a certain composer, >>but one particular track has a different composer.) >> >>I was just curious if there was any existing structure for something >>like this, or if anyone's came across anything like it before. > > > Brian, > > I agree with Pierre that this is an ideal application for the newly defined Chapter Frames. > > I've created a tool for creating these Frames which is available from: http://id3v2-chap-tool.sourceforge.net > > However, you have to bear in mind that the specification is "work in progress" and these frames are not yet supported by any Media Players. > > Any feedback you have about the utility of the Chapter Frames would be very welcome > > Chris > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Dr J.C. Newell > Digital Media Group, BBC Research & Development > Kingswood Warren, Woodland Way, Tadworth, Surrey > KT20 6NP UK > mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd > Tel: +44 (0)1737 839659 > Switchboard: +44 1737 839500 > Fax: +44 (0)1737 839665 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From mitch at honnert.com Wed Nov 30 09:24:17 2005 From: mitch at honnert.com (Mitchell S. Honnert) Date: Wed, 30 Nov 2005 12:24:17 -0500 Subject: [ID3 Dev] Moving forward on Chapter Frames References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <6.1.2.0.2.20051125161419.02cf2418@pop3> <4da424620511251914o43262f92pc19117c8cf3241a2@mail.gmail.com> <14398.195.91.64.52.1133020015.squirrel@195.91.64.52> <6.1.2.0.2.20051128165838.02da7b70@pop3> <57148.195.91.64.54.1133283276.squirrel@195.91.64.54> <6.1.2.0.2.20051130095722.02f37a90@pop3> <438DD9DF.1070403@northpb.com> Message-ID: <002701c5f5d2$e9f4a9b0$87000105@kendle.com> > Any applications using v2.2 would most likely not be favored by a very > modern podcasting user base. That's what I thought too, but...I was shocked recently to discover that the default ID3 version when ripping MP3's in the latest version of iTunes is v2.2! Doh! I was running a scan of a friend's music library as a test of my .NET ID3 tag library when hundreds or errors were reported. I've run several of these kinds of large library scans and very rarely would I see *any* v2.2 tags so I just never got around to implementing it in my lib. It turns out he did all of his ripping using iTunes so almost his entire library was v2.2. So if iTunes, arguably one of the most popular audio players out there now, is going backwards and using v2.2, more consideration might have to be given to this "outdated" version. Mitchell S. Honnert UltraID3Lib - http://home.fuse.net/honnert/hundred?UltraID3Lib ----- Original Message ----- From: "Dan O'Neill" To: Sent: Wednesday, November 30, 2005 11:57 AM Subject: Re: [ID3 Dev] Moving forward on Chapter Frames > Chris Newell wrote: > >> >> A similar statement is present in v2.2 and v2.3. Apologies for not >> noticing this earlier! >> >> This means we could publish an addendum describing how the Chapter Frames >> could be used in both v2.3 and v.2.4 tags. Would it also be useful to >> provide a version of the frames for use with v2.2? >> >> I'll try to draft a first stab at an addendum for everyone to review. > > I would prefer that we encourage the community to move forward and not > support v2.2. Any applications using v2.2 would most likely not be > favored by a very modern podcasting user base. > > dano > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From jid3 at blinkenlights.org Tue Nov 8 14:50:43 2005 From: jid3 at blinkenlights.org (Paul Grebenc) Date: Tue, 8 Nov 2005 17:50:43 -0500 (EST) Subject: [ID3 Dev] Worst cases of "ID3 offenders"? Message-ID: The MP3ext Windows explorer extension corrupts all of its ID3 v2 tags by repeatedly writing an advertisement for itself (ie. "MP3ext V3.3.18(unicode)") in the tag padding, which violates the spec. Winamp ignores the last frame in a v2.3.0 tag if there is no padding in the tag. Mixmeister BPM analyzer (among others it seems) writes floating point values to the TBPM frame. Paul --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at audiott.com Thu Nov 10 10:49:15 2005 From: id3v2 at audiott.com (Michal Vician) Date: Thu, 10 Nov 2005 19:49:15 +0100 (CET) Subject: [ID3 Dev] Suggestion - uniform "Element ID" creation Message-ID: <48758.195.91.64.54.1131648555.squirrel@195.91.64.54> Hi. I have a suggestion to make the creation of "Element ID" uniform. See attachment... Regards. -- Michal Vician id3v2 at audiott.com http://www.audiott.com/ -------------- next part -------------- A non-text attachment was scrubbed... Name: suggestion - uniform element id creation.zip Type: application/zip Size: 3042 bytes Desc: not available URL: -------------- next part -------------- --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From andrew.kernahan at btinternet.com Wed Nov 9 11:38:57 2005 From: andrew.kernahan at btinternet.com (Andy Kernahan) Date: Wed, 9 Nov 2005 19:38:57 -0000 Subject: [ID3 Dev] questions regarding TBPM frame. References: <6.2.5.6.0.20051030223858.02ecdb90@earthlink.net> <6.2.5.6.0.20051031034035.02e9f310@earthlink.net> <000901c5de76$c4d6b600$0500000a@MARVIN> <6.2.5.6.0.20051108075210.02cafa28@earthlink.net> Message-ID: <003001c5e565$3a40ccb0$0500000a@MARVIN> ".....unfortunately, neither one of the apps I use would probably be updated to use the new frame." You have hit the nail on the head there unfortunately. Just changing the spec for the TBPM does not mean that the developers of your app will change their libs and GUIs to support real numbers. Also, the developers of newer apps will see that v2.3.0 is by far the most implemented version of the id3 standard and will probably continue reading/writing tags in that version. The easiest solution to your problem is to find an editor that supports real numbers within the TBPM frame and stick with it. Sorry to be so pessimistic. Andy. ----- Original Message ----- From: "darien" To: Sent: Tuesday, November 08, 2005 3:11 PM Subject: Re: [ID3 Dev] questions regarding TBPM frame. > > hey there andy. > > thanks for taking the time to drop a reply to this thread... > >> the ID3v2.X.0 standard clearly states that the TBPM frame contains a >> string representation of an integer, so the values 132.68 and 95.35 are >> invalid. >>I would not personally recommend changing the current specification of the >>TBPM frame to allow for high precision bpm values but instead I would >>suggest >>you submit a proposal for a new frame (PBPM?). This would allow TBPM aware >>applications to prefer the high precision frame over the standard TBPM >>frame >>whilst also ensuring that existing non-aware applications remain intact. > > i honestly think it would be better to change the TBPM frame to allow > both. > > the reason why i think that way is that most of the apps i've seen that > handle BPM measurement and store it in the TBPM frame all store a > non-whole number. i've only seen a couple of apps that adhere to the > standard, and the rest ignore it and store a non-whole measurement (ie > 13278) in that frame. one of the oldest 'pro' apps that i know of, PCDJ > Red, stores that information in the TBPM frame. i haven't seen a version > of that app in quite a while, but the last version i saw put a value like > '13278' in there. > > because there are apps that i use to do bpm measurement that probably > won't ever be updated (mixmeister bpm analyzer, flatfeetpete's > recordboxing app : > http://sourceforge.net/project/showfiles.php?group_id=70378 ) to adhere to > a standard, i think it would be better to change the standard of that > frame to allow both. since apps already stick non-whole numbers in there, > i reckon that devices/apps that look at that frame already round off > non-whole numbers that they see already if that is necessary. it would be > nice though to have newer apps that adhere to the standard not round off > the number if they see a non-whole number in the frame. i have several > thousand files that have all had their bpm measurements done, and i don't > want to have them all rounded off, as it has taken hours of cpu time to > analyze them. i am not a programmer, and i can't write an application that > would convert the values to a new frame, and don't have the money to hire > a programmer to do that either ... and unfortunately, neither one of the > apps i use would probably be updated to use the new frame. > > so again, i ask ... how does one get the standard changed to allow both > types of entries? > > cheers for any advice. > > --darien! > > > > > > >>----- Original Message ----- From: "darien" >>To: >>Sent: Monday, October 31, 2005 2:07 PM >>Subject: Re: [ID3 Dev] questions regarding TBPM frame. >> >> >>> >>>hey there Pyt ... >>> >>>thanks for replying. >>> >>>>Strictly speaking, TBPM is a text frame, so it is very possible for it >>>>to be set to just about anything textual if a program would allow it. >>>>However, the v2.4 spec is pretty clear that it is an integer and that it >>>>is beats per minute, so you cannot set it to 123.45, and even though you >>>>could set it to 12345, but that would probably meaningless from a >>>>musical standpoint... >>>> >>>>I guess your programmer must have decided that more than 999 beats per >>>>minute is nonsense, which can be understood but is indeed going a bit >>>>further than the spec intends. >>>> >>>>Not sure this helps... >>> >>>it sort of does ... it's brought a couple of things to light, and i have >>>a question... >>> >>>how does one go about getting the spec for the TBPM frame changed to >>>allow for a decimal place and 'non-whole' bpm measurements (ie 132.68, >>>95.35, etc) as allowable and legitimate data for the spec? >>> >>>i feel that it's not right the way it is, i can think of quite a few >>>arguments for why the 'standard' should be changed to allow a decimal >>>place if desired or needed, and i'd like to push to have it changed. it >>>would make my life a bit easier in a few different ways, and i reckon it >>>would probably help other people out there as well. >>> >>>bpm measurement is *never* a solid, honest-to-goodness integer. well, not >>>practically, anyway. it's usually measured in averages, because there are >>>no recordings out there that are perfectly on-beat from start to finish >>>... there are many obvious reasons why... neither midi clocks nor human >>>drummers are ever 100% on the money with regard to keeping time, hence >>>having bpm measurements of 132.68, 95.35, etc. while midi clocks come >>>close, there's always a little bit of slide with regard to the accuracy >>>of its' generation. human drummers are never 100% -- every human drummer >>>is always off the mark by some percentage (usually depending on how drunk >>>they are). the only thing that is pretty much right-on is smpte, and a >>>large percentage of professional musicians don't use smpte for clock >>>generation (though there are a few out there that do, especially if >>>they're working in hollywood on film or television projects). >>> >>>most software applications that measure bpm properly do not end up with a >>>bpm measurement that is a whole integer either (here's one i know of >>>that's free and writes the value into the id3v2.x tag : >>>http://www.mixmeister.com/download_freestuff.html ) ... >>> >>>i'm a dance music dj and i play a lot of electronically-based music. i >>>play house, prog house, hip hop, breaks, and i play some mobile dj gigs >>>too if the money's right. years ago, i used to exclusively dj with vinyl >>>records and cd's, but now i use traktor dj studio to dj with. traktor dj >>>studio has the ability to be able to control/manipulate playback of mp3's >>>using a special hardware audio interface and vinyl records with a >>>recording of timecode cut onto them. the timecode records tell the >>>computer what pitch the record is playing back at, where the needle is on >>>the record and so forth. the records and hardware are essentially a >>>control interface, and a brilliant one at that. >>> >>>about 80% of the mp3's i generate to dj with are from recordings of vinyl >>>records, because that's the medium of choice for dj'ing electronic >>>music -- a lot of prime stuff gets released on vinyl that never sees a >>>digital release, even in this digital world of ours. vinyl, as a rule, is >>>an imperfect medium, which opens up a pretty huge can o' worms in itself >>>with regard to bpm and speed in general. here are some examples of things >>>that cause timing issues with vinyl records: >>> >>>o - vinyl records are never perfectly flat. every record pressed (even a >>>180 gram audiophile grade record) has a certain degree of warp to it. >>>they can be really close to flat, but never perfectly flat >>>o - the stamper plates used to press records are made of nickel, and a >>>high amount of pressure is placed on them for every record pressed -- it >>>takes 120 tons of pressure to press a vinyl record. as a result, every >>>pressing degrades the stampers slightly. stampers are only good for 1000 >>>pressings. after that, the stampers will have degraded enough to create a >>>noticably imperfect product and a new set of stampers must be used. >>>o - consistency of the vinyl material differs slightly from batch to >>>batch >>> >>>couple these factors with a midi clock that doesn't generate time >>>perfectly and you've got a recording that isn't going to be anywhere near >>>perfect, timing and bpm measurement-wise. >>> >>>this is just one example. another that i could explore is disco or funk >>>tracks from the 70's... parliament, the bee gee's, gloria gaynor, cheryl >>>lynn, donna summer, etc. all of that stuff was recorded onto analog tape, >>>and human drummers were employed. analog tape stretches and shrinks with >>>temperature and general use. tape machines of the day weren't digitally >>>regulated, and no analog motor is perfect. pair those imperfections with >>>a human drummer and loads of disco or funk swing, and you've got a >>>recording that isn't anywhere near a whole integer bpm-wise. >>> >>>so yeah ... some good arguments there. ;) >>> >>>any advice on how to go about getting the spec changed for the TBPM field >>>would be greatly appreciated. >>> >>>cheers. >>> >>>--darien! >>> >>> >>> >>>--------------------------------------------------------------------- >>>To unsubscribe, e-mail: id3v2-unsubscribe at id3.org >>>For additional commands, e-mail: id3v2-help at id3.org >>> >> >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: id3v2-unsubscribe at id3.org >>For additional commands, e-mail: id3v2-help at id3.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at audiott.com Wed Nov 30 09:42:43 2005 From: id3v2 at audiott.com (Michal Vician) Date: Wed, 30 Nov 2005 18:42:43 +0100 (CET) Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: <002701c5f5d2$e9f4a9b0$87000105@kendle.com> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <6.1.2.0.2.20051125161419.02cf2418@pop3> <4da424620511251914o43262f92pc19117c8cf3241a2@mail.gmail.com> <14398.195.91.64.52.1133020015.squirrel@195.91.64.52> <6.1.2.0.2.20051128165838.02da7b70@pop3> <57148.195.91.64.54.1133283276.squirrel@195.91.64.54> <6.1.2.0.2.20051130095722.02f37a90@pop3> <438DD9DF.1070403@northpb.com> <002701c5f5d2$e9f4a9b0$87000105@kendle.com> Message-ID: <55198.195.91.64.54.1133372563.squirrel@195.91.64.54> > ...I was running a scan of a friend's music library as a test of my > .NET ID3 tag library when hundreds or errors were reported. > I've run several of... I'm a bit interested in .NET. I work with Java but I have also tried to write some code in C#. Is your library also written in C# ? If yes, is your library open source? Many thanks Miso -- Michal Vician id3v2 at audiott.com http://www.audiott.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From chris.newell at rd.bbc.co.uk Tue Nov 22 06:49:43 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Tue, 22 Nov 2005 14:49:43 +0000 Subject: [ID3 Dev] Whole Album Tags In-Reply-To: <43832A85.9000806@coe.neu.edu> References: <438291CD.4080301@coe.neu.edu> <6.1.2.0.2.20051122102800.02e12558@pop3> <43832A85.9000806@coe.neu.edu> Message-ID: <6.1.2.0.2.20051122143553.02d03a40@pop3> At 14:26 22/11/2005, you wrote: >After just a quick read through of the most updated published spec (rev 3, 25.10.05), the only thing that really stuck out to me was a question about the heirarchical nature of the CTOC frames: should this structure be a tree, or is a graph feasible? The essential difference (as I'm describing it) is that if a graph is allowed, then a CTOC could reference another CTOC as it's child, which could re-reference the first CTOC as it's own child (actually, "neighbor" if we're talking about graphs). > >If you're familiar with Categories in Wikipedia, you should know what I mean. These can be mutually nested, but do not actually form a tree. I don't know of a real life situation in music where this would be required, but I do know that in a lot of different tree-based work, I often find the tree restrictions (as opposed to graphs) aggravating. Brian, There is no restriction on CTOC references in the draft specification so graphs would be feasible. Chris >Just a thought, wondering what people think. I probably won't be working on my database (where I'll be using the CTOC and CHAP frames) for a while yet, but when I do, I'll make sure to post any question/comments, etc. on the evolving format. > >-Brian Mearns ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr J.C. Newell Digital Media Group, BBC Research & Development Kingswood Warren, Woodland Way, Tadworth, Surrey KT20 6NP UK mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd Tel: +44 (0)1737 839659 Switchboard: +44 1737 839500 Fax: +44 (0)1737 839665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From paul_t100 at fastmail.fm Tue Nov 8 00:06:38 2005 From: paul_t100 at fastmail.fm (Paul Taylor) Date: Tue, 08 Nov 2005 08:06:38 +0000 Subject: [ID3 Dev] Java heirarchy In-Reply-To: <1126720984.432865d8f1b97@www.coe.neu.edu> References: <1126720984.432865d8f1b97@www.coe.neu.edu> Message-ID: <43705C8E.80700@fastmail.fm> Also you might like to take a look at jaudiotagger https://jaudiotagger.dev.java.net/ which provides a fairly complete java api for id3 Brian Mearns wrote: >I'm working (slowly) on my own java implementation of ID3, and I'm having some >issues with the heirarchy. > >I've got it set up where mypackage.id3.v2.v3.DefaultID3Frame is the default >class for representing ID3v2.3.0 frames which don't have a more specific >implementation. likewise, mypackage.id3.v2.v3.ID3TextFrame extends from the >above mentioned DefaultID3Frame class, and represents the T*** frames. > >Now I'm trying to plan out a v2.4 library, and so I've got >mypackage.id3.v2.v4.DefaultID3Frame which extends from >mypackage.id3.v2.v3.DefaultID3Frame. Still no problem. Now the tricky part. I >want a class mypackage.id3.v2.v4.Id3TextFrame for v2.4.0 text frames, but does >it make more sense for it to extend from mypackage.id3.v2.v4.DefaultID3Frame, >or from mypackage.id3.v2.v3.ID3TextFrame, in other words from the v2.4 default >frame, or the v2.3 text frame? > >Any thoughts on this? > >Thanks. >-- >-Brian Mearns > (bmearns at coe.neu.edu) > >--------------------------------------------------------------------- >To unsubscribe, e-mail: id3v2-unsubscribe at id3.org >For additional commands, e-mail: id3v2-help at id3.org > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From T.Hammond at nature.com Tue Nov 22 09:09:33 2005 From: T.Hammond at nature.com (Hammond, Tony) Date: Tue, 22 Nov 2005 17:09:33 -0000 Subject: [ID3 Dev] Embedding Cover Art Message-ID: <125F7834E11A5741A7D79412EE3504F91D08CC11@UK1APPS2.mpl.root-domain.org> Hi Guys: I know this is probably a FAQ somewhere but couldn't find it, but have been tearing my hair out with Perl MP3::Tag module - great stuff, but for this one detail: embedding a PNG file for cover art into an MP3. Code I have is: ### my $mp3 = MP3::Tag->new($mp3_file); $mp3->get_tags(); my $id3v2 = $mp3->{'ID3v2'} if exists $mp3->{'ID3v2'}; my $cover; open F, $png_file; my $filesize = (-s F); binmode F; read(F, $cover, $filesize); close F; $id3v2->add_frame('APIC', chr(0x0), 'image/png', chr(0x3), 'Cover art', $cover); ### I seem to just get a corrupted frame which then corrupts the other frames. PNG file seems to be good as I write a copy out to disk and check that. Any help very gratefully received. Cheers, Tony ******************************************************************************** DISCLAIMER: This e-mail is confidential and should not be used by anyone who is not the original intended recipient. If you have received this e-mail in error please inform the sender and delete it from your mailbox or any other storage mechanism. Neither Macmillan Publishers Limited nor any of its agents accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of Macmillan Publishers Limited or one of its agents. Please note that neither Macmillan Publishers Limited nor any of its agents accept any responsibility for viruses that may be contained in this e-mail or its attachments and it is your responsibility to scan the e-mail and attachments (if any). No contracts may be concluded on behalf of Macmillan Publishers Limited or its agents by means of e-mail communication. Macmillan Publishers Limited Registered in England and Wales with registered number 785998 Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS ******************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From robot.gunslinger at gmail.com Wed Nov 2 08:14:13 2005 From: robot.gunslinger at gmail.com (Robot Gunslinger) Date: Wed, 2 Nov 2005 17:14:13 +0100 Subject: [ID3 Dev] Labels And Release Number Message-ID: <0C0E9486-37AC-4B49-BCB7-898BAC438BA0@gmail.com> One thing that always bugged me about id3 is it's inability to provide a field for "Label" and "Release Number". It's especially annoying if you're a fan of electronic or indie music, where where labels (netlabels or otherwise) still are of importance, especially for collectors. I am not a programmer and I don't know if this feature has already been implemented in the latest release, but judging from the most common mp3 players, I guess it hasn't. I am sure this can't be too hard to integrate and would be a very useful feature for Netlabel releases and adding the possibility to defining the Label and the Catalog Number of an id3 tagged music file sure is an valid addition to the metadata capabilities of the id3 standard, so please guys just put it in there. cheers --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From bmearns at coe.neu.edu Tue Nov 1 19:48:39 2005 From: bmearns at coe.neu.edu (Brian Mearns) Date: Tue, 01 Nov 2005 22:48:39 -0500 Subject: [ID3 Dev] ID3v2 In-Reply-To: <43683406.2080908@xtra.co.nz> References: <6.2.5.6.0.20051030223858.02ecdb90@earthlink.net> <6.2.5.6.0.20051031034035.02e9f310@earthlink.net> <000901c5de76$c4d6b600$0500000a@MARVIN> <43683406.2080908@xtra.co.nz> Message-ID: <43683717.2030102@coe.neu.edu> Always keep in mind one of the guiding principles for ID3 development: "Be flexible in what you accept, but strict in what you write." [http://www.id3.org/id3guide.htm#Usage] -Brian Mearns Kirk McMillan wrote: > Many thanks to the couple of folk who answered some questions I had a > few days ago. > > I've reluctantly come to the conclusion there simply isn't an ID3v2 spec > as such that's being adhered to. > Various programs *write* the header frames differently and other > programs interpret then differently. > > BTW, these are just the basic, common headers as used e.g. in Winamp 5. > > It seems the only solution is write tags in such a way that your > preferred reader shows them all. > > Cheers - Kirk > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From andrew.kernahan at btinternet.com Wed Nov 9 11:28:56 2005 From: andrew.kernahan at btinternet.com (Andy Kernahan) Date: Wed, 9 Nov 2005 19:28:56 -0000 Subject: [ID3 Dev] SEEK frame semantics References: Message-ID: <002901c5e563$d3c986d0$0500000a@MARVIN> Pyt, I have interpreted the seek offset as the exact number of bytes from the end of the primary prepended tag to the start of the secondary tag. Please find attached a sample v2.4.0 split tag. Andy. ----- Original Message ----- From: Pyt To: id3v2 at id3.org Sent: Wednesday, November 09, 2005 9:21 AM Subject: [ID3 Dev] SEEK frame semantics From the V2.4 specification, regarding the SEEK frame: This frame indicates where other tags in a file/stream can be found. The 'minimum offset to next tag' is calculated from the end of this tag to the beginning of the next. There may only be one 'seek frame' in a tag.
Minimum offset to next tag $xx xx xx xx The wording "Minimum offset" seems misleading. What does "Minimum" mean in this case ? The next tag is anywhere *after* the offset (e.g., offset+1 or offset+5 would be valid positions) ? or is it supposed to be exactly *at* the offset, as the text seems to imply ? Insights welcome. By the way, has anybody encountered a file using SEEK frames and multiple tags ? If so, I'd be interested in getting my hands on one, for test purposes. Thanks, Pyt. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 240_split.tag Type: application/octet-stream Size: 8597 bytes Desc: not available URL: -------------- next part -------------- --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From py.thoulon at gmail.com Thu Nov 24 08:01:02 2005 From: py.thoulon at gmail.com (Pyt) Date: Thu, 24 Nov 2005 17:01:02 +0100 Subject: [ID3 Dev] APIC frame unsynchronization In-Reply-To: <49562.195.91.64.54.1132780406.squirrel@195.91.64.54> References: <49562.195.91.64.54.1132780406.squirrel@195.91.64.54> Message-ID: Unsynch must be used only if you decide to. In v2.3, there is a global unsynch bit that says whether the tag is unsync'd or not. If this bit is set, all frames have to be unsync'd. In v2.4, there is a bit per frame to specify whether a given frame is unsync'd. If the bit is not set, you shall leave the FF's alone... :-) Hope this helps, Pyt. On 11/23/05, Michal Vician wrote: > > Hi guys. > > I have a problem and need advice: > I've just written library which handles APIC frames. The writing process > looks like this: > > 1. create an array of bytes which represents entire APIC frames > 2. write the byte array to ID3v2 tag > 3. if there is at least one FF Ex byte combination present use the > unsynchonization scheme > > Is this correct? > > Now, why am I asking you this?: > I've downloaded some applications which support APIC frame. As far as this > applications are concerned they do not use unsynchronization scheme when > writing the APIC frame - they are not able to show pictures written with > my library. > I'm just wondering why don't they use it? > Is it just a bug on their side or am I wrong if I claim that > unsynchronization must be used whenever the false sync bytes are found (FF > Ex). > > Regards > Miso > > -- > Michal Vician > id3v2 at audiott.com > http://www.audiott.com/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.newell at rd.bbc.co.uk Tue Nov 22 02:36:31 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Tue, 22 Nov 2005 10:36:31 +0000 Subject: [ID3 Dev] Whole Album Tags In-Reply-To: References: <438291CD.4080301@coe.neu.edu> Message-ID: <6.1.2.0.2.20051122102800.02e12558@pop3> At 06:04 22/11/2005, py.thoulon at gmail.com wrote: >Looks like a job fit for the newly define CHAP and CTOC frames. Check http://www.id3.org/develop.html, under "Work in progress". > >Pyt. > >On 11/22/05, Brian Mearns <bmearns at coe.neu.edu> wrote: >I'm interested in constructing a data base of my record collection using >ID3 format. My plan is to just create a file for each album, the only >contents of the file would be an ID3 tag with the album's meta data. I >want to set it up so that the entire tag contains all the data for the >album, plus a frame for each track which contains any necessary meta >data for that track, including possible "overrides" of the data in the >album (parent) tag (For instance, the album may have a certain composer, >but one particular track has a different composer.) > >I was just curious if there was any existing structure for something >like this, or if anyone's came across anything like it before. Brian, I agree with Pierre that this is an ideal application for the newly defined Chapter Frames. I've created a tool for creating these Frames which is available from: http://id3v2-chap-tool.sourceforge.net However, you have to bear in mind that the specification is "work in progress" and these frames are not yet supported by any Media Players. Any feedback you have about the utility of the Chapter Frames would be very welcome Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr J.C. Newell Digital Media Group, BBC Research & Development Kingswood Warren, Woodland Way, Tadworth, Surrey KT20 6NP UK mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd Tel: +44 (0)1737 839659 Switchboard: +44 1737 839500 Fax: +44 (0)1737 839665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From robot.gunslinger at gmail.com Wed Nov 2 11:12:31 2005 From: robot.gunslinger at gmail.com (Robot Gunslinger) Date: Wed, 2 Nov 2005 20:12:31 +0100 Subject: [ID3 Dev] Labels And Release Number In-Reply-To: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> Message-ID: <2E8638E7-5A2E-4026-BC33-7FEA74311C6D@gmail.com> I am currently using the genre field for storing label information, so I can browse them within iTunes. TPUB and TSRC are not really what I meant. The TSRC is an ISO standard while catalog numbers are handled by Labels themselves. Here are some examples. Ghostly International (Electronic Music) uses GI-xx for Ghostly International releases and SPC-XX (for Spectral Sound) for their more technoid music releases. http://www.ghostly.com/1.0/ (click on Catalog). same with Moor Music http://www.morrmusic.com/ (under releases) and also heavily put do use by netlabels http://www.netlabels.org (list of netlabels) Almost every small label (that is everyone not owned by Sony and Co.) is heavily relying on catalog numbers. Some releases / catalog numbers that are out of print are highly valuable something that is the case with some early Warp Records (www.warprecords.co.uk). Also publishers and labels aren't really the same, with many indie labels using publishing / distributing channels of bigger labels, since they can't afford to do it themselves. This might all sound very niche like, but it really isn't. Those small independent labels represent the musicians that redefine what music is and highly influence the cultural aspect of music in general and almost every good music publication (print or online) are concentrating on those "good" records. Again, I really think that this should be added to the ID3 specifications and I don't think I am alone here. A lot of people think that this is a feature that is clearly missing from the id3 tag specification. Am 02.11.2005 um 19:39 schrieb James J. Williams: > I agree, there should definitely be a standardized Label field, some > programs (NI Traktor) store a Label field, I'm not sure what the > field is > named in the tag but that would be easy enough to find out, anyhow > for now > I've resorted to storing label information in the album field... > It's not > pretty but it works. > > - JW > > -----Original Message----- > From: Robot Gunslinger [mailto:robot.gunslinger at gmail.com] > Sent: Wednesday, November 02, 2005 8:14 AM > To: id3v2 at id3.org > Subject: [ID3 Dev] Labels And Release Number > > One thing that always bugged me about id3 is it's inability to provide > a field for "Label" and "Release Number". > > It's especially annoying if you're a fan of electronic or indie > music, where > where labels (netlabels or otherwise) still are of importance, > especially for collectors. > > I am not a programmer and I don't know if this feature has already > been > implemented in the latest release, but judging from the most common > mp3 players, I guess it hasn't. > > I am sure this can't be too hard to integrate and would be a very > useful feature > for Netlabel releases and adding the possibility to defining the > Label and the Catalog Number of an id3 tagged music file sure is an > valid > addition to the metadata capabilities of the id3 standard, so please > guys > just put it in there. > > > cheers > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: id3v2-unsubscribe at id3.org > For additional commands, e-mail: id3v2-help at id3.org > --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From mitch at honnert.com Wed Nov 9 14:53:55 2005 From: mitch at honnert.com (Mitchell S. Honnert) Date: Wed, 9 Nov 2005 17:53:55 -0500 Subject: [ID3 Dev] Worst cases of "ID3 offenders"? In-Reply-To: <003c01c5e566$2bbc6900$0500000a@MARVIN> Message-ID: <20051109225403.NGTR25752.gx5.fuse.net@avoca> Thanks for all of the responses. If anyone else has any more, keep'em comin'. Otherwise I'll confirm these and post them to an "ID3 Offenders" section. - Mitchell S. Honnert -----Original Message----- From: Andy Kernahan [mailto:andrew.kernahan at btinternet.com] Sent: Wednesday, November 09, 2005 2:46 PM To: id3v2 at id3.org Subject: Re: [ID3 Dev] Worst cases of "ID3 offenders"? Hmmmm, it seems to work ok on my XP machine. Are you sure the BOM is present within the text frame? Andy. ----- Original Message ----- From: "Robert Manson" To: Sent: Wednesday, November 09, 2005 7:39 PM Subject: RE: [ID3 Dev] Worst cases of "ID3 offenders"? You are right that Windows XP does not support v2.4. It does claim to support v2.3, however, and its implementation of the standard is flawed due to the fact that it cannot read "16-Bit Unicode 2.0" strings encoded as big endian. -----Original Message----- From: Andy Kernahan [mailto:andrew.kernahan at btinternet.com] Sent: Wednesday, November 09, 2005 11:13 AM To: id3v2 at id3.org Subject: Re: [ID3 Dev] Worst cases of "ID3 offenders"? XP doesn't actually support V2.4.0 and therefore has no need to support UTF16-BE. ----- Original Message ----- From: "Robert Manson" To: Sent: Wednesday, November 09, 2005 1:38 AM Subject: RE: [ID3 Dev] Worst cases of "ID3 offenders"? Windows XP does not read UTF16-BE encoded text frames -----Original Message----- From: Paul Grebenc [mailto:jid3 at blinkenlights.org] Sent: Tuesday, November 08, 2005 2:51 PM To: id3v2 at id3.org Subject: Re: [ID3 Dev] Worst cases of "ID3 offenders"? The MP3ext Windows explorer extension corrupts all of its ID3 v2 tags by repeatedly writing an advertisement for itself (ie. "MP3ext V3.3.18(unicode)") in the tag padding, which violates the spec. Winamp ignores the last frame in a v2.3.0 tag if there is no padding in the tag. Mixmeister BPM analyzer (among others it seems) writes floating point values to the TBPM frame. Paul --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From chris.newell at rd.bbc.co.uk Mon Nov 14 02:04:46 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Mon, 14 Nov 2005 10:04:46 +0000 Subject: [ID3 Dev] Suggestion - uniform 'Element ID' creation In-Reply-To: <7329.195.91.64.54.1131731492.squirrel@195.91.64.54> References: <48758.195.91.64.54.1131648555.squirrel@195.91.64.54> <6.1.2.0.2.20051111093213.02e0f178@pop3> <7329.195.91.64.54.1131731492.squirrel@195.91.64.54> Message-ID: <6.1.2.0.2.20051114092322.02e86780@pop3> At 17:51 11/11/2005, you wrote: >> I can see the merit of your "uniform Element ID" >> concept in terms of simplicity for parsers. However, I'm concerned that it >> would block one of the useful capabilities of the current scheme - the >> ability to reference chapters from more than one table of contents. >> >> For example, for the recording of a rock festival you could create a CHAP >> frame for each song and then index these frames in three ways using >> different CTOCs to provide: >> - a full, temporally ordered table of contents >> - a table providing an index of band names or genres >> - a table listing highlights >> >> I think it's important to maintain this kind of flexibility because it >> opens up all kinds of interesting opportunities for content developers. > >Oh yes. I had forgotten that there may be more than one table of contents >in each tag. Therefore I have adjusted my "uniform Element ID" concept so >that there may be more than one table of contents. How? >Just by adding the "X#" at the very beggining of each Element ID. >X - the unigue number identifier of each table of contents. >Here is example of 2 tables of contents written in one ID3 tag (there are >also some CHAP frames which are not referenced by any CTOC frame): > >{THIS IS TABLE OF CONTENTS #1} >1#0 (root - zero level) > 1#1 (1st level) > 1#2 > 1#3 > 1#3.1 (2nd level) > 1#3.2 > 1#3.3 > 1#3.3.1 (3rd level) > 1#3.3.2 > 1#3.3.3 > 1#3.3.3.1 (4th level) > 1#3.3.3.2 > ... Michal, How does this scheme allow the an individual chapter frame to be referenced by more than one table of contents? In the example scenario above, the chapters representing individual songs may be referenced three times. >Just tell me and I can generate ID3 tag in whatever version. >See attachment. There is example content in ID3v2.3. Cheers, I'll try it out. Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr J.C. Newell Digital Media Group, BBC Research & Development Kingswood Warren, Woodland Way, Tadworth, Surrey KT20 6NP UK mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd Tel: +44 (0)1737 839659 Switchboard: +44 1737 839500 Fax: +44 (0)1737 839665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at northpb.com Wed Nov 30 08:57:03 2005 From: id3v2 at northpb.com (Dan O'Neill) Date: Wed, 30 Nov 2005 08:57:03 -0800 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: <6.1.2.0.2.20051130095722.02f37a90@pop3> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <6.1.2.0.2.20051125161419.02cf2418@pop3> <4da424620511251914o43262f92pc19117c8cf3241a2@mail.gmail.com> <14398.195.91.64.52.1133020015.squirrel@195.91.64.52> <6.1.2.0.2.20051128165838.02da7b70@pop3> <57148.195.91.64.54.1133283276.squirrel@195.91.64.54> <6.1.2.0.2.20051130095722.02f37a90@pop3> Message-ID: <438DD9DF.1070403@northpb.com> Chris Newell wrote: > > A similar statement is present in v2.2 and v2.3. Apologies for not noticing this earlier! > > This means we could publish an addendum describing how the Chapter Frames could be used in both v2.3 and v.2.4 tags. Would it also be useful to provide a version of the frames for use with v2.2? > > I'll try to draft a first stab at an addendum for everyone to review. I would prefer that we encourage the community to move forward and not support v2.2. Any applications using v2.2 would most likely not be favored by a very modern podcasting user base. dano --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From chris.newell at rd.bbc.co.uk Wed Nov 9 02:17:43 2005 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Wed, 09 Nov 2005 10:17:43 +0000 Subject: [ID3 Dev] New member In-Reply-To: References: <45601.195.91.64.54.1131402561.squirrel@195.91.64.54> <6.1.2.0.2.20051108143503.02fdfdf8@pop3> Message-ID: <6.1.2.0.2.20051109092023.02e2fcf8@pop3> Pyt, At 17:32 08/11/2005, you wrote: >I've been playing with the ChapterTool, but it seems that you can't set chapter start and end times just by typing the time into the text entry boxes, but only by using the media player and clicking on Set Start or Set End on the fly (or am I doing something wrong ? the times don't seem to be saved to the file unless the buttons are used). This is kind of cumbersome and does not allow for precise, to-the-frame, setting of the start and end times. This should be fixed in the latest download (http://prdownloads.sourceforge.net/id3v2-chap-tool/chaptool.zip?download). I've also added some "nudge" buttons to make it easier to set the media times accurately. Cheers, Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr J.C. Newell Digital Media Group, BBC Research & Development Kingswood Warren, Woodland Way, Tadworth, Surrey KT20 6NP UK mailto:chris.newell at rd.bbc.co.uk http://www.bbc.co.uk/rd Tel: +44 (0)1737 839659 Switchboard: +44 1737 839500 Fax: +44 (0)1737 839665 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at audiott.com Wed Nov 23 13:13:26 2005 From: id3v2 at audiott.com (Michal Vician) Date: Wed, 23 Nov 2005 22:13:26 +0100 (CET) Subject: [ID3 Dev] APIC frame unsynchronization Message-ID: <49562.195.91.64.54.1132780406.squirrel@195.91.64.54> Hi guys. I have a problem and need advice: I've just written library which handles APIC frames. The writing process looks like this: 1. create an array of bytes which represents entire APIC frames 2. write the byte array to ID3v2 tag 3. if there is at least one FF Ex byte combination present use the unsynchonization scheme Is this correct? Now, why am I asking you this?: I've downloaded some applications which support APIC frame. As far as this applications are concerned they do not use unsynchronization scheme when writing the APIC frame - they are not able to show pictures written with my library. I'm just wondering why don't they use it? Is it just a bug on their side or am I wrong if I claim that unsynchronization must be used whenever the false sync bytes are found (FF Ex). Regards Miso -- Michal Vician id3v2 at audiott.com http://www.audiott.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at audiott.com Thu Nov 24 14:29:43 2005 From: id3v2 at audiott.com (Michal Vician) Date: Thu, 24 Nov 2005 23:29:43 +0100 (CET) Subject: [ID3 Dev] APIC frame unsynchronization In-Reply-To: References: <49562.195.91.64.54.1132780406.squirrel@195.91.64.54> Message-ID: <36769.195.91.64.54.1132871383.squirrel@195.91.64.54> I'm lucky you assured me that I was right. I'm just wondering that there are so many applications which do not work according to Id3v2 specification. That's terrible... Thanks Miso > Unsynch must be used only if you decide to. > > In v2.3, there is a global unsynch bit that says whether the tag is > unsync'd > or not. If this bit is set, all frames have to be unsync'd. > > In v2.4, there is a bit per frame to specify whether a given frame is > unsync'd. If the bit is not set, you shall leave the FF's alone... :-) > > Hope this helps, > Pyt. > > > On 11/23/05, Michal Vician wrote: >> >> Hi guys. >> >> I have a problem and need advice: >> I've just written library which handles APIC frames. The writing process >> looks like this: >> >> 1. create an array of bytes which represents entire APIC frames >> 2. write the byte array to ID3v2 tag >> 3. if there is at least one FF Ex byte combination present use the >> unsynchonization scheme >> >> Is this correct? >> >> Now, why am I asking you this?: >> I've downloaded some applications which support APIC frame. As far as >> this >> applications are concerned they do not use unsynchronization scheme when >> writing the APIC frame - they are not able to show pictures written with >> my library. >> I'm just wondering why don't they use it? >> Is it just a bug on their side or am I wrong if I claim that >> unsynchronization must be used whenever the false sync bytes are found >> (FF >> Ex). >> >> Regards >> Miso >> >> -- >> Michal Vician >> id3v2 at audiott.com >> http://www.audiott.com/ >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org >> For additional commands, e-mail: id3v2-help at id3.org >> >> > -- Michal Vician id3v2 at audiott.com http://www.audiott.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From py.thoulon at gmail.com Fri Nov 25 08:54:45 2005 From: py.thoulon at gmail.com (Pyt) Date: Fri, 25 Nov 2005 17:54:45 +0100 Subject: [ID3 Dev] Moving forward on Chapter Frames In-Reply-To: <6.1.2.0.2.20051125154923.03179e38@pop3> References: <436907e4.21d9ec78.7fb1.243aSMTPIN_ADDED@mx.gmail.com> <43698AB0.5060409@northpb.com> <4da424620511030618h15df7807g55e46cd01f6a69f2@mail.gmail.com> <003501c5e3ba$0374dde0$b1000105@kendle.com> <436FD7A4.1050102@northpb.com> <6.1.2.0.2.20051121143508.02f2feb8@pop3> <30155.195.91.64.54.1132612773.squirrel@195.91.64.54> <003801c5ef19$143c3c80$4a046c6b@sisodomain.com> <6.1.2.0.2.20051125154923.03179e38@pop3> Message-ID: Agreed... Pyt. On 11/25/05, Chris Newell wrote: > > > I think that any future version of the specification should include a > statement that frames with an unrecognised Frame ID should ignored and > skipped using the Size field. This would allow new frame types to be > introduced in a backwards compatible manner. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: