I think it's worth adding a few points to follow up my previous post. The problem with my own Moto G3 mobile phone seems to be that its camera produces an Exif file that contains enough to suppress the 'Camera and Lens data' window that is shown on first loading images with no Exif file, but not enough to allow the real field of view to be determined. Specifically, I suspect that it lacks information on the focal-plane resolution that is needed to allow the sensor size in pixels to be converted into linear dimensions in say millimetres. Under those circumstances Hugin apparently uses the focal length from the Exif file (3.64 mm in my case) and applies a default crop factor of 1. That does indeed yield the field of view of 156 degrees I met and which is so unhelpfully large that it suppresses the finding of any control points at all.
I have some sympathy with the comment from Greg 'groggy' Lehey (Thu 02 Feb 2017 at 07:26:04) that 'there still seems to be something missing'. The main thing missing is an Exif file for the original photos. Perhaps there was one, but Adam stripped it out, possibly because it contained confidential information about, say, location. If it had contained only partial information, he might well have found Hugin's CPfind utility failed to find any control points. After all, that is what happened to me and is why, in the absence of anything more definite to the contrary, I am prepared to take Adam's subject-line 'CPfind creates few or no control points' literally. One would then have to assume that he never loaded the Exif-free versions into Hugin, because, if he had, he would have met the 'Camera and Lens data' window. Just cancelling it without entering anything is enough to get the control-point finder off the ground, because Hugin - in the cases I tried - allotted the images what I take to be its ultimate default, a field-of-view of 50 degrees. Or you could press Escape to close the window and simply create a few control points by hand to give Hugin something to work on. Roger Broadie ======================================== Message Received: Feb 01 2017, 07:35 PM From: "Roger Broadie" To: hugin-ptx@googlegroups.com Cc: Subject: RE: [hugin-ptx] CPfind creates few or no control points Adam, Well, well: one lives and learns. I have stitched a number of perfectly satisfactory panoramas using photos from my rather basic mobile phone, though, I admit, with the aid of Ptgui rather than Hugin. I therefore assumed that Hugin would work similarly. In fact I hit just the problem you did, with Cpfind failing to discover any control points, or, in one case, a tight cluster that did not permit a satisfactory stitch. A little playing suggested that the problem was that Cpfind (and probably, I guess, other cp detectors) needed at least a rough idea of the field of view to discover a useful set of control points. In the case of my phone (a Moto G3) there was Exif information that the focal length was 3.64 mm, but nothing to allow that to be turned into a field of view. On some basis or other, Hugin assigned a fov of 156 degrees, which is absurdly large. When I substituted 65 degrees, which is the approximate fov for a full set of lens parameters a-e, Cpfind produced a set of control points that allowed the stitch to proceed. In your case there is, as far as I can see, no Exif information in the images you attached and one is presented with a screen to enter lens information. I put in 60 degrees and got 25 control points. With a little work to refine the control points and lens parameters I got the attached stitch (reduced-size version) and pto file. The optimised lens parameters suggest that 65 degrees might be a better starting value for the field of view. I too am using Hugin 2016.2 on 64-bit Windows 10. Roger Broadie ======================================== Message Received: Feb 01 2017, 10:19 AM From: "Adam Kimber" To: "hugin and other free panoramic software" Cc: Subject: [hugin-ptx] CPfind creates few or no control points Hi. I have been attempting to get Hugin to stitch photos from my camera phone for a couple of years with little or no results. I kept thinking it was some bug and it would be fixed in the next version. However maybe I am doing something wrong. I am not sure what though. I also get errors on some of the options on control point finders. I am running 2016.2.0 on Windows 10 x64. Many thanks for your time Adam [ nostitch.jpg (135.4 Kb) ] [ nostitch2.jpg (141.3 Kb) ] [ hugin.jpg (55.0 Kb) ] [ DSC_2940.JPG (1270.4 Kb) ] [ DSC_2941.JPG (1254.3 Kb) ] [ DSC_2940-1h.jpg (822.1 Kb) ] [ DSC_2940-1.pto (14.6 Kb) ] -- 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 hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/6923136.6591486312595166.JavaMail.www%40wwinf3715. For more options, visit https://groups.google.com/d/optout.
