On Tuye 11-Sep-2012 at 21:41 -0700, TvE wrote:
I took a hand-held test spherical pano and would really appreciate if
someone could tell me how to optimize translation in hugin on this. It's a
shot of a boring empty office cubicle, sorry...
And then I hit the same optimize position and
On Wed, 12 Sep 2012 14:41:57 +1000, TvE tvoneic...@gmail.com wrote:
I'm attaching a zip archive with the original JPG's and the four .pto
snapshots corresponding to the 4 screen shots above.
Please refrain from adding large attachments (5 MB) to mailing list
postings, it is bad etiquette.
This looks similar to an older bug with the masking code. Can you
send the .pto project so we can confirm it? (no need to send the
photos).
It's not related to the masking code. The issue with the posted
project is the use of the translation parameters. If the images go
over the 180°
I'm seeing a similar problem in 2012.0.0RC1 (2012.0.0.0fc00635e11f built
by Matthew Petroff). I'm attaching the project file.
Same issue here. Your nadir image has non-zero translation parameters.
Set the translation parameters for the nadir image to 0.
--
You received this message because
Thomas, can you clarify what you mean by go over the 180 degree border?
Do you mean that I have a panorama that covers more than 180 degrees in
some direction? Or that some images cross the nadir or the zenith point? Is
there some explanation of what the limitation of the currently chosen
On Tue 11-Sep-2012 at 11:52 -0700, TvE wrote:
Thomas, can you clarify what you mean by go over the 180 degree border?
Do you mean that I have a panorama that covers more than 180 degrees in
some direction? Or that some images cross the nadir or the zenith point?
The mosaic/translation code
On Tuesday, September 11, 2012 1:28:11 PM UTC-7, Bruno Postle wrote:
On Tue 11-Sep-2012 at 11:52 -0700, TvE wrote:
Thomas, can you clarify what you mean by go over the 180 degree border?
Do you mean that I have a panorama that covers more than 180 degrees in
some direction? Or that some
