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

[Bug Report] "AtomicParsley error: unsupported MPEG-4 file brand found 'iso5'" #49

Open
bypie5 opened this issue Jan 12, 2022 · 1 comment

Comments

@bypie5
Copy link

bypie5 commented Jan 12, 2022

AtomicParsely incorrectly labels MP4 videos with ftypiso5 in their header. This is the error message the gets printed when the following command is run on a video with the header mentioned before:

> AtomicParsely iso5brand.mp4 -T
AtomicParsley error: unsupported MPEG-4 file brand found 'iso5'

This is what the header for a mp4 video that produces this error looks like:
Screenshot from 2022-01-12 09-43-44

Note the ftypiso5 in the first few bytes of the header.

This seems to be an issue with libmagic itself. For more information about this bug, see this bug report for libmagic: https://mailman.astron.com/pipermail/file/2020-November/000441.html

Relevant part quoted below:

Hi,
We use libmagic to detect file formats and we got a report[1] that some MP4 files aren't detected properly. The file in question has a "\0\0\0$ftypiso5" signature of which "ftyp" is correctly detected as "ISO Media" (which annoyingly gives a application/octet-steam MIME type instead of some video/* fallback).
The "iso5" part isn't detected by libmagic and looking into /magic/Magdir/animation and https://github.com/FFmpeg/FFmpeg/blob/290de647595051034d8f021f24bb4610b2f39943/libavformat/movenc.c#L4925-L4961 you seem to be lacking a lot of MP4(-ish?) signatures.
Best regards,
Haelwenn (lanodan) Monnier
1: https://git.pleroma.social/pleroma/pleroma/-/issues/2287

@github-actions
Copy link

Thanks for filing an issue! Please note that this project is only passively maintained, so your best bet for getting an issue resolved is through a pull request that is easy to verify! Please read this for more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant