[matroska-devel] Re: references, KaxCodecPrivate for Vorbis

[Steve Lhomme]

Pamel wrote:

> "Steve Lhomme"  wrote
>
> >>- putting all three packets into the one KaxCodecPrivate: we'd store
> >>  the length1 (four bytes, little endian), packet1, the length2 (again
> >>  four bytes, little endian), packet2, packet3 (the last packet's
> >>  length can be calculated by KaxCodecPrivate's length - length1 -
> >>  length2),
> >
> >That solution is OK.
> >
> >
> >>- putting all three packets into the one KaxCodecPrivate using the
> >>  lacing mechanism.
> >
> >That's also a good solution, but probably overkill :)
>
>
> What about just making KaxCodecPrivate contain subelements?  Then you 
> could
> store all sorts of wacky data that codecs already want to store under
> seperate headers.

Because there is no need to define an element for each codec 
specificities. As you know the element IDs are not infinite... Well, 
they are, but less efficient then ;)

The matroska level doesn't really need to understand what's inside the 
codec.

http://www.matroska.org