fulla is a command-line tool distributed with hugin 0.6 and later. It is suitable for batch correction of:
- Lens distortion such as barrel distortion or pincushion distortion: fulla uses the same a, b, c and d parameters as other Panorama Tools derived programs.
- Vignetting: polynomial correction by division, addition or flatfield images. hugin contains a vignetting calculator that can use a series of overlapping photographs to determine the likely polynomial required to correct common vignetting problems.
Usage: fulla [options] inputfile(s) options are: -g a:b:c:d Radial distortion coefficient for all channels, (a, b, c, d) -b a:b:c:d Radial distortion coefficents for blue channel, (a, b, c, d) this is applied on top of the -g distortion coefficients, use for TCA corr -r a:b:c:d Radial distortion coefficents for red channel, (a, b, c, d) this is applied on top of the -g distortion coefficients, use for TCA corr -f filename Vignetting correction by flatfield division I = I / c, c = flatfield / mean(flatfield) -c a:b:c:d radial vignetting correction by division: I = I / c, c = a + b*r2 + c*r4 + d*r6 -a Correct vignetting by addition, rather than by division I = I + c -p Try to read radial distortion coefficients (-g) from PTLens database -m Canon Camera manufacturer, for PTLens database query -n Camera Camera name, for PTLens database query -l Lens Lens name, for PTLens database query if not specified, a list of possible lenses is displayed -d 50 specify focal length in mm, for PTLens database query -t n Number of threads that should be used during processing -h Display help (this text) -o name set output filename. If more than one image is given, the name will be uses as suffix (default suffix: _corr) -v Verbose
PTLens database lookup
fulla will look-up your camera in a PTLens database and try to automatically determine Lens correction parameters for your pictures. An older free version of the database is required which can be downloaded from sourceforge.
Use the PTLENS_PROFILE environment variable to specify the location of the PTLens database, for example on Linux or OS X:
On Windows something like this (untested) should work: