Consistent Crash with 180+ images "Align"

[salamanders]

Same set of images, trying to align 181 images. Loads the images fine, then when I press "Align" it crashes. If I load less images (say, about the first 100 images) it works fine.

Latest build that I could find for Windows: http://hugin.panotools.org/testing/hugin/index.html Beta 3

[salamanders (salamanders)]

The file ad6c_appcompat.txt was added: Crash file

[hvdwolf (hvdwolf-users)]

This is not a Hugin bug. All programs, also the Control Point generators are limited to 128 arguments. Including the neccessary arguments that leaves you to 123 images maximum. Less images if you use more arguments.

In case you do need to use more images (180 in your case), you can only use autopano-sift-c and you should add the %s parameter to autopano-sift-c. In that case your images will be fed into a temporary script and Hugin & autopano-sift-c automatically work on.

You can adjust that in the hugin preferences pane on the autopano tab: set the arguments to something like --maxmatches %p %o %s

Please test and close this bug report if it works as mentioned above.

Harry

[salamanders (salamanders)]

Perhaps a crash/"report this crash to Microsoft" isn't how the program should react when people load more than 123 images - would it be possible to have the program instead display the instructions you just gave me?

[Bruno Postle (brunopostle)]

This is a wxwidgets problem, the number of photos is limited to 120 or so, the solution is to change the autopano preference to supply the list of photos in a single project file:

  â€“maxmatches %p %o %s

[salamanders (salamanders)]

hvdwolf - Good to know about the hard limit. I will try with the setting you mentioned.

I'm concerned that people that try to use the program without knowing the hard limit are going to have the same experience. Is there any way that instead of crashing with no reason given, it could pop up an error message, prevent more than 123 images, or ideally, throw up a warning of "Max Images exceeded, changing the param to '--maxmatches %p %o %s'"?

[nobody (nobody-users)]

Your solution with changing the parameters works great but isn't it better to add the %s parameter automatically if the max images-limit exceeds?

[harryvanderwolf (harryvanderwolf)]

It would be more userfriendly to do so, I agree, but it's very hard to do as it requires one to have autopano_sift_ on his/her system. I prefer panomatic as it uses less memory, it's much faster and also gives a better spread in CP's as well which is better for stitching. It doesn't allow for more than 122-125 images, depending on the parameters.
It can hardly be done automatically as there are other CPgenerators and all require other settings.

Not the ideal, but the optimal way would be something like:
 - count images and parameters
 - if >= 128 check if autopano_sift-c is used
     yes: alter parameters automatically
     no: Check for existence of autopano-sift-c
           exists: message to user: <blah blah blah> you need to use autopano-sift-c instead with this parameters
           doesn't exist: this is only possible with autopano_sift_c. you need to install it if you want to use this no. of images. if you are in the US pay attention to the copyright infringements
     Or you should you should lower the images below (128 - parameters)

[tmodes (tmodes)]

Current version is warning user about issue and gives hint for workaround