Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a tool to dump an EBML file structure #127

Open
FreezyLemon opened this issue Apr 21, 2023 · 0 comments
Open

Create a tool to dump an EBML file structure #127

FreezyLemon opened this issue Apr 21, 2023 · 0 comments

Comments

@FreezyLemon
Copy link
Contributor

FreezyLemon commented Apr 21, 2023

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:

<EBML>
  <Master(ID 0x1A45DFA3, Size 11)>
    <Element(ID 0x4287, Size 4)>
      [0x0, 0x0, 0x0, 0x4]
    </Element>
    <!-- ... -->
  </Master>
</EBML>

Maybe even with some possible data interpretations:

<EBML>
  <Master(ID 0x1A45DFA3, Size 11)>
    <Element(ID 0x4287, Size 4)>
      [uint: 4]
      [int: 4]
      [float: 1.1e-44]
    </Element>
    <!-- ... -->
  </Master>
</EBML>

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.

@FreezyLemon FreezyLemon created this issue from a note in Demuxer Implementation (TODO) Apr 21, 2023
@FreezyLemon FreezyLemon mentioned this issue Apr 21, 2023
3 tasks
@FreezyLemon FreezyLemon removed this from TODO in Demuxer Implementation Apr 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant