Re: Ogg encapsulation

"Gerard Juyn" <gjuyn-qWit8jRvyhVmR6Xm/[email protected]> Fri, 2 Apr 2004 08:58:46 +0200
Newsgroups gmane.comp.graphics.mng.general
Organization Triple-T
Message-ID <406D2B46.22497.3678A354@localhost>
> > The bits in iMode (now a uint16) become flags:
> > 
> > 0x0001 crc present (or not)
> 
> crc present in datastream (or not)
> 
> > 0x0010 crc must be checked for ancillary chunks (or not)
> 
> crc should be checked...
> 
> > 0x0020 faulty crc on ancillary chunks generate a warning (or not)
> > 0x0040 faulty crc on ancillary chunks generate an error (or not)
> 
> There should also be a note that these fields are ignored if the crc is
> not present/not checked.
> 
> I think that makes the intent of the flags more clear.

Sure. I just wrote this down in a half-delirious frame of mind suffering from a 
head-cold. And naturally there are combinations that don't make any sense, 
like "there's no no crc, but do check it...."
But then this is programmer-stuff and I would hope they'd understand, if 
they'd got as far as to understand they'd need this function. (I also still believe 
in Santa Claus, and if you've got some land for sale in Florida, I'm your guy...)

> > Actually, errors can be ignored as well by #define MNG_SOFTERRORS This
> > will change the error-handling macros to work like a warning. Sure
> > hope people know what they're doing if they start messing with that,
> > as it means the default will then be to ignore errors!!!
> 
> Quite. I wouldn't worry about abuse particularly. Lazy programmers can
> find much easier ways of breaking the format. Just look at the history
> of png support in Photoshop or Internet Exporer.

True enough. And exactly why I'd rather try to avoid those problems. But as 
you say, anyone can muck it up any way they like anyways.

Gerard


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