Displaying 5 results from an estimated 5 matches for "top_granule".
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...:
I. Debated API elements:
A. To my last knowledge there was *STILL* a debate going on re discont.
codecs, even though these have been published by Monty months ago.
A part of this debate the following API additions have been debated:
within ogg2_packet struct:
ogg_int64_t top_granule;
ogg_int64_t end_granule;
vs
ogg_int64_t granulepos;
This, Monty proposed, allows for smarter packet->page handling than
just having the meaning of granulepos differ for different streams.
*THIS IS NOT* a change to the Ogg bitstream, only one granulepos is...
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...:
I. Debated API elements:
A. To my last knowledge there was *STILL* a debate going on re discont.
codecs, even though these have been published by Monty months ago.
A part of this debate the following API additions have been debated:
within ogg2_packet struct:
ogg_int64_t top_granule;
ogg_int64_t end_granule;
vs
ogg_int64_t granulepos;
This, Monty proposed, allows for smarter packet->page handling than
just having the meaning of granulepos differ for different streams.
*THIS IS NOT* a change to the Ogg bitstream, only one granulepos is...
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...:
I. Debated API elements:
A. To my last knowledge there was *STILL* a debate going on re discont.
codecs, even though these have been published by Monty months ago.
A part of this debate the following API additions have been debated:
within ogg2_packet struct:
ogg_int64_t top_granule;
ogg_int64_t end_granule;
vs
ogg_int64_t granulepos;
This, Monty proposed, allows for smarter packet->page handling than
just having the meaning of granulepos differ for different streams.
*THIS IS NOT* a change to the Ogg bitstream, only one granulepos is...
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...:
I. Debated API elements:
A. To my last knowledge there was *STILL* a debate going on re discont.
codecs, even though these have been published by Monty months ago.
A part of this debate the following API additions have been debated:
within ogg2_packet struct:
ogg_int64_t top_granule;
ogg_int64_t end_granule;
vs
ogg_int64_t granulepos;
This, Monty proposed, allows for smarter packet->page handling than
just having the meaning of granulepos differ for different streams.
*THIS IS NOT* a change to the Ogg bitstream, only one granulepos is...
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...:
I. Debated API elements:
A. To my last knowledge there was *STILL* a debate going on re discont.
codecs, even though these have been published by Monty months ago.
A part of this debate the following API additions have been debated:
within ogg2_packet struct:
ogg_int64_t top_granule;
ogg_int64_t end_granule;
vs
ogg_int64_t granulepos;
This, Monty proposed, allows for smarter packet->page handling than
just having the meaning of granulepos differ for different streams.
*THIS IS NOT* a change to the Ogg bitstream, only one granulepos is...