hugin-devs team mailing list archive

[rew <679954@xxxxxxxxxxxxxxxxxx>]

I'm building a pano-head myself as well. Is the pano-head accurate
enough to do exactly 36 degrees for each image? I don't think so. So
doing the whole control-point thing is still neccesary.

If I understand things correctly, hugin will at first try to create
control points between adjacent images. That should reduce the time
required for control point generation significantly. On the other hand,
having a first-guess layout show up as you load the images would be
nice.

A "wishlist item" from myself would be that images are always loaded
with a progressing "pitch", again leading to a slightly more
"reasonable" initial layout....

** Changed in: hugin
   Importance: Undecided => Wishlist

** Changed in: hugin
       Status: New => Triaged

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

Title:
  Mass aligning feature

Status in Hugin - Panorama Tools GUI:
  Triaged

Bug description:
  With panoramic heads, there can be no needs to generate control point.
You usually just need to adjust the image by the given degree steps you used.

This means setting a given angle.
and setting for each picture you want to align a variation based on the angle.

eg: let's suppose the angle is 36° and you did a 360 panorama.

you'll need to align 10 pictures.
so you need to set each image to 36 72 108 144 (...) or -36 -72 -108 -144 (...), depending the spin you used to take the images.

So imo, what is needed:
An angle to use: (can be a positive or negative number.) eg +36 or -36 (°) for each basic parameters (I am thinking to yaw pitch and roll which can be different depending the pano head and camera used).

A button to increment the position of all the selected images by a numerical sequence, so each selected image gets an increment change corresponding to its position in the selection. The first one would get +36, the second +72 in the example.

I don't know if one button and a parameter to play with (yaw / pitch / roll) would be enough or if we need 3 mini buttons somewhere in the interface.

esby