hugin-devs team mailing list archive

[Vladimir Nadvornik <1238673@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I am testing hugin 2013.0.0_rc2 with exiv2 0.23.

On an Image from compact camera canon s95 hugin reads the lens name as "(65535)" and the lensfun lookup fails.
Changing lens name to empty string helps. This is a problem for fully automatic workflow, for example with 
pto_gen --distortion.

The value comes from Exiv2::lensName print method called at
SrcPanoImage.cpp:400

As a workaround I added the lens name "(65535)" to the lensfun database.

I wonder if it can be handled better in hugin, for example by ignoring
lens names like "(65535)" or by repeating the lookup with empty lens
name in SrcPanoImage::readDistortionFromDB and in other methods.

** Affects: hugin
     Importance: Undecided
         Status: New

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

Title:
  lensfun lookup of canon s95

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  I am testing hugin 2013.0.0_rc2 with exiv2 0.23.

  On an Image from compact camera canon s95 hugin reads the lens name as "(65535)" and the lensfun lookup fails.
  Changing lens name to empty string helps. This is a problem for fully automatic workflow, for example with 
  pto_gen --distortion.

  The value comes from Exiv2::lensName print method called at
  SrcPanoImage.cpp:400

  As a workaround I added the lens name "(65535)" to the lensfun
  database.

  I wonder if it can be handled better in hugin, for example by ignoring
  lens names like "(65535)" or by repeating the lookup with empty lens
  name in SrcPanoImage::readDistortionFromDB and in other methods.

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