On Monday, June 25, 2012 8:03:13 AM UTC+2, Bruno Postle wrote: > > cpfind doesn't take filenames on the command line in part because of > limitations if the Windows shell. > > 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? Yes the Windows shell seems to have a relatively narrow limitation on command line length but if you interpret wildcards that limitation is invisible for most users. (I'd be happy to contribute - I'm a programmer). If nothing else maybe Hugin could include a batch script to call pto_gen and cpfind, making it more straight-forward. 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? Supplying a number by hand always makes me nervous about introducing errors if I make up an initial number that's too far off reality. Can I be safe that it's still recalculated just fine regardless what I supply it? How accurate do I have to be? /John -- 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
