From jmartin92 at comcast.net Fri Aug 17 09:55:48 2007 From: jmartin92 at comcast.net (Jim) Date: Fri, 17 Aug 2007 12:55:48 -0400 Subject: [ID3 Dev] extended header In-Reply-To: <8A47F91F-D7F8-4716-8C2E-571DDF9FE95F@gmx.at> References: <8A47F91F-D7F8-4716-8C2E-571DDF9FE95F@gmx.at> Message-ID: <46C5D314.2070205@comcast.net> Hi Clemens. From the 2.3 spec, "Where the 'Extended header size', currently 6 or 10 bytes, excludes itself." I think this means that the 4 bytes used to store the size are not included in the size. So that leaves 2 bytes for the flags, 4 bytes for the size of the padding and an optional 4 bytes for the CRC data. Giving possible sizes of 6 (2+4) or 10 (2+4+4) bytes. Jim Clemens Hammerl wrote: > Hello > > I have still problems understanding the extended header. In the > specification stands that the size of header in v2.3 ist either 6 or 10 > Bytes. > > Jim wrote that the header is 10 Bytes if he is followed by a 4 Byte CRC > data is appended after the header. > But the headers size would be 14 Bytes cause the minimum size is 10 (4 > Bytes header size, 2 Bytes flags, 4 Bytes padding size = 10 Bytes). Or > is the checksum size note included in the header size? Ist it possible > that there is an extended header but no padding? > > > Extended header size $xx xx xx xx > Extended Flags $xx xx > Size of padding $xx xx xx xx > CRC-32 data $xx xx xx xx ( optional ) > > clemens > > > --------------------------------------------------------------------- > 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 jmartin92 at comcast.net Tue Aug 14 12:31:29 2007 From: jmartin92 at comcast.net (Jim) Date: Tue, 14 Aug 2007 15:31:29 -0400 Subject: [ID3 Dev] id3v2-3 extended header In-Reply-To: <099FAB87-223D-401B-A4A7-6D7E9150403A@gmx.at> References: <46C1D3E6.1040108@comcast.net> <099FAB87-223D-401B-A4A7-6D7E9150403A@gmx.at> Message-ID: <46C20311.3030600@comcast.net> I believe the 6 or 10 byte size only applies to v2.3 tags. The extended header size will be 10 bytes when the CRC flag is set (4 added bytes for the CRC value) and 6 byte when the CRC flag is unset. To find the beginning of the frames, you would start at position 10 + size of extended header if present. For v2.3 tags, you would read the first ten bytes (tag header) and then, if there is an extended header, read 4 bytes to get its size and then skip that many bytes. (The padding that is given in the extended header comes AFTER the frames.) For v2.4 tags, you would read the first ten bytes (tag header) and then, if there is an extended header, read 4 bytes to get its size and then skip (size - 4) bytes ahead. (I believe in v2.4 tags, the size given in the extended header includes the 4 bytes you would have already read.) And don't forget that in v2.4 tags, the extended header size is stored as a syncsafe integer. Check out this diagram. It should help: Overall tag structure: +-----------------------------+ | Header (10 bytes) | +-----------------------------+ | Extended Header | | (variable length, OPTIONAL) | +-----------------------------+ | Frames (variable length) | +-----------------------------+ | Padding | | (variable length, OPTIONAL) | +-----------------------------+ | Footer (10 bytes, OPTIONAL) | +-----------------------------+ Clemens Hammerl wrote: > hi > > more questions inline... > > Am 14.08.2007 um 18:10 schrieb Jim: > >> Hi Clemens. >> >> I'm not sure which version of ID3v2 you are asking about. However, in >> both v2.3 and v2.4 tags, the extended header size is the first four >> bytes. For v2.3: >> >> Extended header size $xx xx xx xx >> Extended Flags $xx xx >> Size of padding $xx xx xx xx > > So the extended header size is variable in 2.3/4 and not constantly 10 > Bytesin size? Im just confused about the variable size of the header. > > I will not implement extended headers im only interested in parsing the > Text Information Frames, so i have to search for the beginning of the > frames at position 10(Tag header) + extendedHeaderSize + SizeOfPadding. > Am I right? > >> >> And for v2.4: >> >> Extended header size 4 * %0xxxxxxx >> Number of flag bytes $01 >> Extended Flags $xx >> >> >> Is that what you were asking? (Both of those descriptions were taken >>> from the specs available on the ID3 website so you can look there for a >> more thorough description of each field.) >> >> I can only guess why the size is stored as 4 bytes. My guesses would >> be both for future compatability if the extended header becomes larger >> in later versions and to make it standard with the rest of the sizes >> (overall tag size & frame sizes). >> >> Jim >> >> >> Clemens Hammerl wrote: >>> Hi >>> Im new to id3 an this list and i'm currently working on an >>> implementation of ID3 for Java. >>> I dont understand how the length of extended header is calculated. In >>> the specification stands that: >>> "...Where the 'Extended header size', currently 6 or 10 bytes, excludes >>> itself..." >>> But were in the header is the size of the header stored. Is it in the >>> first 4 bytes. Why do you use 4 bytes when the maximum length is 10B? >>> best regards clemens >>> --------------------------------------------------------------------- >>> 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 beat84 at gmx.at Fri Aug 17 09:38:06 2007 From: beat84 at gmx.at (Clemens Hammerl) Date: Fri, 17 Aug 2007 18:38:06 +0200 Subject: [ID3 Dev] extended header Message-ID: <8A47F91F-D7F8-4716-8C2E-571DDF9FE95F@gmx.at> Hello I have still problems understanding the extended header. In the specification stands that the size of header in v2.3 ist either 6 or 10 Bytes. Jim wrote that the header is 10 Bytes if he is followed by a 4 Byte CRC data is appended after the header. But the headers size would be 14 Bytes cause the minimum size is 10 (4 Bytes header size, 2 Bytes flags, 4 Bytes padding size = 10 Bytes). Or is the checksum size note included in the header size? Ist it possible that there is an extended header but no padding? Extended header size $xx xx xx xx Extended Flags $xx xx Size of padding $xx xx xx xx CRC-32 data $xx xx xx xx ( optional ) clemens --------------------------------------------------------------------- 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 Aug 16 02:37:01 2007 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Thu, 16 Aug 2007 10:37:01 +0100 Subject: [ID3 Dev] CHAP tags and their embedded frames In-Reply-To: <200708031144.48429.onlymeok@nildram.co.uk> References: <200708031144.48429.onlymeok@nildram.co.uk> Message-ID: <6.2.0.14.2.20070816100715.02d82ac0@pop3> At 11:44 03/08/2007, you wrote: >According to the V2.4 standard a typical text frame need not contain null >termination since it does not contain multiple chained text strings for which >the null terminator is introduced to separate them, yet in the definition of >the chapter tag 'CHAP' (described in the chapter tag addendum) it explicitly >shows embedded text frames which have null terminators. Stephen, You're correct - the null terminations in the sub-frames are superfluous. Luckily, the diagrams are only examples but it would make sense to revise them to avoid confusion. Cheers, Chris _______________________ Chris Newell Lead Technologist BBC Research Kingswood Warren Tel: +44 (0)1737 839659 -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul_t100 at fastmail.fm Mon Aug 6 06:21:03 2007 From: paul_t100 at fastmail.fm (Paul Taylor) Date: Mon, 06 Aug 2007 14:21:03 +0100 Subject: [ID3 Dev] Distingusihing between v10 and v11 Message-ID: <46B7203F.70207@fastmail.fm> Hi just want to double check, that if there is no track number present it is not possible to differentiate between ID3v1 and ID3v11. To put it another way if a user requested that a tag should be saved as ID3v11 and thy have not supplied a track number a subsequent read should return the track as ID3v10 ? thanks paul --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From beat84 at gmx.at Tue Aug 14 11:09:29 2007 From: beat84 at gmx.at (Clemens Hammerl) Date: Tue, 14 Aug 2007 20:09:29 +0200 Subject: [ID3 Dev] id3v2-3 extended header In-Reply-To: <46C1D3E6.1040108@comcast.net> References: <46C1D3E6.1040108@comcast.net> Message-ID: <099FAB87-223D-401B-A4A7-6D7E9150403A@gmx.at> hi more questions inline... Am 14.08.2007 um 18:10 schrieb Jim: > Hi Clemens. > > I'm not sure which version of ID3v2 you are asking about. However, > in both v2.3 and v2.4 tags, the extended header size is the first > four bytes. For v2.3: > > Extended header size $xx xx xx xx > Extended Flags $xx xx > Size of padding $xx xx xx xx So the extended header size is variable in 2.3/4 and not constantly 10 Bytesin size? Im just confused about the variable size of the header. I will not implement extended headers im only interested in parsing the Text Information Frames, so i have to search for the beginning of the frames at position 10(Tag header) + extendedHeaderSize + SizeOfPadding. Am I right? > > And for v2.4: > > Extended header size 4 * %0xxxxxxx > Number of flag bytes $01 > Extended Flags $xx > > > Is that what you were asking? (Both of those descriptions were taken >> from the specs available on the ID3 website so you can look there >> for a > more thorough description of each field.) > > I can only guess why the size is stored as 4 bytes. My guesses > would be both for future compatability if the extended header > becomes larger in later versions and to make it standard with the > rest of the sizes (overall tag size & frame sizes). > > Jim > > > Clemens Hammerl wrote: >> Hi >> Im new to id3 an this list and i'm currently working on an >> implementation of ID3 for Java. >> I dont understand how the length of extended header is calculated. >> In the specification stands that: >> "...Where the 'Extended header size', currently 6 or 10 bytes, >> excludes >> itself..." >> But were in the header is the size of the header stored. Is it in >> the first 4 bytes. Why do you use 4 bytes when the maximum length >> is 10B? >> best regards clemens >> --------------------------------------------------------------------- >> 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 dalepres at msn.com Mon Aug 6 19:37:19 2007 From: dalepres at msn.com (Dale Preston) Date: Mon, 6 Aug 2007 21:37:19 -0500 Subject: [ID3 Dev] Distingusihing between v10 and v11 References: <46B7203F.70207@fastmail.fm> Message-ID: In my apps, if the last two bytes of the comment field are 0 values, then I always call it a 1.0 tag. There is no way, when reading the tag back, to know the intention of the creator. I haven't really thought about it before but now that you raised the question I may, in the future, raise an exception if a 1.1 version frame is requested and the user does not supply a track number. Dale ----- Original Message ----- From: "Paul Taylor" To: Sent: Monday, August 06, 2007 8:21 AM Subject: [ID3 Dev] Distingusihing between v10 and v11 > Hi just want to double check, that if there is no track number present it > is not possible to differentiate between ID3v1 and ID3v11. To put it > another way if a user requested that a tag should be saved as ID3v11 and > thy have not supplied a track number a subsequent read should return the > track as ID3v10 ? > > thanks 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 rmanson at gracenote.com Mon Aug 6 12:06:03 2007 From: rmanson at gracenote.com (Robert Manson) Date: Mon, 6 Aug 2007 12:06:03 -0700 Subject: [ID3 Dev] Distingusihing between v10 and v11 In-Reply-To: <46B7203F.70207@fastmail.fm> References: <46B7203F.70207@fastmail.fm> Message-ID: <119461A3B1C2A847BABA421E6EB62CEA1841FF@EMAIL1.gracenote.gracenote.com> If there is no track number it is not possible to distinguish between the two. Distinguishing between the two and surfacing that distinction in an application or even at the API level is not useful IMHO. -R -----Original Message----- From: Paul Taylor [mailto:paul_t100 at fastmail.fm] Sent: Monday, August 06, 2007 6:21 AM To: id3v2 at id3.org Subject: [ID3 Dev] Distingusihing between v10 and v11 Hi just want to double check, that if there is no track number present it is not possible to differentiate between ID3v1 and ID3v11. To put it another way if a user requested that a tag should be saved as ID3v11 and thy have not supplied a track number a subsequent read should return the track as ID3v10 ? thanks 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 onlymeok at nildram.co.uk Fri Aug 3 03:44:48 2007 From: onlymeok at nildram.co.uk (Stephen Fairchild) Date: Fri, 3 Aug 2007 11:44:48 +0100 Subject: [ID3 Dev] CHAP tags and their embedded frames Message-ID: <200708031144.48429.onlymeok@nildram.co.uk> According to the V2.4 standard a typical text frame need not contain null termination since it does not contain multiple chained text strings for which the null terminator is introduced to separate them, yet in the definition of the chapter tag 'CHAP' (described in the chapter tag addendum) it explicitly shows embedded text frames which have null terminators. This is an inconsistency which I would like to see cleared up. Was it intentionally done this way or was it a mistake? Surely it is a mistake to call an embedded TIT2 subframe which does not conform to the same format as a non embedded TIT2 frame a TIT2 frame in the first place unless it is the case that it is within the standard for a TIT2 frame which contains one string of text and is not embedded to be null terminated however on reading about text frames this is not the impression that I got. Am I also to assume due to the non standardness I have illustrated that normally valid use cases that involve embedding multiple strings (null separated) within text frames are not supported within chapter frames? -- Stephen Fairchild. --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From beat84 at gmx.at Wed Aug 15 02:09:27 2007 From: beat84 at gmx.at (Clemens Hammerl) Date: Wed, 15 Aug 2007 11:09:27 +0200 Subject: [ID3 Dev] id3v2-3 extended header In-Reply-To: <46C20311.3030600@comcast.net> References: <46C1D3E6.1040108@comcast.net> <099FAB87-223D-401B-A4A7-6D7E9150403A@gmx.at> <46C20311.3030600@comcast.net> Message-ID: <788FDD94-1074-42C7-855E-FA632D8657F7@gmx.at> Is there a test suite for id3v2 tags too? If not, can you send me a testfile with an extended header for v2.3 and 2.4, otherwise i cannot test my code becaus i have no mp3s with extended header. How do i know how long the frame part of the tag is if there is an extended header? Am 14.08.2007 um 21:31 schrieb Jim: > I believe the 6 or 10 byte size only applies to v2.3 tags. The > extended header size will be 10 bytes when the CRC flag is set (4 > added bytes for the CRC value) and 6 byte when the CRC flag is unset. > > To find the beginning of the frames, you would start at position 10 > + size of extended header if present. > > For v2.3 tags, you would read the first ten bytes (tag header) and > then, if there is an extended header, read 4 bytes to get its size > and then skip that many bytes. (The padding that is given in the > extended header comes AFTER the frames.) > > For v2.4 tags, you would read the first ten bytes (tag header) and > then, if there is an extended header, read 4 bytes to get its size > and then skip (size - 4) bytes ahead. (I believe in v2.4 tags, the > size given in the extended header includes the 4 bytes you would > have already read.) And don't forget that in v2.4 tags, the > extended header size is stored as a syncsafe integer. > > Check out this diagram. It should help: > > Overall tag structure: > > +-----------------------------+ > | Header (10 bytes) | > +-----------------------------+ > | Extended Header | > | (variable length, OPTIONAL) | > +-----------------------------+ > | Frames (variable length) | > +-----------------------------+ > | Padding | > | (variable length, OPTIONAL) | > +-----------------------------+ > | Footer (10 bytes, OPTIONAL) | > +-----------------------------+ > > > > Clemens Hammerl wrote: >> hi >> more questions inline... >> Am 14.08.2007 um 18:10 schrieb Jim: >>> Hi Clemens. >>> >>> I'm not sure which version of ID3v2 you are asking about. >>> However, in both v2.3 and v2.4 tags, the extended header size is >>> the first four bytes. For v2.3: >>> >>> Extended header size $xx xx xx xx >>> Extended Flags $xx xx >>> Size of padding $xx xx xx xx >> So the extended header size is variable in 2.3/4 and not >> constantly 10 Bytesin size? Im just confused about the variable >> size of the header. >> I will not implement extended headers im only interested in >> parsing the Text Information Frames, so i have to search for the >> beginning of the frames at position 10(Tag header) + >> extendedHeaderSize + SizeOfPadding. Am I right? >>> >>> And for v2.4: >>> >>> Extended header size 4 * %0xxxxxxx >>> Number of flag bytes $01 >>> Extended Flags $xx >>> >>> >>> Is that what you were asking? (Both of those descriptions were >>> taken >>>> from the specs available on the ID3 website so you can look >>>> there for a >>> more thorough description of each field.) >>> >>> I can only guess why the size is stored as 4 bytes. My guesses >>> would be both for future compatability if the extended header >>> becomes larger in later versions and to make it standard with the >>> rest of the sizes (overall tag size & frame sizes). >>> >>> Jim >>> >>> >>> Clemens Hammerl wrote: >>>> Hi >>>> Im new to id3 an this list and i'm currently working on an >>>> implementation of ID3 for Java. >>>> I dont understand how the length of extended header is >>>> calculated. In the specification stands that: >>>> "...Where the 'Extended header size', currently 6 or 10 bytes, >>>> excludes >>>> itself..." >>>> But were in the header is the size of the header stored. Is it >>>> in the first 4 bytes. Why do you use 4 bytes when the maximum >>>> length is 10B? >>>> best regards clemens >>>> ------------------------------------------------------------------- >>>> -- >>>> 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 jmartin92 at comcast.net Tue Aug 14 09:10:14 2007 From: jmartin92 at comcast.net (Jim) Date: Tue, 14 Aug 2007 12:10:14 -0400 Subject: [ID3 Dev] id3v2-3 extended header In-Reply-To: References: Message-ID: <46C1D3E6.1040108@comcast.net> Hi Clemens. I'm not sure which version of ID3v2 you are asking about. However, in both v2.3 and v2.4 tags, the extended header size is the first four bytes. For v2.3: Extended header size $xx xx xx xx Extended Flags $xx xx Size of padding $xx xx xx xx And for v2.4: Extended header size 4 * %0xxxxxxx Number of flag bytes $01 Extended Flags $xx Is that what you were asking? (Both of those descriptions were taken from the specs available on the ID3 website so you can look there for a more thorough description of each field.) I can only guess why the size is stored as 4 bytes. My guesses would be both for future compatability if the extended header becomes larger in later versions and to make it standard with the rest of the sizes (overall tag size & frame sizes). Jim Clemens Hammerl wrote: > Hi > > Im new to id3 an this list and i'm currently working on an > implementation of ID3 for Java. > I dont understand how the length of extended header is calculated. In > the specification stands that: > > "...Where the 'Extended header size', currently 6 or 10 bytes, excludes > itself..." > > But were in the header is the size of the header stored. Is it in the > first 4 bytes. Why do you use 4 bytes when the maximum length is 10B? > > best regards clemens > > --------------------------------------------------------------------- > 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 beat84 at gmx.at Tue Aug 14 06:15:09 2007 From: beat84 at gmx.at (Clemens Hammerl) Date: Tue, 14 Aug 2007 15:15:09 +0200 Subject: [ID3 Dev] id3v2-3 extended header Message-ID: Hi Im new to id3 an this list and i'm currently working on an implementation of ID3 for Java. I dont understand how the length of extended header is calculated. In the specification stands that: "...Where the 'Extended header size', currently 6 or 10 bytes, excludes itself..." But were in the header is the size of the header stored. Is it in the first 4 bytes. Why do you use 4 bytes when the maximum length is 10B? best regards clemens --------------------------------------------------------------------- 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 Mon Aug 6 14:33:51 2007 From: paul_t100 at fastmail.fm (Paul Taylor) Date: Mon, 06 Aug 2007 22:33:51 +0100 Subject: [ID3 Dev] Distingusihing between v10 and v11 In-Reply-To: <119461A3B1C2A847BABA421E6EB62CEA1841FF@EMAIL1.gracenote.gracenote.com> References: <46B7203F.70207@fastmail.fm> <119461A3B1C2A847BABA421E6EB62CEA1841FF@EMAIL1.gracenote.gracenote.com> Message-ID: <46B793BF.4010406@fastmail.fm> Robert Manson wrote: > Distinguishing between the two and surfacing that distinction in an > application or even at the API level is not useful IMHO. > > -R yes ive come to same conclusion myself, definently wrt to application, not sure about api --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From mpompu at yahoo.com Tue Aug 14 23:41:46 2007 From: mpompu at yahoo.com (Michael Pomputius) Date: Tue, 14 Aug 2007 23:41:46 -0700 (PDT) Subject: [ID3 Dev] id3v1/v2 tags in windows media player Message-ID: <28468.8313.qm@web38912.mail.mud.yahoo.com> Hi, I'm not sure if this is the wrong mail list for this or not. Does anyone know how to get Windows Media player to read id3v1 or id3v2 tags in mp3 files? My laptop hard disk crashed, I got a new disk and mp3 files copied over. When I port them into realplayer it grabs all the tagging info, but when I import them into Windows Media player (version 10) it does not get any tagging information. My mp3 player (iRiver H10) can only be used with Windows Media Player. Some shareware I got says the files have id3v1 or id3v2 tags. Thanks, Mike ____________________________________________________________________________________ Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow -------------- next part -------------- An HTML attachment was scrubbed... URL: From dalepres at msn.com Wed Aug 15 16:45:32 2007 From: dalepres at msn.com (Dale Preston) Date: Wed, 15 Aug 2007 18:45:32 -0500 Subject: [ID3 Dev] id3v1/v2 tags in windows media player References: <28468.8313.qm@web38912.mail.mud.yahoo.com> Message-ID: Try my Raw Tag Viewer at http://www.dalepreston.com/Blog/2007/02/id3-raw-tag-viewer.html. It might point you in the direction of what is wrong in your tags. ----- Original Message ----- From: Michael Pomputius To: id3v2 at id3.org Sent: Wednesday, August 15, 2007 1:41 AM Subject: [ID3 Dev] id3v1/v2 tags in windows media player Hi, I'm not sure if this is the wrong mail list for this or not. Does anyone know how to get Windows Media player to read id3v1 or id3v2 tags in mp3 files? My laptop hard disk crashed, I got a new disk and mp3 files copied over. When I port them into realplayer it grabs all the tagging info, but when I import them into Windows Media player (version 10) it does not get any tagging information. My mp3 player (iRiver H10) can only be used with Windows Media Player. Some shareware I got says the files have id3v1 or id3v2 tags. Thanks, Mike ------------------------------------------------------------------------------ Need a vacation? Get great deals to amazing places on Yahoo! Travel. -------------- next part -------------- An HTML attachment was scrubbed... URL: