How should I set up and stitch multi-row panoramas in Hugin with a Nodal Ninja head?

Asked 4/16/2015

2 views

2 answers

0

I shoot larger multi-row panoramas (around 6 columns × 4 rows) using a Nodal Ninja pano head and Hugin, often with exposure-bracketed sets. My main issues are speed and reliability when stitching 20–30 source images per pano, and I’d like to avoid manually placing lots of control points.

I can usually predict the camera rotation fairly well from the pano head/rotator, so I have a decent estimate of image placement. In Hugin, though, automatic control points sometimes land on poor areas, and entering initial positions manually is awkward.

What’s the best workflow in Hugin for this kind of panorama? In particular:

  • Can approximate initial image placement be used effectively?
  • What control point generation approach tends to work best?
  • Are there recommended preparation or stitching steps for more reliable results?

Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0

Photography Stack Exchange contributor

11y ago

2 Answers

1

This isn't a comprehensive answer to your question but here a few things I've found to help give good results with Hugin. I'm no guru but I've used it for around four years now and got some decent results. If you can put any or all of these into action you will need to make very few changes, if any, from Hugin's default settings.

  1. If you have access to Adobe Camera Raw and have a profile available for your lens in the Lens Correction tab, use it. This will help reduce Hugin's workload by ironing out geometric distortions that are otherwise going to need compensating for, either by just letting Hugin get on with it during alignment or by using Hugin's camera and lens correction page. Most of the hard work is already done for you if you use ACR. If you're using a decent prime with low distortion this step isn't so important, but it's worth performing with zooms. This leads us onto...

  2. Use a prime lens if you can as these will generally have better edge and corner performance than zooms. Control points are always in overlapping regions and are frequently near edges or in the corners. The better the lens performance in these areas the greater the accuracy of control point auto-detection. Using an aperture around the f8 mark often gives the best edge/corner quality. As for choice of lens, you don't need to break the bank as most manufacturers basic 50mm lenses offer great picture quality thanks to their simple design, and are well suited to panoramic photography.

  3. While it's a little time-consuming I find it's worth manually getting rid of all control points in sky areas as they don't make good reference points (same goes for any scene with moving elements). The Celeste function can help but it's not fool-proof, and definitely not as effective as manual CP removal.

  4. If you're going down the HDR route with your bracketed images I'd suggest processing your bracketed images into HDR using your preferred application, rather than using Hugin's built-in HDR functions. Your mileage will definitely vary with the built-in tools and I find using a familiar HDR application gives much more predictable results (and a much finer degree of tone-mapping control too).

Addressing your specific questions, the Yaw setting in the Image tab is the one you need if you want to specify the degree of rotation when using your pano head. Select a central image as your anchor, with yaw and pitch values of 0. Images to the left will have -yaw values and those to the right will be +yaw. If you're going multi-row, +pitch values are up and -pitch are obviously going to be down.

Regarding control points, I've never had need to look at other CP creation algorithms beyond the default cpfind as it works very well if given a decent set of images.

As for stitching protocols, if you mean Projection Type then it's a case of experimenting and going with whatever gives a good looking end result.

Originally by user38190. Source · Licensed CC BY-SA 4.0

user38190

11y ago

0

AI Answer

Generated from our catalog & community — verify before relying on it.

A practical Hugin workflow is to make the images as easy as possible to match before stitching.

Good preparation helps most: apply lens correction first if you have a reliable profile, because reducing distortion gives Hugin less work during alignment. Shoot with consistent overlap and exposure where possible, and if you bracket exposures, treat those as stacks/HDR inputs rather than unrelated frames.

For control points, automatic generation can work well when the source images are clean and corrected, but it will struggle on low-detail areas like blank walls. In those cases, add or fix only a small number of control points manually in strong features such as corners and edge intersections rather than trying to place many by hand.

Approximate initial placement from your pano head can be useful as a starting point, but in practice the biggest gains usually come from accurate shooting geometry, lens correction, and letting Hugin optimize from good overlaps. If automatic points are poor, the issue is usually image content or distortion rather than just missing initial position data.

So the recommended protocol is: preprocess/lens-correct, group bracketed shots appropriately, generate automatic control points, inspect weak image pairs, and manually correct only the few problematic areas before optimizing and stitching.

UniqueBot

AI

11y ago

Your Answer