-
Notifications
You must be signed in to change notification settings - Fork 20
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 support CRC32 elements #10
Comments
Problem investigated, the current demuxer does not know anything about CRC32 elements. |
Partially address #10, the crc is not validated as should yet.
Now we can parse the files but we aren't checking the crc. |
Since #108, CRC elements are read and verified for every master element. What's missing now is the "proper" CRC handling:
<CONTACT>
<CRC-32>c119a69b</CRC-32><!-- does not validate -->
<NAME>
<CRC-32>1f59ee2b</CRC-32><!-- does not validate -->
<FIRST-NAME>invalid data</FIRST-NAME>
<LAST-NAME>invalid data</LAST-NAME>
</NAME>
<ADDRESS>
<CRC-32>df941cc9</CRC-32><!-- validates -->
<STREET>valid data</STREET>
<CITY>valid data</CITY>
</ADDRESS>
</CONTACT> In this case, the ADDRESS Element validates, so it MAY be used even though the rest of the CONTACT Element is invalid. |
Modified @lu-zero list with @FreezyLemon update |
here the broken vp9 sample.
Libav and mkvtoolnix have no problems in parsing it.
The text was updated successfully, but these errors were encountered: