[Matroska-devel] Several (minor) issues or underspecified areas in the MKV spec
mjbshaw at google.com
Tue Sep 29 18:05:35 CEST 2015
On Mon, Sep 28, 2015 at 6:35 PM, Dave Rice <dave at dericed.com> wrote:
> On Sep 28, 2015, at 9:03 PM, Michael Bradshaw <mjbshaw at google.com> wrote:
> - How can the EBMLMaxIDLength be less than 4, when the EBML and
> Segment IDs are 4 bytes? Shouldn’t the EBML spec require the range to be >
> 4 and the MKV speck require it be exactly 4?
> As you note the EBMLMaxIDLength can not be less than 4 because of the
> 4-byte EBML Element ID. You’ll see the description for EBMLMaxIDLength is
> clarified here:
> https://github.com/Matroska-Org/ebml-specification/blob/master/specification.markdown so
> that it doesn’t hint of less than 4 which is not possible. I think the
> understanding is that the Matroska spec can constrain the EBMLMaxIDLength
> to 4 (which means that 4 is the only valid EBMLMaxIDLength for the Matroska
> docType but another doctype of EBML could use a higher value.
The reason I ask this question is because the MKV spec says EBMLMaxIDLength
<http://matroska.org/technical/specs/index.html#EBMLMaxIDLength> is "4 *or
less* in Matroska". It's that "or less" that I'm unsure of. I think it
should probably read "4 in Matroska".
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Matroska-devel