issue aligning single-row indoor panorama

104 views
Skip to first unread message

jose1711

unread,
Apr 15, 2025, 8:33:59 AMApr 15
to hugin and other free panoramic software
Hello,

struggling to stitch a panorama of 6 images of an indoor foodcourt, using Hugin 2024.0.1, Hugin's CPFind to find control points. I've tried many things but for some reason I cannot get a satisfactory result.

I've also tried the online stitcher at https://sisik.eu/pano and it was able to stitch them without issues.

Can someone please help?

Source images:

Thanks!

dkloi

unread,
Apr 15, 2025, 11:39:49 AMApr 15
to hugin and other free panoramic software
CPFind is finding some erroneous matches between the 2nd and 4th images. If you remove them it should stitch OK.

jose1711

unread,
Apr 15, 2025, 4:55:25 PMApr 15
to hugin and other free panoramic software
Thank you, that worked! So in cases like these I guess I am supposed to make sure Hugin only found CPs between adjacent images.

Dátum: utorok 15. apríla 2025, čas: 17:39:49 UTC+2, odosielateľ: dkloi

Erik Keever

unread,
Apr 15, 2025, 6:04:58 PMApr 15
to hugi...@googlegroups.com
Hi Jose,

If you have a single-row panorama like this, you should be able to use the default "Hugin's cpfind" which will only look for control points between successive images in the selected list (0 and 1, 1 and 2, ..., N-1 and N). The "cpfind prealigned" will only look between images which already overlap in the panorama sphere, and there's the fully general one (cpfind multirow/stacked) that looks between all image pairs. (unless this is all changed from 2023.0 to 2024.0).

-- Erik 

--
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+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/hugin-ptx/c20081f5-d8f4-40ce-b024-ce59a60967bcn%40googlegroups.com.

dkloi

unread,
Apr 16, 2025, 3:57:55 PMApr 16
to hugin and other free panoramic software
I usually manually place my control points. But it's generally a good idea to check the table of control points after alignment and look at the maximum errors to see if there are any wrongly placed ones. In the Expert Interface, under the View tab is Control point table. You can sort by Distance. Clicking on the row will take you to the Control Points tab where you can check whether they are on the correct feature.

jose1711

unread,
Jun 17, 2025, 5:26:51 AMJun 17
to hugin and other free panoramic software
Thank you, inside Hugin's preferences I created a new Control Point Detector with the following settings:

Description: CPFind - single row
Program: cpfind
Arguments: --linearmatch -o %o %s

This seems to work best for my single-row panoramas taken by a smartphone camera.



Dátum: streda 16. apríla 2025, čas: 21:57:55 UTC+2, odosielateľ: dkloi

David W. Jones

unread,
Jun 17, 2025, 5:33:24 AMJun 17
to hugi...@googlegroups.com
Hmm, just wondering, but...isn't that exactly what the CPFind prealigned detector does???

--
David W. Jones
gnome...@gmail.com
exploring the landscape of god
http://dancingtreefrog.com

Sent from my Android device with F/LOSS K-9 Mail.

T. Modes

unread,
Jun 17, 2025, 11:56:58 AMJun 17
to hugin and other free panoramic software
GnomeNomad schrieb am Dienstag, 17. Juni 2025 um 11:33:24 UTC+2:
Hmm, just wondering, but...isn't that exactly what the CPFind prealigned detector does???

No, it is different.

David W. Jones

unread,
Jun 17, 2025, 4:12:28 PMJun 17
to hugin-ptx
How so? When I look through CPFind's command line options, there's no mention of it. I have cpfind 2024.0.1.ead3af10a01a.
-- 
David W. Jones
gnome...@gmail.com
wandering the landscape of god
http://dancingtreefrog.com
My password is the last 8 digits of π.

T. Modes

unread,
Jun 17, 2025, 4:31:37 PMJun 17
to hugin and other free panoramic software
GnomeNomad schrieb am Dienstag, 17. Juni 2025 um 22:12:28 UTC+2:
 
How so? When I look through CPFind's command line options, there's no mention of it. I have cpfind 2024.0.1.ead3af10a01a.
I don't know where you look.
>cpfind --help
Hugin's cpfind 2024.0.1.ead3af10a01a built by Thomas
based on Pan-o-matic by Anael Orlinski
<snip>
Matching strategy (these options are mutually exclusive)
  --linearmatch   Enable linear images matching
                  Can be fine tuned with
      --linearmatchlen=<int>  Number of images to match (default: 1)
  --multirow      Enable heuristic multi row matching
                  default matching strategy, keep for backward reason
  --prealigned    Match only overlapping images,
                  requires a rough aligned panorama
  --allpairs      Match all image pairs (slow)
<snip>


David W. Jones

unread,
Jun 17, 2025, 9:53:59 PMJun 17
to hugin-ptx
In the terminal, info cpfind gives me this:
Matching strategy
       All pairs

       This is the default matching strategy. Here all image pairs are matched against each other. E.g. if your project contains 5
       images then cpfind matches the image pairs: 0-1, 0-2, 0-3, 0-4, 1-2, 1-3, 1-4, 2-3, 2-4 and 3-4

       This strategy works for all shooting strategy (single-row, multi-row, unordered). It finds (nearly) all connected image
       pairs. But it is computational expensive for projects with many images, because it test many image pairs which are not
       connected.

       Linear match

       This matching strategy works best for single row panoramas:

          cpfind --linearmatch -o output.pto input.pto

       This will only detect matches between adjacent images, e.g. for the 5 image example it will matches images pairs 0-1, 1-2,
       2-3 and 3-4. The matching distance can be increased with the switch --linearmatchlen. E.g. with --linearmatchlen 2 cpfind
       will match a image with the next image and the image after next, in our example it would be 0-1, 0-2, 1-2, 1-3, 2-3, 2-4 and
       3-4.

       Multirow matching

       This is an optimized matching strategy for single and multi-row panorama:

          cpfind --multirow -o output.pto input.pto

       The algorithm is the same as described in multi-row panorama. By integrating this algorithm into cpfind it is faster by using
       several cores of modern CPUs and don't caching the keypoints to disc (which is time consuming). If you want to use this
       multi-row matching inside hugin set the control point detector type to All images at once.

After that, it goes on to cover "Keypoints caching to disk".

whereis shows cpfind at /usr/local/bin/cpfind.

Ideas?
--
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+...@googlegroups.com.

T. Modes

unread,
Jun 18, 2025, 10:47:02 AMJun 18
to hugin and other free panoramic software
GnomeNomad schrieb am Mittwoch, 18. Juni 2025 um 03:53:59 UTC+2:
In the terminal, info cpfind gives me this:
<sigh> I mentioned 2 places which provide the current infos. And you found the third place - the man pages. They are only used on Linux - and there is nobody which takes care of the maintenance of these man pages.
So patches are welcome.

David W. Jones

unread,
Jun 18, 2025, 4:26:55 PMJun 18
to 'T. Modes' via hugin and other free panoramic software

How are man pages made? I'm usually just a consumer of them.

Reply all
Reply to author
Forward
0 new messages