I've realised I should have tried removing the parameters one at a time to try 
to find which was the problem. What works is removing "-m" "Optimize field of 
view for all images, except for first. Useful for aligning focus stacks with 
slightly different magnification." I've been using this command for so long 
I've forgotten why -m was included and don't really understand what it does. 
I'll remove it and hope it doesn't cause any problems.
It's probably still a bug though as ais probably shouldn't get stuck in a loop 
whatever options are used.

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/2002813

Title:
  align_image_stack hangs

Status in Hugin:
  Incomplete

Bug description:
  I have an application that uses align_image_stack, which works very well.
  Unfortunately it sometimes hangs up when aligning two images, I assume that's 
because they are too difficult to align. It states "Number of good matches: 0, 
bad matches: 40" many times, then that it has done "n iterations" up to 259. At 
that point it states "Run called" and then gets stuck. This would be alright if 
I was using it from a terminal, but it's embarrassing when it does it in my app 
- there's no easy way to detect the condition and stop it.
  It would be better to prevent it - is that possible? If not I think it's a 
bug. I can supply the two  images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/2002813/+subscriptions


_______________________________________________
Mailing list: https://launchpad.net/~hugin-devs
Post to     : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp

Reply via email to