I have a strange problem with a specific set of images (not shot by me).
When I run them through hugin's "automatic" process, autopano-sift-c
seems to hang on the control point generation (on my machine at around
6+ minutes). This set is not a complete pano, there's a missing image I
think and the features are very much alike across all images.
After setting manual control points, the connected set stitches very
well, so the problem isn't that the panorama wasn't shot from a single
point or similar.
I was using rev. 2957 of both hugin and autopano for this (though I
think I tried an earlier version as well and then updated to this
version to see if this was already fixed).
The images (and manual pto) can be found at:
http://margo.student.utwente.nl/simon/temp/wall.zip
BTW, which image editor will retain the "uncrop" information in the tiff
files? I noticed the gimp loses this info after editing...
Cheers
Simon
Simon Oosthoek wrote:
> I have a strange problem with a specific set of images (not shot by me).
> When I run them through hugin's "automatic" process, autopano-sift-c
> seems to hang on the control point generation (on my machine at around
> 6+ minutes). This set is not a complete pano, there's a missing image I
> think and the features are very much alike across all images.
Would you mind posting your autopano-sift-c settings in the hugin
preferences dialog ?
I've tried control point generation on your image set with the default
options (which is much faster than 6 minutes on my box) and it works
fine. It works also when I run autopano-sift-c from the command line,
e.g.:
autopano-sift-c autopano-sift-c.pto p10208*.jpg
.
But what happens here is that aligning the image after the control
point generation hangs ... and even more: I cannot operate hugin
anymore, e.g. press the cancel button. No reaction at all.
Kind regards,
Stephan.
--maxmatches %p %o %i
This is the default setting I think.
> I've tried control point generation on your image set with the default
> options (which is much faster than 6 minutes on my box) and it works
(I'm using a 4 year old machine (P4), but I do have 2GB ;-)
> fine. It works also when I run autopano-sift-c from the command line,
> e.g.:
> autopano-sift-c autopano-sift-c.pto p10208*.jpg
> .
I didn't try that, but your next observation is what I see as well, so
the problem isn't in autopano, but just after that in hugin?
>
> But what happens here is that aligning the image after the control
> point generation hangs ... and even more: I cannot operate hugin
> anymore, e.g. press the cancel button. No reaction at all.
>
Exactly, that's what I have as well.
thanks for verifying this!
Simon
Simon Oosthoek wrote:
>> Would you mind posting your autopano-sift-c settings in the hugin
>> preferences dialog ?
>
> --maxmatches %p %o %i
>
> This is the default setting I think.
It depends on the %p settings in hugin. When you run autopano-sift-c from
the command line the default is 25. Run autopano-sift-c without any options
for usage help.
>> But what happens here is that aligning the image after the control
>> point generation hangs ... and even more: I cannot operate hugin
>> anymore, e.g. press the cancel button. No reaction at all.
> Exactly, that's what I have as well.
Are you going to file a bug report ?
> thanks for verifying this!
You're welcome.
BTW, when I create a pto-file from the command line with autopano-sift-c
or panomatic and load it into hugin, aligning works. It is complaining
about unconnected images, though, but hugin proceeds.
Rgds,
Stephan.
When I remove the --maxmatches parameter, I don't get the failure
>
>>> But what happens here is that aligning the image after the control
>>> point generation hangs ... and even more: I cannot operate hugin
>>> anymore, e.g. press the cancel button. No reaction at all.
>> Exactly, that's what I have as well.
> Are you going to file a bug report ?
I did
https://sourceforge.net/tracker/index.php?func=detail&aid=1922119&group_id=77506&atid=550441
Cheers
Simon