hugin-bug-hunters team mailing list archive
-
hugin-bug-hunters team
-
Mailing list archive
-
Message #00166
[Bug 678705] Re: suboptimal usage of EXIF data
Re-reading this old wish of mine and ensuing thread, a few things come
to my mind:
1. after generating CP, run two optimization runs - one assuming
rectilinear and one assuming fisheye. retain the best result.
applicable only to FoV < 16°
2. pre-calibrated lenses. add a table for pre-calibrated lenses.
recognize them based on some exiv-combination / fingerprint (can't be
perfect, for example my Sigma 15mm is recognized as Minolta 15mm by
RAWstudio) and access a lens.ini file with all the information.
** Changed in: hugin
Status: New => Triaged
** Changed in: hugin
Importance: Undecided => Wishlist
--
suboptimal usage of EXIF data
https://bugs.launchpad.net/bugs/678705
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Hugin.
Status in Hugin - Panorama Tools GUI: Triaged
Bug description:
it seems to me that hugin assumes by default a rectilinear lens and calculates HFOV based on the focal distance reported by EXIF and that default assumption.
Is it possible to take the EXIF-FOV instead, and to infer the lens type by comparing the expected focal distance with the EXIF-focal_distance?
Also, if hugin is not able to determine the lens type, I'd prefer for it to leave it empty rather than default to rectilinear. Or to give the user a preference to set the default lens type if it can't be inferred.