Thanks Bruno for the Reply. The offset makes sense explained like that. My next question is *where is the "cropped tiff" setting?* Is it something that can only be accessed when rendering using the terminal? Can you show me an example on how to use it?
Thanks again for your help On Monday, February 24, 2025 at 11:15:17 PM UTC-8 [email protected] wrote: > Hugin saves these tiff offsets because otherwise images with large amounts > of empty space can be huge. You can turn off this behaviour with the > 'cropped tiff' output setting. > > -- > Bruno > > > On Tue, 25 Feb 2025, 01:21 Claudio Rocha wrote: > >> Upon further investigation using *Tifftools* ( >> https://libtiff.gitlab.io/libtiff/tools/tiffset.html), the Tiff file in >> question is showing an* offset* in the *XPosition* and the *YPosition* >> tags. Using *tiffset -s XPosition 0* and *Yposition 0* resets the top >> edge of the RGB picture to the expected top left position. >> >> That fixes the tiff file, but I would love to know where this Offset was >> coming from and, more importantly, how to prevent it from happening in >> future image stitching with Hugin. >> > -- 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 visit https://groups.google.com/d/msgid/hugin-ptx/a0f9b052-98c3-4994-a85d-96d14069f572n%40googlegroups.com.
