On Jul 23, 3:34 am, Gilles San Martin <[email protected]>
wrote:
> Bruno, your solution works if you want the last image to be used in case
> of no contrast differences. If you want an other image (from the middle
> of the stack) as reference, you have a problem with align_image_stack
> that is used before enfuse in the script.
What are you doing? What is the exact
command line you use to call Enfuse? In
particular, I'd be interested whether you use a
hard or a soft mask.
For a soft mask each pixel contributes according
to its total weight (with the "interesting"
corner case of all weights being equal to zero).
Identical weights lead to arithmetic averaging.
For a hard mask and identical weights Enfuse
prefers the first image unless all weights are
zero, where it uses a value between the minimum
and the maximum weight. See "enfuse.h" around
line 1290.
How does your problem look like such that image
order matters despite all weights being the
same?
> But it is possible I guess to
> first use align_image_stack and then rename the reference image so that
> it is placed in first position. This is however not very convenient (the
> script runs generally during 1-2 hours for each stack, during the night...)
Though I neither know where you started
from, nor where you are headed to, I'd say this
clearly sounds sub-optimal.
> Erik, your solution is really wonderful ! The transition from the sharp
> area to the out of focus area is much more natural but additionally the
> halo problems seem to be much better managed (in the few tests I made).
(1) Activating another weighting
category besides contrast weighting may break
the tie between the weights as you report above.
However, be aware that one category can
overpower another, especially if the latter is
based on faint differences.
(2) On how to attack the halo problem
with focus-stacking in Enfuse see the manual
Section 5.4 in general an Sec. 5.4.3 in
particular.
> The information is in the man page of enfuse (example section) but not
> in the enfuse reference manual (and I read only this one...) where
> example are given with 0 values for saturation and exposure .
Wow, you are the first one to publicly
confess that he actually has read the manual!
But you must have run into an old and
conceivably outdated manual page. The man pages
for versions 4.x do not feature any example
sections at all.
You'll have more fun if the documentation you
refer to matches the Enblend and Enfuse versions
you are using. For the 4.x series this is
particularly easy as both Enblend and Enfuse
know how to identify themselves with the
"--version" option:
$ ~/projects/enblend/BUILD/src/enfuse --version
enfuse 4.1-125ae50943b4
...
and the manual pages also feature a version id:
ENFUSE(1) User Commands ENFUSE(1)
NAME
enfuse - manual page for enfuse 4.1-125ae50943b4
SYNOPSIS
enfuse [options] [--output=IMAGE] INPUT...
...
BTW, for the same reasons the manuals carry
version ids, too.
> Maybe it could be useful to add this information to the wiki ?
I'd prefer to add useful information to
the official manual[s]. As I know one of the
hacker dudes who have access to the repository,
perhaps we can get that into the official
distribution.
Thank you,
Chris
--
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
