[email protected] schrieb am Freitag, 29. Januar 2021 um 18:58:39 UTC+1:
> El viernes, 29 de enero de 2021 a las 17:27:33 UTC+1, T. Modes escribió: > >> >> >> [email protected] schrieb am Freitag, 29. Januar 2021 um 13:38:51 >> UTC+1: >> >>> I'm finding too slow the process (40+ mins each panorama), specifically >>> the autooptimiser part. I was wondering if there is any way of make this >>> tool to take advantage of the GPU power or maybe antoher kind of >>> optmization in my workflow. >> >> >> Run cpclean before autooptimiser to remove unlikely cp which will confuse >> the optimiser. (with other words skip step 4). >> > > Then I will not improve the quality of the stitch. I run the cpclean > aiming to clean the outliers control points, if I run autooptimiser twice > nothing happens and I will get and unacceptable average distance between > control points. > I said skip the first autooptimiser call (step 4 in your list), not cpclean. So the sequence is cpfind - cpclean - autooptimiser - … -- 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/55527689-a4c5-4df6-b772-4cadaccc285an%40googlegroups.com.
