In short: I strongly suggest making Cpfind accept filenames and wildcards to make it usable for scripting.
Elaborated: For the last few years I've been on-off working on a big panorama project where over 60.000 individual images of mine are to be stitched into a couple of hundred panormas for a virtual tour. With this huge amount of material, a streamlined workflow becomes crucial. I have developed a tightly slimmed workflow where I develop several panoramas in parallel through my processing pipeline. I work mostly in the command prompt through batch scripts and avoid the Hugin GUI for the most part. My control point generator of choice has always been Alexandre Jenny's great old Autopano 1.03, which wins out over Autopano-SIFT in ease of use (Autopano-SIFT does not interpret wildcards, which makes usage a pain on Windows systems where the shell does not expand them for me). After upgrading my system, I've found that Autopano crashes on Windows 7 and I'm suddenly out of control point generator. The introduction of CPFind in the Hugin package is even worse from a batch-usage standpoint as it inconceivably expects a complete pre-made project file as input which would force me to handle every panorama in the GUI. As most of my images are preprocessed (including a stacking utility I developed myself), EXIF information is usually not preserved. This has never meant any trouble as Autopano doesn't need it anyway (thus I'd venture to say no control point generator or panorama stitcher should ever need it). Now having to manually add images and enter bogus lens parameters in Hugin to make CPFind work seems ridiculous. I'd wholeheartedly suggest adding an alternative method of calling CPFind by supplying images and making it process wildcards. I'm currently unsure how to get past this setback. I guess until CPfind is fixed, either I'll have to adjust to using Autopano-SIFT (and spend most of my time editing endless command lines of filenames), change to Linux or install Windows XP on a virtual machine just to get good old Autopano to work again. Any suggestions? Best regards John Eklund, Sweden -- 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
