From treaves at silverfieldstech.com Mon Dec 1 10:36:09 2008 From: treaves at silverfieldstech.com (Timothy Reaves) Date: Mon, 1 Dec 2008 13:36:09 -0500 Subject: [ID3 Dev] v2.4 frame syntax: compression and data length indication In-Reply-To: <48A88F80.8020606@multrus.com> References: <48A88F80.8020606@multrus.com> Message-ID: <30DFD07E-5043-4231-854E-110C0407A197@silverfieldstech.com> On Aug 17, 2008, at 4:52 PM, Markus Multrus wrote: > Hi, > > I'm trying to understand the correct syntax in v2.4 with regards to > compression and data length indication. In section 4.1 is written: > > " > Some frame format flags indicate that additional information fields > are added to the frame. This information is added after the frame > header and before the frame data in the same order as the flags that > indicates them. I.e. the four bytes of decompressed size will precede > the encryption method byte. These additions affects the 'frame size' > field, but are not subject to encryption or compression. > " This means that every flag that is set in the frame header flags, that requires additional data, will have it's data after the frame header but before the frame payload. Each one of the flags requiring extra storage are: h - one byte for the group ID k - indirectly, as it then REQUIRES p to be set. m - one byte to connote encryption method p - a four byte sync safe integer. This value differs from the size in that this value does not take into account the possible six bytes for [h,m,p], and the payload being non-compressed, and non-encrypted. If encryption or compression is used, it is applied to the payload only. Not to the header and the possible extra data outlined above. > > > But in section 4.1.2 is written: > > " > k - Compression > > This flag indicates whether or not the frame is compressed. > A 'Data Length Indicator' byte MUST be included in the frame. > > 0 Frame is not compressed. > 1 Frame is compressed using zlib [zlib] deflate method. > If set, this requires the 'Data Length Indicator' bit > to be set as well. > " > > There are several things I do not understand: > > 1) What is a "'Data Length Indicator' byte"? Should this not read as > something like "4 bytes indication data length"? > > > 2) There is written that the 'Data Length Indicator' bit should be > set. > As I understand this, I would ad the data length indication only once, > i.e. at the very end of the additional payload, where it corresponds > to > the data length indicator bit. > In case for a frame format flag like '01001111' (which complies to the > requirement above) I would add the following data right after the > frame > header (and before the real frame payload): > > 1 byte grouping id > 1 byte encryption method > 4 byte data length indication (32 bit synchsafe) > > But this contradicts to the above cited section 4.1: > "(...) I.e. the four bytes of decompressed size will precede > the encryption method byte. (...)" > > Can anybody tell me, what is the correct implementation? > > Best, > > Markus > > --------------------------------------------------------------------- > 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 treaves at silverfieldstech.com Mon Dec 1 10:21:28 2008 From: treaves at silverfieldstech.com (Timothy Reaves) Date: Mon, 1 Dec 2008 13:21:28 -0500 Subject: [ID3 Dev] Suggestion For having multilingual id3 tags In-Reply-To: <5d6a96c10811301223w4e40214fv128cbe33fe38eeee@mail.gmail.com> References: <5d6a96c10811301223w4e40214fv128cbe33fe38eeee@mail.gmail.com> Message-ID: The spec does support it, but in an off-hand way. Each text frame can store more than one string. You would have to choose an encoding that would support all the characters in question. UTF8 would general suffice, but UTF16 to be sure; it's not like the extra bytes are relevant. The problem is most libraries do not support this aspect of the spec, nor do players - or other software - display them. On Nov 30, 2008, at 3:23 PM, Anton Stroganov wrote: > Yup. Same idea I suggested on this list back in Jun 07, see the > ensuing discussion on > http://thread.gmane.org/gmane.comp.multimedia.id3v2/437 > http://thread.gmane.org/gmane.comp.multimedia.id3v2/442 > > Not sure what to suggest, other than writing up a spec, releasing > some patched code to the id3 library and trying to get people to > start using it. Seems like the main spec is pretty much frozen, > nobody's developing it, and any significant changes are application- > specific using PRIV frames. > > On Sat, Nov 29, 2008 at 11:43 PM, Ahmed Sobhi > wrote: > Hello, > I'm a software developer but I'm not at all experienced with id3 > tagging system from a developer's perspective. > I'm facing a problem as a user and I just wanted to share that > problem and propose how I want it to be solved. > I'm Egyptian so part of my mp3s collection is for Egyptian and Arab > artists. The problem is with the songs, albums titles and artists > names. I'd like to see them in Arabic. > I know that this is possible with unicode and for sure that works > quite well for me. > > I'm talking about storing the names in multiple languages, like > having an artist's name in arabic and english. > For example, I have an artist called " ?? ?????" and in > English she is called Um Kalthoum. > I'd like to be able to search in my music library with either names. > A also believe that each can be used in a proper context > The original artist's language (in my case arabic) because it's only > logical to do so > English as a current universal standard > > I think it'd be a great feature for those whose first language is > not English. > > So what I'm suggesting is to allow some fields to be stored with > different language versions. > So there will Artist (english): Um Kalthoum and Artist (arabic): ?? > ????? > The same can co for album and title and any other fields that can > expose such behavior. > > What do you think? > Regards, > Ahmed Sobhi > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brendanfromireland at gmail.com Sat Dec 6 23:25:40 2008 From: brendanfromireland at gmail.com (Brendan Kehoe) Date: Sun, 7 Dec 2008 07:25:40 +0000 (UTC) Subject: [ID3 Dev] Re: popularimeter tag References: <6a819a10811251704m5e9a6f09xc0823c152367e46c@mail.gmail.com> <20081126022044.GA22198@ayup.limey.net> <4D1B17C7-0E0D-43E0-A30A-F54AE7658795@mp3tag.de> Message-ID: Wyatt I want a manual rating stored in the files. Sorry I didnt reply until now. I didnt get any notification of responses. I just happened to go back to this newsgroup. I am using mediamonkey and mp3tag at the moment. mediamonkey is not working on my home computer but i use it in college. I havnt found any application, tag editor or otherwise, other than mp3tag that can read or edit mediamonkeys ratings. They do not seem to use the popularimeter tag properly because easytag and kid3 seem to support popm popularimeter tag but cant read the mm rating. I searched "support for popm" and have searched a lot on this before with no luck. I tried using windows media player to store the ratings but they werent saved when i used wmp on another computer. I havnt looked extensively in wmp settings but i doubt wmp uses the tag properly if mm doesnt. Maybe I should have a look. I just thought there might be some good open source player for linux that could use the popularimeter tag and would not stop working like mediamonkey has for me at home. Does anybody know software that uses popm properly? Also I will check this newsgroup soon to reply faster than before. Thanks very much Brendan --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From trent.arms at gmail.com Fri Dec 5 09:09:06 2008 From: trent.arms at gmail.com (Wyatt) Date: Fri, 5 Dec 2008 12:09:06 -0500 Subject: [ID3 Dev] PCNT question In-Reply-To: <20081205010944.GA22748@ayup.limey.net> References: <92BD0EEC-41D7-4A68-89B2-F068D01973FF@silverfieldstech.com> <49387E11.3060104@northpb.com> <20081205010944.GA22748@ayup.limey.net> Message-ID: Perhaps something like how OpenGL works does only done within the community instead of by vendors (and under a benevolent dictatorship or high ruling council or something to streamline it). If someone extends the spec or makes a change, see if people remember or care about it after six months or a year or so. If the reaction is positive, even from a vocal minority, consider modifying the official spec and bump it's revision. Or, let it sit and "cure" longer-- in either case you have a fair litmus for the direction that meta information is headed). Every few years, take a week (or however long it would take.) to evaluate what's in and what's gone in, prune out the cruft, and keep the good stuff. Bump the minor. Or hell, we could always do what they do with D and just break everything, start fresh, and call it ID3v3 ;) While I strongly agree that "willy-nilly" editing of the spec is absolutely inexcusable, so too do I feel that a successful specification should be flexible; either by being relatively easy to modify incrementally or by being sufficiently future-proof that it can survive the unforeseeable. Obviously I'm pulling this particular process straight out of my rear, right now, but even as an idea; as long as the end result is in the control of "responsible" persons for the "official" copy, others are encouraged then to stick close to it in spirit, even as they add things. Anyway, that's enough rambling from me, for now. -Wyatt On Thu, Dec 4, 2008 at 20:09, Ben Bennett wrote: > On Thu, Dec 04, 2008 at 05:04:17PM -0800, Dan O'Neill wrote: > > Hi Timothy, > > > > It's like mostly my fault for not having a more collaborative wiki setup > > that enables discussion and revision of the spec. I've been busy with > > my day job (http://trusonic.com) over the last year. New hardware and > > software and stuff took up a considerable amount of bandwidth. I *will* > > make some changes over the next month to enable this spec to get fixed > > by those who want to contribute. My apologies to the entire group. > > That's great, but I want to urge you to discuss your plans here first > because I really don't want people to edit the spec willy-nilly. I > think the language of the spec should remain unchanged, but then we > can add clarifications to particular items, but they must be clearly > not part of the official spec. > > -ben > > --------------------------------------------------------------------- > 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 fiji at ayup.limey.net Thu Dec 4 17:09:44 2008 From: fiji at ayup.limey.net (Ben Bennett) Date: Thu, 4 Dec 2008 20:09:44 -0500 Subject: [ID3 Dev] PCNT question In-Reply-To: <49387E11.3060104@northpb.com> References: <92BD0EEC-41D7-4A68-89B2-F068D01973FF@silverfieldstech.com> <49387E11.3060104@northpb.com> Message-ID: <20081205010944.GA22748@ayup.limey.net> On Thu, Dec 04, 2008 at 05:04:17PM -0800, Dan O'Neill wrote: > Hi Timothy, > > It's like mostly my fault for not having a more collaborative wiki setup > that enables discussion and revision of the spec. I've been busy with > my day job (http://trusonic.com) over the last year. New hardware and > software and stuff took up a considerable amount of bandwidth. I *will* > make some changes over the next month to enable this spec to get fixed > by those who want to contribute. My apologies to the entire group. That's great, but I want to urge you to discuss your plans here first because I really don't want people to edit the spec willy-nilly. I think the language of the spec should remain unchanged, but then we can add clarifications to particular items, but they must be clearly not part of the official spec. -ben --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From id3v2 at northpb.com Thu Dec 4 17:04:17 2008 From: id3v2 at northpb.com (Dan O'Neill) Date: Thu, 04 Dec 2008 17:04:17 -0800 Subject: [ID3 Dev] PCNT question In-Reply-To: <92BD0EEC-41D7-4A68-89B2-F068D01973FF@silverfieldstech.com> References: <92BD0EEC-41D7-4A68-89B2-F068D01973FF@silverfieldstech.com> Message-ID: <49387E11.3060104@northpb.com> Hi Timothy, It's like mostly my fault for not having a more collaborative wiki setup that enables discussion and revision of the spec. I've been busy with my day job (http://trusonic.com) over the last year. New hardware and software and stuff took up a considerable amount of bandwidth. I *will* make some changes over the next month to enable this spec to get fixed by those who want to contribute. My apologies to the entire group. Dan Timothy Reaves wrote: > This is a great example of what is wrong with ID3 specification. The > 2.4 version of the write-up shows this as > 4.16. Play counter > > This is simply a counter of the number of times a file has been > played. The value is increased by one every time the file begins to > play. There may only be one "PCNT" frame in each tag. When the > counter reaches all one's, one byte is inserted in front of the > counter thus making the counter eight bits bigger. The counter must > be at least 32-bits long to begin with. > >
> Counter $xx xx xx xx (xx ...) > > Now, there are several possible ways to interpret this. Most of the > libraries seem to just read it as a 32bit int, but that's just wrong. > > The way I interpret it is it's an arbitrary width uint. So at the > outset, it's a 32bit uint, and when that is full, it becomes a 40bit > uint, etc. > > I've subscribed to this list for a while now, and people have > questions on the current spec's. But the spec's never are updated for > errors or ambiguities. Is it really a dead spec, as everyone else (with > meta data libraries) is saying? > > --------------------------------------------------------------------- > 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 Erol.Dumm at web.de Wed Dec 10 11:36:02 2008 From: Erol.Dumm at web.de (Erol Dumm) Date: Wed, 10 Dec 2008 20:36:02 +0100 Subject: [ID3 Dev] iTunes 7 Message-ID: <822332569@web.de> For some tests I need iTunes 7. Does anyone knows how to get iTunes 7. Erol _______________________________________________________________________ Sensationsangebot verl?ngert: WEB.DE FreeDSL - Telefonanschluss + DSL f?r nur 16,37 Euro/mtl.!* http://dsl.web.de/?ac=OM.AD.AD008K15039B7069a --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From brendanfromireland at gmail.com Wed Dec 10 12:27:04 2008 From: brendanfromireland at gmail.com (brendan kehoe) Date: Wed, 10 Dec 2008 20:27:04 +0000 Subject: [ID3 Dev] iTunes 7 In-Reply-To: <822332569@web.de> References: <822332569@web.de> Message-ID: <78c50a160812101227i5afabc46v99fda45cf159deba@mail.gmail.com> Erol Dumm www.apple.com/itunes/ use google :) --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org