[hugin-ptx] Different photometric results with GUI and AutoOptimiser -m

[Stéphane Péneau]

Hello,




GUI : If I use "Low dynamic range, variable white balance", the result is ok

If I use the same .pto file and launch :


"${autooptimiser}" -m -o default5.pto default4.pto

I sometime have a lot of posterization on one part of the pano.

I thinked that these two methods should have the same result. Am I wrong ?

how to get rid of this problem within a script ?


(pto before photometric optimisation attached)


Best,


Stéphane


--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/b1d74739-9a00-b210-819e-52dd63aa7515%40wanadoo.fr.

I'd like to create pano for about 2000 sets (6 pictures from 6 identical action cam for each set). I'm trying to script the stitching process, but there is (at least) one thing I don't understand. sed -i '/#hugin_optimizerPhotoMasterSwitch/c\#hugin_optimizerPhotoMasterSwitch 23' default4.pto --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

default4.pto
Description: application/ptoptimizer-script