Erik Krause wrote: > The latter can be checked easily: I have a panorama project consisting > of 10 rectilinear images each 2566 pixels wide. The hFoV of each image > is 35.9°. Now if I set output hFoV to 35.9° and projection rectilinear > the optimal size hugin suggests is 2802 pixels wide, which is about 10% > too large.
Ooops, I must apologize: This was a PTGui project and I didn't think of the cropping. PTGui calculates FoV based on the cropped size, whereas hugin always uses the total size. If I re-optimize and compare the total pixels anything is ok. That's BTW one of the reasons why PTgui projects can't be imported successfully to hugin without re-optimizing. In the tested case hugin didn't account for the individual cropping either. -- Erik Krause http://www.erik-krause.de --~--~---------~--~----~------------~-------~--~----~ 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
