-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
ZeroDivisionError exception caused by JPEG with incomplete LensInfo #319
Comments
I'm not able to reproduce this despite your detailed instructions. Both rinohtype 0.5.3 and the current master happily process the JPEG file. I think
I assume you bumped into this because you had another JPEG with incomplete lens info? Can you share that image (privately, if needed? |
Sure, it is in GitHub: I have exiftool (12.30) as well... |
This image causes another error for me:
A ResolutionUnit value of 1 is currently not being handled by rinohtype. I'll try to address this. Temporarily mapping 1 to inches, I do see the error you reported, so I can also look into handling that case. 👍
|
I finally figured out why exiftool wasn't working for me. I'm using xon.sh, which handles command line arguments differently. This works: exiftool -exif:resolutionunit=inches "-LensInfo=100 100 undef undef" lensinfo.jpg |
Try installing from the master branch to verify whether the issue is fixed now:
|
Change in 28737c4 fixes this for me. Thanks! |
Steps to reproduce (with exiftool and ImageMagick):
Create index.rst:
Then:
Catching the exception and returning
raw_value
seems to work OK for me.(missing resolutionunit also causes an exception but I haven't seen that one in a real photo)
Please also provide the following information:
The text was updated successfully, but these errors were encountered: