[Matroska-devel] Element order in EBML/libebml
steve.lhomme at free.fr
Mon Oct 20 17:37:22 CEST 2003
> Yes we all write the data in the correct order because
> for us the order matter for the data.
> It's true that for some elements in the file the order
> doesn't really matter (e.g. KaxChapters could be
> before KaxTracks, after KaxTracks and before the first
> KaxCluster, or even at the end of the file; of course
> in this case the KaxSeekHead would help to know where
> the element is if we need it right at the start), but
> in the case of the data (KaxBlock) the order matter if
> you want to be able to decode the stream. So IMO
> "order doesn't matter" ... for some elements and
> matters for others.
MMmm, let's say order doesn't matter. And for some elements we need to
have the order written because order matters. We already have the
timecode (and order in some other places). If we need more (for safety
and editing/correcting) we can add it.
More information about the Matroska-devel