Am Dienstag, 31. Oktober 2017 07:52:15 UTC+1 schrieb [email protected]: > > The cpfind command costs about 90s in hugin version 2017.0.0, but only > costs about 30s in hugin version 2016.2.0 > > I see the changed about cpfind in 2017 release notes, should I change my > command arguments or maybe is it a performance bug? > > The changes in 2017.0 should only affect some pre-processing. I can't imaging that this changes do increase the processing time in this extend. You have not mentioned your os and if you compiled Hugin itself or using a packaged version. First thing to check if Hugin/cpfind is compiled with OpenMP support: Add -v to cpfind command line. It should print something like: Hugin's cpfind Pre-Release 2017.1.0.03aad827e9f9 built by Thomas based on Pan-o-matic by Anael Orlinski Input file : demo.pto Output file : demo2.pto Number of threads : 4 <-- the number here should be bigger than 1
Input image options Downscale to half-size : yes Sieve 1 Options <snip> Also your pto file contains some strange settings: a FOV of 357.4 is very big, also for a fisheye. Also the lens distortion parameter a very high (a1.2 b-2.5 c0.46), probably to tweak the wrong fov. Thomas PS: Please post only once. A second, identical post is not necessary. -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/9054eaf4-8db7-45e9-ae2a-be48ead0a932%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
