Hullo Bruno/All, On Jan 13, 10:31 am, Bruno Postle <[email protected]> wrote:
[snip] > gigastart creates a vast number of temporary files, but these are > reused by the Makefile system, so images are only opened once for > classifying features (though looking at the code, I don't see how > gigastart would work from the Hugin GUI as it is). It does work, unless there is something else going on that I'm unaware of. I just re-ran my multi-row tutorial project using the 'Assistant' and using gigastart as the hugin detector, as defined in my earlier posting. I needed to be sure that I hadn't been imagining things, or had only gone to the preview stage or somesuch. It did the whole business, no problem, producing a nice stitched pano. My earlier impression that using gigastart this way was faster than having APSC defined as a 'multi-row' type, is probably wrong. having been through the process again I would say there is probably not much in it. > > Calling autopano-sift-c multiple times will result in a lot of > duplicated work, probably what is needed is to go back to the old > autopano-c-complete.sh script which will cache features as .key > files between runs. Arguments would be (untested as usual): > > --points %p --size 1600 --output %o %i OK. Cheers, Terry
-- 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
