On Mon 25-Jun-2012 at 10:35 -0700, John Eklund wrote:
On Monday, June 25, 2012 8:03:13 AM UTC+2, Bruno Postle wrote:
Hugin now has a tool called pto_gen for preparing the input files for
cpfind and autopano-sift-c: http://wiki.panotools.org/Pto_gen
This does take filenames as input. If you have problems with the command
line length, you can use pto_merge to do it in steps:
http://wiki.panotools.org/Pto_merge
Thanks! Pto_gen was new to me. I assume it will be in the regular Hugin
package?
It should be in any recent snapshot since December and will be in
the 2012.0.0 release.
If nothing else maybe Hugin could include a batch script to call pto_gen
and cpfind, making it more straight-forward.
A Windows batch script for this would be welcome and can be distributed
with Hugin.
It still seems pto_gen needs an FOV number for non-EXIF files. I'm not
knowledgeable on the complex optic math but just pragmatically notice that
Autopano was fine without. :-) AFAIK that's something that can be deduced
at a later stage with control points in place?
Yes it can, but a good initial estimate will get you a better spread
of control points. With a 'normal' lens you can usually do ok
giving a FoV of 50, with any other lens it would be better to try
and estimate the actual angle.
--
Bruno
--
You received this message because you are subscribed to the Google Groups "Hugin and
other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
