I'm shocked it worked that well (though I can see obvious issues in the sky hue and saturation). I suspect the clouds may be incorrectly determined to be part of the sky -- and are affecting the estimate of sky hue and saturation.
To see where it estimates the start of sky and end of sky, run it with "-d3" -- the start of sky will be marked with red, end of sky with green, and the depth of the blending area marked with black. Changing the tolerance of where it chooses the end of the sky may then be helpful. If you look near the end of the huge amount of screen output, you will find a line like: --- sky detect tolerances (hsv) are 360.000000, 0.300000, 0.030000 --- Using the tolerance flag can then allow the end of sky to stop sooner, by making the tolerances smaller. Maybe lower the saturation tolerance a bit from the last run will help. When i get in these situations I generally keep running with the "-d3" flag until the sky detection is acceptable, so I'd run it with: "-d3 -tol ...". When you like it, just leave out the "-d3" and it will complete the process. On Wednesday, December 22, 2021 at 1:14:30 PM UTC-8 [email protected] wrote: > It certainly works with this simple test, it isn't a panorama, but I was > able to crop out some clouds in GIMP and replace them with blue sky: > [image: 1.jpg] > [image: 2.jpg] > [image: 3.jpg] > -- 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/682f00b5-0d2f-4a1c-9997-d852aa73ca9dn%40googlegroups.com.
