-
Notifications
You must be signed in to change notification settings - Fork 22
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
DCDM - more checks needed #140
Comments
Hi @kieranjol , Just to be sure, what version of ClairMeta where you using, and was it the DSM or DCDM checker ? In the latest versions, we no longer use Mime type as it was found to be unreliable, we check for:
That being said we could add more and also make sure there is no change in the way mediainfo extract those that would make ClairMeta outdated. Would be nice to have the corrupted frame and another valid one (no matter which). Will probably look into this next week if there is a need. Thanks |
Hi, thanks for getting back so quick and I apologise for having so many things missing from my report. and i'd say i't sht latest version cos we reinstalled lately and
I think the mediainfo checks are not running on my end - is there a chance that this is only in git-master but not in the latest pip version? I'll shoot you an email now too. Thanks! |
It should be deployed! Maybe mediainfo was not found on the host, but you should see warning in that case. Or there is a bug somewhere / version incompatibility, will have to look at the files when you send them and let you know. |
Thanks remi! Mediainfo is definitely available in.$PATH as its involved in
almost all our scripts...
K
|
We have a sequence where one corrupted tif resulted in DCP-O-Matic not being able to make a DCP. After doing an audit in exiftool, we found a corrupt frame. ClairMeta approved this sequence as the filesize, mimetype and sequence continuity were all ok. I suggest some further probing, for example:
Width/Height, Bit Depth , some sort of check that a valid tiff header is present. Whatever is the least intensive for the greatest chance of detecting corruption.
Here's the exiftool report on the corrupt frame:
and here's the previous frame which is fine:
Best,
Kieran.
The text was updated successfully, but these errors were encountered: