paolobenve schrieb: > But, in general, how does cropping an image affect the way hugin > works? Hugin needs information on some parameters of the images to be able to compute others. Usually it gets ordinary photographs which are centered (not cropped, not asymmetrically cropped) and contain (exif) information about the focal length (and multiplier) from which the HFOV (horizontal field of view) can be determined. So one assumption is that the eye point (correct english term?) is in the centre of the image. If this is not the case you have to optimize for d and e which are the x and y offsets of the eye point from the centre of the present crop. Another assumption is that images of identical pixel size and exif information have identical geometry. If your 2 crops have the same size but are cropped from different regions of the original you would have to assign them different lens numbers manually so that d and e can be optimized separately. (If size and/or exif info are different hugin assigns different lens numbers automatically) A third assumption is of course that the exif info contained is true. In a case where the cropped images still contain the exif info the computed HFOV is not true but too great. So you would have to optimize for HFOV, too - which unfortunately is only possible with 360° panoramas. You would have to calculate a corrected crop factor yourself and enter it. But I am not sure how you would calculate it for an asymmetric crop.
regards Joachim --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
