-
Notifications
You must be signed in to change notification settings - Fork 244
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
mp4 uuid code fails with unpack(): Type H: not enough input #226
Comments
I notice the uuid code was only added recently, it has a note from 2019-Oct-31 in the code. |
Hey @JamesHeinrich i rebased on latest and the bug is still there. It's actually a container parsing bug! I have a patch. PR incoming |
This patch fixes the bug and guards against similar parsing errors. It's also possible that it may be an underlying off-by-some bug with the data passed to the atom-parsing code, though. But I didn't find one, and in any case this patch contains a reasonable safety check. |
FYI what was happening was that the |
By the way, http://fileformats.archiveteam.org/wiki/Boxes/atoms_format has a shortlist of "known" UUIDs - which of course it's impossible to enumerate, as they're essentially app-specific. But it would seem the right way to identify "360Fly Sensor Data" or otherwise may be to match on the UUID, rather than the content of the atom? |
360fly and XMP are now parsed when their matching UUID is found, other recognized UUIDs from the shortlist are included but have no special parsing. |
The full error is
The file in question is 2.5Gb in size and AtomicParsely shows the following structure (uuid near the bottom):
I get the same output with php 7.1.32 and php 7.4.1
I'll see if I can debug any further.
The text was updated successfully, but these errors were encountered: