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! On Thursday, September 9, 2021 at 2:19:07 PM UTC+3 Fotis Kalafatis wrote: > I've been using hugin quite some time to "digitize" paintings in higher > resolution than my camera sensor allows. I just realized that my latest > mosaic (tiff) has considerably lower fidelity/resolution/sharpness compared > to the partial tiles (16bit tiff) throughout the image. the Hugins gui > loads the images in their proper resolution since it appears fine at 100% > in the "control points" preview window. My source images are all from the > same 16mpx sensor, shot from the same distance, with minimal perspective > distortion. > I always chose "calculate optimal size" and assumed it would squeeze from > it as many megapixels as possible. Now I'm baffled. I can't verify whether > this had always been the case since I don't keep the originals. > > Any idea why this might be happening and where I should look for the > culprit? > Thanks! > > [image: Screen Shot 2021-09-09 at 13.56.19.png][image: Screen Shot > 2021-09-09 at 13.56.11.png] > -- 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/5dfd5991-2df2-41d8-9368-259511c6cc67n%40googlegroups.com.
