I work on a variety of panos made with different cameras, from 5Mp to 12Mp per frame.
My main work recently have been produced with one 8Mp camera and another 10Mp camera. 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. I'm using Tom Glastonbury's most recent Windows 64-bit build, but have tested this with the current sourceforge win32 build [2009-4-0] as well as the current Mac build and they behave the same way. Is this expected, i.e. that I'm misjudging what it's supposed to be doing, or is something else weird going on? Cheers, Derek. -- 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
