The 'calculate optimal size' function is initially run by the Assistant, but after that it has to be run manually. So even if you make lots of changes to the panorama, such as changing the overall field of view, the pixel width of the output doesn't get updated dynamically.
-- Bruno On 9 September 2021 15:09:59 BST, Fotis Kalafatis wrote: >as soon as I posted, I decided to reopen the project in hugin, play a bit >more with the "cropping" to shake things up, re-ding "calculate optimal >size" and finally pressed "Stitch!" again, and the new file, despite being >the same dimensions as the older output (~8500x13000px) is perfectly sharp >this time! > >I wonder where that glitch(?) came from; any thoughts are appreciated! -- 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/CB675EAD-3F95-4AB8-A7BD-1EC7127E431F%40postle.net.
