It's caused by enblend/enfuse. I've tried to figure out what conditions causes it but never really found anything definitive. I just use the previously suggested setting, "--blend-colorspace=IDENTITY" (used to use "--no-ciecam" before they changed the options) to prevent it happening.
On Friday, 5 March 2021 at 12:19:34 UTC [email protected] wrote: > Yes, something like that... then again I'm sure my name should be written > somewhere, but that is besides the point. > > There really aren't any error messages popping up. I have tried the > command now and the result is nearly identical. I say nearly because there > might be differences I can't see, but from what I can tell noise is equal. > > Did you find out what was causing the noise in your case? In my case I am > guessing it has to do with badly aligned images - the camera stand was > swaying. I usually merge stacks to hdr in a different program because of > this, but in this case the images must be aligned before merging and Hugin > is the only one that I have alignment control over. > On Thursday, March 4, 2021 at 3:33:01 PM UTC+1 Luís Henrique Camargo > Quiroz wrote: > >> >> Hi Mathias (if I recall well) >> >> >> I had problems like you long ago, with lots of messages about problems >> along the processing of the panorama. It turned out that using >> "--blend-colorspace=IDENTITY" for enblend and enfuse solved the issue. Have >> you already used this parameter? >> >> Em qui., 4 de mar. de 2021 às 05:55, [email protected] < >> [email protected]> escreveu: >> >>> Hello. >>> >>> I have noticed a few times already that some of the resulting images >>> have very high noise. In this case the red channel is going crazy - there >>> are small pink dots all over the scene, that are not present in the >>> original files. >>> >>> https://pasteall.org/pic/1563c8e25b3f423fb6942064187b7dbb >>> >>> Of course brightening the originals would bring out noise like this, but >>> even then there would be less of it. Moreover, to my understanding once the >>> hdr is brightened it should (at most) correspond to the image that was >>> taken at that exposure level. >>> >>> Any hint into how this happens, and how to fix it? >>> >>> https://pasteall.org/pic/1563c8e25b3f423fb6942064187b7dbb >>> >>> -- >>> 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/1ae4a988-03f6-488c-8a4f-2949090cbe0en%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/hugin-ptx/1ae4a988-03f6-488c-8a4f-2949090cbe0en%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> >> >> -- >> -- >> Luis Henrique Camargo Quiroz >> http://luishcq.br.tripod.com - http://www.christusrex.org/www2/cantgreg >> http://panoramaslh.net/ >> > -- 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/63e8dbb7-5b7c-49f9-b2bd-f65370e0b1fen%40googlegroups.com.
