[ptx] Autopano-sift -> Hugin -> Enblend Workflow

[Rik Littlefield]

"Good" means having all images tied together, with a high proportion of 
correct control points.

I will repeat an exercise from yesterday and keep notes.....

OK, here is literally everything I did.

0.1 run autopano
0.2 double-click .pts file to launch PTGui.  Then...

1. In Lens Settings panel, click EXIF button to load focal length and 
multiplier.
2. In Optimizer panel, "Set all" yaw, pitch, roll to optimize for each 
image, then clear these for one anchor image.
3. In Optimizer panel, "Clear all" to initially disable lens parameter 
optimization.
4. Run Optimizer.
5. Examine table of control point errors, see no obvious control point 
errors.
6. In Panorama Editor window, set center point of panorama and 
appropriate width/height.
7. Set line controls (one horizontal, one vertical).
8. Enable pitch and roll optimization on all images.
9. Enable b optimization.
10. Run Optimizer.
11. Re-examine table of control point errors, now see one incorrect 
control point, delete that.
12. Run Optimizer, re-examine errors, see no more.
13. Save file, render, etc.

I can't run autopano-sift, so I can't make a direct comparison. 

I do note that the project file created by Autopano 1.02 was directly 
readable by PTGui and all of the changes I needed to make were easily 
done using PTGui's interface, no manual file editing required. 

This project had only one control point error, usually there a few more, 
and I have read that autopano-sift may do better.

The initial project settings are to optimize yaw, pitch, roll for only 
one image, which seems clearly not right (and I have reported this 
separately as a bug).

--Rik

Ian Sydenham wrote:

> Rik,
>
> Rik Littlefield wrote:
>
>> For what it is worth, I get good results with Autopano 1.02 Alexandre 
>> Jenny ...
>
>
> Does autopano 1.02 Alexandre Jenny with PTGui output give you a "good" 
> project file, or do you have to manually adjust it like I had to do 
> for the Hugin project file?
> Each time I created a Hugin project file using autopano I had to 
> change the output file before I could use it. What I did was:
> 1. Open the file in Hugin then save it
>    (this made the file easier for me to read)
> 2. Change all the control point types from t7143541 to t0
>    (Not sure if this is neccessary, but I did it anyway as
>      standard control points created in Hugin are t0)
> 3. Correct the field of view on the first image to v=50.391
>    (this is unique to my camera on full wide angle)
> 4. Change the image file parameters on all other image lines to
>    a=0 b=0 c=0 d=0 e=0 g=0 p0 r0 t=0 v=0 y0
>
> As a comparison when using autopano-sift I only have to manually set 
> the fov.
>
> regards,
>
> Ian Sydenham
>