Harry, The Fisheye lens that I use is an old "manual everything" lens mounted on the Canon DSLR via an M42 -->EOS adapter ... it provides no data to the camera. Hence the focal length and aperture numbers are blank.
However when I load the images I use the "load lens data" button shown in your dialogue to load the following data: Lens Type: "Full-Frame FishEye" HFOV: 83.85 Focal Length: 16.4 Focal Length Multiplier: 1 This is the lens/camera/EXIF data that Hugin and I have worked with for the last four years. I have spent the evening trying to find a way of changing the EXIF data, but so far none of the software available to me allows me to change it. I tried Apple Aperture (my primary image processing program), Adobe Photoshop (admittedly an old version), Graphic Converter and Reveal (a program specifically for viewing and editing EXIF data). None of them will allow me to change the entry for focal length of the lens. Did something else change in this version of Hugin to cause it to use the EXIF data rather than the Lens-data loaded from the .ini file? all the best George On Sep 22, 8:12 pm, Harry van der Wolf <[email protected]> wrote: > Hi George, > > 2011/9/22 grow <[email protected]> > > > > I tried again with 8-bit TIFF files and got all the same error > > messages > > > I googled the error message and found that in other contexts it is > > described as > > " an exception thrown by the libTIFF [when] it does not like the > > layout of your IPTC profile." > > > So then I tried it with a set of JPEGS and the error messages did not > > appear but the control point search still ends in: > > "Failed to execute ...cpfind". > > > I tried all the top images from the exposure-stacks and I tried the > > whole of a stack the result was the same in each case. > > > George > > I do get the same message. It's not an error though but a warning. Somehow > the tiff library can't read the IPTC data, maybe because of the copyright > sign in the data, which might mean that the tiff library is not unicode, but > that's a guess. > Next to that there is another issue with the images: they are lacking a > focal length value. > If I open your tiff images in OSX's preview I can't find a focal length > either. That's the issue, I think. In Hugin the images are nicely read as > such, but the iptc data can't be used and the same is valid for cpfind. > > Then the issue of your cpfind error in the end of the run. > In the assistant I get the question as displayed in the attached image. I > have to quess a FOV (50 degrees, not so important) and select a lens type. > In manual workflow I need to select the lens type in "Camera and Lens". I > selected Circular Fisheye. When I select or leave it to "normal > (rectilinear)" (default) I get erroneous results. I do not get the cpfind > error but the results are horrible. > > So my remark/question: > - please confirm (or not) that Hugin in your case can't "recognise" the FOV > either. > - Did you select "circular Fisheye" (or whatever fisheye you use)? > > Hoi, > Harry > > assistantquestion.png > 66KViewDownload -- 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
