You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EBML is a "binary equivalent to XML", so it should be plausible to write a small tool that converts the EBML input into a human-readable representation.
The output should be similar to XML, but obviously does not need to conform to XML specs.
The tool should be able to recognize Elements (ID, Length, Data/Value) and differentiate Master Elements from "primitives".
Something optional would be reading and validating CRC-32 inside of Master Elements.
Again, the actual output format isn't that important. It just needs to be readable and should be helpful to check what's going on inside any given EBML file.
The text was updated successfully, but these errors were encountered:
EBML is a "binary equivalent to XML", so it should be plausible to write a small tool that converts the EBML input into a human-readable representation.
The output should be similar to XML, but obviously does not need to conform to XML specs.
The tool should be able to recognize Elements (ID, Length, Data/Value) and differentiate Master Elements from "primitives".
Something optional would be reading and validating CRC-32 inside of Master Elements.
An output example:
Maybe even with some possible data interpretations:
Again, the actual output format isn't that important. It just needs to be readable and should be helpful to check what's going on inside any given EBML file.
The text was updated successfully, but these errors were encountered: