On Mar 1, 9:45 am, Felix Hagemann <[email protected]> wrote: > On 1 March 2010 14:44, Bruno Postle <[email protected]> wrote: > > > > > You need to be using the 2.5.1 release or a recent snapshot (which > > should be fixed but I haven't heard any reports of success or failure > > yet). > > Just to contribute one data point: > Using a snapshot from yesterday's trunk with fisheye images (5D + > Sigma 8mm, HFOV about 190 degrees, 4 images around with large overlap) > was giving a fairly large number of control points with acceptable > spread. So whatever issue was occuring, I haven't seen it. > > Felix And another data point: I'm using the snapshot build from Zorin from a few days ago(2010.1.0.5010). It includes Autopano-SIFT-C 2.5.2 23July2009, and I saw the same issue. I looked at the Control Points Detectors tab and the Autopano-SIFT-C configuration, and found extra arguments compared to Hugin 0.7. I took them out, and it started working. Precisely, I changed: --maxmatches %p --projection %f,%v %o %i to: --maxmatches %p %o %i and it started giving me many more matches.
I'm not familiar with the problems that Autopano had - does changing these arguments actually fix the problem? Or do I still have a problem that's less obvious? Thanks, Aron -- 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
