Thank you. That loads and will optimize now. Based on the initial results I'm not so sure that Hugin will be able to get itself out of this state. I have a lot of manual control points that I'd rather not recreate, but may need to. Lesson learned, save the project with a new name after all changes. On Mon, 2021-12-27 at 11:35 -0800, [email protected] wrote: > Oops. I should have realized that would happen (Never before tried > to work with a .pto without images). > > Did you add control points by hand or just let the program add them > automatically? > If automatically, you have no serious value in the .pto file, so > unless this is pure learning (preparation for recovery from future > accidents) starting over might be easier. But in case you do have > value in the .pto file, here is the correction to that field of view > problem. I wouldn't bet that was my only error, but maybe: > > > On Monday, December 27, 2021 at 2:27:31 PM UTC-5 Jon Schewe wrote: > > Thank you. I tried loading it and then doing an optimization and > > just get "Field of View must be positive". The FOV has positive > > values in it, so I'm not sure what it's upset about. > > > > On Mon, 2021-12-27 at 10:43 -0800, [email protected] wrote: > > > I was curious enough (after not seeing a reply to your attached > > > .pto file from Bruno, to look up something I'd seen before but > > > forgotten.In the documentation of "i" lines in the .pto file it > > > says: > > > > > > # Parameters in different images can be linked using '=' > > > # followed by the image number starting with 0. > > > # Example 'v=0' sets horizontal field of view as > > > in# image number 0. This feature works for the > > > variables# v, a, b, c, (r, p, y with caution) d, e, g, and t > > > In your .pto file, each image other than the anchor has a line > > > like: > > > i w4608 h3456 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev3.85299770079307 > > > Er1 Eb1 r=0 p=0 y=0 TrX=0 TrY=0 TrZ=0 Tpy=0 Tpp=0 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"IMG_20210728_114219.jpg" > > > > > > > > > All those = in that line force every parameter to match the > > > parameters of the anchor image, so optimize can't optimize > > > anything. > > > Inside Hugin, I don't know how to undo all that. In a text > > > editor, it is trivial to undo (global replace of =0 with 0 in the > > > section holding all the i lines. I don't know if the result of > > > that is correct enough to get you back on track. But I'll attach > > > it in case it helps. > > > On Monday, December 27, 2021 at 10:22:19 AM UTC-5 Jon Schewe > > > wrote: > > > > On Mon, 2021-12-27 at 14:52 +0000, Bruno Postle wrote: > > > > > On Mon, 27 Dec 2021, 12:47 Jon Schewe, wrote: > > > > > > With a small experiment I managed to get into this state by > > > > > > telling Hugin to optimize X, Y, Z only for the images. It > > > > > > ran the optimize and told me that the average distance > > > > > > between all control points was zero. At this point the > > > > > > project appears to be in an unusable state. > > > > > > > > > > Maybe attach a PTO project (no need for the images), it may > > > > > be obvious what the problem is. > > > > > > > > Attached. > > > > > > > > > > > >
-- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/e62364f2babe3c960a775d5eb735c3daedaa30b8.camel%40mtu.net.
