Displaying 7 results from an estimated 7 matches for "header_type_flag".
2008 Feb 24
2
eos on continued page
...engths. I would have expected the eos
to refer to the same packet that the granulepos refers to, ie. the
segment of length 1653.
However, when later reading this file via libogg, no packets in that
track are marked as eos, and hence it fails oggz-validate.
RFC3533 and framing.html both simply say:
header_type_flag bit 0x04: set: this is the last page of a logical
bitstream (eos)
Is this a bug in libogg (should it assign eos to the last completed
packet on the page marked eos), or in the specification (should it say
that the last page must not contain any incomplete packets, in which
case a page chopper will...
2008 Aug 15
0
Fwd: Fwd: New Ogg Dirac mapping draft
...8()
if (len == 255):
len += read_uint16()
if (len == 255+65535):
len += read_uint32()
And a len of 2^32 - 1 would indicate a continued packet?
We can't change the lacing scheme without changing the stream
structure version. So I'd propose something like:
stream_structure_version = 1
header_type_flags:
bit 0 : fresh/continued packet
bit 1 : bos
bit 2 : eos
new flags:
bit 3 : CRC is only the header data
bit 4-5: 0 is traditional lacing, 1 is 16 bit packet length, 2 is 32
bit packet length, 3 is 64 bit packet length.
The packet length field would start on byte 26 where the segment
table len...
2008 Aug 12
7
New Ogg Dirac mapping draft
David Flynn has proposed a new Ogg Dirac mapping. The draft is here:
http://davidf.woaf.net/dirac-mapping-ogg.pdf
This is a much bigger break from other codecs than my draft (at
http://wiki.xiph.org/index.php/OggDirac). We talked a bit about it on
IRC today. Below is my summary; hopefully David can correct anything
I got wrong or misleading. Comments?
There are two main differences
2003 Mar 02
1
Final Ogg 1.0 submission to IETF
...capture pattern is found, the decoder verifies page sync and
integrity by computing and comparing the checksum.
2. stream_structure_version: 1 Byte signifying the version number of
the Ogg file format used in this stream (this document specifies
version 0).
3. header_type_flag: the bits in this 1 Byte field identify the
specific type of this page.
* bit 0x01
set: page contains data of a packet continued from the
previous page
unset: page contains a fresh packet
* bit 0x02
set: this is the first page o...
2003 Mar 02
1
Final Ogg 1.0 submission to IETF
...capture pattern is found, the decoder verifies page sync and
integrity by computing and comparing the checksum.
2. stream_structure_version: 1 Byte signifying the version number of
the Ogg file format used in this stream (this document specifies
version 0).
3. header_type_flag: the bits in this 1 Byte field identify the
specific type of this page.
* bit 0x01
set: page contains data of a packet continued from the
previous page
unset: page contains a fresh packet
* bit 0x02
set: this is the first page o...
2003 Feb 13
2
Changes to Ogg format IETF I-D
...capture pattern is found, the decoder verifies page sync and
integrity by computing and comparing the checksum.
2. stream_structure_version: 1 Byte signifying the version number of
the Ogg file format used in this stream (this document specifies
version 0).
3. header_type_flag: the bits in this 1 Byte field identify the
specific type of this page.
* bit 0x01
set: page contains data of a packet continued from the
previous page
unset: page contains a fresh packet
* bit 0x02
set: this is the first page o...
2003 Feb 13
2
Changes to Ogg format IETF I-D
...capture pattern is found, the decoder verifies page sync and
integrity by computing and comparing the checksum.
2. stream_structure_version: 1 Byte signifying the version number of
the Ogg file format used in this stream (this document specifies
version 0).
3. header_type_flag: the bits in this 1 Byte field identify the
specific type of this page.
* bit 0x01
set: page contains data of a packet continued from the
previous page
unset: page contains a fresh packet
* bit 0x02
set: this is the first page o...