I used the expression Align stack/icpfind because that was what, if I remember correctly, Hugin showed in the windows at various points. I didn't set anything so perhaps my terminology is incorrect. I just did a clean, install of the Hugin beta and ran it with a set of images without touching any of the default preference settings or addinng anything. It was only when the default settings found very few control points with the Samyang images I added panomatic to check the beta. Panomatic found many more control points in a much shorter time. So there appears to be a problem.
According to the release notes "For the first time Hugin can be considered feature-complete. A third-party control points generator is no longer necessary. This release delivers some major new features, integrates some projects from the 2010 Google Summer of Code, and includes many general improvements." I was highlighting an issue which I thought might mean that statement was not correct and new users of Hugin could well be disappointed because of the out-of-the-box performance. On Dec 5, 3:35 pm, Harry van der Wolf <[email protected]> wrote: > 2010/11/29 namklim <[email protected]> > > > > > > > > > > > I did a clean install of the 2010.4.0-beta1 Win32 on a Pentium P4 3MHz > > running WinXP sp3. No GPU. It installed without any problems. > > > Align | Running assistant and Batch Processor Assistant > > - If either of the Assistants is cancelled the window closes but the > > align stack process continues to run. If another align is started and > > cancelled there are then two align stack processes continue to run.... > > - no minimize/maximize buttons > > > Align stack/icpfind > > - very slow for Samyang 8mm using 9 images (6 round, 1 up 2 down) > > - Align stack/icpfind only found 8 points and took about 15 min 10 sec > > to run (repeatable timing) (I tried with both fisheye and > > stereographic settings) > > - in comparison, Panomatic found 94 points (and connected all images) > > in 1 min 40 sec > > Align_image_stack is very slow as it is not properly "optimized". CPfind > itself has approximately the same speed as panomatic. > > Anyway, I don't understand why you run align_image_stack in combination with > cpfind, and not with panomatic? > > align_image_stack does something completely different from cpfind and > panomatic, either you use it with both or not at all. > > The situations where you want to run align_image_stack is when the images in > your panorama are sets of images with different exposure that you want to > align first, then (en)fusing them and then (en)blend the fused images to a > panorama. In that case you run align_image_stack before cpfind or panomatic > or autopano-sift-c. > > Harry -- 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
