On Monday, 21 August 2023 at 20:36:26 -0600, dgjohnston wrote:

> Greg, thanks for the additional information. The images in this set
> are well suited to the quick run though using the Fast Pano Preview
> because of the randomness of the rocks, trees, and water. It’s hard
> to detect any minor discrepancies like one would with images of
> manmade structures. With those the iterative process that David
> covered works well to get the best alignment.

... except that it didn't at first.  And I found it surprisingly
complicated.

> I don’t know why David’s version of Hugin wasn’t able to find
> connections between so many images. He used 2022.0 and I’m using
> 2022.1 (listed as pre-release).

FWIW, mine is ancient: 2018.0.0.  It's been some time since we've had
issues in this area.

> 1. Another reason that Hugin might be coming up with the “image
>    stacks” is the difference in shutter speed of the images … they
>    run from 1/125 s to 1/500 s (but I don’t know what Hugin is
>    basing its decision on).

I'm not sure either, but I tried a second panorama with only the top
and bottom rows (leaving out the middle row).  I no longer got the
"has image stacks detected" message, and it stitched perfectly.  The
error was down to 1.9 average and 14.7 max.  See the second image at
http://www.lemis.com/grog/photos/Photos.php?dirdate=20230817
So my guess is that the overlap with the middle row confused it.

> Stanley … I’ve seen many suggestions that pano images be taken in
> manual mode with the settings base on the brightest part of the
> image.

Yes, that's the recommendation IIRC.  I used to set aperture priority
mode with my older panos (10 years or so ago), but then I started
using HDR images and moved to manual mode with 3 bracketed images:
+1.7 EV, +4.7 EV and -1.3 EV.

> Also, keeping the white balance fixed might help the colour
> tinting that shows up.

We only have TIFF images here, but my guess is that Stanley is using
raw images, so the colour balance doesn't really count.  But it would
be interesting to see what Hugin thinks.

> 2. After Align, I get a mean error of 5.5 pix with max 38.6.

That's strange.  But I've seen this before, years ago (round 26
December 2012 if you want to go searching).  You might also like to
look at
http://www.lemis.com/grog/diary-dec2012.php?subtitle=Control%20point%20detector%20or%20random%20number%20generator?&article=D-20121226-230249#D-20121226-230249

> I received the same colour tint issues that showed in David’s
> stitched image. The top-right corner has a green tinge.

Can you confirm that that's not the case with my images?  I
deliberately didn't try any tuning.
--
Sent from my desktop computer.
Finger groog...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

-- 
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 hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20230822063706.GH55746%40eureka.lemis.com.

Attachment: signature.asc
Description: PGP signature

Reply via email to