Well, this is an interesting point. I also shoot the horizon row
first, then the zenith, then the nadirs. That is, I don't proceed top
to bottom or bottom to top but shoot the middle row, the top "row" and
then the bottom "row."
For me, the assumption that "pictures that are next to each other in
the shooting sequence are also next to each other in the panorama."
will be incorrect.
On the other hand, if I (we) are shooting a sequence that is standard
for us, it seems that using a Template would work. Apply the template
would distribute the images in close to the correct locations on the
sphere. Then the trick would be to get the control point generators
to generate points only between adjacent images.
Next, it would be nice to specify a series of optimization runs (that
preferably could be run automatically). For example, first a series
of runs on the horizon row, then a series on the zenith using also the
horizon row's control points but *not* optimizing the horizon row this
time. Then a similar run for the nadir images. And now that things
are very close, maybe optimize the whole bunch again.
eo
On Oct 31, 2010, at 1:47 PM, Bernd Hohmann wrote:
Me (and likely most of the others) is shooting 360° around then
zeniths and nadir.
so the whole patterns boils down to a "snake" from zenith to nadir
or the
other way around. Can't know which one is which, so this must be
manual
input.
--
You received this message because you are subscribed to the Google Groups "Hugin and
other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
