On Sat, 2010-05-22 at 14:06 -0700, dex Otaku wrote: > I can load one of my panos and hit "Calculate Optimum Size" on the > stitcher tab, but the behavior is not consistent / as expected: > * With the pano assembled of 8Mp images, it selects a size ~21,000 > pixels wide > * With the pano assembled of 10Mp images, it selects a size ~16,000 > pixels wide > > How exactly does hugin figure out its optimal size? I was under the > impression that it's supposed to gauge the optimal size by scaling the > entire pano so that the centre images would be as close to 1:1 [input > pixels:output pixels] as possible, but it's not behaving that way. > You'd expect that the 10Mp/frame pano would be larger, not smaller.
If the only difference is the number of pixels in the frame, then more megapixels input should give more megapixels optimal size for output. It is supposed to scale to the pixel density of the centre of the output. Since you are using different cameras, you could also be varying something else which affects the resolution. The field of view of the camera, the amount of overlap between the images, the field of view of the output, and the output projection type could all affect the optimal size too. Are these similar between your panoramas? -James -- 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
