search for: rfc_3533_errata

...discrepancy between Ogg docs and the RFC, and > I think someone (either Silvia or Conrad, probably Silvia) fixed the RFC. > (That was the reason I'd originally included the low counter bits for Kate). Right, thanks for pointing that out. The correction is recorded at http://wiki.xiph.org/RFC_3533_Errata David's proposal still violates that without the "stop the press" fancier encoding. > I'll take this opportunity to mention my pet idea (don't think I ever mentioned > it on ogg-dev), to start with a byte, then, if larger than 255, add two bytes, > then for packets...

On 15/03/07, Ralph Giles <giles@xiph.org> wrote: > On Wed, Mar 14, 2007 at 12:23:47PM +0000, Mathias Kunter wrote: > > > > In contrast to that, http://www.ietf.org/rfc/rfc3533.txt stats the following: > > "Ogg Vorbis provides the name and revision of the Vorbis codec, > > the audio rate and the audio quality on the Ogg Vorbis bos page. > > It also uses

On 25-Feb-08, at 9:34 AM, xiphmont@xiph.org wrote: > I'd say both; libogg should ignore the incomplete packet or flag a > structural error, and the spec should be clarified. I guess libogg should return -1 if you try to ogg_stream_packetout() after the eos packet. The eos flag pretty clearly applies to the *page* not the packet, so I think how that gets translated into the

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