search for: detirmin

...ng 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 pointing out that it's possible to have > images wthere the xstride/ystride between components is not cons...

...ter a discussion I had with Michael Richardson at HOPE5 (summer '04), a crypto guru who was more than happy to share his advice for this project.. Instead of sending the entire 160 bit hash for each page, only a variable amount of the hash for each page in a range was given. This could be detirmined by the tracker, and because a malicious peer (ie, one trying to introduce advertising into another person's music stream by feeding altered audio content to others) would have no way of knowing which part of the hash would be tested, or how much, for any peer (and this is likely to be dif...

...ge header. Even if the packet were to use just one granulepos value this is nessesary 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...

...ge header. Even if the packet were to use just one granulepos value this is nessesary 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...

...ge header. Even if the packet were to use just one granulepos value this is nessesary 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...

...ge header. Even if the packet were to use just one granulepos value this is nessesary 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...

...ge header. Even if the packet were to use just one granulepos value this is nessesary 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...

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