When creating control points manually, I note that auto-estimate
is not very clever (albeit better than nothing).
From the documentation:
> auto estimate Tries to estimate the position of the second point by
> estimating the translation between the two images. This is very
> crude and probably only works for single row panoramas
> created from Rectilinear Projection images.
Given that hugin has a handy panotools library available,
might I suggest that a quick 'n' dirty YPR model be applied
to the two windows?
For the first CP, only YP would be optimised, but after that YPR is possible.
I *think* that YPR is general enough (and the relationship between
adjacent images of a pano restricted enough) that this would give very good
results.
BugBear
--
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/55659472.7050903%40papermule.co.uk.
For more options, visit https://groups.google.com/d/optout.
