hugin-devs team mailing list archive

[Bruno Postle <1239609@xxxxxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon 14-Oct-2013 at 10:30 -0000, Christopher Allen wrote:
>
>When the user knows the focal lengh and horizontal field of view (v),
>Hugin should either compute the crop factor or, if it is not otherwise
>needed, simply ignore it.
>
>Consider cylindrical panorama camera images, which have an arbitrary
>hfov unrelated to the lens and focal length, and for which 'crop factor'
>is usually not a meaningful piece of information.  At present,
>attempting to import such images is frustrating because when you enter
>the hfov hugin resets the focal length (based on irrelevant default crop
>factor of 1.0) and vice versa.  Instead, the crop factor should be
>computed automatically (if it is needed at all).

Hugin should do this calculation, however this is just a convenience 
for photographers who are more familiar with concepts like focal 
length - The only number that is actually used in the stitching 
process is the horizontal field of view (v) parameter.

You can set the crop factor to anything you like so long as the 'v' 
parameter is correct.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFSXGgIFqOhwCjyCLoRAqEIAKDSDBrSh9Dd50w1fIcQmgXNkTcQ4gCgyqiy
55PGHUlIeNokd0Ansdx382U=
=z2Gn
-----END PGP SIGNATURE-----

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

Title:
  Allow easy entry of focal length and hfov

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  When the user knows the focal lengh and horizontal field of view (v),
  Hugin should either compute the crop factor or, if it is not otherwise
  needed, simply ignore it.

  Consider cylindrical panorama camera images, which have an arbitrary
  hfov unrelated to the lens and focal length, and for which 'crop
  factor' is usually not a meaningful piece of information.  At present,
  attempting to import such images is frustrating because when you enter
  the hfov hugin resets the focal length (based on irrelevant default
  crop factor of 1.0) and vice versa.  Instead, the crop factor should
  be computed automatically (if it is needed at all).

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