Re: Fusing before or after

Harry van der Wolf wrote:
> I also fuse first

+1 most of the time, but not all the time.

> As an addition to what Gerry said about hand-held images: You can use
> align_image_stack to perfectly align your bracketed photos before fusing
> them. The better fusing gui's come with align_image_stack and do support
> that.

my wish is to eventually have a "composing GUI" to deal with the
"sequence of images" - whatever that sequence is.

constrains and actions are boxes of different sizes, that the user can
drag and drop on the working surface; and that smart logic can auto-create.

actions are things like:
- determine CP
- add masks
- blend / fuse
- optimize position in space
- manual edit of individual parameters
- remap
- forks (to have mutliple processing, e.g. for different outputs from
the same project)

constraints are things like:
- defining which images belong to a bracket and what type of bracket it is
- which images share the same set of parameters
- areas/mask of an image not to be considered for CP generation
- areas/mask fo an image that *must* be preserved or *must* be hidden


a GUI to move around and connect the boxes with a little bit of logic to
make sense of the connections (e.g. don't blend a single image or don't
enfuse images with same EV) sort of like a syntax checker before a
controller engine starts the different tools in the appropriate order
and with the appropriate parameters.

Ideally the interface between the GUI and the controller engine would be
an XML file, although if the GUI understands the Makefile format it
could create a Makefile directly, but that would make the Makefile part
of the project and I am not sure how it will affect the projects in
terms of portability to a different box? rather go safe, describe it in
an XML and have an XML to MakeFile thing...

Yuv