swapping input images for scaled images and project file fixup

Asked by Bob Mahar

Hugin persists the absolute rectilinear coordinates of control points and other features in its PTO files. Should there be a need to swap out the original source images with different resolution images, the project is broken and cannot be stitched. Is there a way to fix up an existing PTO, scaling the X - Y coordinates to conform to the actual size of the images as they exist at run time? Or some proper way to use scaled proxy images?

After proxy images are swapped out with larger ones, all the control points are clustered in a mass in the upper left quadrant of each images - indicating the values are not scaled in response to changes in the input images.

Part of the motivation is that Hugin control point detection does not seem to support scaling options ( like sift-autopano ), which would sidestep my issues with blurry source materials where scaling the images first help the point detector to find features by reducing the absolute blur radius.

Before I start plying hands to keyboard, I wonder if there is some tool / script that does this fixup or if there is a hidden "make it all better" button I missed.


Question information

English Edit question
Hugin Edit question
No assignee Edit question
Last query:
Last reply:
Revision history for this message
tmodes (tmodes) said :

In the Panotools-Scripts package there are ptohalve and ptodouble for such tasks.

Cpfind does scale the images by default by 50 % before running the main algorithm. This is can switch off with the --fullscale switch. So there is a scaling option in cpfind.

Can you help with this problem?

Provide an answer of your own, or ask Bob Mahar for more information if necessary.

To post a message you must log in.