hugin-devs team mailing list archive

[Daniel Scharrer <803432@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Steps to reproduce:
- Add multiple images and control points.
- Link images into stacks. (Images tab -> Change stack...)
- Unlink some geometric properties (hfov (v), distortion (a,b,c), center shift(d,e), image shearing(g,t): Uncheck "Link" in "Camera and Lens" -> "Geometric"
- Optimize / align

Expected results:
- All images in the same stack have the same geometric properties.

Actual results:
- Each image has different properties

Additional details:
The affected properties' values are saved for each image in the .pto file, unlike yaw (y), pitch (p), roll (r), which are only saved for the first image in the stack and then liked from the other image using the y=image_index notation.
If I manually change the values to links using the v=image_index notation, Hugin loads the correct values for the images, but
a) Thinks the values are linked for the whole project, even though they were only linked for each stack.
b) When unliking the images again, optimization will not produces different values for each image in the stacks, as described above.
c) Saving the project again writes the values for each image and not the links that were there.

Hugin version: 2011.0.0.0f9fdaf56720

** 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/803432

Title:
  Geometric image attributes are not correctly linked for image stacks

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Steps to reproduce:
  - Add multiple images and control points.
  - Link images into stacks. (Images tab -> Change stack...)
  - Unlink some geometric properties (hfov (v), distortion (a,b,c), center shift(d,e), image shearing(g,t): Uncheck "Link" in "Camera and Lens" -> "Geometric"
  - Optimize / align

  Expected results:
  - All images in the same stack have the same geometric properties.

  Actual results:
  - Each image has different properties

  Additional details:
  The affected properties' values are saved for each image in the .pto file, unlike yaw (y), pitch (p), roll (r), which are only saved for the first image in the stack and then liked from the other image using the y=image_index notation.
  If I manually change the values to links using the v=image_index notation, Hugin loads the correct values for the images, but
  a) Thinks the values are linked for the whole project, even though they were only linked for each stack.
  b) When unliking the images again, optimization will not produces different values for each image in the stacks, as described above.
  c) Saving the project again writes the values for each image and not the links that were there.

  Hugin version: 2011.0.0.0f9fdaf56720

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