Inconsistent positioning after saving?

Asked by Erik on 2012-05-10

I am in the process of using Hugin & friends to stitch together a gigapixel sized panorama from 520 images, of which I can load roughly 100 at a given time before the process becomes unbearably slow.

I have been thoroughly confused by positioning results before and after saving/loading. When I start fresh, load up pictures, detect control points, and optimise positions starting with anchor, the system will report (after an hour spent finding and removing bad control points and re-optimizing) an rms distance between points less than /one pixel/. However, if I ever save or apparently even execute the final compositing process, the minimum achievable distance becomes several pixels, even if I wipe out all control points and for all intents and purposes start over from nothing.

Out front I will say that several pixels nearest fit for pictures taken at high zoom looking through miles of turbulent mid-day air is far more plausible than half a pixel, but then what ever led to the claim of a half-pixel fit in the first place?

Question information

English Edit question
Hugin Edit question
No assignee Edit question
Last query:
Last reply:
Launchpad Janitor (janitor) said : #1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.