Hello John,
On Tue, 26 Jan 2016 20:52:21 +1100, panostar <[email protected]>
wrote:
On Monday, January 25, 2016 at 10:15:12 PM UTC, Tduell wrote:
Hello All,
I recently helped a PTGui user who was having trouble getting a good
stitch from his project images.
I stitched the project using Hugin-2016.0.0 beta1, and could only
describe
to him how I went about it.
It would be much clearer to him if he could load my project file.
Does anyone know if PTGui can read and make sense of Hugin's .pto files?
No, it can't. It's difficult to edit the .pto to produce a file that
PTGui
will accept, because PTGui uses a dummy image to hold global parameters.
This has the effect of altering the numbering of the actual images and
hence the image reference numbers in the control points - e.g. n0 -> n1.
One fairly easy solution which might be good enough is to create a new
PTGui project and add the images files. Then copy/paste the control
points from the .pto file into the .pts file. Then optimize. For this
to work,
you need to add an extra dummy image into the Hugin project and move it
up to the top of the lens list so that the control point image numbers
then
start at n1 instead of n0.
Thanks for that explanation.
I guess another approach is for the PTGui user to also install Hugin, then
he has the best of both worlds.
Cheers,
--
Regards,
Terry Duell
--
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/op.ybu4itb7rs0ygh%40localhost.
For more options, visit https://groups.google.com/d/optout.
