Hugin doesn't return the offset pixels values

70 views
Skip to first unread message

João Pedro Carvalho

unread,
Sep 3, 2019, 12:56:30 PM9/3/19
to hugin and other free panoramic software
Hello,

See the next lines:

# image lines
#-hugin  cropFactor=1
i w1200 h880 f0 v47.2000007629395 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p0 y0 TrX0 TrY0 TrZ0 Tpy0 Tpp0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0  Vm5 n"1.png"
#-hugin  cropFactor=1
i w1200 h880 f0 v47.2000007629395 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p0 y0 TrX-0.121819009948815 TrY-0.0529604267434427 TrZ-0.00222984674391696 Tpy0 Tpp0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0  Vm5 n"2.png"

It is possible to have the x and y offset values (in pixels) giving the Trx, try and trz? 

T. Modes

unread,
Sep 4, 2019, 10:51:57 AM9/4/19
to hugin and other free panoramic software
Am Dienstag, 3. September 2019 18:56:30 UTC+2 schrieb João Pedro Carvalho:

It is possible to have the x and y offset values (in pixels) giving the Trx, try and trz? 

No, this is not possible. Tr[xyz] don't describe a simple translation in 2D. Instead they describe a 3D translation of the camera (which can also be rotated), which does not translate into a simple offset.

João Pedro Carvalho

unread,
Sep 4, 2019, 11:03:52 AM9/4/19
to hugin and other free panoramic software
Thank you for your answer. But when I run hugin executer, it gives me an ouput image ( with these two images) and I can see the offset between them. I know that the image could be rotated but it is also has a x / y offsets too. Do you know a solution to have these parameters?

T. Modes

unread,
Sep 4, 2019, 12:23:46 PM9/4/19
to hugin and other free panoramic software


Am Mittwoch, 4. September 2019 17:03:52 UTC+2 schrieb João Pedro Carvalho:
Thank you for your answer. But when I run hugin executer, it gives me an ouput image ( with these two images) and I can see the offset between them. I know that the image could be rotated but it is also has a x / y offsets too. Do you know a solution to have these parameters?

Hugin calculates the non-linear transformation for each pixel separately. So there is no fixed offset and therefore can't be calculated.

João Pedro Carvalho

unread,
Sep 11, 2019, 11:02:27 AM9/11/19
to hugin and other free panoramic software
Thanks again for the answer. However is not possible to to have a Rectangle to tell us the limits x and y?

Jens Scheidtmann

unread,
Sep 13, 2019, 12:36:06 PM9/13/19
to hugi...@googlegroups.com
Hello Joao,

may be you describe what the problem is, that you want to solve with
those values. Please also give some context.

Jens


Am Mi., 11. Sept. 2019 um 17:02 Uhr schrieb João Pedro Carvalho
<jpl.ca...@campus.fct.unl.pt>:
> --
> 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 hugin-ptx+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/c93456cf-aae6-4f8f-86b1-ba2c167ca16b%40googlegroups.com.

João Pedro Carvalho

unread,
Sep 13, 2019, 12:39:28 PM9/13/19
to hugin and other free panoramic software
Hello,

I just want to know the x and y limits of the second image in relation to the firt image, i.e. The max and min x y pixels values when the second image is rotated, transladed and scaled

João Pedro Carvalho

unread,
Sep 18, 2019, 3:55:42 PM9/18/19
to hugin and other free panoramic software
Hello, 

I already could find a solution and now I can find the x and y limits. Thanks again!
Reply all
Reply to author
Forward
0 new messages