Kay,
Thanks as always!

Comments interspersed..........


On 29/01/12 17:02, kfj wrote:
On 29 Jan., 14:07, Doug<[email protected]>  wrote:

Meanwhile I've tried a last resort, chickening out of doing
everything at once, and settled for fusing each stack as an
individual hugin session (having removed sky points) -
obviously not very practical if I'd had a lot of stacks
instead of only six! -  and then running a separate session
to blend the fused images together. That finally produced a
decent result.

This does indicate that you had interstack control points between more
than only one image per stack. Maybe you'll have to doublecheck on
your use of the control point generator parameters in your settings,
as explained in the help (quote from hugin help on Hugin Parameters
for Control Point Detectors dialog):

If I remember rightly CPfind did produce some extra interstack control points. But I deleted them all in order to set manual control points.



"Panorama with stacks

This setting is intended for panoramas with stacks. In the first step
it selects the image with the median exposure of every stack. Then it
tries to match these median exposed images. After this step all image
stacks should be connected.


I think I could have run into trouble with this as you mention in your next post:

 "But if you use align_image_stack, it
assumes that the median exposure is in the middle (I tried with 3-shot brackets), and if it isn't it wil not deliver it's optimal result"

.................My median image was always the first one in the stack

Then it tries to connect the images of every stack by using the
program given under Detector for stacks.

When your panorama does not contain stacks, it's does the same as All
images at once."

Creating a panorama from fused stacks does nothing other than first
fusing the stacks and then stitching the fused stacks together.

Five of the six stacks fused individually as simple
panoramas without problems, but the sixth - on the
right-hand edge of the picture, much to my surprise, as I
would have expected the problem to lie with the middle
stack(s) - took quite a bit of effort to bring it into good
register. I had to unlink the images, set each image a new
lens, and optimise for y,p,r,X,Y,Z and v (having tried
optimising fewer parameters first unsatisfactorily).

As you see, the possibilities are endless... hugin is a complex tool
and takes a while to get to know - and it does have odd and annoying
quirks as well. But if you get it to do what you want done, the
results are often very good.

The three bracketing images would have been taken within a
fraction of a second of one another, seeing that the camera
was set to AEB and continuous shooting, so I can't imagine
what would have been able to go wrong in such a brief interval!

Think of how you can easily spoil an exposure by shaking the camera in
as little as 1/10 of a second.

  Kay

How right you are!!

Doug


--
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

Reply via email to