On Mon 06-Dec-2010 at 01:09 -0800, kfj wrote:
On 5 Dez., 21:40, Yuval Levy <[email protected]> wrote:
not really. Thomas has shown that with good design you can have the best of
both world, e.g. cpfind and celeste. They started life as separate tools and
you can use them both as separate tools and within the GUI process.
This makes me curious. Are you saying that cpfind and celeste are
closer integrated than just being separate processes executed by hugin
to do their bit and then deliver back a result?
cpfind now links directly to libceleste and uses it to mask out
areas of photos containing clouds before control-point generation.
Previously with autopano-sift-c we had to wait for control-points to
be generated, and then remove points from clouds with celeste - The
result could theoretically be zero control-points.
It seems to me that enblend could only produce seam data by opening
all the (nona-warped) files, calculating where it would put the seams,
and then maybe produce some output it could pass back to hugin so
hugin could show where the seams are
An alternative would be to turn off enblend mask optimisation
altogether, in which case Hugin could predict the location of seams.
Now that we have masking in the Hugin GUI this is a viable workflow,
though I'm not sure I would want it to be the default.
Note that ptgui doesn't have mask optimisation at all, since it
decomposes the image pyramid before remapping and has no opportunity
to compare overlapping photos.
--
Bruno
--
You received this message because you are subscribed to the Google Groups "Hugin and
other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
