> On 19 Aug 2019, at 17:44, T. Modes <[email protected]> wrote: > > HHugin assigns different lenses, if the images are shoot at different focal > length (as indicated by EXIF data)
They are not. > or have different image dimension. They may have. If at all, usually +/-1 pixels > In both cases, forcing the the same lens introduce additional errors. So > better fix your input instead. Good information. Since I will have to do that anyway, I can at the same time ensure that the pixel dimensions are even numbers, as "AKS-Gmail-IMAP" suggested. Oooohhh, I need a script! > Create CPs using cpfind + celeste (I still find CPs that seem totally random, > in the middle of nowhere) > Menu>Edit>Fine-tune all Points > Cpfind finds control points by using a multi-scale approach. So the detected > cps can include information from different scales. If you simply fine-tune > all cp you destroy this (valuable) information. (Fine-tune works always on > the same (1:1) scale). So no need to stubborn fine-tune all points. OK, let's skip that one as well. But I rely on the correlation coefficient to weed out less successful CP pairs. I will have to find an alternative approach to that one. > But I agree that the fact that it still mixes distances and correlations in > the same column – even at the same time – is not really very elegant. > You must be using a different version. Latest Mac build. The latest Mac build is perhaps not based on the latest Linux build? When displaying all CPs, I get one – 1 – Normal CP (not a line) which is a number > 1.0 Vegard Brenna [email protected] -- 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/8007B953-D379-4614-AE6C-D089A2A1778A%40online.no.
