Roger Broadie wrote:
I therefore generated a new set of my own and stitched that by the method I
have described (map 2.pto, attached).
> Now I can't find any stitching glitches at all, though heaven knows they can
suddenly catch one's eye later, however well
one thinks one has searched for them at the time and found none. So I suppose
the moral is the rather trite one that
For those wanted to REALLY check for glitches, it's easy to use a sort of
blink-test (c.f. http://en.wikipedia.org/wiki/Blink_comparator).
Simply make a multi layer tiff of your data, as per
http://hugin.sourceforge.net/docs/manual/Hugin_FAQ.html
How can I postprocess the image using multiple layers in The Gimp?
Use the nona stitcher on the command-line, to output to a multilayer TIFF
format:
nona -m TIFF_multilayer -o multi_layer.tif project.pto
Then load this into Gimp (hope you've got lots of RAM)
order the layers to your liking and just click on an "eyeball"
icon in the layer display to turn layers on and off. This can be done
at 1:1 display resolution, and any errors will (for better of worse)
leap out at you.
In the case at hand, I'm afraid there are errors, but I don't think Roger's
careful works is at fault; since the map has been folded, there are slight
hills and valleys in it. These cause genuine (if small) parallax errors
which hugin simply cannot resolve.
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/5436938E.7030002%40papermule.co.uk.
For more options, visit https://groups.google.com/d/optout.
