-
Notifications
You must be signed in to change notification settings - Fork 31
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
Try to understand the output of a damaged JPEG #7
Comments
About the first output, there is an error while checking an image, from the error detail ... the error does not look not about the file being broken BUT the lack of (or installation problem of) the imagemagik libraries, which prevents the tool to work properly. I think the python module --the imagemagik wrapper-- installation should force people/the OS, into imagemagik libs installation. I'll dig into this. About the second one, test_damage.py is not a script useful for the normal user, it is a suite of mine which I used to get the probability of error detection in relation to the type of damage. |
Please consider that describing your enviroment is the basic (like 101) when reporting a problem or asking for help. You should be more detailed when submitting a request or issue |
Thanks for the reply. I reinstalled the brew formula Regarding the environment, here are the details:
|
Thank you for the details, from the terminal/commandline, can you try calling "indentify" command, do you find the command? The first try is looking for the correct path for the identify command, and add this path to the enviroment path, I have the impression that brew does not force too many search paths into the into the enviroment... for safety reason I think. The second try: we will comment the identify code in the script (I can also improve by adding a "command available" check, but it comes with imagemagick ...so..) |
About making improvements I can improve/apply fixes about once every 6-9 months. |
Sorry for late reply.
no. The Terminal said:
|
After I added the Imagemagick to the path using: The output of
However, the JPEG thumbnail is indeed corrupted. |
Not all image damages are detectable, you can also try strict level 2 (also try to explicitly set strict level 1--the should be the default, but need to double check ), but there are cases where the damage cannot be detected. I'm thinking on an AI based approach wich classify decoded images. But I'll need 6-9 months at least to implement this. Real life .... is hard :-) Truncation is usually always detected, while zero-fill has a 50% chance of triggering the errors, a random noise in part of the file has an higher ratio. But these limitation are described in the main page. |
Thanks for your reply. I tried with strict level 1 & 2. The script still reports OK. Really thanks for your effort in making this wonderful script. |
Hi there, I would like to understand the output of the commands.
and for
test_damage.py
:What does that mean?
The text was updated successfully, but these errors were encountered: