my experience has been that cpfind creates a fair number of outright bad
points and a few that are just a bit off and fine-tune tends to fix all of
that fairly cleanly (where cpclean tends to miss many of these)
for reference i've been working on stitching 600dpi rectilinear scans of
newsprint sized comics, this "information from several size scales" cpfind
uses might very well be what's giving me these bad points as the size
scaling between overlapping images should always be 1:1 here
in any case i went through the effort of getting this working and figured
i'd share it for anyone else interested, even if it's considered "only for
manually set points" it could still be useful for someone to batch-tune old
projects or if they simply chose to manually set the points instead of
using cpfind
On Wednesday 15 May 2024 at 10:41:41 UTC-4 T. Modes wrote:
jak schrieb am Mittwoch, 15. Mai 2024 um 07:45:23 UTC+2:
i wanted to script it in an assistant so here it is
the fine-tune function was written at a time without automatic control
point detector in Hugin and was intended for fine-tuning manually set
control points. Therefore scripting was not intending for this function.
For automatic found control points you should not call fine tune. Fine-tune
works only at the 100 % scale. But the control points by cpfind are already
optimized and contain information from several size scales. If you
fine-tune these control points you destroy this information and so this
should be avoided.
--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/c765345a-2638-4935-8ed8-179b979a8a23n%40googlegroups.com.
