[Last post had wrong command copy .. retry...]
Many thanks for that. Making progress :-). My script generates the correct commands, I think: pto_gen -o project.pto p*.jpg pto_var "--set=y=(floor(i/6)*13.5719189)-20.3578783,p=25.5922968-(i%6)*10.2369187" --output=project.pto project.pto cpfind --output=project.pto --prealigned project.pto geocpset --output=project.pto project.pto but the cpfind command gives the following errors (varies according to the run): i0 : Analyzing image... i1 : Analyzing image... i2 : Analyzing image... i3 : Analyzing image... i4 : Analyzing image... i5 : Analyzing image... i6 : Analyzing image... i7 : Analyzing image... An error happened while loading image : caught exception: bad allocation i8 : Analyzing image... An error happened while loading image : caught exception: bad allocation i9 : Analyzing image... An error happened while loading image : caught exception: bad allocation i10 : Analyzing image... An error happened while loading image : caught exception: bad allocation [more of the same deleted] The geocpset command seems to work, but when I then open the .pto file in Hugin there are severe stitching errors -- presumably only the geometrical control points are being used. This is on Windows 64 with 16GB of RAM (free RAM typically 10-12GB). Any ideas? Mike -- 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/bff7d13c-1e19-4cb8-9e9d-db0a10da9a45%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
