[Hugin-devs] [Bug 732359] Re: use image metadata to determine crop-factor and hfov

2011-03-11 Thread tmodes
Fixed in repository. Will be included in 2011.0 beta 3.

** Changed in: hugin
   Status: New = Fix Committed

** Changed in: hugin
Milestone: None = 2011.0beta3

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

Title:
  use image metadata to determine crop-factor and hfov

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  Hi.

  Currently when I open some images in hugin, it only detects the focal length 
(by using metadata information).
  It would be nice if the same could be done, too, for the crop factor and the 
HVOF.

  I'm not sure whether these are standardised Exif-Tags or not, but some
  camera manufacturers (at least) encode this in their binary fields.

  If I take e.g. images made by my Olympus E-5 or the E-510 and do a:
  exiv2 -pt image.orf
  I don't find any tag which I'd say it's the crop factor or the HFOV.

  However:
  exiftool seems to be very well able to get these information, e.g.:
  $ exiftool P3096244.ORF | grep ^Scale Factor
  Scale Factor To 35 mm Equivalent: 2.0

  $ exiftool P3096244.ORF | grep ^Field
  Field Of View   : 65.1 deg (3.51 m)

  Actually it seems to be able to get even more data out of Olympus'
  binary fields, you should have a look at them some might be perhaps of
  use for hugin?!

  It's (especially for end-users) a pain to decide their lense type 
(rectified, etc.),.. this would AFAIU make this not longer needed.
  And the values are probably more correct (at least they differ from what 
hugin caculates if I enter just the crop factor and focal length).

  I'd suppose that the other major manufacturers have similar fields
  encoded.

  
  Cheers,
  Chris.

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 703736] Re: Hugin contains a bundled zthread-2.3.1

2011-03-11 Thread tmodes
Thanks Andreas, pushed to repository.

** Changed in: hugin
   Status: Confirmed = Fix Committed

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

Title:
  Hugin contains a bundled zthread-2.3.1

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  src/foreign/zthread is a bundled version of zthread
  http://zthread.sourceforge.net/ This is a problem with some Linux
  distributions such as Debian and fedora that have policies to not ship
  multiple versions of the same library.

  The solution would be to modify the cmake configuration to allow
  building against a system version of this library, and/or to remove
  the bundled library altogether.

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 732359] Re: use image metadata to determine crop-factor and hfov

2011-03-11 Thread Christoph Anton Mitterer
thx =)

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

Title:
  use image metadata to determine crop-factor and hfov

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  Hi.

  Currently when I open some images in hugin, it only detects the focal length 
(by using metadata information).
  It would be nice if the same could be done, too, for the crop factor and the 
HVOF.

  I'm not sure whether these are standardised Exif-Tags or not, but some
  camera manufacturers (at least) encode this in their binary fields.

  If I take e.g. images made by my Olympus E-5 or the E-510 and do a:
  exiv2 -pt image.orf
  I don't find any tag which I'd say it's the crop factor or the HFOV.

  However:
  exiftool seems to be very well able to get these information, e.g.:
  $ exiftool P3096244.ORF | grep ^Scale Factor
  Scale Factor To 35 mm Equivalent: 2.0

  $ exiftool P3096244.ORF | grep ^Field
  Field Of View   : 65.1 deg (3.51 m)

  Actually it seems to be able to get even more data out of Olympus'
  binary fields, you should have a look at them some might be perhaps of
  use for hugin?!

  It's (especially for end-users) a pain to decide their lense type 
(rectified, etc.),.. this would AFAIU make this not longer needed.
  And the values are probably more correct (at least they differ from what 
hugin caculates if I enter just the crop factor and focal length).

  I'd suppose that the other major manufacturers have similar fields
  encoded.

  
  Cheers,
  Chris.

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


Re: [Hugin-devs] [Bug 703735] Re: Hugin contains a bundled tclap-1.2.0

2011-03-11 Thread Yuv
On March 7, 2011 12:13:20 PM tmodes wrote:
 I have no experience with PPA.

The PPA is documented at http://wiki.panotools.org/Hugin_PPA in more detail 
than a developer really need to know.

From a developer perspective it is a very simple concept:  source packages are 
uploaded to a clean automated build system.  At 
https://launchpad.net/~hugin/+archive/nightly the uploads are automatic as 
well (nightlies).  In case of success there is a new nightly to install/test.  
In case of failure there is a failure log that can help debugging.  As a 
member of Hugin PPA I receive emails with links to the failed build logs.

You can see all build logs (more than 400 of them) at 
https://launchpad.net/~hugin/+archive/nightly/+builds?build_text=build_state=all


 I added a more general FindTclap.cmake.
 Please test.

The latest I received :(

http://launchpadlibrarian.net/66165728/buildlog_ubuntu-maverick-
i386.hugin_2010.5.0%2B2011.0.0%2Bhg5099-0ubuntu1~maverick_FAILEDTOBUILD.txt.gz

I'm setting up a build environment on my Natty netbook now and will try the 
attached FindTclap.cmake later.

Yuv

 status new


** Changed in: hugin
   Status: Fix Committed = New

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

Title:
  Hugin contains a bundled tclap-1.2.0

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  src/foreign/tclap is a bundled version of tclap
  http://tclap.sourceforge.net/ This is a problem with some Linux
  distributions such as Debian and fedora that have policies to not ship
  multiple versions of the same library.

  The solution would be to modify the cmake configuration to allow
  building against a system version of this library, and/or to remove
  the bundled library altogether.

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp