bugbear wrote:
T. Modes wrote:
Thanks for stripping down. That makes debugging a lot easier.
I found the issue and fixed in changeset daffca65ed45. It was an issue with the
translation parameters and the center pano horizontal function, so on the first
look total unrelated to the the photometric optimizer.
Looks like my project is throwing up several bugs - I must be doing something
unusual.
Many thanks for this (and previous) bug fixes.
The new version definitely fixed my reported bug.
However, I have a more general difficulty.
In my large panorama (173 images), after exposure and colour optimisation
I still have a severe, localised, discontinuity in tone/colour.
And yet, if I use the preview to select ONLY those two images,
and optimise, they match each other nicely.
Now, my data has at least one property which
exposure optimisation may well not handle nicely.
My image were captured as a mosaic using a moving
tripod, which cast a shadow in a different place
on the subject at each instance. Many areas of the pano
do indeed have different pixel value on different sub-images.
But this capture fault applies (sadly) to the whole
pano, but the particular difficulty only arises in one corner.
So - how good should I expect the result to be?
Does the exposure optimiser work like the usual
geometric optimiser, using (complex) alorithms
to minimise overall error? If so I really
would not expect what I'm seeing (unless there's a bug...).
Or is it more direction/piecemeal, matching up successive pairs?
BugBear
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/56275D6D.8050509%40papermule.co.uk.
For more options, visit https://groups.google.com/d/optout.