PTOptimizer.txt is for PTOptimizer, which is a standalone tool that is independent of Hugin. The nona.txt file describes the behaviour of the Hugin stitcher.
Panotools supports both 'C' and 'S' image parameters, they do similar things, describing the rectangle of interest in the photo, but are not interchangeable. 'C' parameters discard all data outside the rectangle, and then all image parameters (angle of view, lens distortion) relate to this new image boundary. This is a model that makes a lot of sense if all your photos are digitised with a flat-bed scanner - the cropped-out areas are not part of the photo. 'S' parameters set the area outside the rectangle to 'transparent', but the image parameters still relate to the original image frame. This model makes more sense with digital cameras where all the pixels have come from the sensor, just that some of them are not wanted (in Hugin there is a lot of overlap with the masking functionality, which came much later). It is not straightforward to convert from a project that uses one method to the other method, so it makes sense for a GUI tool to support one only (since you don't need both). This is the original schism between Ptgui and Hugin - Ptgui uses 'C' and Hugin uses 'S'. So if you are importing a Ptgui project into Hugin, you need to re-optimise lens parameters because the C parameters have been silently converted to S. -- Bruno On 12 September 2021 07:46:03 BST, 'kfj' via hugin and other free panoramic software wrote: >Thanks, Bruno, that explains TrX0 TrY0 TrZ0 Tpy0 Tpp0 j0, and it has much >more information than the docu I was using! > >I have another issue with the i-lines. In PTOptimizer.html ><http://hugin.sourceforge.net/docs/manual/PTOptimizer.html>, there is the >option to use cropped source images with the 'C' field: > ># C100,600,100,800 Crop(l,r,t,b), Only pixels inside the rectangle will be >used for conversion. ># Cropped image size is used for all image >parameters ># (e.g. field-of-view) refer to the >cropped part of the image. > >I tried to use a PTO file with such C fields with hugin, but the cropping >information was silently changed to a selection field ('S' tag) >Is this field type not used by the hugin processing chain? > >Kay > -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/38B9A8A1-9B59-45C2-AFB4-7994EB26C887%40postle.net.
