Panorama scripting in a nutshell - Revision history

Thomas: /* Project file modification */

2013-04-18T17:05:00Z

‎Project file modification

2013-01-19T07:30:31Z

‎Project file modification: Added new tools

2012-03-20T20:14:42Z

‎Creating hugin projects on the command-line

2012-03-18T09:32:03Z

‎Creating hugin projects on the command-line

2012-03-18T09:22:02Z

‎Full list of command-line tools

2011-01-30T20:27:33Z

‎Simple command-line stitching

2010-05-22T07:38:00Z

Added autooptimiser -m switch

2010-05-21T22:44:13Z

‎Full list of command-line tools

2010-05-21T21:36:18Z

some new tools in hugin 2010.2.0

2010-02-17T01:43:31Z

‎PanoTools 'Scripting'

@@ Line 329: / Line 329: @@
 * [[pto_var]] - Manipulate image variable, can also set [[optimization|optimisation]] variables
 * [[pto_lensstack]] - Manipulate lenses and stacks
 * ptsed - Set any project parameter, convert .pto into PanoTools format
 * [[ptosort]] - Sort [[control points]] or images, remove duplicate control points

@@ Line 327: / Line 327: @@
 * ptoset - Change global parameters and project options
 * [[ptovariable]] - Set typical [[optimization|optimisation]] variables
 * ptsed - Set any project parameter, convert .pto into PanoTools format
 * [[ptosort]] - Sort [[control points]] or images, remove duplicate control points

@@ Line 95: / Line 95: @@
      pano_modify -o project.pto --center --straighten --canvas=AUTO --crop=AUTO project.pto
 This command will straighten the pano, center it on the canvas, calculates the optimal size and calculates the optimal output region.
 = Stitching hugin projects on the command-line =

@@ Line 27: / Line 27: @@
 The entire panorama creation process can be performed on the command-line, and therefore scripted, doing this involves a series of steps similar to the workflow in a GUI tool.
 == Generating control points ==
-There are a number of tools available for generating [[control points]] from groups of photos, such as [[autopano-sift]], [[autopano-sift-c]], [[panomatic]] and [[match-n-shift]]. Here is an example using autopano-sift-c:
+There are a number of tools available for generating [[control points]] from groups of photos, like [[cpfind]]. Here is an example using cpfind
    autopano-sift-c --projection 0,50 project.pto DSC_1234.JPG DSC_1235.JPG DSC_1236.JPG
@@ Line 78: / Line 89: @@
    ptovariable --vignetting --response --exposure project.pto
    vig_optimize -o project.pto project.pto
 = Stitching hugin projects on the command-line =

@@ Line 270: / Line 270: @@
 == Control point generation ==
 * [[autopano-sift-c]] - All in one keypoint generator and matcher
 * [[match-n-shift]] - All in one wrapper around [[align_image_stack]] and [[autopano-sift-c]]
@@ Line 284: / Line 285: @@
 == Project file modification ==
 * [[match-n-shift]] - (see above) Default usage is to initialise a new .pto project from EXIF data
 * ptoset - Change global parameters and project options

@@ Line 15: / Line 15: @@
 = Simple command-line stitching =
-Lets start with a basic but common use case: Photographers with quality [[Nodal point adapters|panoramic tripod heads]] can reproduce identical sets of photos every time, in this situation there is no need to create a new stitching project for every panorama, it is enough to use a single project as a template.
+Lets start with a basic but common use case: Photographers with quality [[Heads|panoramic tripod heads]] can reproduce identical sets of photos every time, in this situation there is no need to create a new stitching project for every panorama, it is enough to use a single project as a template.
 This example takes a pre-existing project called template.pto, created with three photos. It uses [[nona]] for remapping, and [[enblend]] for blending the remapped photos into a finished [[TIFF]] image:

@@ Line 59: / Line 59: @@
 Now you could just skip ahead and render the output if photometric [[optimization|optimisation]] isn't required.
 ([[PToptimizer]] is an alternative geometrical optimiser)
@@ Line 66: / Line 70: @@
 Photos have photometric exposure variables which can be [[optimization|optimised]] in much the same way as aligning positions. Doing this can remove brightness, [[white balance]] and [[vignetting]] differences between photos, giving better blending or allowing creation of [[HDR]] images.
-[[vig_optimize]] does the equivalent job for photometric parameters as [[autooptimiser]] does for geometric parameters. It doesn't have an equivalent of the autooptimiser -a 'auto' mode, so you need to indicate in the .pto project which parameters are 'variables', use a tool such as [[ptovariable]]:
+For doing an automatic photometric optimisation like Hugin's assistant, run [[autooptimiser]] with -m switch:
    ptovariable --vignetting --response --exposure project.pto

@@ Line 276: / Line 276: @@
 == Project file modification ==
 * ptoset - Change global parameters and project options
 * [[ptovariable]] - Set typical [[optimization|optimisation]] variables
@@ Line 331: / Line 332: @@
 * gigastart - All-in-one assembly of multi-row panoramas
 * [[pto2mk]] - Create platform specific ''Makefile'' for stitching a project
 * [[ptodummy]] - Generate missing input photos to debug .pto projects
 * [[calibrate_lens]] - Automatic lens calibration using straight-line detection
-* pano_trafo - transform between image and panorama coordinates (and vice versa)
+* [[pafextract]] - Tool to use [[panoglview]] as a [[Zenith and Nadir editing overview|zenith and nadir editor]]
 == Chromatic aberration ==
@@ Line 347: / Line 349: @@
 * PTinfo - Display info about a panotools generated [[TIFF]] file
 * [[panoinfo]] - Display information about installed [[libpano13]] library
 == TIFF files ==

@@ Line 283: / Line 283: @@
 * [[transform-pano]] - [[Roll]], [[pitch]] and [[yaw]] rotation of .pto projects
 * ptocentre - Rotate projects to put images in panorama centre
 * [[ptomerge]] - Join two or more projects
 * [[ptosplit]] - Extract subsets of images from a project into a new project

@@ Line 11: / Line 11: @@
 The file format first used in Helmut Dersch's [[Panorama tools]] is often referred to as a 'script', but a 'PanoTools' script is really a data file describing a 'panorama stitching project'.
-Although these original PanoTools are obsolete, the file format is alive and well with several variations used as project files by [[PTGui]], [[PTAssembler]], [[hugin]] and related tools. These files are simple plain-text, sometimes it is useful to modify them directly with a text editor - Further on we will introduce various methods for manipulating them via the 'programming' kind of scripts.
+Although these original PanoTools are less used today, the file format is alive and well with several variations used as project files by [[PTGui]], [[PTAssembler]], [[hugin]] and related tools. These files are simple plain-text, sometimes it is useful to modify them directly with a text editor - Further on we will introduce various methods for manipulating them via the 'programming' kind of scripts.
 = Simple command-line stitching =