Re: Ogg encapsulation

"Gerard Juyn" <gjuyn-qWit8jRvyhVmR6Xm/[email protected]> Sun, 4 Apr 2004 11:26:38 +0200
Newsgroups gmane.comp.graphics.mng.general
Organization Triple-T
Message-ID <406FF0EE.12594.414C019B@localhost>
> > 0x0002 generate crc in output streams
> > (the default then becoming 0x093)
> 
> I'd suggest this mean libmng does not calculate the crc, but 
> nevertheless writes 4 bytes (e.g. zeros) for that field. It's easy
> enough to stip it out, and the client can fix it up later.
> 
> If you want to add another bit for not writing it; I wouldn't object.
> Hmmm. I guess from the abuse point of view, one chooses between parsable
> datastreams with incorrect crcs, and completely unparsable ones. That
> argues for the flag above *not* writing a dummy field.

How 'bout:

0x0002 calculate and write crc to output streams
0x0004 write dummy crc to output streams

These two are obviously mutually exclusive, where neither of them specified 
means no crc in output streams.

G


--
Send the message body "help" to [email protected]