From rmanson at gracenote.com Thu May 25 15:46:15 2006 From: rmanson at gracenote.com (Robert Manson) Date: Thu, 25 May 2006 15:46:15 -0700 Subject: [ID3 Dev] ID3v2.4 support in real world Message-ID: <27905705A869164CBE58B96BA8547557036593BE@mail.internal.cddb.com> Also you should consider the iTunes Frame size bug, whereby v2.4 frames are written with an incorrect non-syncsafe frame size. (Actually I haven't verified that they are *still* doing this... has anyone tested with the latest iTunes?) My opinion is that writing 2.3 tags would be your best bet for compatibility with other players. -Rob -----Original Message----- From: Jiri Cincura [mailto:diskuze at cincura.net] Sent: Thursday, May 25, 2006 3:40 PM To: id3v2 at id3.org Subject: [ID3 Dev] ID3v2.4 support in real world Hi *, I'm doing some refactoring in my code of ID3 renamer and i'm thinking about writing tags in ID3v2.4 (now I'm writing 2.3). But I've tested the support for it and it seems to be, that it's not good. Some SW simply reads it, but writes new tag in front of ID3v2.3 (Windows Shell), some SW don't read it, but writes new tag in front of it (WinAmp 2.x) and WMP also isn't able to read it. I've also tested some SW for writing into clean file, and all writes ID3v2.3. So what's your expirience? Am I stay writing ID3v2.3 'cause v2.4 isn't supported at all? -- Jiri Cincura http://www.cincura.net/ --------------------------------------------------------------------- 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 paul_t100 at fastmail.fm Thu May 4 14:15:02 2006 From: paul_t100 at fastmail.fm (Paul Taylor) Date: Thu, 04 May 2006 22:15:02 +0100 Subject: [ID3 Dev] Jaudiotagger API version 1.0.0 released Message-ID: <445A6ED6.2060908@fastmail.fm> Version 1.0.0 of Jaudiotagger which is a java api for reading and writing ID3 tags has just been released, but it could do with some testing over a wider range of files. Included is a test program called ReadTest.bat which attempts to read all mp3 files within a directory (and subdirectories), it then flags any files it could not process, I would be very interestes in any files that the api could not process that you believe are ok. If any java developers want to get involved that would be great, we could especially do with some more junits tests been written. --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From diskuze at cincura.net Thu May 25 15:44:08 2006 From: diskuze at cincura.net (Jiri Cincura) Date: Fri, 26 May 2006 00:44:08 +0200 Subject: [ID3 Dev] ID3v2.4 support in real world In-Reply-To: <44763235.3000501@cincura.net> References: <44763235.3000501@cincura.net> Message-ID: <44763338.40700@cincura.net> Just one note. Fix me, if I'm wrong. There's no change in header structure between v2.3 and v2.4, right? Because for testing I've just changed the number indicating the version in my hex editor. -- Jiri Cincura http://www.cincura.net/ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From diskuze at cincura.net Fri May 26 00:13:44 2006 From: diskuze at cincura.net (Jiri Cincura) Date: Fri, 26 May 2006 09:13:44 +0200 Subject: [ID3 Dev] ID3v2.4 support in real world In-Reply-To: <27905705A869164CBE58B96BA8547557036593BE@mail.internal.cddb.com> References: <27905705A869164CBE58B96BA8547557036593BE@mail.internal.cddb.com> Message-ID: <4476AAA8.3070900@cincura.net> On 26.5.2006 0:46 +0200 Robert Manson wrote: > My opinion is that writing 2.3 tags would be your best bet for > compatibility with other players. OK. I'll stay on v2.3. :) -- Jiri Cincura http://www.cincura.net/ --------------------------------------------------------------------- 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 May 2 06:20:02 2006 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Tue, 02 May 2006 14:20:02 +0100 Subject: [ID3 Dev] ID3v2 extensions to support audible metadata In-Reply-To: <20060427203317.GA11712@audioslave.beatnik.com> References: <6.2.0.14.2.20060421145243.0254da30@pop3> <20060427203317.GA11712@audioslave.beatnik.com> Message-ID: <6.2.0.14.2.20060502123437.025690f0@pop3> Brandon, Thanks for your comments. At 21:33 27/04/2006, you wrote: >One thing you might consider is allowing different formats for the audio >data. For example, the track audio may be 44.1kHz stereo, while the >narrative data would sound fine at 11.025kHz mono. This is allowed although not explicitly stated - the only stipulation is that the encoding of the audible metadata must match the MIME type of the audio file. >Also, since I don't see it mentioned, what if the track audio is encryped >via an AENC frame? I presume you wouldn't want this audio data to be >encrypted as well, but in either case it should be noted in the spec. If desired you could encrypt the audible metadata by encrypting the ATXT frame itself (in which case the frame header encryption bit would be set). I'll add a note to clarify that encryption of the track audio data is decoupled from encryption of the ATXT frame audio data. Best regards, Chris ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Chris Newell Lead Technologist 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 traut at gmx.de Thu May 4 06:43:36 2006 From: traut at gmx.de (Martin Trautmann) Date: Thu, 4 May 2006 15:43:36 +0200 (MEST) Subject: [ID3 Dev] Tags for classical music References: <18534.1146750005@www001.gmx.net> Message-ID: <29711.1146750216@www001.gmx.net> Hi all, I just joined the id3 mailing list. Are there any archives around? This is a repost since the original message was rejected. Is the list owner still active? My question is how classical music could be supported best. I've seen some comments within the comparison of different tag formats on http://age.hobba.nl/audio/tag_frame_reference.html Special needs for classical music are * artist and related instrument or either artist or instrument * composer - already within TCOM (but it does not split first and last name explicitly?) Classical music can be categorized in multiple ways. One would be e.g. by the composer's own ordering, such as * concert number concerto 11 for piano and orchestra cantata 2 etc. This ordering might require alphanumeric sorting, since one composer may have 'cantata 2', '2nd clarinet concerto' and 'piano concerto 2' which might sort as e.g. 02can, 02-cl and 02-p. For some composers later research created an additional ordering of all works, such as Bach: Bach-Werke-Verzeichnis Mozart: K?chelverzeichnis This could be kept within an * opus number A logical consequence would be to include * year of composition Nice to have: * chord (minor/major) The track title itself may be one of many variations. Example: 'concerto', 'concerto for piano', 'piano concerto', 'concerto for cembalo and orchestra' etc. all may be variations of the same piano concerto. There may be even more variations across different languages. Thus it's helpful to have a * reference title which is normalized for personal usage (e.g. using 'Symphonie' as typical for one composer, while another one used 'Sinfonie'. Different language settings might open a huge field of further options. This would require e.g. a notation of the used language and the knowledge of all variations. I feel that this should be kept out of the ID3 tag - it's a simple external database operation to convert titles or composer names to the locally preferred writing All of this may require some ID3 tag extensions. Much of this could be applied to other music and audio files as well. However, there's one very special mechanism for classical music which I do not understand yet: Classical music is organized many times in movements. Example: CD1 contains "Konzert f?r Klavier und Orchester Nr. 20 d-moll" Track 1: 1: Allegro Track 2: 2: Romance Track 3: 3: Rondo. (Allegro assai) "Konzert f?r Klavier und Orchester Nr. 21" Track 4: 1: Allegro Track 5: 2: Andante Track 6: 3: Prestoprontotrallala Another CD2 may contain: Track 1: "Konzert f?r Klavier und Orchester Nr. 21" - 2: Andante Track 2: "Konzert f?r Klavier und Orchester Nr. 20 d-moll" - 1: Allegro I'd like to see this info e.g. sorted and categorized as Composer: Mozart, Wolfgang Amadeus Concerto: 20 "Konzert f?r Klavier und Orchester Nr. 20 d-moll" [CD1] 1: Allegro [CD1-01] 2: Romance [CD1-02] 3: Rondo. (Allegro assai) [CD1-03] "Konzert f?r Klavier und Orchester Nr. 20 d-moll" 2: Andante [CD2-02] This would require hierarchical mechanisms which tracks are sons of a higher level sub-playlist. This may be useful not only for classical music, but e.g. for audio books, for live concertos etc. I'm not sure whether the concept of TIT1, TIT2, TIT3 is sufficient here. What's the actual status and recommendation for classical music? Thanks, Martin - Germany -- "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From maillist at steelskies.com Fri May 26 00:41:20 2006 From: maillist at steelskies.com (Jonathan del Strother) Date: Fri, 26 May 2006 08:41:20 +0100 Subject: [ID3 Dev] ID3v2.4 support in real world In-Reply-To: <27905705A869164CBE58B96BA8547557036593BE@mail.internal.cddb.com> References: <27905705A869164CBE58B96BA8547557036593BE@mail.internal.cddb.com> Message-ID: <2412F7EC-F96E-4D50-8401-6543DD5F229E@steelskies.com> On 25 May 2006, at 23:46, Robert Manson wrote: > Also you should consider the iTunes Frame size bug, whereby v2.4 > frames > are written with an incorrect non-syncsafe frame size. (Actually I > haven't verified that they are *still* doing this... has anyone tested > with the latest iTunes?) They were still doing it when I wrote my id3 parser for CoverFlow, about 4 months ago. Sucks, huh? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2114 bytes Desc: not available URL: From kipp at gremillion.org Fri May 12 07:15:19 2006 From: kipp at gremillion.org (Kipp Gremillion) Date: Fri, 12 May 2006 09:15:19 -0500 Subject: [ID3 Dev] Catalog # Message-ID: <000501c675ce$80a927c0$6400a8c0@thedjbooth> Is there a tag for the Catalog #? If not seems that there should be. With multiple releases of the same album/single, and the editions very often being different and having different tracks, how would you know track 3 on one album/single is the same on another. I work with singles a lot and if you don't have the label/catalog number you could be talking about multiple single releases with the same title. Sometimes even double digit releases with the same title. Thanks, Kipp -------------- next part -------------- An HTML attachment was scrubbed... URL: From rmanson at gracenote.com Thu May 25 19:05:04 2006 From: rmanson at gracenote.com (Robert Manson) Date: Thu, 25 May 2006 19:05:04 -0700 Subject: [ID3 Dev] ID3v2.4 support in real world Message-ID: <27905705A869164CBE58B96BA8547557269FC2@mail.internal.cddb.com> Assuming the he wants to be as compatible as possible with the most popular MP3 players (Windows XP shell, iTunes, WMP and WinAmp) I would rate being able to rewrite an ID3 tag in TagLib while preserving Genre and Year frames as pretty low priority since none of those use TagLib. Not that I have anything against either taglib or KDE. -----Original Message----- From: Ben Bennett [mailto:fiji at ayup.limey.net] Sent: Thursday, May 25, 2006 6:54 PM To: id3v2 at id3.org Subject: Re: [ID3 Dev] ID3v2.4 support in real world On Fri, May 26, 2006 at 12:44:08AM +0200, Jiri Cincura wrote: > Just one note. Fix me, if I'm wrong. There's no change in header structure > between v2.3 and v2.4, right? Because for testing I've just changed the > number indicating the version in my hex editor. Tag header or frame header? I assume you mean tag header. There are some minor changes to the tag header: - The meaning for the unsynchronization flag is different - The extended header is different - There is a new flag to indicate a footer is present I think that's all. http://www.id3.org/id3v2.4.0-changes.txt has the full details of the changes. As a note, Amarok (well, taglib) only writes 2.4 (it converts 2.3 to 2.4 on any write). And it seems to do a crappy job interpreting the 2.3 frames (dates and genres in particular)... sigh. The best solution that I have come up with to navigate between the peculiarities of iTunes (bust frame length in 2.4) and Amarok (see above) is to write a 2.4 tag but only attatch one image to it, and make sure the image is at the end. -ben --------------------------------------------------------------------- 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 fiji at ayup.limey.net Thu May 25 18:54:25 2006 From: fiji at ayup.limey.net (Ben Bennett) Date: Thu, 25 May 2006 21:54:25 -0400 Subject: [ID3 Dev] ID3v2.4 support in real world In-Reply-To: <44763338.40700@cincura.net> References: <44763235.3000501@cincura.net> <44763338.40700@cincura.net> Message-ID: <20060526015425.GA25539@ayup.limey.net> On Fri, May 26, 2006 at 12:44:08AM +0200, Jiri Cincura wrote: > Just one note. Fix me, if I'm wrong. There's no change in header structure > between v2.3 and v2.4, right? Because for testing I've just changed the > number indicating the version in my hex editor. Tag header or frame header? I assume you mean tag header. There are some minor changes to the tag header: - The meaning for the unsynchronization flag is different - The extended header is different - There is a new flag to indicate a footer is present I think that's all. http://www.id3.org/id3v2.4.0-changes.txt has the full details of the changes. As a note, Amarok (well, taglib) only writes 2.4 (it converts 2.3 to 2.4 on any write). And it seems to do a crappy job interpreting the 2.3 frames (dates and genres in particular)... sigh. The best solution that I have come up with to navigate between the peculiarities of iTunes (bust frame length in 2.4) and Amarok (see above) is to write a 2.4 tag but only attatch one image to it, and make sure the image is at the end. -ben --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From diskuze at cincura.net Thu May 25 15:39:49 2006 From: diskuze at cincura.net (Jiri Cincura) Date: Fri, 26 May 2006 00:39:49 +0200 Subject: [ID3 Dev] ID3v2.4 support in real world Message-ID: <44763235.3000501@cincura.net> Hi *, I'm doing some refactoring in my code of ID3 renamer and i'm thinking about writing tags in ID3v2.4 (now I'm writing 2.3). But I've tested the support for it and it seems to be, that it's not good. Some SW simply reads it, but writes new tag in front of ID3v2.3 (Windows Shell), some SW don't read it, but writes new tag in front of it (WinAmp 2.x) and WMP also isn't able to read it. I've also tested some SW for writing into clean file, and all writes ID3v2.3. So what's your expirience? Am I stay writing ID3v2.3 'cause v2.4 isn't supported at all? -- Jiri Cincura http://www.cincura.net/ --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org