From chris.newell at rd.bbc.co.uk Wed Aug 13 04:25:48 2008 From: chris.newell at rd.bbc.co.uk (Chris Newell) Date: Wed, 13 Aug 2008 12:25:48 +0100 Subject: [ID3 Dev] Flash-based ID3v2 chapter player Message-ID: <7.0.1.0.2.20080813121741.022f6230@rd.bbc.co.uk> Just a heads-up to let you know we've released a Flash-based player for ID3v2 chapters: http://sourceforge.net/forum/forum.php?forum_id=856231 Chris --------------------------------------------------------------------- To unsubscribe, e-mail: id3v2-unsubscribe at id3.org For additional commands, e-mail: id3v2-help at id3.org From markus at multrus.com Sun Aug 17 13:52:16 2008 From: markus at multrus.com (Markus Multrus) Date: Sun, 17 Aug 2008 22:52:16 +0200 Subject: [ID3 Dev] v2.4 frame syntax: compression and data length indication Message-ID: <48A88F80.8020606@multrus.com> 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. " 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