Yes it can be done and a howto document is being written, it's just
going very slowly.
>I finally focused in Hugin, it shipped with lots of command line
>tools. But which tool can I use to generate the panorama? Is it
>autopano, nona or something else? There must be some ways to realize
>my dream.
You can use autopano-sift-C, panomatic or match-n-shift to create a
project file with control points (I use match-n-shift, but only
because I haven't tested the others thoroughly), use autooptimiser
to align the images and level the panorama, and then use pto2mk to
generate a Makefile for stitching.
>If there is a utility that allows me to pass a series of photos name,
>and output the final panorama, that will be just what I need.
Yes panostart from Panotools::Script will do something like this and
it even works a lot of the time.
--
Bruno
>step 2. when I use autooptimiser.exe output.pto, I was told "HFOV in image1
>is invalid, please specify HFOV with -v". checking the help, it said
>'autopano-sift generate pto with invalid HFOV'. So can you tell me the
>choice of the value of HFOV? I just used "autooptimiser -v 1 output.pto" to
>went through, and no idea if right or not;
HFOV is 'horizontal angle of view' in degrees, so unless you have a
telephoto lens 1 degree is too small. A 'normal' lens is usually
about 50 degrees (if you are using a fisheye lens then you need a
slightly different autopano-sift-c command-line).
autooptimiser has some more options, I would use something like
this (assuming a 50 degree lens):
autooptimiser -v 50 -a -l -s -o optimised.pto output.pto
This will create optimised.pto (I suggest opening these .pto files
in hugin to see what is happening at each step).
>Step 3. I used "pt2tomk -o final -p final_ output.pto", and got make file -
>final
>
>Then I lost. How to stitch by using this makefile? In command line, which
>utility should I use?
Makefiles are usually used when building software, we use them for
'building' panoramas as the process is somewhat similar (lots of
tools creating intermediate files and assembling them).
Makefiles are processed by the 'make' tool, so you can now do this:
make -f final
--
Bruno
As you figured out the output is created anyway, just EXIF data
isn't added. This is a known quirk of pto2mk that will get fixed at
some point, basically it doesn't read the hugin preferences when it
creates the Makefile so the exiftool settings are undefined.
The workaround is to define the two missing variables in the shell
and call `make -e` instead of just `make`. I'm not sure how you set
windows environment variables, but this is how I do it on Linux:
export EXIFTOOL_COPY_ARGS='-ImageDescription -Make -Model -Artist -WhitePoint -Copyright -GPS:all -DateTimeOriginal -CreateDate -UserComment -ColorSpace -OwnerName -SerialNumber'
export EXIFTOOL=exiftool
--
Bruno
The Makefile has lots of rules defined in addition to the default
'all', so you need to run the 'clean' rule too:
make -e -f final all clean
>2. Can I trop the dark edge of the generated panorama by some utility? It is
>really a little pity to have the black edge around the panorama;
Removing all the black is a hard problem, as far as I know there is
no solution to do this programatically.
>3. The generated format is tif, how can I convert it to jpeg? I remembed
>there are some command in linux to convert tif to jpeg, just forgot it. But
>in windows, do we have that command as well?
You can install ImageMagick and run convert:
convert -quality 75 project.tif project.jpg
..but actually the enblend step in the Makefile is quite capable of
creating JPEG output, you need to edit the .pto project before
running pto2mk and change this line:
#hugin_outputImageType tif
--
Bruno
The problem is that for most cases there are many hundreds of
rectangles that could all be the 'right' crop, do you want the most
pixels? the widest crop? the tallest crop? a crop that keeps the
centre of the image in the centre?
--
Bruno
Using panostart from Panotools::Script and current hugin SVN, I
process a days photos and stitch them into panoramas like so:
panostart -o Makefile -f 2 -v 111 -k -459,2459,-57,2861 -l *.JPG
make qtvr
..but this doesn't help explain what is going on or help you fix
things when it goes wrong.
--
Bruno
This is going to be difficult since hugin depends on lots of system
libraries which are easily available for all Linux distributions but
which require Administrator access to install.
You could build the command-line stuff locally with a minimal set of
dependencies and upload the lot, but I wouldn't recommend this as a
first Linux project.
--
Bruno
http://wiki.panotools.org/Hugin_Control_Points_tab
--
Bruno