Displaying 10 results from an estimated 10 matches for "packet0".
Did you mean:
packet
2005 Nov 08
0
OggYUV
...t
came from (and thus, we could say that "AXYZ" usually uses 4:4:4), just as
knowing that something is of the "WAVE" fourcc, also known as a .wav file,
doesn't tell us what samplerate, bits per sample, or number of channels is used.
In Ogg, we tell compatability by page0/packet0. The entire first packet,
including all it's configuration variables, versions, etc is used to detirmine
compatability. The fields we're talking about will go into packet0, so that a
list of which plugins can accept it can be easily generated.
> Agreed.. Though it's worth poin...
2005 Nov 08
3
[Theora-dev] Re: OggYUV
Timothy B. Terriberry wrote:
>Chapter 4 of the Theora specification does a reasonable job of laying
>out all of the possible parameters for a Y'CbCr-style color space, which
>includes as a subset those needed for RGB. Much more detailed
>information is available from Charles Poynton's Color and Gamma FAQs:
>http://www.poynton.com/Poynton-color.html
>If you wish to do any
2005 Nov 10
1
OggPCM proposal feedback
On Thu, Nov 10, 2005 at 01:35:47PM -0800, Arc wrote:
> > "Please don't make determination of the data format depend on
> > multiple fields. Instead use an enumeration so that something
> > like little endian 16 bit PCM can be specifed as OGG_PCM_LE_PCM_16
> > and big endian 64 bit doubles can be specified as OGG_PCM_BE_FLOAT_64.
> >
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...esary as we want to use the
first packet's granulepos, not the last, when multiple packets are
in a single page. This is only usable before Packet#1 is processed,
so a codec needs to be able to be detirmined to be cont/discont
based only on the information aquired from Page0/Packet0. An error
is generated if this change is requested later in the stream.
The debate is not over wether this is a good way of doing it, but
rather, wether treating different codecs/streams differently is a
good idea. Before you argue this you had better read Monty's full
d...
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...esary as we want to use the
first packet's granulepos, not the last, when multiple packets are
in a single page. This is only usable before Packet#1 is processed,
so a codec needs to be able to be detirmined to be cont/discont
based only on the information aquired from Page0/Packet0. An error
is generated if this change is requested later in the stream.
The debate is not over wether this is a good way of doing it, but
rather, wether treating different codecs/streams differently is a
good idea. Before you argue this you had better read Monty's full
d...
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...esary as we want to use the
first packet's granulepos, not the last, when multiple packets are
in a single page. This is only usable before Packet#1 is processed,
so a codec needs to be able to be detirmined to be cont/discont
based only on the information aquired from Page0/Packet0. An error
is generated if this change is requested later in the stream.
The debate is not over wether this is a good way of doing it, but
rather, wether treating different codecs/streams differently is a
good idea. Before you argue this you had better read Monty's full
d...
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...esary as we want to use the
first packet's granulepos, not the last, when multiple packets are
in a single page. This is only usable before Packet#1 is processed,
so a codec needs to be able to be detirmined to be cont/discont
based only on the information aquired from Page0/Packet0. An error
is generated if this change is requested later in the stream.
The debate is not over wether this is a good way of doing it, but
rather, wether treating different codecs/streams differently is a
good idea. Before you argue this you had better read Monty's full
d...
2005 May 26
1
libogg2 branch->trunk (deadline: 5/30)
...esary as we want to use the
first packet's granulepos, not the last, when multiple packets are
in a single page. This is only usable before Packet#1 is processed,
so a codec needs to be able to be detirmined to be cont/discont
based only on the information aquired from Page0/Packet0. An error
is generated if this change is requested later in the stream.
The debate is not over wether this is a good way of doing it, but
rather, wether treating different codecs/streams differently is a
good idea. Before you argue this you had better read Monty's full
d...
2005 Nov 10
0
Ogg audio surround-sound
...mail, below)
I emailed David (author of that email) and asked him to join this list.
I'm thinking, as I look at the problem, that surround sound needs to be defined
_outside_ the audio codec stream. Comments are inappropriate, since we need to
know if our apps can support a stream based on packet0.
As Silvia mentioned recently, we've been lacking a multi-audio codec handling
system for a long time. Wether that be for surround sound, prehaps with
different samplerate/samplesize, or for alternative languages, or for recorded
tracks which need to be mixed.
Let's begin with the abo...
2004 Sep 10
2
Ogg encapsulation
I've been implementing Ogg FLAC support in an editor I'm working on, and
I must admit to being frustrated by the lack of support for the codec on
the Ogg layer... and this is more than lacking granulepos.
The codec's I've worked with, and my own (Writ), use Page 0 for general
information about the codec. Specifically, the samplerate, bitrate,
quality, number of channels, all