Why can Autopano stitch a large 360° panorama more reliably than Hugin?
Asked 10/2/2016
5 views
2 answers
0
I shot an indoor 360° panorama from a tripod using about 300 overlapping images with a 35mm lens on a Nikon DX body. In Hugin, the project became slow and error-prone: it seemed to try matching every image against every other image, produced many bad control points, flipped some images, and the preview was badly scrambled. Reducing image resolution and using only half the frames sped things up, but the result was still poor and required lots of manual correction.
By contrast, Autopano processed the full set quickly and produced a correct panorama on the first try. Why does this happen? Is it mainly due to different defaults or project setup, or are Autopano’s matching and stitching algorithms simply more robust for very large multi-row panoramas?
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
9y ago
2 Answers
1
I could be trite and say: better QA (debugging) process and algorithmic improvements... but I can be much more specific:
Two reasons (and I've seen the same effect BTW, having recently cleaned up a multi-row 360 pano shot with 70-200 Nikon and FX sensor.)
1) Hugin definitely attempts to match every photo to every other photo. That's not necessarily a problem except that it can require quite a lot of memory and scratch disk space. One bug/limitation of Hugin is that it doesn't monitor free space well and doesn't overflow temp file usage to other partitions. YES, reducing resolution for the matching can help. But then you've got to go through and clean up the matches.
2) Hugin definitely gets confused at times, not only about significant overlaps, but also about the specific order in which they are presented. For example, suppose you have a row sequence like this, with significant overlap: 1 2 3 4 5
I have found many cases where even though everything appears to be fine, photo #3 will be improperly integrated into the pano (and/or the whole thing may crash etc)... yet if I simply resequence so #3 is "on top" then all is well: 1 2 5 3 4 (ie the order in the list becomes P1,P2, P4,P5,P3 or even 1 2 4 3 5 (ie just move P3 over one: P1, P2, P4, P3, P5)
Obviously, if these kinds of bugs had been fully diagnosed, Hugin wouldn't have these issues.
Originally by user72796. Source · Licensed CC BY-SA 4.0
user72796
8y ago
0
Generated from our catalog & community — verify before relying on it.
From the answers, the main difference is not your camera profile so much as how the software searches and organizes matches.
Hugin may try to match every image with every other image. With a 300-image pano, that creates a huge search space, heavy memory/scratch-disk use, and more chances for false control points. It can also get confused about image order and overlap, especially in large multi-row or 360° sets, which leads to flipped or misplaced frames unless you manually clean things up.
Autopano is described as being better optimized for this job: it more intelligently narrows likely neighboring images, handles large sets faster, and is generally more robust at building the pano structure automatically. In practice, that means fewer bad matches and less manual intervention.
So yes: based on the answers, Autopano’s algorithms and implementation are effectively superior here, especially for large, complex panoramas. Hugin can still work, but it may need more manual control-point cleanup and more careful management of resources and workflow.
Recommended products
UniqueBot
AI9y ago
Your Answer
Related Questions
How can I tone map a very large HDR panorama after stitching?
How can I align more than 120 images in Hugin with align_image_stack?
Where can I find Creative Commons 360° panorama photos for a project?
Fastest way to make reference scans of 20,000 archived 35mm negatives
How can I fix a stitching error in AutoPano when adding another image breaks part of the panorama?