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

The demuxer does not handle Void elements in random places #11

Open
lu-zero opened this issue Oct 4, 2018 · 3 comments
Open

The demuxer does not handle Void elements in random places #11

lu-zero opened this issue Oct 4, 2018 · 3 comments
Labels
bug spec-compliance Related to EBML or Matroska specification compliance

Comments

@lu-zero
Copy link
Member

lu-zero commented Oct 4, 2018

A Void element should be always ignored and skipped. See the usual file for an example.

@lu-zero lu-zero added the bug label Oct 4, 2018
@lu-zero
Copy link
Member Author

lu-zero commented Oct 4, 2018

Actually the problem was different, still we might have problems if some files are creative I'm afraid.

@FreezyLemon
Copy link
Contributor

If we're talking about Void Elements within a Master Element, that case is covered as long as the matroska_permutation helper is used. Void Elements can also happen at the Root level though, which is probably not covered at the moment.

@Luni-4
Copy link
Member

Luni-4 commented Apr 11, 2023

Let's leave this issue opened up till Void Elements at the Root level will be covered

@FreezyLemon FreezyLemon added the spec-compliance Related to EBML or Matroska specification compliance label Apr 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug spec-compliance Related to EBML or Matroska specification compliance
Projects
None yet
Development

No branches or pull requests

3 participants