I've been trying to use Hugin to align an image sequence of 360 equirectangular photos and found that using "align_image_stack" as a control point detector works the best and fastest for my useage of reorientating subsequent images to match the starting anchor image.

When attempting to create control points for over 120 images or so, I get the error "Too many arguments (images). Try using the %s parameter in preferences." [* I cannot find any documentation on the %s parameter btw)

My brute force solution has been to 1) "Create control points" for 101 images at a time, 2) Calculate optimization incrementally from image #0 (Anchor Image), 3) Export the now aligned 101 images as TIFF files, 4) Start a new project and Repeat the process for the next 100 images using the now aligned image #101 as my new "image #0 (Anchor image)"

A) Is there a way to increase the number of images the "align_image_stack" can process?

and / or

B) Would it be possible to write an automated script to repeat my above process for 100 images at at a time?

Thanks for any insights.

  • \$\begingroup\$ Unfortunately I don't have a solution, but according to the code it's a limitation of the toolkit hugin uses rather than deliberate limit imposed by the developers of hugin. As for writing a script - yes, it should be relatively easy to automate it using a script, because almost all functionality of hugin is available as various command line tools \$\endgroup\$
    – stativ
    Commented Sep 24, 2022 at 18:05

1 Answer 1


I'm not that knowledgeable about align_image_stack, but what I'm googling up seems to indicate that running align_image_stack on smaller batches of files with the -p option to create a .pto project file, and then using pto_merge to combine the project files together is a viable solution for larger batches of images.



Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.