Chuck Norcutt wrote:
> With the right software the knowledge required is about zilch. I use
> PTGUI these days because I'm familiar with it and have owned it for a
> long time. I had abandoned it for a while in favor of Autostitch
> <http://www.cs.ubc.ca/~mbrown/autostitch/autostitch.html> because
> Autostitch seemed like magic in comparison and had the great advantage
> of being absolutely free. Since then PTGUI seems to have absorbed some
> of the magical qualities of Autostitch so I returned to using it as it
> also had functions that Autostitch doesn't. But it is definitely not
> free.
I've been making up a bunch of panoramas recently, and have settled on
the following process:
1. try autostitch. If it works, great, I'm done; if it doesn't work,
there's not a lot you can do to fix it (tweaking the various mystery
coefficients sometimes helps, but mostly not), and when autostitch
doesn't work it just misses out big chunks of images.
2. if autostitch fails, use hugin.
Hugin's a free (open source) version of PTGui, and recent versions are
hooked into autopano, so if you're lucky it'll all work automatically,
just like autostitch.
The big advantage is that if it _doesn't_ automatically align
everything, you can still go in there and add control points by hand to
get it going.
Comparing hugin to PTGui: hugin is free, works pretty much as well,
but has a much more awkward 'panorama preview' window -- ptgui you can
almost get all the alignment done in that, but in hugin it's just for
viewing the results of control point alignment and setting the horizon
level.
-- dan
==============================================
List usage info: http://www.zuikoholic.com
List nannies: olympusadmin@xxxxxxxxxx
==============================================
|