Oh. Dear.
I just loaded one of the shots into a fresh project,
and Hugin shows Hfov(v) 38.
It looks like the fault may well be all of my own making,
and not Hugin's at all.
I'm wondering if I did an ill advise optimise that included the FOV early
on, and forgot about it.
BugBear (off to hang his head in shame)
paul womack wrote:
Paul Womack wrote:
I think you (and T Modes) may have found the issue.
The camera was pointing STRAIGHT DOWN when the shots were taken, so its angle
sensor reading would have been meaningless.
I shall check the exif of these images against more "normal" samples from other
shooting sessions, and see what I find. If needed, I will force the vert/port sensor
reading in the files to tell the truth (or at least my version of the truth).
Thanks to both - I shall report back.
OK; I have some info.
In the original (flawed) set, the Hfov(v) was 16.5;
this show in the GUI on the Photos tabs as
Focal Length: 25.03, Focal length multiplier 4.769
I attempted to optimise Hfov(v), but nothing came of it.
I then simply tweaked it, and fairly rapidly converged on 38
as the angle that gives the straightest borders.
(I had other issues with blending, which I'll post separately).
I've cut and pasted the result of exiftool -S on one of the images.
I note (with interest) the "FOV: 38.4 deg"
--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/595624B8.6090501%40papermule.co.uk.
For more options, visit https://groups.google.com/d/optout.
