Message from discussion
PTGui 9.1.3 Fails to Level Horizon
Received: by 10.58.151.15 with SMTP id um15mr3140965veb.26.1352121620094;
Mon, 05 Nov 2012 05:20:20 -0800 (PST)
X-BeenThere: ptgui@googlegroups.com
Received: by 10.52.16.79 with SMTP id e15ls5253382vdd.6.gmail; Mon, 05 Nov
2012 05:20:18 -0800 (PST)
Received: by 10.52.34.205 with SMTP id b13mr1273310vdj.3.1352121618132;
Mon, 05 Nov 2012 05:20:18 -0800 (PST)
Date: Mon, 5 Nov 2012 05:20:17 -0800 (PST)
From: AlanWB <a.j.wh...@blueyonder.co.uk>
To: ptgui@googlegroups.com
Message-Id: <60e73f40-54eb-4336-8f13-773aeaf1087c@googlegroups.com>
In-Reply-To: <2e0929b1-7187-4d9a-9fb1-82090ff8d12d@k21g2000vbj.googlegroups.com>
References: <ced652a0-5e2b-497f-9b30-391bc09989ee@googlegroups.com>
<acf52662-e4ad-4211-8934-5275589ff445@googlegroups.com> <75BAF1C2-A352-4A1C-A6BF-92250755468A@ptgui.com>
<f7951ccb-1840-43ee-bea8-aaae4df97b9a@googlegroups.com> <5096D168.8050802@gmx.de>
<577539be-72c6-453f-aca7-610598f1eadc@googlegroups.com>
<2e0929b1-7187-4d9a-9fb1-82090ff8d12d@k21g2000vbj.googlegroups.com>
Subject: Re: PTGui 9.1.3 Fails to Level Horizon
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_690_33059543.1352121617699"
------=_Part_690_33059543.1352121617699
Content-Type: multipart/alternative;
boundary="----=_Part_691_3916516.1352121617700"
------=_Part_691_3916516.1352121617700
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
John,
Many thanks to you, Erik, Mathew, et al. Success!
I have tried the various techniques you suggested and I am now confident
that I can fix saggy horizons in future. (And avoid the pitfalls in the
field that make it difficult.)
Alan W
On Monday, 5 November 2012 08:45:25 UTC, John Houghton wrote:
>
> On Nov 4, 9:14 pm, AlanWB <a.j.wh...@blueyonder.co.uk> wrote:
> > Erik,
> >
> > Thanks for the advice about parallax.
> >
> > I tried to repeat your procedure, but I still got a saggy panorama.
>
> Mostly doing the same as Erik, I levelled the panorama with horizontal
> line control points. I also deleted image 1, which is more-or-less
> identical to image 0. I have uploaded my project file and stitched
> image at:
>
> http://www.ge.tt/5YbEbxQ/v/0?c
>
> Panorama blending is compromised by variations in exposure and white
> balance, and also by the effects of parallax. Auto exposure and white
> balance camera settings should be avoided, and as already mentioned, a
> panorama head is also recommended. I output a PSD layered file and
> after some manual image adjustements used the auto blend option in
> Photoshop for the result included in my upload.
>
> John
>
------=_Part_691_3916516.1352121617700
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
John,<br><br>Many thanks to you, Erik, Mathew, et al. Success! <br><br>I have tried the various techniques you suggested and I am now confident that I can fix saggy horizons in future. (And avoid the pitfalls in the field that make it difficult.) <br><br>Alan W<br><br>On Monday, 5 November 2012 08:45:25 UTC, John Houghton wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">On Nov 4, 9:14 pm, AlanWB <<a>a.j.wh...@blueyonder.co.uk</a>> wrote:
<br>> Erik,
<br>>
<br>> Thanks for the advice about parallax.
<br>>
<br>> I tried to repeat your procedure, but I still got a saggy panorama.
<br>
<br>Mostly doing the same as Erik, I levelled the panorama with horizontal
<br>line control points. I also deleted image 1, which is more-or-less
<br>identical to image 0. I have uploaded my project file and stitched
<br>image at:
<br>
<br><a href="http://www.ge.tt/5YbEbxQ/v/0?c" target="_blank">http://www.ge.tt/5YbEbxQ/v/0?c</a>
<br>
<br>Panorama blending is compromised by variations in exposure and white
<br>balance, and also by the effects of parallax. Auto exposure and white
<br>balance camera settings should be avoided, and as already mentioned, a
<br>panorama head is also recommended. I output a PSD layered file and
<br>after some manual image adjustements used the auto blend option in
<br>Photoshop for the result included in my upload.
<br>
<br>John
<br></blockquote>
------=_Part_691_3916516.1352121617700--
------=_Part_690_33059543.1352121617699--