[ptx] Comments&questions

[J. Schneider]

Mike Runge wrote:

>>If I'm not wrong in PTGUI it is possible to place two points in the same >image
>>for vert/horiz line, while in hugin they can't.
> 
> Just create 2 points in the same image 

(Maybe we should add: ... by selecting the same image in the two image 
panes and placing one point of the pair in each pane.)
> ... - it will automatically be
> interpreted as "horizontal" or "vertical". You can manually change
> that as well (control points tab, mode)


> The last thing: what is the best stitcher? PTStitcher or nona? and the
> best
> autopano? kolor/sift/autopano/panosifter?
> 
> Depends on waht you're doing. I have godd experiences with both -
> PTStitcher and nona. I actually have some trouble with nona stitching
> full sphaericals, so I use PTStitcher for that.
And there is one more thing: PTStitcher has a "morph to fit" switch 
(-o), which is helpful in badly shot freehand panoramas. But hugin does 
not support this switch in the GUI, you have to set it manually in the 
script.
(BTW: Hugin doesn't even save the -o in the project file. Maybe at least 
this should be fixed.)

>>I also think that including in hugin a viewer for the final image possibly
>>including a built-in cropper for the black borders would be very useful...
> 
> It's there (preview) and it's good and fast. If you see to mach
> borders, try adjusting the field of view and the yaw of the anchor
> image. Except for very asymetrical panoramas this will help to minimize
> the black borders.

viewer:
I think it would not be a bad idea to add an option to open the 
resulting image in the associated or in a specified viewer. I guess this 
would not be too complicated to implement. The preview with its limited 
size/magnification does not replace seeing the final result.

crop:
The hint about adjusting the fov is correct of course. But hugin 
optimizes the fov in a way so that no image content is cropped (which is 
good as a default - though an option "leave no black edge" as an 
alternative m ode for fov computation would not be bad)). So you always 
have rests of black edges. To get rid of these completely you have to 
enter a smaller fov by hand. And this helps only for the left and right 
edges, the upper and/or lower edges remain black depending on the pitch.

Nevertheless I would argue in favour of bug hunting instead of including 
new features - particularly if those features are already included in 
other software.

>>Although hugin is a great piece of software...
> 
> Totally agree ;-)

me too!

Bye
Joachim