Re: [hugin-ptx] Multi-row panorama

[Greg 'groggy' Lehey]

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.


signature.asc
Description: PGP signature

Re: [hugin-ptx] Drone Pano Scripting - Cannot get rid of the Black Hole Sky

[Bruno Postle]

On Tue, 22 Aug 2023, 04:34 PanoSeek wrote:

>
> The closest I found was Bruno talking about the l-29 setting for enblend -
> https://groups.google.com/g/hugin-ptx/c/aghpJeyIvQo/m/k6iOJVImjskJ - I
> did attempt Bruno's solution, but got an error about couldn't do 29, could
> only do 9 and some errors that said 10.  So I tweaked the setting to 9
> (#hugin_enblendOptions -l 9) and ran it.  No errors, but no change to the
> image that I could tell...still have big black hole sky.
>

This technique is basically to create a new fake blue photo, add it to the
set at yaw=90, and hope that enblend will smooth out the transition. You
need as many enblend levels as possible for maximum smoothing (the
parameter should be -l 27, my mistake), the patch photo needs a big enough
angle of view to cover the whole black area, but all skys are different so
you won't be able to use the same shade of blue on all panoramas.

-- 
Bruno

>

-- 
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/CAJV99Zhj2JUejEvzj3ojfArBxHABFThQeZB0ASQPZ8JU5wtGtw%40mail.gmail.com.

Re: [hugin-ptx] Scripted Hugin Panos from Drone - Fighting the curvature of the earth?

[Bruno Postle]

On Tue, 22 Aug 2023, 03:58 PanoSeek wrote:

>
> After reading the latest thread about multi-row pano's, I have been
> inspired to refine my hugin script I use to build 360 spheres from my DJI
> Mini 2.  I ran into an interesting artifact that I cannot get rid of - A
> jagged line in the horizon.
>

Curvature of the earth shouldn't be a problem, it would just result in a
slightly lower horizon line. More likely this is a more mundane problem:
too much fixity (none of your images should have roll or pitch fixed);
wrong camera angle of view (360° panoramas are very sensitive to this, you
should always optimise angle of view); or bad control points (look for
problems near where there are high control point distances).

-- 
Bruno

>

-- 
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/CAJV99Zh6-zD-XpYp0xhrtRytDRyy120OqR3ksZ8ZL6zR4Q3ZzA%40mail.gmail.com.

Re: [hugin-ptx] Force Hugin CPFind to create/find more Control Points? Problem with lots of snow.

[PanoSeek]

Hello!

Just in case someone comes across this thread, I have figured out the 
solution suggested above that is currently working….templates and 
prealigned commands to re-use known locations of images. The DJI Mini 2 
shoots a pano in the same manner each time thankfully. 

I have modified my script that stitches my DJI Mini 2 Pano photo sets and 
it does the following -

Here is what my script does - 

   1. Generates a new PTO for the specific folder 
   2. import template details. 
   3. cpfind (with pre-aligned as the drone uses the same pattern each time) 
   4. clean control points 
   5. geocpset to “match” images without CP’s…this was needed for areas of 
   water/snow that are mostly featureless. 
   6. clean control points 
   7. linefind (not really seeing a benefit to this one, but that is 
   another story) 
   8. Autooptimiser 
   9. Pano_Modify - tweak the settings to get the output I want. 
   10. send the PTO to batch processor to not completely kill my computer 
   when doing large sets. 

The trick with the featureless images (water this time, but I think it will 
be similar with my snow photos) was the creation of a template and using 
the pre-aligned parameter along with the geocpset tool. 

This is not perfect yet, but far better. 

Note - Templates - I used a pto file that was very close to perfect for my 
template.pto. The script ingests this template file and uses the needed 
data for positioning. I could not find a good reference for the —prealigned 
parameters/process, so this was a lot of trial and error. 

The full script as of writing this -
REM 2023-08-21- This script is being built to take a folder full of folders 
containing groups of .jpg photos from the drone 360 photo tool and export a 
2:1 aspect ration photo to be uploaded to google Maps/Streetview. REM Guide 
followed located here - 
https://wiki.panotools.org/Panorama_scripting_in_a_nutshell#Creating_hugin_projects_on_the_command-line
 
REM - dji.assistant file uses a similar process, but dynamically pulls 
data. If the template I have setup does not work well, this may be a new 
idead - http://www.wse.fr/How-TO/dji-30.assistant REM Hugin needs to be 
installed here C:\Program Files\Hugin REM - This script is being called by 
the deployment script. The Deployment script copies this to each folder in 
the specified directory and then executes it. All sub-folder tasks will run 
at the same time, so it will take a bit of time when doing many panos. REM 
- MAKE SURE YOU DO NOT HAVE ANY NON-PANO IMAGES IN THE FOLDER. THE SOFTWARE 
TRIES TO EAT THEM AND ADD TO YOUR PANO. REM - set the name of the variable 
we will be using. This will be the name of the directory the file is in. 
@echo off for %%I in (.) do set "current_folder=%%~nxI" echo The current 
folder is: %current_folder% REM Build the PTO file with the contents of the 
directory we are currently in. "C:\Program Files\Hugin\bin\pto_gen" *.jpg 
-o %current_folder%.pto REM Add detail from the template example (a good 
DJI Mini2 pano in my case) to new PTO file from the template of a known 
good file. REM - 
https://groups.google.com/g/hugin-ptx/c/Af7TG2Bq-ko/m/3g3y-xIoEAAJ 
"C:\Program Files\Hugin\bin\pto_template" --o %current_folder%.pto 
--template=template.pto %current_folder%.pto REM Create Control Points in 
the project "C:\Program Files\Hugin\bin\cpfind" --prealigned -o 
%current_folder%.pto %current_folder%.pto REM Clean up the control points 
"C:\Program Files\Hugin\bin\cpclean" -o %current_folder%.pto 
%current_folder%.pto REM Use the non-conntected tool to align non-CPlinked 
images REM - 
https://groups.google.com/g/hugin-ptx/c/Af7TG2Bq-ko/m/3g3y-xIoEAAJ 
"C:\Program Files\Hugin\bin\geocpset" -o %current_folder%.pto 
%current_folder%.pto REM Clean up the control points "C:\Program 
Files\Hugin\bin\cpclean" -o %current_folder%.pto %current_folder%.pto REM 
Find Vertical Lines "C:\Program Files\Hugin\bin\linefind" -o 
%current_folder%.pto %current_folder%.pto REM Optimize "C:\Program 
Files\Hugin\bin\autooptimiser" -a -l -s -m -o %current_folder%.pto 
%current_folder%.pto REM set output/stitcher options REM These options are 
to setup the pano for upload to Google Maps. "C:\Program 
Files\Hugin\bin\pano_modify" -o %current_folder%.pto --fov=360x180 --center 
--straighten --canvas=9000x4500 --ldr-file=JPG --ldr-compression=100 
--output-exposure=AUTO %current_folder%.pto REM Stitch the output - un-rem 
the next line if you want the script to stitch right away. I had too many 
at once so I moved over to the batch tool, which is the command below. REM 
"C:\Program Files\Hugin\bin\hugin_executor" --stitching 
--prefix=%current_folder% %current_folder%.pto REM send to batch to run 
sequentially. REM Only use the next line if the "hugin_executer" line is 
commented out. "C:\Program Files\Hugin\bin\PTBatcherGui.exe" --batch 
%current_folder%.pto REM - Figure out how to get rid of the black blocks at 
the top. 
​
On Thursday, February 16, 2023 at 10:09:09 AM UTC-

Re: [hugin-ptx] Multi-row panorama

[dgjohnston]

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.

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).

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).
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. Also, keeping the 
white balance fixed might help the colour tinting that shows up.

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

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

Don J.

> On Aug 21, 2023, at 6:27 PM, Greg 'groggy' Lehey  wrote:
> 
> On Sunday, 20 August 2023 at  6:34:23 -0400, Stanley Green wrote:
>> If the link is still active, you can try to get the images directly:
>> 
>> https://wetransfer.com/downloads/c5b1b40878f4f80c5b68af6a6767392b20230817102250/51d164ee951b6c084af7ed1d0d27730e20230817102250/2ee2fd
> 
> Thanks for that.
> 
> I'm confused.  A week ago I wrote:
> 
> On Tuesday, 15 August 2023 at 11:02:08 +1000, Greg 'groggy' Lehey wrote:
>> 
>> My suggestion: use the Align tab on the Fast Panorama Preview.
> 
> Specifically,
> 
> 1. Load the files from the "Load Images" tab in the Fast Panorama
>   Preview.
> 2. Select "Align" from the Fast Panorama Preview.
> 3. Select "Create Panorama" from the Fast Panorama Preview.
> 
> And that's all.
> 
> In a little more detail for this specific panorama:
> 
> 1. Loading the files produced the popup
> 
> Hugin has image stacks detected in the added images and will
> assign corresponding stack numbers to the images.  Should the
> position of images in each stack be linked?
> 
>   That's incorrect.  There are no image stacks here, so you should
>   answer No.  I've almost never seen this message, and I suspect it
>   comes here because of the overlap between images.  30% should be
>   enough.  This will give you fewer images and will greatly reduce
>   the stitching time.
> 
> 2. Aligning the images gave me an image with mean error 3.8 pixels,
>   maximum 28.4.  Potentially you could improve on this with more
>   attention to the position of the entrance pupil, but part of it
>   will be due to the water, which doesn't stay the same from one
>   image to the next.  You could tune the control points, but in this
>   case I don't think you need to: I don't see any inconsistencies in
>   the finished panorama.
> 
> 3. "Create Panorama" offers you a choice of stitching options,
>   defaulting to "exposure corrected, low dynamic range".  That's the
>   one.
> 
> But that's all.  In particular, I don't understand the problems that
> David W. Jones had, but then I don't understand the complexity either.
> I also didn't see the colour discrepancies that he mentions.
> 
> So: the final image is at
> http://www.lemis.com/grog/photos/Photos.php?dirdate=20230817
> I have also put the .pto file at
> http://www.lemis.com/grog/Day/20230817/GF_6-panels_-3-Rows-0-GF_6-panels_-3-Rows-17.pto
> This will not be directly applicable, because I have removed the
> spaces from the file names you provided.
> 
> Click on the image up to three times to increase the size up to the
> original (about 113 MP).  Also let me know if you want this image
> removed after we're done.
> 
> Greg
> --
> 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/20230822002739.GE55746%40eureka.lemis.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 hugin-ptx+unsubscr...@googlegroups.com.
To view t

Re: [hugin-ptx] What do I wrong?

[Greg 'groggy' Lehey]

On Monday, 21 August 2023 at  3:42:13 -0700, Martin wrote:
>
> I just started to test Hugin, and prepared four well matching  levelled
> images . I got this bent panorama:

Without seeing the input files, it's hard to know if anything went
wrong.  But you can fix this from the Move/Drag tab in the Fast
Panorama Preview: there's a “Straighten” option that lets you bend the
pano to match reality.

If you need more help, please don't send images to this list.  If you
have difficulty finding somewhere to put them, we should discuss.

Greg
--
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/20230822003157.GF55746%40eureka.lemis.com.


signature.asc
Description: PGP signature

Re: [hugin-ptx] Multi-row panorama

[Greg 'groggy' Lehey]

On Sunday, 20 August 2023 at  6:34:23 -0400, Stanley Green wrote:
> If the link is still active, you can try to get the images directly:
>
> https://wetransfer.com/downloads/c5b1b40878f4f80c5b68af6a6767392b20230817102250/51d164ee951b6c084af7ed1d0d27730e20230817102250/2ee2fd

Thanks for that.

I'm confused.  A week ago I wrote:

On Tuesday, 15 August 2023 at 11:02:08 +1000, Greg 'groggy' Lehey wrote:
>
> My suggestion: use the Align tab on the Fast Panorama Preview.

Specifically,

1. Load the files from the "Load Images" tab in the Fast Panorama
   Preview.
2. Select "Align" from the Fast Panorama Preview.
3. Select "Create Panorama" from the Fast Panorama Preview.

And that's all.

In a little more detail for this specific panorama:

1. Loading the files produced the popup

 Hugin has image stacks detected in the added images and will
 assign corresponding stack numbers to the images.  Should the
 position of images in each stack be linked?

   That's incorrect.  There are no image stacks here, so you should
   answer No.  I've almost never seen this message, and I suspect it
   comes here because of the overlap between images.  30% should be
   enough.  This will give you fewer images and will greatly reduce
   the stitching time.

2. Aligning the images gave me an image with mean error 3.8 pixels,
   maximum 28.4.  Potentially you could improve on this with more
   attention to the position of the entrance pupil, but part of it
   will be due to the water, which doesn't stay the same from one
   image to the next.  You could tune the control points, but in this
   case I don't think you need to: I don't see any inconsistencies in
   the finished panorama.

3. "Create Panorama" offers you a choice of stitching options,
   defaulting to "exposure corrected, low dynamic range".  That's the
   one.

But that's all.  In particular, I don't understand the problems that
David W. Jones had, but then I don't understand the complexity either.
I also didn't see the colour discrepancies that he mentions.

So: the final image is at
http://www.lemis.com/grog/photos/Photos.php?dirdate=20230817
I have also put the .pto file at
http://www.lemis.com/grog/Day/20230817/GF_6-panels_-3-Rows-0-GF_6-panels_-3-Rows-17.pto
This will not be directly applicable, because I have removed the
spaces from the file names you provided.

Click on the image up to three times to increase the size up to the
original (about 113 MP).  Also let me know if you want this image
removed after we're done.

Greg
--
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/20230822002739.GE55746%40eureka.lemis.com.


signature.asc
Description: PGP signature

[hugin-ptx] What do I wrong?

[Martin]

I just started to test Hugin, and prepared four well matching  levelled 
images . I got this bent panorama:

[image: TheCastle.png]

-- 
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/6e7b0bd7-e024-48b5-8540-b2f9844577a8n%40googlegroups.com.

Re: [hugin-ptx] Multi-row panorama

[David W. Jones]

Excellent!

Try the various drag-and-drop options, see how things turn out. I think 
the problem is rooted in drag-and-drop identifying bogus stacks, but I 
could be wrong.


On 8/20/23 13:51, dgjohnston wrote:
Stanley … thanks, the download worked. If I run into anything 
interesting I’ll send an update.


Don J.


On Aug 20, 2023, at 4:34 AM, Stanley Green  wrote:

If the link is still active, you can try to get the images directly:

GF_6 panels_ 3 Rows 17.tif 

wetransfer.com 

	 
 





It is supposed to be active through 8/24.

--
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/C330880B-452B-4E0B-9D30-01444C4727CC%40vt.edu 
.


--
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/C234488A-BA73-4B54-BF32-96781C22EE84%40accesscomm.ca 
.



--
David W. Jones
gnomeno...@gmail.com
wandering the landscape of god
http://dancingtreefrog.com
My password is the last 8 digits of π.

--
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/a73c244d-87e5-dbd5-6d42-9ae815126412%40gmail.com.