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

[Rik Littlefield]

For what it is worth, I get good results with Autopano 1.02 Alexandre 
Jenny with following parameters:

autopano /keys:20 /search:2 /ransac:1 /size:1024 /ptgui /nomove /noclean

This is in a workflow that is typically
  Canon Digital Rebel at large/fine JPEG resolution
  Pano12.dll : 2.7.0.3  Jim Watters
  Autopano 1.02 Alexandre Jenny
  PTGui with PTStitcher
  Enblend 1.3 Andrew Mihal

I recall that it took some messing around to get good parameters for 
Autopano 1.02. 

Like others I never succeeded in getting autopano-sift to work under 
Windows.

--Rik

Mike Runge wrote:

>Hi Ian,
>thanks for sharing you workflow in that detail.
>
>My setup:
>Elitegroup K7S5A
>AMD Athlon 1400
>1024 MB RAM
>
>OS: W2K, SP3
>
>Panorama software:
>Pano12.dll: v2.7 Beta3 - Rik Littlefield
>Autopano 1.02 Alexandre Jenny, like shipped with hugin package
>Hugin: hugin snapshot - hugin_2004_03_25-08_41_win32
>Enblend: Enblend1.3- with patch by Edouard Gomez as incorporated into the
>latest enblend at http://wurm.wh-wurm.uni-ulm.de/~redman/enblend.exe
>
>I didn't managed to compile autopano-sift on my own. I treid several times
>the autopano.exe shipped with hugin, but only with bad results. Even autopano
> did not incule all images belonging to the pano or it finds to much unwanted
>points. I also have difficulties with the created pto-file, where each images
>seems to have its individual lens. I corrected that editing the pto-file by
>hand, but till now I never managed to get good results using autopano. 
>Would you be so kind to share the autopano-sift executable with me so that I
>can try this one?
>
>Agreed on all steps, I normally do 11 before 10.
>I totally agree on seperating optimisation steps.
>
>How do you do 14a and 15?
>I understand, that in the moment it is nessesairy to remove the blank 1 Pixel
>column, but how do you save that in gimp preserving the multiple layers for
>the later enblend run?
>
>16:
>If I understand to right, you can edit the multilayer Tiff and save it back.
>Could you step back to 14a and do some tweaks (e.g removing ghosts) before
>running enblend? I understand, that some of the nessesairy tweak will be
>identifyable after the enblend run and that you want to avoid running enblend
>again. And I still don't understand how you remove the 1 pixel column and
>save back the file?!  
>
>best, mike
>
>=========================================================================
>  
>
>>1. Copy the images I want to use for the panorama into my image working
>>    
>>
>folder
>  
>
>>(C:Program Filesautopano-sifttmp)
>>2. Run a batch file I have created
>>(C:Program Filesautopano-siftbinAutopanoIt.cmd) to create the Hugin Project
>>File (normally Hugin.pto). The batch file checks to make sure that I have
>>    
>>
>got
>  
>
>>some files to work with, creates the autopano key files and then calls
>>autopano-sift to create the hugin file.
>>3. Start Hugin and then open the Hugin.pto file.
>>4. Change the image hfov to my camera's setting (normally 38mm), set the
>>reference image for position (and exposure), and create vertical line
>>    
>>
>control
>  
>
>>points for images (if I can), and add any additional control point pairs
>>    
>>
>where I
>  
>
>>think they may be of some use.
>>5. Optimise for the default setting of "Positions (pairwise optim.,
>>    
>>
>starting
>>from anchor)", then save.
>  
>
>>6. Look at the "points" table and see if there are any wild points with
>>    
>>
>large
>  
>
>>distances. If there are then review the point pair to see if is correct and
>>decide to adjust it, remove it, or keep it. If I changed anything then re-do
>>    
>>
>the
>  
>
>>optimisation step.
>>7. Preview the image in the preview window, check that it looks OK, then
>>    
>>
>centre
>  
>
>>the image and save the project.
>>8. Optimise using custom optimisation - for Yaw roll and pitch (yaw fixed
>>    
>>
>for
>  
>
>>the reference image).
>>9. Optimise again adding barrel.
>>10. Optimise again adding view v.
>>11. Optimise again adding distortion a and b.
>>(Sometimes I get better results by swapping steps 10 and 11)
>>
>>(I separate these optimisation steps because it seems to be a more reliable
>>    
>>
>way
>  
>
>>to get a "good" solution without drifting off to a wild set of parameters.
>>    
>>
>After
>  
>
>>each step I look at the preview window and the points table to see if
>>    
>>
>anything
>  
>
>>has gone wild, and if it has then I revert to the previous step and try to
>>    
>>
>find
>  
>
>>what went wrong)
>>
>>12. Open the Hugin Stitcher Tab and set the pixel width to 1024, image
>>    
>>
>format to
>  
>
>>JPG (90%) and then stitch now!
>>13. I then open this image (using irfanview) and check that it looks OK. If
>>    
>>
>it
>  
>
>>does not then I try lots of things - more control points, less control
>>    
>>
>points...
>  
>
>>14. Assuming it looks OK then I set the pixel width to the default (click
>>    
>>
>on
>  
>
>>"Calculate Pixel Dimensions") and stitch again using nona and multiple Tiff
>>    
>>
>with
>  
>
>>the file name nona.tiff saved into the folder C:Program
>>    
>>
>Filesautopano-sifttmp
>  
>
>>14a. If the image is a 360 deg panorama then (since I started using the
>>    
>>
>patched
>  
>
>>enblend) I open the created tiff file in GIMP and resize the image by one
>>    
>>
>pixel
>  
>
>>column to remove the blank column of pixels at the right side of the image
>>15. I delete the 0 byte file nona.tiff (leaving nona.tif for later use)
>>    
>>
>then
>  
>
>>start enblend using a batch file I have created
>>C:Program Filesautopano-siftbinEnblendIt.cmd.
>>The batch file looks for tiff files in the directory C:Program
>>Filesautopano-sifttmp and runs enblend to create a JPG file enblended.tif.
>>This works not only with multiple layer tiff files, but also with multiple
>>    
>>
>tiff
>  
>
>>files (I have not tried it with a mix of both). It then uses image magic
>>"convert.exe" to convert this to a (smaller) PNG file and deletes the
>>    
>>
>enblended
>  
>
>>tiff file.
>>16. I preview this then do any final "tweaks" using Gimp. If there are any
>>    
>>
>very
>  
>
>>bad join problems (I mostly take hand-held shots and sometimes it's not so
>>    
>>
>good)
>  
>
>>I use pieces of the images from the the Hugin output tiff file to paste
>>    
>>
>over
>  
>
>>with corrections.
>>
>>regards,
>>
>>Ian Sydenham
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>    
>>
>
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.email-lists.org/pipermail/ptx/attachments/20040624/e964e9bc/attachment.htm