[ogg-dev] eos on continued page
giles at xiph.org
Mon Feb 25 15:47:38 PST 2008
On 25-Feb-08, at 3:42 PM, Conrad Parker wrote:
> ok. If the correct behaviour should be to ignore the incomplete
> packet, that should also be clarified in the spec.
Fair enough. What if no packet ends on the eos page? What about
additional pages after the eos page?
> I'd find it useful if it was not considered a structural error, as it
> allows us to very simply chop files apart and put them back together.
> The eos flag on the page is then a very clear way of saying to ignore
> the extra data during decode.
There general idea with Ogg has been to distinguish non-fatal from
fatal errors. libogg reports these by returning -1 while still
returning the next valid bit of data.
More information about the ogg-dev