Exclude image borders from control point generation

[Ulrich-windl]

Enhancement request: Allow `n' percent of the image at the border to be excluded from automatic control point placement, i.e.: place the control points in a centered rectangle making up `100 -n' percent of the image. Maybe for fisheye it has to be a circle, maybe it can be an ellipsoid anyway, maybe the likelihood of a control point should decrease with the distance from the image center... You get the idea...

[zarl (carl-einem)]

Have you tried working with masks and/or crop masks?

Simple exclude masks prevent control point generators from placing CPs in those areas, these masks can be copied to other images.

Cropping (available from the masks tab -> switch from "Masks" to "Crop") can be used for scans and e.g. also for images from fish eye lenses. A typical use would be to define a crop mask for a non full frame fish eye, save that to your lens database, apply that lens setting to other images in your project.

[Ulrich-windl (ulrich-windl)]

From a user's point of view, it's much easier to say "exclude 10%" of the image at the borders rather than to draw some mask on every image.
Maybe even the border tuning could be automated depending on the overlap of each pair of images.

>>> zarl <email address hidden> schrieb am 20.10.2016 um 09:19 in Nachricht
<email address hidden>:
> Have you tried working with masks and/or crop masks?
>
> Simple exclude masks prevent control point generators from placing CPs
> in those areas, these masks can be copied to other images.
>
> Cropping (available from the masks tab -> switch from "Masks" to "Crop")
> can be used for scans and e.g. also for images from fish eye lenses. A
> typical use would be to define a crop mask for a non full frame fish
> eye, save that to your lens database, apply that lens setting to other
> images in your project.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1635132
>
> Title:
> Exclude image borders from control point generation
>
> Status in Hugin:
> New
>
> Bug description:
> Enhancement request: Allow `n' percent of the image at the border to
> be excluded from automatic control point placement, i.e.: place the
> control points in a centered rectangle making up `100 -n' percent of
> the image. Maybe for fisheye it has to be a circle, maybe it can be an
> ellipsoid anyway, maybe the likelihood of a control point should
> decrease with the distance from the image center... You get the
> idea...
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hugin/+bug/1635132/+subscriptions

[zarl (carl-einem)]

Sorry, "...it's much easier to say 'exclude 10%'..." won't work since Hugin doesn't understand your voice. SCNR, this reminded me of a Star Treck movie: https://youtu.be/hShY6xZWVGE

Your personal wish to exclude 10% of each image isn't what all other Hugin users want or need. But Hugin has a solution.

A convenient way to save personal workflow preferences is to store values in a lens .ini file and apply that on your projects.

Please make yourself comfortable with http://wiki.panotools.org/Hugin_Mask_tab#Cropping_images which also includes a description about how to save and apply crop values.

The .ini file can store values like lens type (projection), a/b/c from your own calibration, crop mask, and other values. When you load lens data from such a file to one file alone Hugin asks you if you want to apply that to all other files of the same lens number. Easy, just try it out.

Also you can edit .ini files with a standard ascii text editor (I think on Windows notepad++ works great)

[tmodes (tmodes)]

Crop or mask are already there for special cases. Often there are only small overlaps. When then ignore more parts of the images, no cp will be found.
Also during cp generation the overlap is unknown. So it is impossible to take x % of the overlap.
So closing here.