hugin-devs team mailing list archive

[tduell <1388469@xxxxxxxxxxxxxxxxxx>]

Hello Thomas,
I think it is fixed now...not entirely sure.
I eventually managed to delete all the records from the lens database for the offending lens, then attempted to recalibrate that lens (using hugin_calibrate_lens) , but kept getting an error when attempting to save to the database.
The lens focal length of 50mm was being detected but not the crop factor, which I was entering as 1, when I entered a crop factor of 1.0 it saved OK.
When I load images (one of which is the example image provide earlier) from that camera/lens into hugin it pops up the HFOV dialog box with the 50mm focal length entered, but it doesn't know the crop factor. I guess there is insufficient info in the exif data.
If it helps I have attached one of the calibration images which 

Cheers,
Terry


** Attachment added: "calibration image"
   https://bugs.launchpad.net/hugin/+bug/1388469/+attachment/4253192/+files/Calibrator4.jpg

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1388469

Title:
  Hugin loads images, but thinks hfov is -nan

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  Build of hugin-executor branch (6759:6d52a5552e08) on Fedora 20 x86_64.
  Select a group of 4 images which are loaded without complaint, but 'lens parameters' show hfov = -nan for all images.
  My previous hugin build (6758:624abeb108a1) could not find the hfov in the image data for these images (tiff files supplied by others) and would pop up the dialog box requesting input.  The latest build happily loads the images, maybe it finds the hfov, but then appears to store the hfov as -nan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1388469/+subscriptions