Valid but should they be - #2
Conversation
This files are all valid to the specifications AFAICT, but perhaps they shouldn’t be.
|
Mh, github needs a visualizer for EBML files. |
|
|
||
| ## currently_undefined_EBMLVersion.mkv | ||
|
|
||
| The EBMLVersion is restricted to a range of defined values. At the time of this writing, only EBMLVersion=1 is defined. This value has an EBMLVersion of 255. |
There was a problem hiding this comment.
It's not invalid if EBMLReadVersion is 1.
There was a problem hiding this comment.
in EBML draft the EBMLVersion has a range of 1 reference as that is the only defined version of EBML, so EBMLVersion=2 is invalid since it goes outside of the range.
|
Re visualizer for EBML. I thought of using mkvparse's mkv2xml to update an xml representation for each but many of these files would not be possible to depict in mkvparse's output. Perhaps if the file is small enough we could have a hexadecimal text document with spacing to depict the data. For instance to convert this to an EBML file, pipe the text to
The grep is to strip comments. This would allow sample files as text and then we could have a Makefile to convert them to EBML. |
This files are all valid to the specifications AFAICT, but perhaps they
shouldn’t be.