A little more info on the bug Kay found: It happens when an area of the mosaic is covered by two or more images, and the particular layout of images around that area means that multiblend decides that an image which doesn't actually cover that area is the correct choice. I think (looking at the PTO) the problem with Kay's nadir is that there are two nadir images, so there is no area which is exclusively one image or the other from which the seam can grow.
Possible workarounds could be to remove overlapped images from consideration if the problem is detected and recalculate the seams (though there may still be ambiguous cases that will cause the problem, or you'd be losing out on images that should be kept, such as one of the two nadir images above), or arbitrarily choosing an image to represent the area (which then re-introduces the Enblend issue I was trying to address with multiblend, that there is not a unique solution). Perhaps there could be some semi-intelligent grouping done, so the nadirs are seamed first, then the middle images, then the two groups are seamed together (though again, there may be cases with no unique solution). Or maybe multiblend is only suited to narrower-FOV mosaics :( David -- 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
