Hugin Batch Processor - Revision history

Thomas: /* Image sets (create project files) */

2011-12-11T08:43:27Z

‎Image sets (create project files)

Harryvanderwolf: /* Image sets (create project files) */

2011-12-10T11:52:10Z

‎Image sets (create project files)

Harryvanderwolf: /* Image sets (create project files */

2011-12-10T11:45:15Z

‎Image sets (create project files

Harryvanderwolf: /* Installation on Mac OS X */

2011-12-10T11:29:56Z

‎Installation on Mac OS X

Thomas: Updated flags

2011-10-21T19:01:39Z

Updated flags

Thomas: /* Usage */

2011-06-07T19:11:13Z

‎Usage

Thomas: /* PTBatcherGUI */ Some formatting

2011-06-07T19:09:29Z

‎PTBatcherGUI: Some formatting

Zarl: /* PTBatcher */ typos and some formatting

2011-06-07T17:04:25Z

‎PTBatcher: typos and some formatting

Harryvanderwolf: /* Add some Mac OS X specific details */

2011-06-07T16:41:54Z

‎Add some Mac OS X specific details

Zarl: /* Usage */ One more hint by Harry. Thanks!

2011-06-07T15:53:22Z

‎Usage: One more hint by Harry. Thanks!

@@ Line 74: / Line 74: @@
 * First file - last file.pto: The project files will by named by the first and last image of the panorama.
 * Foldername.pto: In this case the project file is named like the containing folder.
-Existing project files will not be overwritten, instead it appends an increasing number (unless the "Overwrite always" tickmark is set).
+Existing project files will not be overwritten, instead it appends an increasing number.
 If the images are shot with auto bracketing it tries to generate the appropriate stacks. In this case check that your default control point generator setting is such that it works with stacks (check [[Hugin_Preferences#Control_Point_Detectors|Preferences in Hugin]] and [[Hugin Parameters for Control Point Detectors dialog|control point detector parameters]]).

@@ Line 66: / Line 66: @@
 === Image sets (create project files) ===
-First select a folder in which should be searched. After pressing start is searches for image files in the folder (and optionally its sub folders). It uses the information stored in the EXIF data to decide which images could belong to a panorama. This works only in one folder level, it does not match images in different folders. (It uses camera maker, camera model, focal length, image size and date/time for this decision.)
+First select a folder in which PTBatcherGui should search for image sets. After pressing start it will search for image files in the folder (and optionally its sub folders). It uses the information stored in the EXIF data to decide which images could belong to a an image set forming a panorama. This works only in one folder level, it does not match images in different folders. (The algorithm uses camera maker, camera model, focal length, image size and date/time for this decision.)
-After the search has finished it shows a list of the found panoramas. With '''Send selected panoramas to queue''' the project files are created and send to the assistant queue. You can deselect individual panoramas from this processing step by untick the panorama.
+After the search has finished it shows a list of the found panoramas. With '''Send selected panoramas to queue''' the project files are created and sent to the assistant queue. You can deselect individual panoramas from this processing step by untick the panorama.
 The project files are named with the selected name scheme
@@ Line 74: / Line 74: @@
 * First file - last file.pto: The project files will by named by the first and last image of the panorama.
 * Foldername.pto: In this case the project file is named like the containing folder.
-Existing project files will not be overwritten, instead it appends an increasing number.
+Existing project files will not be overwritten, instead it appends an increasing number (unless the "Overwrite always" tickmark is set).
-If the images are shoot with auto bracketing it tries to generate the appropriate stacks. In this case check that you default control point generator setting is one which works with stacks (check [[Hugin_Preferences#Control_Point_Detectors|Preferences in Hugin]] and [[Hugin Parameters for Control Point Detectors dialog|control point detector parameters]]).
+If the images are shot with auto bracketing it tries to generate the appropriate stacks. In this case check that your default control point generator setting is such that it works with stacks (check [[Hugin_Preferences#Control_Point_Detectors|Preferences in Hugin]] and [[Hugin Parameters for Control Point Detectors dialog|control point detector parameters]]).
 If you shoot from a tripod then you can select also '''Create links'''. This will link the positions of all images of one stack. If you deselect this option, it will create the stacks but will not link the positions of the images (e.g. when shooting free hand).
 = Command line switches =

@@ Line 64: / Line 64: @@
 With File->Search directory for...->Projects you can search recursively in the given folder for (existing) project files and appends them to (stitching) queue.
-=== New project files ===
+=== Image sets (create project files) ===
 First select a folder in which should be searched. After pressing start is searches for image files in the folder (and optionally its sub folders). It uses the information stored in the EXIF data to decide which images could belong to a panorama. This works only in one folder level, it does not match images in different folders. (It uses camera maker, camera model, focal length, image size and date/time for this decision.)

@@ Line 7: / Line 7: @@
 = Installation on Mac OS X =
-At least on Mac OS X you have to download and install the BatchProcessor separately. You will find it at the [http://sourceforge.net/projects/hugin/files/hugin/ Sourceforge page] inside the folder for the latest version, e.g. [http://sourceforge.net/projects/hugin/files/hugin/hugin-2011.0/ptbatchergui-mac-2011.0.0.dmg/download ptbatchergui-mac-2011.0.0.dmg]. Just copy the app into the same folder as hugin and run it.
+Versions before the 2011.2.0 series required you to separately download and install the BatchProcessor. You will find the 2011.0.0 and older versions at the [http://sourceforge.net/projects/hugin/files/hugin/ Sourceforge page] inside the folder for the latest version, e.g. [http://sourceforge.net/projects/hugin/files/hugin/hugin-2011.0/ptbatchergui-mac-2011.0.0.dmg/download ptbatchergui-mac-2011.0.0.dmg]. Just copy the app into the same folder as hugin and run it.
 = Usage =

@@ Line 25: / Line 25: @@
 * '''parallel execution''': Execute stitching of projects in the list parallel rather than in sequential order. Check this only if you are certain your computer is up for the task of stitching multiple projects at the same time.
 * '''overwrite always''': Always(for each project) overwrite output filename if it exists. Otherwise, you will get a dialog box whether you want to overwrite files or not.
 * '''Shutdown when done''': Turn off computer when batch process ends.
 = Functions =

@@ Line 13: / Line 13: @@
 Just create several project files (do everything and just skip the export step), load them in the batch processor and start the process. This way you can run several large projects unattended. The output file name will be the same as the name of the corresponding project file (xyz.pto -> xyz.tif) and is saved in the same folder.
-At least on Mac OS X there are some minor issues to pay attention to:
+At least on Mac OS X there are some minor issues to pay attention to (This should be fixed in 2011.1, rev. 43043d2742e4):
 * You should only add the project files you want to process by using the "add project" (see below) or the menu "File - Add Project". Be aware that you will not be able to delete or deactivate a single project from the list - you will have to clean up the whole list using the menu "File - Clean List".<br>If you want to process all projects inside a folder, just use the "folder search" (see below).
 * Some older entries in PTBatcherGUI's list view (those with status "File missing") may not be removable by clicking the 'minus' symbol or the "Remove complete" button.<br>To remove those just close PTBatcherGui, open it again and immediately select one of the missing pto files and start deleting them using the 'minus' symbol. As an alternative, use the button "Remove completed"  on the right side which will remove all completed projects in one go.

@@ Line 108: / Line 108: @@
 Some of the above described options can be accessed also by command line switches:
-*  /h, --help            show this help message
+*  <code> /h, --help </code>           show this help message
-*  /b, --batch           run batch immediately
+*  <code> /b, --batch </code>          run batch immediately
-*  /p, --parallel        run batch projects in parallel
+*  <code> /p, --parallel </code>       run batch projects in parallel
-*  /d, --delete          delete *.pto files after stitching
+*  <code> /d, --delete </code>         delete *.pto files after stitching
-*  /o, --overwrite       overwrite previous files without asking
+*  <code> /o, --overwrite </code>      overwrite previous files without asking
-*  /s, --shutdown        shutdown computer after batch is complete
+*  <code> /s, --shutdown </code>       shutdown computer after batch is complete
-*  /v, --verbose         show verbose output when processing projects
+*  <code>/v, --verbose </code>        show verbose output when processing projects
 Please keep in mind that only one instance of PTBatcherGUI can run at one time. Starting PTBatcherGUI a second time with command line switches will influence the already running instance and not start a second instance with own options.

@@ Line 120: / Line 120: @@
 == PTBatcher ==
-PTBatcher provide a very similar interface like the GUI version. It works with the same list as the GUI version.
+PTBatcher provides a very similar interface compared to the GUI version. It works with the same list that is used by the GUI version.
-Attention: Only the short name of the switches are recognized.
+Attention: Only the short names of the switches are recognized.
-*  -a file         add project to queue. Unless -o option is present, the default prefix is appointed.
+*  <code>-a file</code> add project to queue. Unless -o option is present, the default prefix is appointed.
-*  -o              output prefix (together with -a option)
+*  <code>-o</code> output prefix (together with -a option)
-*  -l              list all projects in batch queue
+*  <code>-l</code> list all projects in batch queue
-*  -c              clear all projects from batch queue
+*  <code>-c</code> clear all projects from batch queue
-*  -x id           remove project with specified id
+*  <code>-x id</code> remove project with specified id
-*  -r              reset all projects to waiting status
+*  <code>-r</code> reset all projects to waiting status
-*  -b              start batch process
+*  <code>-b</code> start batch process
-*  -p              use parallel processing (together with -b option)
+*  <code>-p</code> use parallel processing (together with -b option)
-*  -d              delete .pto files when complete (together with -b option)
+*  <code>-d</code> delete .pto files when complete (together with -b option)
-*  -s              shutdown computer when complete (together with -b option)
+*  <code>-s</code> shutdown computer when complete (together with -b option)
-*  -v              verbose mode
+*  <code>-v</code> verbose mode
-*  -h              print this
+*  <code>-h</code> print this
 [[Category:Software:Hugin]]

@@ Line 82: / Line 82: @@
 To add a project to the (stitching) queue use
      PTBatcherGUI project.pto output_prefix
-You can also add several projects
+on Mac OS X use
      PTBatcherGUI project1.pto prefix1 project2.pto prefix2
 The prefix is optionally. If you don't provide a prefix, the filename (without extension) of the project file is used as prefix.
 You can also add a project to the assistant queue.
      PTBatcherGUI --assistant project.pto
 Some of the above described options can be accessed also by command line switches:

@@ Line 14: / Line 14: @@
 At least on Mac OS X there are some minor issues to pay attention to:
-* You should only add the project files you want to process by using the "add project" (see below) or the menu "File - Add Project". Be aware that you will not be able to delete or deactivate a single project from the list - you will have to clean up the whole list using the menu "File - Clean List". If you want to process all projects inside a folder, just use the "folder search" (see below).
+* You should only add the project files you want to process by using the "add project" (see below) or the menu "File - Add Project". Be aware that you will not be able to delete or deactivate a single project from the list - you will have to clean up the whole list using the menu "File - Clean List".<br>If you want to process all projects inside a folder, just use the "folder search" (see below).
-* Some older entries in PTBatcherGUI's list view (those with status "File missing") may not be removable by clicking the 'minus' symbol or the "Remove complete" button. To remove those just close PTBatcherGui, open it again and immediately select one of the missing pto files and start deleting them using the 'minus' symbol.
+* Some older entries in PTBatcherGUI's list view (those with status "File missing") may not be removable by clicking the 'minus' symbol or the "Remove complete" button.<br>To remove those just close PTBatcherGui, open it again and immediately select one of the missing pto files and start deleting them using the 'minus' symbol. As an alternative, use the button "Remove completed"  on the right side which will remove all completed projects in one go.
 Apart from this, all works fine.