Hi Terry, > Thanks for that info. > My only impatience, if that is how it appeared, was in trying to > understand whether it was a problem in the trunk or a local problem > with my build. > It is a bit curious that others haven't been seeing the problem. >
I commited a fix for the photometric optimization (rev. 4862). I tested with your example San-G3. When using p1020264-p1020266-4852.pto as it is (without reset) and now optimizing I'm getting similiar values for the photometric variables (Eev, vignetting, response) as in p1020264-p1020266-4742.pto. But the photometric optimization is still slower than the previous version, especially when using the default settings in the photometric tab (when using the custom parameter set it not so different regarding the speed). > I have a project that would always end up haywire prior to the > implementation of cpclean. I could only get a good result with > manually selected control points, so this project has become one of > those that I use to test any new version. > My test project is handled really well by the 2009.4.0 release > version, without any intervention on my part...just using the > assistant; this version (4852) manages to put two control points in an > unconnected pair of images. Could you provide this test project? So I could have a look to check whats going wrong in the trunk. The project file pto (after running cp generator and before cpclean) is suifficient. Also give the image pairs which share wreong cp but are not overlapping. Thomas
-- 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
