I am talking about a single row pano and I am definitely not an expert. My solution was to significantly over-sample. I went from 30% overlap to something approaching 50%. I use an index rotator and decreased the rotation angle by about 50%.
Sent from my iPhone > On Oct 19, 2021, at 2:36 PM, Juha Kallioinen <[email protected]> wrote: > > > Thomas, thanks a lot for the analysis! > > If there's just a single/few control points between images, does it pay to > manually create more points in th GUI, or will those be too inaccurate? > > When looking at the control points between the images in the GUI, I see that > hugin shows a red/yellow/green color bar between different images. Is it an > indication of the quality of the control points? I've tried to manually add > control points if the color is red, but it's never turned into yellow or > green that way. > >> On Tuesday, October 19, 2021 at 7:01:54 PM UTC+3 T. Modes wrote: >> The main cause is there is only a single control point between image 2 and >> 3. Then the optimizer goes haywire. It sets the TrZ parameter of all images >> >=3 to -1.003 and then the output does not contain the images >=3. And now >> you try to calculate the HDR crop - the area which is contained in all >> images. But there are images with size 0 and therefore pano_modify/crop >> can't find a solution and runs infinitely. (The normal crop calculates >> without problems.) >> >> This can be easily seen in the GUI: open pto file and check (fast) preview. >> You will see that preview contains only 3 images (all other images have >> "zero" size in the output). >> >> Some more comments: >> Juha Kallioinen schrieb am Montag, 18. Oktober 2021 um 17:37:47 UTC+2: >>> 1. pto_gen IMG*.png >>> 2. <hugin IMG_0000-IMG_0318.pto, created a crop mask that covers the middle >>> of the first image in the series, saved as default.pto> >> >> The crop can also set with pto_gen --crop=... or pto_var --crop >> >>> 3. cpfind --sieve1width=20 --sieve1height=20 --sieve1size=300 >>> --kdtreesteps=400 --ransaciter=2000 --ransacdist=100 --sieve2width=10 >>> --sieve2height=10 --sieve2size=2 --linearmatch -o cpfind.pto default.pto >>> 4. celeste_standalone -s 1440 -i cpfind.pto -o celeste.pto >> >> You should combine these 2 steps. Simply add --celeste to cpfind parameters >> >>> 5. cpclean -o cpclean.pto celeste.pto >>> 6. <hugin cpclean.pto, reset crop mask for the first image, save as >>> cpclean.pto> >>> 7. pto_var --opt="y, p, r, TrX, TrY, TrZ" -o ptovar.pto cpclean.pto >> >> If all images are shot with the same camera/lens (iPhone) you should not >> optimize TrZ. There are too less information to optimize the field of view >> (and therefore TrZ) from a single image stack. >>> 8. autooptimiser -n -o mod_input.pto ptovar.pto >>> 9. pano_modify -o mod_out.pto --projection=0 --fov=AUTO --center >>> --canvas=AUTO --crop=AUTOHDR --output-type=REMAPORIG mod_input.pto > > -- > 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/d0ec02a3-251f-4174-aaba-34730d95905fn%40googlegroups.com. -- 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/D57EA37A-9395-43DD-8549-B9964AF5964A%40verizon.net.
