Control points are not generated reliably

Bug #1629667 reported by Michael von Glasow
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Hugin
Invalid
Undecided
Unassigned

Bug Description

I am trying to generate control points for a stack of images (which I intend to process into a time-lapse sequence). All images were taken from the same position (save for some camera shake) at intervals between 1 and 4 seconds, thus there are plenty of control point candidates.

I import them (using the Advanced interface) and select a batch of 120 consecutive images (as I get an error about to many arguments being supplied when the number of images approaches 127), then I generate control points.

When I examine the control points, I notice that sporadically there are pairs of consecutive images that do not have any control points between them. I have to go back to the first tab, select those two images separately, then regenerate the control points again (with the same settings as before). After that, the control points are there.

This has happened on every sequence I have processed so far. In 120 images, I usually have around a dozen image pairs without control points. Since explicitly regenerating control points works, the images are similar enough for Hugin to recognize similar features in them. It looks like the script which generates the control points occasionally skips some of the images it iterates over.

I use the "Align image stack" script to create control points. The Hugin version is 2015.0.0.cdefc6e53a58, as supplied with Ubuntu 16.04 LTS.

A full description of the procedure I follow is at http://photo.stackexchange.com/questions/83155/how-to-align-a-stack-of-images-for-a-timelapse-with-foss-tools/83156#83156.

Revision history for this message
Michael von Glasow (michael-vonglasow) wrote :

Looking at another project with the same issues, I see that image #0 shares no control points with #1, but it does share some with #6 and #11. It appears that the order of images gets messed up as they are passed to, or processed by, the feature matching script.

Revision history for this message
Michael von Glasow (michael-vonglasow) wrote :

... and #6/#7 as well as #10/#11 don't share any control points either.

Revision history for this message
tmodes (tmodes) wrote :

For this use case add --use-given-order to the call of align_image_stack.
By default images will be sorted by exposure values.

Changed in hugin:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.