-
Notifications
You must be signed in to change notification settings - Fork 11
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] quicktime antics #107
Comments
It looks like this is likely to be a magic number issue, not an ffprobe issue. checkrr uses h2non/filetype to check if a file is video/audio before passing to ffprobe blindly. That library uses magic numbers to match the file and checks that the extension matches [1]. Honestly, it might make sense to just swap the container type and extension using ffmpeg in this case. Otherwise, h2non/filetype needs to be patched and I've been waiting on them for 2 years on h2non/filetype#120. [1] https://github.com/h2non/filetype/blob/master/matchers/video.go#L53-L62 |
Ugh, looks like it downloaded new mp4 versions of the files and now I don't have the .mov files in my library any more. File sees it as a Movie file on my Mac, let me dig up my archives of the .mov files and I will see what it does in the container. Interesting that file also sees it as an ISO though...
|
If it sees it as ISO media, I suspect it might be directly related to the magic number used. |
@sjthespian did you ever get the original copy of this file? I'm curious to see what ffprobe says about it too |
Describe the bug
I have several older Quicktime files that checkrr not recognizing Quicktime files as valid videos. The logs show
Type=Unknown
:In this case, these are files that were downloaded via. Steam from the long-ago Kickstarter for Will Wheaton's TableTop videos.
But ffprobe run from in the container has no trouble with the files:
To Reproduce
Steps to reproduce the behavior:
Bad Files
Expected behavior
I would expect checkrr to scan these files just like any other video files.
Screenshots
N/A
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: