Keep in mind that I have not found it in the documentation and am just 
guessing by trial and error as I write this. If anyone has better thoughts, 
please speak up.

I load 3 images into a file my third image:
On Load
i w5184 h3456 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev1.52160036448132 Er1 Eb1 
r270 p0 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 
Vx=0 Vy=0  Vm5 n"W:\zoober\source\weekend B\bridge\IMG_5303.JPG"
I set control points and optimize for starting at anchor.
i w5184 h3456 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev1.52160036448132 Er1 Eb1 r-
79.5612487857035 p7.99448156318547 y109.37396929857 TrX0 TrY0 TrZ0 j0 a=0 b=
0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 
n"W:\zoober\source\weekend 
B\bridge\IMG_5303.JPG"
I optimize all.
i w5184 h3456 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev1.52160036448132 Er1 Eb1 r-
91.0853510851596 p0.839286712216139 y115.117872304818 TrX0 TrY0 TrZ0 j0 a=0 
b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 
n"W:\zoober\source\weekend 
B\bridge\IMG_5303.JPG"

Now looking at the first image.
Loaded
i w5184 h3456 f0 v105 Ra0 Rb0 Rc0 Rd0 Re0 Eev1.52160036448132 Er1 Eb1 r270 
p0 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0  Vm5 
n"W:\zoober\source\weekend 
B\bridge\IMG_5301.JPG"
optimized position, no change
i w5184 h3456 f0 v105 Ra0 Rb0 Rc0 Rd0 Re0 Eev1.52160036448132 Er1 Eb1 r270 
p0 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0  Vm5 
n"W:\zoober\source\weekend 
B\bridge\IMG_5301.JPG"
optimized all
i w5184 h3456 f0 v112.42242938554 Ra0 Rb0 Rc0 Rd0 Re0 Eev1.52160036448132 
Er1 Eb1 r270 p0 y0 TrX0 TrY0 TrZ0 j0 a0.0234907215216856 b-
0.0197428064061075 c-0.375993809538199 d-607.606164547881 e8.53622220734315 
g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0  Vm5 n"W:\zoober\source\weekend 
B\bridge\IMG_5301.JPG"

Looking around hugin I know what most of those do. I have not seen j or Vm5 
before in hugin. I am guessing that Vm5 has something to do with 
Vignetting, but I could be wrong. Just looking around I have no idea what j 
does, from looking at my pto files in the past I have a good idea that it 
has something to do with stacks, beyond that I do not know.
--------------------
Just for the heck of it I changed both anchors to the third image(2 as it 
is zero based)

Near as I can tell it added "k2" (That is the exposure anchor,I tested it) 
to the output line and changed which variables should be optimized in the v 
lines. 

--------------------
Back on the main topic I started changing the j value on the third image in 
a text editor.

j1 does nothing
>
 

>  jany# does nothing
>

j=1 stacks my third image to my second image.
>

Any thoughts on why some vars use an = and some do not?

p0 y0 TrX0 TrY0 TrZ0 j0 all equal null?
>

To my eye it appears that anyvar0 is the same as null. To test it I have 
tried deleting most of them from an image and hugin opens it just fine. If 
I save it and open with text editor again they are back.


I copy and pasted my 2nd and 3rd i lines enough times to make 10 images. I 
then played with those more extensively. I thought that I was having some 
problems in the past figuring out the target. Just editing the text file I 
get it right every time. Just set the image number that I want to link to 
and it works. No mater how the other images are linked.  If I remember 
right and was correct in what I was seeing that is not how "pto_lensstack" 
works. I was having a very hard time figuring out the correct targets for 
it.

Editing the pto file in a text editor, I can even link to an image that is 
linked to another image. When I open hugin, hugin is able to figure it out 
that all three are linked together. Then if I save it and open as text, it 
will have saved everything with the correct links instead of the chain of 
links that I set.

j does appear to be what I want. If I link j the masks work on each image, 
but each is left in their own position and can be optimized. If I put in 
the wrong number for j anything bigger than the current image and try to 
open with hugin, hugin crashes.


On Saturday, November 29, 2014 4:02:13 PM UTC-8, Tduell wrote:
>
> Hello Brandon, 
>
> [snip] 
> Cheers, 
> -- 
> Regards, 
> Terry Duell


A big thanks Terry. Mostly motivation to get me to do the work. I had not 
changed the pto  file in a text editor before that is actually a lot of 
fun. I think we have solved Question 2 and Question 3. Anyone have thoughts 
on Question 1? How does a person normally go about changing the j var from 
the command line?

 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/971dbcaa-9e21-4f4b-9283-c710fce10c48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: optimizedallplay.pto
Description: Binary data

Attachment: loaded.pto
Description: Binary data

Attachment: optimized.pto
Description: Binary data

Attachment: optimizedall.pto
Description: Binary data

Attachment: optimizedallanchor3.pto
Description: Binary data

Reply via email to