PanoTools.org Wiki - User contributions [en]

Hugin SDK (MSVC 2008) Patches

2009-08-11T22:17:35Z

Dedalus: directions to add glut

'''The current SVN version of hugin depends not only on this SDK but also on glut, see [http://groups.google.com/group/hugin-ptx/msg/5bfc12ee00c5ac3c?hl=en this message] for directions how to add glut to your installation of the SDK.'''

This is the list of changes from source distributions that need to be made to get the [[Hugin SDK (MSVC 2008)|Hugin SDK compiled using Microsoft Visual Studio 2008 Express Edition]], which is a precondition to compiling Hugin on Windows.

The changes listed here apply to both 32-bit and 64-bit versions of the Hugin SDK. In addition, all of the diff files supplied performed an additional step of converting the projects to have two platforms supported (Win32 and x64), although this is not a necessary step if you're only compiling on Win32.

Changes that were specific to x64 are not documented explicitly in here, because they would essentially be the same as the diff files supplied, as they were purely source changes.

The most recent version of the files can be obtained at [https://sourceforge.net/tracker/download.php?group_id=77506&atid=550443&file_id=334027&aid=2789320 https://sourceforge.net/tracker/?func=detail&aid=2789320&group_id=77506&atid=550443]
== wxWidgets ==
<ol>
<li>Open the file <tt><SDKHOME>\wxWidgets-2.8.10\include\wx\msw\setup.h</tt></li>
<li>Search for following line
<pre>
#define wxUSE_GLCANVAS 0
</pre>
and replace it by
<pre>
#define wxUSE_GLCANVAS 1
</pre>
</li>
<li>Save the file</li>
<li>Open the file <tt><SDKHOME>\wxWidgets-2.8.10\src\jpeg\jpeglib.h</tt></li>
<li>Search for following line
<pre>
#include "../src/jpeg/jconfig.h"
</pre>
and replace it by
<pre>
#include "jconfig.h"
</pre>
</li>
<li>Save the file</li>
<li>Open the file <tt><SDKHOME>\wxWidgets-2.8.10\src\tiff\tiffconf.h</tt></li>
<li>Search for following line
<pre>
#ifndef COMPRESSION_SUPPORT
</pre>
and extend it to
<pre>
#define TIF_PLATFORM_CONSOLE 1
#ifndef COMPRESSION_SUPPORT
#define ZIP_SUPPORT
</pre>
</li>
<li>Save the file</li>
</ol>

== OpenEXR ==
<ol>
<li>Open solution file <tt><SDKHOME>\OpenEXR\ilmbase-1.0.1\vc\vc8\IlmBase\IlmBase.sln</tt> 
The Visual Studio Conversion Wizard dialog appears. Click Next, select option No, click Next and Finish. Unselect the option "Show the conversion log when the wizard is closed" and click Close</li>
<li>Due to the fact that the Visual Studio solutions of OpenEXR are configured to build dynamic libraries, some modifications are necessary to build the required static libraries: 

For each project in Solution Explorer open the Property Pages dialog by choosing Project > Properties. Process the following steps for Debug and Release configuration. Some of the properties are not avaliable in every project, thus continue with next step.

<ul>
<li>Choose Configuration Properties > General. For Configuration Type property choose Static Library (.lib) if Dynamic Library (.dll) was selected.
</li>
<li>Choose Configuration Properties > C/C++ > Preprocessor. In the Preprocessor Definitions entry remove defines <tt>OPENEXR_DLL</tt>, <tt>_USRDLL</tt> and <tt>*_EXPORTS</tt> (all with suffix <tt>_EXPORTS</tt>).
</li>
<li>Choose Configuration Properties > C/C++ > Code Generation. For Runtime Library property choose Multithreaded-Debug (/MTd) in Debug configuration and Multithreaded (/MT) in Release configuration.
</li>
<li>Choose Configuration Properties > C/C++ > Code Generation. For Enable Enhanced Instruction Set property choose Not Set.
</li>
<li>Choose Configuration Properties > Build Events > Post-Build Event. In Command Line entry remove the <tt>createDLL</tt> command, but keep the <tt>install*.cmd</tt> command. For example in createDLL project only the statement "<tt>..\..\..\installCreateDLL.cmd $(IntDir)</tt>" should remain, in Half project only "<tt>..\..\..\installHalf.cmd $(IntDir)</tt>" etc.
</li>
</ul>
</li>
<li>Close Property Pages dialog</li>
<li>(64-bit) Add x64 Configuration</li>
<li>Open solution file <tt><SDKHOME>\OpenEXR\openexr-1.6.1\vc\vc8\OpenEXR\OpenEXR.sln</tt> 
The Visual Studio Conversion Wizard dialog appears. Click Next, select option No, click Next and Finish. Unselect the option "Show the conversion log when the wizard is closed" and click Close</li>
<li>For project IlmImf do the same configuration property changes as in IlmBase solution described above</li>
<li>Right-click IlmImf in Solution Explorer, and then choose Properties from shortcut menu</li>
<li>In the Property Pages dialog do the following for Debug and Release configuration: 
Choose Configuration Properties > C/C++ > General. In Additional Include Directory entry enter following additional include directory:
<pre>
..\..\..\..\..\..\wxWidgets-2.8.10\src\zlib
</pre>
</li>
<li>(64-bit) Add x64 Configuration</li>
</ol>

== Enblend/Enfuse/libxmi ==
<ol>
<li>Open the file <tt><SDKHOME>\enblend-enfuse-3.2\enblend_msvc2008.sln</tt></li>
<li>Add x64 Configuration</li>
<li>Choose "File" > "New Project"</li>
<li>For the path, give it <tt><SDKHOME>\libxmi</tt> and the name of libxmi</li>
<li>In the Solution Explorer, select the new libxmi project</li>
<li>Choose "Project" > "Add Existing Item"</li>
<li>Navigate to <tt><SDKHOME>\libxmi</tt> and select all the .c and .h files</li>
<li>Click OK</li>
<li>Open <tt><SDKHOME>\libxmi\sys-defines.h</tt></li>
<li>Change the line
<pre>
#include <config.h>
</pre>
to read
<pre>
#include "config.h"
</pre></li>
<li>Close the file</li>
<li>Open <tt><SDKHOME>\libxmi\config.h</tt></li>
<li>Change the line
<pre>
#define HAVE_VALUES_H 1
</pre>
to read
<pre>
/* #undef HAVE_VALUES_H */
#define HAVE_STRERROR 1
</pre></li>
<li>Save and Close the file</li>
</ol>

{| class="wikitable" width="100%"
|-
! style="padding:5px; text-align:left" | Note
|-
| style="padding:5px; text-align:left" | Pure ASM isn't supported when compiling x64, so an SSE4/SSE4.1 intrinsics replacement is used instead, which x64 machines will support.
|}

== expat ==
<ol>
<li>Open the file <tt><SDKHOME>\expat-2.0.1\Source\expat.dsw</tt> 
A Visual C++ Project conversion dialog appears. Click "Yes To All".</li>
<li>(64-bit) Add x64 Configuration</li>
</ol>

== exiv2 ==
<ol>
<li>Open solution file <tt><SDKHOME>\exiv2-0.18.1\msvc\exiv2.sln</tt> 
The Visual Studio Conversion Wizard dialog appears. Click Next, select option No, click Next and Finish. Unselect the option "Show the conversion log when the wizard is closed" and click Close</li>
<li>Right-click exiv2lib in Solution Explorer, and then choose Properties from the shortcut menu</li>

<li>In the Property Pages dialog do the following for the Debug and Release Configuration, selecting All Platforms</li>
<ul>
<li>Choose Configuration Properties > C/C++ > General. In Additional Include Directories entry replace
<pre>
../../../zlib-1.2.3
</pre>
by
<pre>
../../../wxWidgets-2.8.10/src/zlib
</pre>
</li>
<li>(64-bit) Add x64 Configuration</li>
</ul>
</li>
<li>Close Property Pages dialog</li>
</ol>

== glew ==
<ol>
<li>Open the file <tt><SDKHOME>\glew\build\vc6\glew.dsw</tt> 
A Visual C++ Project conversion dialog appears. Click "Yes To All".</li>
<li>(64-bit) Add x64 Configuration</li>
</ol>

== Panorama Tools ==
<ol>
<li>Open solution file <tt><SDKHOME>\libpano\pano13\libpano.sln</tt> 
The Visual Studio Conversion Wizard dialog appears. Click Next, select option No, click Next and Finish. Unselect the option "Show the conversion log when the wizard is closed." and click Close</li>
</ol>

[[Category:Software:Hugin]]

Hugin SDK (MSVC 2008) Patches

2009-05-14T12:58:12Z

Dedalus: add a interwiki

This is the list of changes from source distributions that need to be made to get the [[Hugin SDK (MSVC 2008)|Hugin SDK compiled using Microsoft Visual Studio 2008 Express Edition]], which is a precondition to compiling Hugin on Windows.

The changes listed here apply to both 32-bit and 64-bit versions of the Hugin SDK. In addition, all of the diff files supplied performed an additional step of converting the projects to have two platforms supported (Win32 and x64), although this is not a necessary step if you're only compiling on Win32.

Changes that were specific to x64 are not documented explicitly in here, because they would essentially be the same as the diff files supplied, as they were purely source changes.

The most recent version of the files can be obtained at [http://sourceforge.net/tracker/download.php?group_id=77506&atid=550443&file_id=326306&aid=2789320 http://sourceforge.net/tracker/download.php?group_id=77506&atid=550443&file_id=326306&aid=2789320]
== wxWidgets ==
<ol>
<li>Open the file <tt><SDKHOME>\wxWidgets-2.8.10\include\wx\msw\setup.h</tt></li>
<li>Search for following line
<pre>
#define wxUSE_GLCANVAS 0
</pre>
and replace it by
<pre>
#define wxUSE_GLCANVAS 1
</pre>
</li>
<li>Save the file</li>
<li>Open the file <tt><SDKHOME>\wxWidgets-2.8.10\src\jpeg\jpeglib.h</tt></li>
<li>Search for following line
<pre>
#include "../src/jpeg/jconfig.h"
</pre>
and replace it by
<pre>
#include "jconfig.h"
</pre>
</li>
<li>Save the file</li>
<li>Open the file <tt><SDKHOME>\wxWidgets-2.8.10\src\tiff\tiffconf.h</tt></li>
<li>Search for following line
<pre>
#ifndef COMPRESSION_SUPPORT
</pre>
and extend it to
<pre>
#define TIF_PLATFORM_CONSOLE 1
#ifndef COMPRESSION_SUPPORT
#define ZIP_SUPPORT
</pre>
</li>
<li>Save the file</li>
</ol>

== OpenEXR ==
<ol>
<li>Open solution file <tt><SDKHOME>\OpenEXR\ilmbase-1.0.1\vc\vc8\IlmBase\IlmBase.sln</tt> 
The Visual Studio Conversion Wizard dialog appears. Click Next, select option No, click Next and Finish. Unselect the option "Show the conversion log when the wizard is closed" and click Close</li>
<li>Due to the fact that the Visual Studio solutions of OpenEXR are configured to build dynamic libraries, some modifications are necessary to build the required static libraries: 

For each project in Solution Explorer open the Property Pages dialog by choosing Project > Properties. Process the following steps for Debug and Release configuration. Some of the properties are not avaliable in every project, thus continue with next step.

<ul>
<li>Choose Configuration Properties > General. For Configuration Type property choose Static Library (.lib) if Dynamic Library (.dll) was selected.
</li>
<li>Choose Configuration Properties > C/C++ > Preprocessor. In the Preprocessor Definitions entry remove defines <tt>OPENEXR_DLL</tt>, <tt>_USRDLL</tt> and <tt>*_EXPORTS</tt> (all with suffix <tt>_EXPORTS</tt>).
</li>
<li>Choose Configuration Properties > C/C++ > Code Generation. For Runtime Library property choose Multithreaded-Debug (/MTd) in Debug configuration and Multithreaded (/MT) in Release configuration.
</li>
<li>Choose Configuration Properties > C/C++ > Code Generation. For Enable Enhanced Instruction Set property choose Not Set.
</li>
<li>Choose Configuration Properties > Build Events > Post-Build Event. In Command Line entry remove the <tt>createDLL</tt> command, but keep the <tt>install*.cmd</tt> command. For example in createDLL project only the statement "<tt>..\..\..\installCreateDLL.cmd $(IntDir)</tt>" should remain, in Half project only "<tt>..\..\..\installHalf.cmd $(IntDir)</tt>" etc.
</li>
</ul>
</li>
<li>Close Property Pages dialog</li>
<li>(64-bit) Add x64 Configuration</li>
<li>Open solution file <tt><SDKHOME>\OpenEXR\openexr-1.6.1\vc\vc8\OpenEXR\OpenEXR.sln</tt> 
The Visual Studio Conversion Wizard dialog appears. Click Next, select option No, click Next and Finish. Unselect the option "Show the conversion log when the wizard is closed" and click Close</li>
<li>For project IlmImf do the same configuration property changes as in IlmBase solution described above</li>
<li>Right-click IlmImf in Solution Explorer, and then choose Properties from shortcut menu</li>
<li>In the Property Pages dialog do the following for Debug and Release configuration: 
Choose Configuration Properties > C/C++ > General. In Additional Include Directory entry enter following additional include directory:
<pre>
..\..\..\..\..\..\wxWidgets-2.8.10\src\zlib
</pre>
</li>
<li>(64-bit) Add x64 Configuration</li>
</ol>

== Enblend/Enfuse/libxmi ==
<ol>
<li>Open the file <tt><SDKHOME>\enblend-enfuse-3.2\enblend_msvc2008.sln</tt></li>
<li>Add x64 Configuration</li>
<li>Choose "File" > "New Project"</li>
<li>For the path, give it <tt><SDKHOME>\libxmi</tt> and the name of libxmi</li>
<li>In the Solution Explorer, select the new libxmi project</li>
<li>Choose "Project" > "Add Existing Item"</li>
<li>Navigate to <tt><SDKHOME>\libxmi</tt> and select all the .c and .h files</li>
<li>Click OK</li>
<li>Open <tt><SDKHOME>\libxmi\sys-defines.h</tt></li>
<li>Change the line
<pre>
#include <config.h>
<pre>
to read
<pre>
#include "config.h"
</pre></li>
<li>Close the file</li>
<li>Open <tt><SDKHOME>\libxmi\config.h</tt></li>
<li>Change the line
<pre>
#define HAVE_VALUES_H 1
</pre>
to read
<pre>
/* #undef HAVE_VALUES_H */
#define HAVE_STRERROR 1
</pre></li>
<li>Save and Close the file</li>
</ol>

{| class="wikitable" width="100%"
|-
! style="padding:5px; text-align:left" | Note
|-
| style="padding:5px; text-align:left" | Pure ASM isn't supported when compiling x64, so an SSE4/SSE4.1 intrinsics replacement is used instead, which x64 machines will support.
|}

== expat ==
<ol>
<li>Open the file <tt><SDKHOME>\expat-2.0.1\Source\expat.dsw</tt> 
A Visual C++ Project conversion dialog appears. Click "Yes To All".</li>
<li>(64-bit) Add x64 Configuration</li>
</ol>

== exiv2 ==
<ol>
<li>Open solution file <tt><SDKHOME>\exiv2-0.18.1\msvc\exiv2.sln</tt> 
The Visual Studio Conversion Wizard dialog appears. Click Next, select option No, click Next and Finish. Unselect the option "Show the conversion log when the wizard is closed" and click Close</li>
<li>Right-click exiv2lib in Solution Explorer, and then choose Properties from the shortcut menu</li>

<li>In the Property Pages dialog do the following for the Debug and Release Configuration, selecting All Platforms</li>
<ul>
<li>Choose Configuration Properties > C/C++ > General. In Additional Include Directories entry replace
<pre>
../../../zlib-1.2.3
</pre>
by
<pre>
../../../wxWidgets-2.8.10/src/zlib
</pre>
</li>
<li>(64-bit) Add x64 Configuration</li>
</ul>
</li>
<li>Close Property Pages dialog</li>
</ol>

== glew ==
<ol>
<li>Open the file <tt><SDKHOME>\glew\build\vc6\glew.dsw</tt> 
A Visual C++ Project conversion dialog appears. Click "Yes To All".</li>
<li>(64-bit) Add x64 Configuration</li>
</ol>

== Panorama Tools ==
<ol>
<li>Open solution file <tt><SDKHOME>\libpano\pano13\libpano.sln</tt> 
The Visual Studio Conversion Wizard dialog appears. Click Next, select option No, click Next and Finish. Unselect the option "Show the conversion log when the wizard is closed." and click Close</li>
</ol>

Hugin SDK (MSVC 2008)/Patches

2009-05-14T12:56:31Z

Dedalus: moved Hugin SDK (MSVC 2008)/Patches to Hugin SDK (MSVC 2008) Patches over redirect: revert - doesn't do the trick on this mediawiki installation

#REDIRECT [[Hugin SDK (MSVC 2008) Patches]]

Hugin SDK (MSVC 2008) Patches

2009-05-14T12:56:31Z

Dedalus: moved Hugin SDK (MSVC 2008)/Patches to Hugin SDK (MSVC 2008) Patches over redirect: revert - doesn't do the trick on this mediawiki installation

This is the list of changes from source distributions that need to be made to get the Hugin SDK compiled using Microsoft Visual Studio 2008 Express Edition, which is a precondition to compiling Hugin on Windows.

The changes listed here apply to both 32-bit and 64-bit versions of the Hugin SDK. In addition, all of the diff files supplied performed an additional step of converting the projects to have two platforms supported (Win32 and x64), although this is not a necessary step if you're only compiling on Win32.

Changes that were specific to x64 are not documented explicitly in here, because they would essentially be the same as the diff files supplied, as they were purely source changes.

The most recent version of the files can be obtained at [http://sourceforge.net/tracker/download.php?group_id=77506&atid=550443&file_id=326306&aid=2789320 http://sourceforge.net/tracker/download.php?group_id=77506&atid=550443&file_id=326306&aid=2789320]
== wxWidgets ==
<ol>
<li>Open the file <tt><SDKHOME>\wxWidgets-2.8.10\include\wx\msw\setup.h</tt></li>
<li>Search for following line
<pre>
#define wxUSE_GLCANVAS 0
</pre>
and replace it by
<pre>
#define wxUSE_GLCANVAS 1
</pre>
</li>
<li>Save the file</li>
<li>Open the file <tt><SDKHOME>\wxWidgets-2.8.10\src\jpeg\jpeglib.h</tt></li>
<li>Search for following line
<pre>
#include "../src/jpeg/jconfig.h"
</pre>
and replace it by
<pre>
#include "jconfig.h"
</pre>
</li>
<li>Save the file</li>
<li>Open the file <tt><SDKHOME>\wxWidgets-2.8.10\src\tiff\tiffconf.h</tt></li>
<li>Search for following line
<pre>
#ifndef COMPRESSION_SUPPORT
</pre>
and extend it to
<pre>
#define TIF_PLATFORM_CONSOLE 1
#ifndef COMPRESSION_SUPPORT
#define ZIP_SUPPORT
</pre>
</li>
<li>Save the file</li>
</ol>

== OpenEXR ==
<ol>
<li>Open solution file <tt><SDKHOME>\OpenEXR\ilmbase-1.0.1\vc\vc8\IlmBase\IlmBase.sln</tt> 
The Visual Studio Conversion Wizard dialog appears. Click Next, select option No, click Next and Finish. Unselect the option "Show the conversion log when the wizard is closed" and click Close</li>
<li>Due to the fact that the Visual Studio solutions of OpenEXR are configured to build dynamic libraries, some modifications are necessary to build the required static libraries: 

For each project in Solution Explorer open the Property Pages dialog by choosing Project > Properties. Process the following steps for Debug and Release configuration. Some of the properties are not avaliable in every project, thus continue with next step.

<ul>
<li>Choose Configuration Properties > General. For Configuration Type property choose Static Library (.lib) if Dynamic Library (.dll) was selected.
</li>
<li>Choose Configuration Properties > C/C++ > Preprocessor. In the Preprocessor Definitions entry remove defines <tt>OPENEXR_DLL</tt>, <tt>_USRDLL</tt> and <tt>*_EXPORTS</tt> (all with suffix <tt>_EXPORTS</tt>).
</li>
<li>Choose Configuration Properties > C/C++ > Code Generation. For Runtime Library property choose Multithreaded-Debug (/MTd) in Debug configuration and Multithreaded (/MT) in Release configuration.
</li>
<li>Choose Configuration Properties > C/C++ > Code Generation. For Enable Enhanced Instruction Set property choose Not Set.
</li>
<li>Choose Configuration Properties > Build Events > Post-Build Event. In Command Line entry remove the <tt>createDLL</tt> command, but keep the <tt>install*.cmd</tt> command. For example in createDLL project only the statement "<tt>..\..\..\installCreateDLL.cmd $(IntDir)</tt>" should remain, in Half project only "<tt>..\..\..\installHalf.cmd $(IntDir)</tt>" etc.
</li>
</ul>
</li>
<li>Close Property Pages dialog</li>
<li>(64-bit) Add x64 Configuration</li>
<li>Open solution file <tt><SDKHOME>\OpenEXR\openexr-1.6.1\vc\vc8\OpenEXR\OpenEXR.sln</tt> 
The Visual Studio Conversion Wizard dialog appears. Click Next, select option No, click Next and Finish. Unselect the option "Show the conversion log when the wizard is closed" and click Close</li>
<li>For project IlmImf do the same configuration property changes as in IlmBase solution described above</li>
<li>Right-click IlmImf in Solution Explorer, and then choose Properties from shortcut menu</li>
<li>In the Property Pages dialog do the following for Debug and Release configuration: 
Choose Configuration Properties > C/C++ > General. In Additional Include Directory entry enter following additional include directory:
<pre>
..\..\..\..\..\..\wxWidgets-2.8.10\src\zlib
</pre>
</li>
<li>(64-bit) Add x64 Configuration</li>
</ol>

== Enblend/Enfuse/libxmi ==
<ol>
<li>Open the file <tt><SDKHOME>\enblend-enfuse-3.2\enblend_msvc2008.sln</tt></li>
<li>Add x64 Configuration</li>
<li>Choose "File" > "New Project"</li>
<li>For the path, give it <tt><SDKHOME>\libxmi</tt> and the name of libxmi</li>
<li>In the Solution Explorer, select the new libxmi project</li>
<li>Choose "Project" > "Add Existing Item"</li>
<li>Navigate to <tt><SDKHOME>\libxmi</tt> and select all the .c and .h files</li>
<li>Click OK</li>
<li>Open <tt><SDKHOME>\libxmi\sys-defines.h</tt></li>
<li>Change the line
<pre>
#include <config.h>
<pre>
to read
<pre>
#include "config.h"
</pre></li>
<li>Close the file</li>
<li>Open <tt><SDKHOME>\libxmi\config.h</tt></li>
<li>Change the line
<pre>
#define HAVE_VALUES_H 1
</pre>
to read
<pre>
/* #undef HAVE_VALUES_H */
#define HAVE_STRERROR 1
</pre></li>
<li>Save and Close the file</li>
</ol>

{| class="wikitable" width="100%"
|-
! style="padding:5px; text-align:left" | Note
|-
| style="padding:5px; text-align:left" | Pure ASM isn't supported when compiling x64, so an SSE4/SSE4.1 intrinsics replacement is used instead, which x64 machines will support.
|}

== expat ==
<ol>
<li>Open the file <tt><SDKHOME>\expat-2.0.1\Source\expat.dsw</tt> 
A Visual C++ Project conversion dialog appears. Click "Yes To All".</li>
<li>(64-bit) Add x64 Configuration</li>
</ol>

== exiv2 ==
<ol>
<li>Open solution file <tt><SDKHOME>\exiv2-0.18.1\msvc\exiv2.sln</tt> 
The Visual Studio Conversion Wizard dialog appears. Click Next, select option No, click Next and Finish. Unselect the option "Show the conversion log when the wizard is closed" and click Close</li>
<li>Right-click exiv2lib in Solution Explorer, and then choose Properties from the shortcut menu</li>

<li>In the Property Pages dialog do the following for the Debug and Release Configuration, selecting All Platforms</li>
<ul>
<li>Choose Configuration Properties > C/C++ > General. In Additional Include Directories entry replace
<pre>
../../../zlib-1.2.3
</pre>
by
<pre>
../../../wxWidgets-2.8.10/src/zlib
</pre>
</li>
<li>(64-bit) Add x64 Configuration</li>
</ul>
</li>
<li>Close Property Pages dialog</li>
</ol>

== glew ==
<ol>
<li>Open the file <tt><SDKHOME>\glew\build\vc6\glew.dsw</tt> 
A Visual C++ Project conversion dialog appears. Click "Yes To All".</li>
<li>(64-bit) Add x64 Configuration</li>
</ol>

== Panorama Tools ==
<ol>
<li>Open solution file <tt><SDKHOME>\libpano\pano13\libpano.sln</tt> 
The Visual Studio Conversion Wizard dialog appears. Click Next, select option No, click Next and Finish. Unselect the option "Show the conversion log when the wizard is closed." and click Close</li>
</ol>

Hugin SDK (MSVC 2008) Patches

2009-05-14T12:53:55Z

Dedalus: moved Hugin SDK (MSVC 2008) Patches to Hugin SDK (MSVC 2008)/Patches: magic trick with subpages to keep related pages connected

Hugin Compiling Windows with SDK

2008-08-17T15:11:09Z

Dedalus: /* Get Tools */ http://www.cmake.org/files/v2.6/cmake-2.6.1-win32-x86.exe new version ...

This article gives step-by-step instructions for building hugin from a source code snapshot using Visual C++ 2008 Express Edition and precompiled dependencies. That is the recommended way to build hugin for Windows, and the only way that has worked for me. It also shows how to build enblend 3, which hugin now requires, with the same tools.

Bear in mind that a source snapshot of hugin is a transient stage in an incomplete and rapidly evolving package, so may have a short useful life, and will contain bugs and defects. Your main purpose in building one should be to help find, report, and maybe correct some of those.

== Background ==

The hugin build is based on cmake, a cross platform makefile generator. On Windows, cmake can generate project files for various Microsoft Visual Studio toolsets, from the same specifications it uses to create makefiles on other platforms. The current release (cmake 2.4.7) only supports VC 2003 and 2005; the unreleased 2.4.8 and the current development trunk (2.5) support VC 2008 too, so you will need one of those.

Pablo has recently published an sdk containing all the support components needed to build hugin and enblend (and AutoPano-SIFT-C) on Windows. Version 1 of the sdk has two flavors, one built with Visual C++ 2003 Express, the other with VC 2008 Express. Version 2, which is more complete, is only for VC 2008 at present.

If if you already have VC 2003 (and the corresponding Windows Platform SDK) installed you might want to try that. Otherwise use VC 2008, which is currently available and easier to install because the Platform SDK is bundled. You can install VC 2008 Express beside other Microsoft compiler versions, even professional ones, without damaging either toolset.
The enblend source tree has projects for building with both the 2003 and 2008 tools (also 2005 but there is no sdk for that).

The following instructions are for starting from scratch on a Windows PC without any software building tools installed. If you already have some of these things installed, you will need to take care that the right tools and components are used. It is vitally important that all object code is generated by the same compiler version and targeted to the same VC runtime library.

The recommended Tortoise archive clients work through the Windows File Explorer: right-click a target directory and follow the popup menus.

== Get Tools ==

1) install Visual C++ 2008 Express
http://www.microsoft.com/express/download/

2) install cmake -- not the currently released version 2.4.7, but either
version 2.4.8 (stable, works)
[http://www.cmake.org/files/v2.4/cmake-2.4.8-RC-13-win32-x86.exe 2.4.8 link to a 404 page ... 17-Aug-2008]
or version 2.5 (may not be stable)
http://www.cmake.org/HTML/Download.html
Pending release of 2.5, follow the link "nightly CVS binary" and download the .exe installer for a recent snapshot (cmake-2.5.20080117-win32-x86.exe worked for me).

version 2.6.1 (untested)
http://www.cmake.org/files/v2.6/cmake-2.6.1-win32-x86.exe

3) install Tortoise CVS and SVN clients
http://sourceforge.net/project/platformdownload.php?group_id=48103
http://sourceforge.net/project/showfiles.php?group_id=138498

== Get hugin SDK ==

4) download the precompiled sdk
http://hugin.panotools.org/sdk/MSVC/hugin_enblend_sdk_msvc2008_v2.7z
unpack it into new directory huginbase with winrar or 7zip.
NOTE The version 1 sdks, which are zip files, lack the unix utilities (unxutils) required for hugin installaiton. You get that at http://sourceforge.net/project/showfiles.php?group_id=9328.

== Build enblend 3 ==

5) check out enblend 3 source tree into huginbase. Right click on huginbase in Windows Explorer and select "CVS Checkout..." from the popup menu. Enter the following incantation into the CVSROOT: box in the resulting dialog and click OK.
:pserver:anonymous@enblend.cvs.sourceforge.net:2401/cvsroot/enblend
If OK is grayed out, click Fetch list..., select enblend module and then click OK.

The result should be a new directory, huginbase/enblend, containing the source tree.

6) open huginbase/enblend/enblend_msvc2008.sln with Visual Studio 2008 Express. Change the target configuration to 'release' (build menu, configuration manager). Click build solution. After it completes, copy enblend/INSTALLDIR into huginbase/enblend-3.1/. The hugin install script expects this directory.

== Build hugin ==

7) check out hugin source tree into huginbase. Make a new folder called hugin inside huginbase. Right click on huginbase/hugin in Windows Explorer, select "SVN Checkout...", enter this source URL, set target directory to "hugin" and click OK.
https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk

The result should be a new directory, huginbase/hugin, containing the source tree. Write down the reported SVN revision number, you will need it later.

8) Start the cmake gui (cmakesetup.exe). To ensure that the environment is set right, run cmakesetup.exe from the VC 2008 command shell (available under the Windows Start Menu) - essential if you have other compilers installed. You might want to create a desktop shortcut that does this with one click.

Set cmake's source code directory to huginbase/hugin and its build directory to huginbase/hugin-build (this will create a new directory for the build). Click Configure and tell it to use Visual C++ 2008. Cmake then checks the build tools and if that goes well does the first round of searching for components. When done it displays a list of configuration variable settings, on a red background. Click "Show Advanced Values" to display all of them.

This is when you get to correct anything that needs correcting. First, set HUGIN_WC_REVISION to the SVN revision number (which should be automatic but currently is not on Windows). And set CMAKE_BUILD_TYPE to "Release". It is an error to leave HUGIN_WC_REVISION blank, and you will get a warning message later if CMAKE_BUILD_TYPE is "Debug". Heed it.

Next, check that all component pathnames start at huginbase. Cmake may have found some things installed in standard places on your system; but it should only be using the ones in the sdk. To correct a pathname, click on it and either type in the right one or click '...' to pop a fileselector. Look out for values with "_NOT_FOUND" in them; these may indicate problems with your directory names or structure. You will need to set ENBLEND_EXE_DIR to huginbase/enblend-3.1/INSTALLDIR that that was created when you built enblend. Also, you need to set HUGIN_BUILDER and HUGIN_BUILDATE -- this is you name and date of the build that will appear on application splash screen.

When you are satisfied the paths are right, click Configure again, and Cmake will try to validate the variables. That might set some new ones, which will appear in red. Recheck all values, even the grey ones. If a variable keeps coming up wrong try deleting it from cache (right click on name pops menu) and configure again; this is often necessary to trigger a new search. Keep fixing and clicking Configure until everything is OK. Then click OK to generate the project files.

9) Open hugin.sln in the build directory with Visual Studio 2008 Express and wait while it loads and checks all the projects. Then select a target configuration and click "build solution". After a long time, and many warnings, you should get a successful build.

10) Build the INSTALL project. This should put a complete hugin installation in huginbase/hugin-build/INSTALL/FILES.

NOTE any missing file stops the install script, leaving the installation more or less incomplete. If this happens, first look at the install scripts, cmake_install.cmake (several places in the hugin-build tree) to identify all the files that were not found (paths with "_NOT_FOUND" in them). If you can find all of them, put them where the install script expects them -- hugin/cmakemodules/winbundle.cmake will help indentify those places. You can't just build INSTALL again, because the files are searched for at configuration time, so the install scripts will still contain invalid pathnames until you run cmakesetup again. Exit Visual Studio first, since all project files must be rebuilt. It may be necessary to delete pathnames of the failed places (such as enblend-3.1) from cache to ensure everything gets regenerated. Then Configure, OK, open the new hugin.sln and build INSTALL.

== Updating the hugin build ==

To update your source tree to to the latest revision, right click on huginbase/hugin in Windows Explorer and select "SVN Update". Remember to note the revision number.

Check if there is a new release of the sdk, and if so, download and install it.

Then you have to run cmakesetup again. Proceed as in 8) above, but click "Delete Cache" before "Configure", so that the new configuration gets built from scratch.

Remember to "Clean" or "Rebuild" the entire solution in MSVC.

== Installing hugin on Windows ==

Directory hugin-build/INSTALL/FILES contains a complete, self-contained hugin installation. You can use this as is, or copy it to a directory of your choice if you wish to delete the build tree (it is a good idea to put the the SVN version number in the name of that directory. e.g. FILES becomes "hugin_0.7.0.2766"). You should create a shortcut to hugin.exe on your desktop (note you can start new projects by dragging and dropping groups of files on the shortcut). You may also want to associate the new hugin.exe with the hugin project file (.pto) file extension.

This way of installing can be undone simply by deleting the files. It will not break any other hugin installation that may be on your system. However, note that all instances of hugin do share the same persistent settings, so options you set in one version will affect the others, too.

The source tree and sdk contain support for building Windows Installer (.msi) packages with War Setup and/or Innosetup. At present these are under development and could potentially damage your Registry and/or prior installations of hugin, so I would advise not using them until a stable release is issued.

The hugin team periodically publishes "snapshot" builds for testing. The Windows versions of these come in two forms, as a self-installing archive that automates the simple "copy files" method described above, and as a Windows Installer package.

== Some things that don't work ==

Trying to target the dll versions of the Visual C runtimes. Only the static C libraries (libcmt, libcmtd) will do. You can't mix static and dll runtimes, so all (static) dependencies must also have been compiled with /MT or /MTd. While it might be possible to use dll versions of some of the support libraries, such as tiff or OpenEXR, it is safest to keep a strict policy of "static libraries only".

Trying to use dependencies built with a different compiler. For all practical purposes, Microsoft runtime libraries are now usable with only one compiler version. Although linking code built with more than one compiler sometimes seems to work, the resulting program is likely to fail.

Trying to link Boost libraries of a different source version than the Boost headers. Boost takes some trouble to lock object code to source version as well as compiler version, so it is rarely possible (and always a mistake) to do this.

Occasionally a build step fails mysteriously, that has succeeded before. The main cause of this is a file being marked in the Windows filesystem as in use when a tool tries to open it. On a slow, heavily loaded machine, the filesystem may not update a closed file's status quickly enough -- solution: reduce the load. On any machine, Google Desktop Search (or other automatic indexer) may grab a recently updated file and really have it open -- solution: pause or disable indexing and retry the build step.

--[[User:Tksharpless|Tksharpless]] 16:42, 23 January 2008 (CET)

[[Category:Software:Hugin]]
[[Category:Software:Platform:Windows]]

Talk:Hugin Compiling Windows with SDK

2008-08-17T15:07:31Z

Dedalus: New section: 1) install Visual C++ 2008 Express

TortoiseSVN has a tool called SubWCRev. Quoting from the help file:

<code>
SubWCRev is Windows console program which can be used to read the status of a Subversion working copy and optionally perform keyword substitution in a template file.
</code>

<code>
SubWCRev reads the Subversion status of all files in a working copy, excluding externals by default. It records the highest commit revision number found, and the commit timestamp of that revision, It also records whether there are local modifications in the working copy, or mixed update revisions.
</code>

<code>
If you want SubWCRev to perform keyword substitution, so that fields like repository revision and URL are saved to a text file, you need to supply a template file SrcVersionFile and an output file DstVersionFile which contains the substituted version of the template.
</code>

Full details can be found [http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-subwcrev.html here]

Does anyone else think it is worth the effort to be incorporated into Windows build process? This will improve "fool-profeness" of test build, as the executable will always be traceable back to the SVN revision and one of CMake config parameters can be eliminated. I'm yet not proficient enough in the current toolchain to do this myself, but eager to help in testing, etc.

--[[User:MaximTee|MaximTee]] 17:50, 16 March 2008 (CET)

== 1) install Visual C++ 2008 Express ==

The Microsoft site asks to install Silverlight first. Done. After downloading Visual C++ 200 Express (vcsetup.exe) trying to install. Setup discovers (on my machine) a previous install of Visual Studio 2008 that must be updated to SP1 before installation can proceed. Trying to fetch that SP1 - estimated download time over 20 minutes on my relatively fast ADSL line. [[User:Dedalus|Dedalus]] 17:07, 17 August 2008 (CEST)

Talk:Build pano12 from sourcecode

2008-08-16T22:40:37Z

Dedalus: checking for jpeg_read_header in -ljpeg... no

Trying to build pano12 on Vista. I had to copy some .manifest files in the /bin directory to grant permission to run /bin/install.
The ./configure for libpano gets stuck with this error: 
checking for JPEG support ... 
configure: jpeg home set to /usr/local 
checking jpeglib.h usability... yes 
checking jpeglib.h presence... yes 
checking for jpeglib.h... yes 
checking for jpeg_read_header in -ljpeg... no 
checking for JPEG library is version 6b or later... yes 
checking if JPEG package is complete... no -- some components failed test 
configure: error: 
the jpeg library must be installed on your system 
but configure could not find it. 

I can't figure out what is wrong .. Anyone an idea?
[[User:Dedalus|Dedalus]] 00:40, 17 August 2008 (CEST)

Talk:Lens correction model

2008-07-16T11:00:51Z

Dedalus: /* Kannala and Brandt */ @Erik

For (circular) fish eye lenses another way to model the lens (distortion) is:
r = a sin (b*theta)
where r is the distance from the center of the camera image to the point of interest, theta is the angle between the central axis of
the fisheye lens and the line to the point of interest in the real image, a is a scale factor, in these cases to convert from angle
in space to millimeters in the image plane, and b is the radial mapping parameter. (It should be noted that b effects a very
strongly.) The theoretical fisheye map of r = a*theta is approached as b approaches zero. The perfect fish eye lens is F-Theta mapping so to say, while rectilinear lenses do f tan(theta) mapping.

:We have a page about fisheye mapping as well: [[Fisheye Projection]] which mentions the sine mapping, too.--[[User:Erik Krause|Erik Krause]] 21:02, 10 July 2008 (CEST)

I copied these ideas from: [http://www.360vr.com/fisheye41/coastal-fisheyep.pdf Fisheye lens designs and their relative performance] by James “Jay” Kumler, Martin Bauer from Coastal Optical Systems and Internet Pictures Corporation.

They've estimated a and b for example for the Peleng as 23.8 and 0.34 which would imply if my computations are correct a=0,001691363 b=-0,051282569 c=0,000469245 and (1-(a+b+c))=1,049118709 in the Fish eye quartic distortion model. However given parameters of the sinus model above with r in millimeters from the sensor of the image, that can be easily renormalized to pixels on a cropped sensor.

The article cited discusses also "relative illumination" or vignetting as we speak. They have found this to be dependent on f-number, higher f-numbers producing greater uniformity, or less severe vignetting.

== Kannala and Brandt ==

Kannala and Brandt have researched correction models for fish eye lenses, see http://www.ee.oulu.fi/~jkannala/calibration/Kannala_Brandt_calibration.pdf

:Interresting reading! However, panotools lens correction model already takes fisheye mapping into account. It works quite well. Even very non-standard mappings like the Nikkor 10.5 fisheye can be corrected. See [http://michel.thoby.free.fr/Blur_Panorama/Nikkor10-5mm_or_Sigma8mm/Sigma_or_Nikkor/Comparison_Short_Version_Eng.html] for details.--[[User:Erik Krause|Erik Krause]] 21:02, 10 July 2008 (CEST)
::[[General lens model|Fish eye]] projections could be equidistance, equisolid angle or orthogonal. The Peleng is something in between equidistance and equisolid. I know panotools (hugin) handles fisheye mapping, that is, equidistance mapping. However, the panotools (hugin) lens correction model only takes radial distortion into account, not any tangential distortion due to misalignment of lens elements. I'll have a look at the paper you reference. [[User:Dedalus|Dedalus]] 13:00, 16 July 2008 (CEST)

Talk:Chromatic aberration

2008-07-16T10:54:34Z

Dedalus: /* Great article on LCA/TCA */

==Strange Example==
In the strange example on the page are we perhaps seeing chromatic aberration of longer wavelength red (approaching near IR)? Most plants reflect a lot of longwave red (as made obvious in IR photographs of plants)... this would explain why correction for the plant would cause more problems for red elsewhere in the image. I'd only expect to see this if the error of the lens was fairly steep with respect to wavelength, but that wouldn't be shocking if the lens was designed for a sensor (film?) with less NIR response. --[[User:Gmaxwell|Gmaxwell]] 05:33, 30 October 2006 (CET)

== Great article on LCA/TCA ==

I found http://www.vsg.dcu.ie/papers/prl_2007_chrom.pdf an article to measure and correct LCA/TCA chromatic aberration. Based on a fundamental model it measures CA on a test image (chess board pattern) to calibrate a lens. [[User:Dedalus|Dedalus]] 22:59, 6 July 2008 (CEST)

:The upcoming [[hugin]] package will contain a tool to automatically determine TCA correction parameters ([[tca_correct]]) to be use with [[fulla]] to correct TCA. Unfortunately I don't know enough about it to write something... --[[User:Erik Krause|Erik Krause]] 21:54, 10 July 2008 (CEST)

::As far as I know tca_correct only takes radial TCA into account, while the paper takes asymmetric distortion due to misalignment of lens elements into account as well (so called tangential distortion). [[User:Dedalus|Dedalus]] 12:54, 16 July 2008 (CEST)

General lens model

2008-07-16T09:55:35Z

Dedalus: generic models

General lens model are based on mathematical descriptions of ideal projections.
In the radially symmetric models below theta (θ) is the angle between view ray and optical axis.
Next to the model name mathematical descriptions in three colums. Firstly the ideal projection, secondly a two parameter polynomial estimation using odd powers of theta only (based on Kannala and Brandt), thirdly a ''one'' parameter (catadioptric) model due to Ying and Hu. A rough estimate for the popular Peleng 8mm lens has been added, based on calibration by Kumler and Bauer.

{| class="prettytable"
| '''model name'''
| '''ideal projection'''
| <math>r = k_{1}\theta+k_{2}\theta^3</math>
| <math> r = \frac {(l+1) \sin \theta}{l+\cos \theta}</math>
|-
| perspective projection(pinhole camera )
| <math>r = f \tan \theta </math>
| <math>r = \theta+\frac{1}{3}\theta^3</math>
| <math> l = 0 </math>
|-
| stereographic projection
| <math>r = 2 f \tan(\theta/2)</math>
| <math>r = \theta+\frac{1}{12}\theta^3</math>
| <math> l = 1 </math>
|-
| equidistance projection
| <math>r = f</math>
| 1
| <math> l = </math>
|-
| Peleng
| <math>r = 3f \sin (\theta/3)</math>
| <math>r = \theta-\frac{1}{54}\theta^3</math>
| <math> l = \frac{19}{8} </math>
|-
| quisolid angle projection
| <math>r = 2 f \sin(\theta/2)</math>
| <math>r = \theta-\frac{1}{24}\theta^3</math>
|| <math> l = \frac{527}{259} </math>
|-
| orthogonal projection
| <math>r = f \sin (\theta)</math>
| <math>r = \theta-\frac{1}{6}\theta^3</math>
| <math> l = \infty </math>
|}

A ''one'' parameter generic lens model might be handy in optimizing panorama's for example [[hugin]] to have an independent initial check based on the control points of multiple images what kind of lens really is used, and providing an initial estimate for multiple parameter models, like the well known a, b, c [[lens correction model]]. The table above suggests to set a and c always to zero, and only use b, as a and c represent ''even'' powers.

Apart from radial distortion of the ideal model - producing [[barrel distortion]] - most lenses will show tangential distortion, or asymmetric distortion, mainly due to not all elements in the lens being exactly aligned with the optical axis.

==references==
[http://www.ee.oulu.fi/mvg/files/pdf/pdf_697.pdf Kannala and Brandt 1]
[http://www.ee.oulu.fi/~jkannala/publications/visapp2008.pdf K&B 2, citing Ying and Hu]
[http://www.360vr.com/fisheye41/coastal-fisheyep.pdf Kumler and Bauer]

General lens model

2008-07-16T09:14:22Z

Dedalus: New page: General lens model are based on mathematical descriptions of ideal projections. In the radially symmetric models below theta (θ) is the angle between view ray and optical axis. {| | '''m...

General lens model are based on mathematical descriptions of ideal projections.
In the radially symmetric models below theta (θ) is the angle between view ray and optical axis.

{|
| '''model name'''
| '''ideal projection'''
| <math>r = k_{1}\theta+k_{2}\theta^3</math>
| <math> r = \frac {(l+1) \sin \theta}{l+\cos \theta}</math>
|-
| perspective projection(pinhole camera )
| <math>r = f \tan \theta </math>
| <math>r = \theta+\frac{1}{3}\theta^3</math>
|-
| stereographic projection
| <math>r = 2 f \tan(\theta/2)</math>
| <math>r = \theta+\frac{1}{12}\theta^3</math>
|-
| equidistance projection
| <math>r = f</math>
|-
| quisolid angle projection
| <math>r = 2 f \sin(\theta/2)</math>
|-
| Peleng
| <math>r = f \sin (b\theta)</math>
|-
| orthogonal projection
| <math>r = f \sin (\theta)</math>
|}

Talk:Lens correction model

2008-07-09T15:49:40Z

Dedalus: New section: Kannala and Brandt

Talk:Lens correction model

2008-07-08T21:55:45Z

Dedalus: r = a sin (b*theta)

Talk:Chromatic aberration

2008-07-06T20:59:48Z

Dedalus: New section: Great article on LCA/TCA

User talk:Markdfink

2006-11-11T08:16:51Z

Dedalus: the call for volunteers for the moderator position?

"the call for volunteers for the moderator position" I got per e-mail is probably not for this wiki. [[User:Dedalus|Dedalus]] 09:16, 11 November 2006 (CET)

Fulla

2006-09-11T19:52:55Z

Dedalus: /* Windows batch usage */ batch example

'''fulla''' is a command-line tool distributed with [[hugin]] 0.6 and later. It is suitable for batch correction of:

* [[Chromatic aberration]]: See a full tutorial, [http://hugin.sourceforge.net/tutorials/tca/en.shtml Correcting TCA with hugin and fulla].

* [[Lens correction model|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.

'''fulla''' can work with the same range of image types as [[nona]], including 8bit and 16bit [[TIFF]] and 32bit floating-point [[HDR]] TIFF data.

== Command-line usage ==

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

== Windows batch usage ==

Once you have calculated fulla parameters as described above, you can create a custom ''droplet''
for batch correcting photos like so:

* Create a ''Shortcut to fulla.exe'' by dragging the '''fulla''' icon to another directory in Windows explorer
* Edit ''properties''
* Change the ''target'' to include your correction parameters:

"C:\Program Files\hugin\fulla.exe" -r 0:0:0.00056:1.00015 -b 0:0:-0.00026:1.0011 -c 1:0.20:-0.51:0.2

* Rename the shortcut to something descriptive like ''fulla-peleng''
* Now you can correct photos by dragging and dropping them onto the icon

Expanding on the above example is to create a batchfile in the hugin directory called "fulla.bat" containing the line:
FOR %%I IN (%1) DO C:\Program Files\hugin\fulla.exe -p -v -l Standard %%1
Assuming the name of the lens in the PTLens Database (see below) is "Standard" (as most are). Now, upon calling from any directory containing pics you can run "C:\Program Files\hugin\fulla.bat *.jpg" having fulla correcting all pics using the parameters retrieved from the PTLens Database mentioned below (don't forget to SET PTLENS_PROFILE)

== PTLens database lookup ==

'''fulla''' will look-up your camera in a [[PTLens]] database and try to automatically determine [[Lens correction model|Lens correction parameters]] for your pictures. An older free version of the database is required which can be [http://sourceforge.net/project/showfiles.php?group_id=77506&package_id=187932 downloaded from sourceforge].

Use the PTLENS_PROFILE environment variable to specify the location of the PTLens database, for example on Linux or OS X:

PTLENS_PROFILE=$HOME/.ptlens/profile.txt

On Windows something like this (untested) should work:

set PTLENS_PROFILE=%HOMEPATH%\PTLens\profile.txt

[[Category:Software:Platform:Linux]]
[[Category:Software:Platform:Windows]]
[[Category:Software:Platform:Mac OS X]]

HP Photosmart M417

2006-08-26T14:24:30Z

Dedalus: the other parameters

A small 5 megapixel camera from Hewlett Packard.
Zoomlens 6.25 to 17.25 mm (though it advertises a 3x zoom).
The sensor is a factor 6.02 smaller than SLR film
Lensparameters:
{|
| '''focallength'''
| ''' a '''
| ''' b '''
| ''' c '''
|-
| 6.25 mm
| +0.00000
| -0.01837
| +0.00000
|-
| 7.83 mm
| 0
| -0.00611
| 0
|-
| 9.37 mm
| 0
| -0.00523
| 0
|-
| 11.63 mm
| 0
| -0.00173
| 0
|-
| 13.97 mm
| 0
| -0.00074
| 0
|-
| 17.25 mm
| 0
| -0.00054
| 0
|}

HP Photosmart M417

2006-08-25T11:34:31Z

Dedalus: lensparameters

Cameras

2006-08-25T11:28:47Z

Dedalus:

List here your camera
----
[[HP Photosmart M417]]

----
OK - I guess I'll start :)
I've got 2 camera's, a [http://www.dpreview.com/reviews/specs/Pentax/pentax_optios.asp Pentax Optio S] for portability on long hikes and the like and a [http://www.dpreview.com/reviews/specs/Canon/canon_eos20d.asp Canon 20D] for everything else.

The Pentax shows minor barrel distortion at the widest side, so I have to correct for this a bit. Here's an example from 15 images (3 mpix each) from the Pentax. It's ~ 370 degrees by 45 degrees

http://tautologous.com/gallery2/d/3540-6/bald_mountain_med.jpg

The Canon 20D takes huge images (8 MPix) and thus the processing time and computer hardware requirements are a lot more.

[[User:Jeff|Jeff]] 12:18, 10 Dec 2004 (EST)

Hugin FAQ

2006-08-18T07:17:59Z

Dedalus: /* How do I straighten a curved horizon? */ typos

== General Questions ==

== Control Point creation ==

=== How do I add control points ===
The [[control points]] editor is quite powerful, but its usage is probably not obvious on the first try. Here are some ways the developers use the Control Point panel:

1. Selecting control points in 100% zoom.

This method needs some scrolling, if big images are used. You might want to try the fit to window zoom setting in that case. Switch to the Control Points tab, and use the following settings:

Zoom: 100%
[X] auto fine tune
[X] auto add
[X] auto estimate

Click on a prominent feature in the left image. If the image pair already contains control points, [[hugin]] will try to select the point in the other image. If its the first point in this pair, click near the same feature on the right image. The second point will be placed and fine tuned automatically. If you are not happy with the placement, both points can be moved by dragging them to a better position. Press the "f" key to fine tune the point in a small area.

2. Selecting control points in fit to window mode.

I uses this mode if I need to set points on big images. Switch to the Control Points tab, and use the following settings:

Zoom: fit to window
[X] auto fine tune
[ ] auto add
[X] auto estimate

Click on left image. The image will be shown in 100% view. Within the detailed view, click on a prominent feature. If the image pair already contains control points, hugin will try to select the point in the other image. If its the first point in this pair, click near the same feature on the right image. The point will be placed and fine tuned automatically. If you are not happy with the placement, both points can be moved by clicking at the desired position. Move the point close to the desired feature and press the "f" key to fine tune the point. When the points are on the same feature, press the right mouse button, or press the "a" key to add the control point pair. It will then be shown in the list below the image.

=== How do I scroll both images at the same time? ===

Try pressing the shift key while moving the mouse. The control key or the middle mouse button can be used to scroll only the image under the mouse cursor.

== Common problems when creating a panorama ==

=== How do I straighten a curved horizon? ===
If the panorama looks nice but the horizon is curved, there are two ways to improve the image and straighten the horizon. First, try optimizing the view by selecting "Positions and View" as the optimization mode and run the optimizer afterwards. By clicking "Calculate Field of View" in the "Stitcher" tab and displaying the preview window afterwards you can check if the image has been improved.

If it is still curved, you have to add vertical guide control points in the "Control Points" tab. Usually two [[vertical control points]] are enough to straighten the horizon nicely. Often edges of buildings, poles or other man made structures provide good vertical lines. To add a vertical control point, switch to the control point editor and select the same image on both sides. Place a control point on the left image on the upper area of the vertical feature. In the right image, select a control point on the lower area of the features, and press the Add button. Once the new point has been added, its type should automatically switch to "vertical line". You might want to switch off the auto-add and auto-estimate options while doing this to avoid naggy dialogs while adding this guide points.

Two points that are roughly 90 degrees apart provide the best effect.

See also the related perspecitve correction tutorials: [http://hugin.sourceforge.net/tutorials/architectural/en.shtml hugin tutorial on perspective correction], [[Perspective correction]], [[Leveling a Finished Panorama]]. While these are concerned with correction of the perspective in one image, the same technique can be used for
leveling a panorama.

== Postprocessing ==

=== Why is the ICC profile of my input images not preserved? ===

Since hugin 0.5 and enblend 2.4 ICC profiles in the input files are transfered to the output panorama. Please update to a current version.

=== How can I postprocess the image using multiple layers in The Gimp? ===

Unfortunately, The [[Gimp]] can't read [[PSD]] formatted files generated by [[PTStitcher]], and the multiple [[TIFF]] output it produces is cumbersome to use. There are two possibilities to work around this:

*Use the [[nona]] stitcher, to output to a multilayer TIFF format.
This will will produce a multi_layer.tif file, that contains all remapped images, cropped to their bounding box. This will save a lot of space, compared to a "traditional" PTStitcher layered output file, where all layers have the full panorama size.

Unfortunately, The Gimp 1.2 and 1.3 can't load multilayer TIFF files. Please use Gimp 2.0 or later.

*If you need [[PTStitcher]] features not supported by nona, you can also use [[tif2xcf]], to combine the multiple TIFF output into a multilayer XCF.
Unfortunately this requires a lot of memory because it stores each remapped image in a layer with the size of the final panorama.

User:Dedalus

2006-08-15T11:07:49Z

Dedalus: me

[[w:nl:Gebruiker:Dedalus|Dedalus]]

Lens correction model

2006-08-15T11:07:06Z

Dedalus: /* Lens distortion a, b & c parameters */ more math formulas

== Lens correction model ==

The panorama tools have a very flexible model to correct for typical geometrical lens errors. Even better, it can often even estimate the correction parameters directly from the images in a panorama.

There are a total of 6 parameters that have to do with lens correction.
* First of all there is the lens [[Field of View]] (FoV) - not exactly an error, but a parameter that determines the image perspective distortion.
* The actual lens correction parameters '''a''', '''b''' and '''c''' which are used to correct for [[barrel distortion]], [[pincushion distortion]] and even [[wavy distortion]].
* The lens shift parameters '''d''' and '''e''' that correct for the lens [[optical axis]] not being in the image center.

Two more parameters correct for image errors that are not induced by the lens but by a scanner or scanning camera for example. These are the shear parameters '''f''' and '''g'''.

=== Field of View ===

The [[Focal Length]] is a physical property of the lens. Together with the effective sensor or film size and the focusing distance it approximates the image [[Field of view]] (there are other factors that influence it). '''Caution''': Cropping the image changes the Field of View. If you need to crop your source images for a panorama, crop them all to the same size!

The Field of View together with the lens projection ([[Rectilinear Projection|rectilinear]], [[Fisheye Projection|fisheye]] or [[Cylindrical Projection|cylindrical]] for swing lens cameras) determine the image [[perspective distortion]]. Perspective distortion is less with a smaller Field of View. See Helmut Dersch page [http://www.path.unimelb.edu.au/~dersch/perspective/Wide_Angle_Perspective.html] for details about different wide angle perspectives.

=== Lens distortion a, b & c parameters ===

For perfect [[Rectilinear Projection|rectilinear]] camera optics, all you would need to know is the field of view. Perfect results could be achieved by simply mapping pixels in the image to the [[tangent plane]]. Real lenses deviate from this perfect tangent plane projection. The deviations push and pull fixed points in the scene away from where they would have fallen. Luckily, rather than arbitrary pushes and pulls, almost all deviations occur radially, towards or away from some common center, and luckily the deviation amount is almost the same at a given radius around that center. Hence a model that corrects for this deviation based on the radius gives pretty good results.

The [[lens distortion]] '''a''', '''b''' and '''c''' parameters correspond to a third degree polynomial describing radial lens distortion:
:<math>
r_{src} = ({a}r_{dest}^3+{b}r_{dest}^2+{c}r_{dest}+d)r_{dest}
</math>

where <math>r_{dest}</math> and <math>r_{src}</math> refer to the normalized radius of an image pixel. The center point of this radius is where the [[optical axis]] hits the image - normally the image center. Normalized means here that the largest circle that completely fits into an image is said to have radius=1.0 . (In other words, radius=1.0 is half the smaller side of the image.) A perfect lens would have '''a'''='''b'''='''c'''=0.0 and '''d'''=1.0 which resolves into <math>r_{src} = r_{dest}</math>.

Sometimes the above formula is written as
:<math>
r_{src} = {a}r_{dest}^4+{b}r_{dest}^4+{c}r_{dest}^2+d{r_{dest}}
</math>

which is essentially the same.

Usual values for '''a''', '''b''' and '''c''' are below 1.0, in most cases below 0.01. Too high values suggest that you chose a wrong lens type, f.e. fisheye instead of rectilinear or vice versa. This refers to the absolute values of course since '''a''', '''b''' and '''c''' can be positive or negative (f.e. both 4.5 and -4.5 are considered too high values).

The fourth parameter ('''d''') is only available in the [[Panorama Tools Plugins#Radial_Shift|Correct, Radial Shift]] filter of the [[Panorama Tools Plugins]]. It controls the result image size and is calculated implicitly by [[pano12]] (used by PTOptimizer, PTStitcher and the GUIs) in order to keep the same image size:

:<math>
d = 1 - (a+b+c)
</math>

Hence it is not available in the different [[GUI front-ends]] (you can see it in the PTOptimizer result script).

Unfortunately a different parameter also named '''d''' refers to image shift in PTStitcher and PTOptimizer scripts and the GUIs. This sometimes causes confusion. (See more discussion below.)

This polynomial approach is never exact, but can give a pretty good approximation to the real behaviour of a given lens. If you need better correction you must use a distortion matrix, as used by '''Distortion Remove''' (see link below).

==== Lens distortion and fisheyes ====

Unlike rectilinear lenses, fish-eye lenses do not follow the tangent-plane geometry, but instead have ''built-in'' distortions designed to achieve wide fields of view. The radial lens distortion parameters are used the same way for rectilinear lenses and [[Fisheyes|fisheye lenses]], but they should never be used to attempt to remap a fisheye to a rectilinear image. This is done by selecting the proper source and destination projection. Fisheye geometry follows a rapidly-changing trigonometric function which can hardly be approximated by a third degree polynomial.

For fisheyes, the lens correction parameters correct for the deviation between a real lens and the [[Fisheye Projection|ideal fisheye geometry]].

=== Lens or image shift d & e parameters ===

Sometimes a lens and image sensor might not be centered with respect to each other. In this case the [[optical axis]] doesn't fall on the image center. This is particularly the case for scanned images where you never can say whether the film is centered on the scanner or not.

If the above lens correction algorithm is used on such images both lens correction and perspective correction work on the wrong center point. The lens shift parameters '''d''' (horizontal shift) and '''e''' (vertical shift) compensate for that problem. They contain values in pixel units which determine how far the center for radial correction is shifted outside the geometrical image center.

=== Image shear f & g parameters ===

Image shear is not a [[lens distortion]] but nevertheless is part of the panotools lens correction model. It corrects for a distortion induced by scanners or scanning cameras that causes a rectangular image being sheared to the form of a parallelogram (one side of the images is shifted parallel to the opposite side)

=== Determine lens correction ===

'''a''', '''b''', '''c''' and '''FoV''' are physical properties of a lens/camera-combination at a given focus distance. If you always shoot at the same focus setting, f.e. infinity or the [[Depth of Field#Hyperfocal_distance|hyperfocal distance]], then you can safely reuse the parameters. At different focus settings, '''FoV''' will change noticeably, but usually it is fineto reuse '''a''', '''b''', and '''c''' even then.

There are a number of ways to determine the a, b, c and [[field of view|fov]]
parameters for a particular lens/camera combination:

* Taking a single photograph of a subject containing straight lines, defining one or more sets of [[straight line control points]] (types t3, t4, etc.), and optimising for just a, b, c. You need to set the output format to [[Rectilinear Projection]] for this technique to work. This method is used by the author of [[PTLens]].

* Taking a single photograph of a rectangular object, selecting lots of [[horizontal control points|horizontal]] and [[vertical control points]], then optimising [[roll]], [[pitch]], [[yaw]], [[field of view|fov]], a, b & c. You need to set the output format to [[Rectilinear Projection]] for this technique to work. The process is similar to this [http://hugin.sourceforge.net/tutorials/architectural/ hugin architectural tutorial]:

* Taking two or more overlapping photographs and selecting lots of normal control points, then optimising [[roll]], [[pitch]], [[yaw]], [[field of view|fov]], a, b & c. This technique works with any output [[Projections|projection format]] but requires [[parallax]] free images shot exactly from the [[Nodal Point]]. Note that to get a precise measure of the [[field of view]], you have to take a full 360 degree panorama.

* Using a tool such as [[PTLens]] or [[clens]] to read the [[JPEG]] [[EXIF]] data and correct the image automatically by looking up the lens in an existing database.

=== Optimize for lens correction ===

If you optimize for lens correction in order to calibrate your lens you should keep some facts in mind:

Since lens correction parameters are determined by evaluating the distortion at different radius values you should provide enough control points at a large range of radii from the image center.
* If you use a rectangular pattern or straight lines for that task, make sure you set control points in all distances from the center.
* If you use two or more images make sure you overlap regions with large potential distortion (f.e. the corners) with regions with low possible distortion (f.e. the center). An only horizontal overlap would do, but use at least 50% in order to overlap the image center of one image with the border of the other.

'''a''', '''b''' and '''c''' parameters influence [[Field of View]], especially for images in landscape orientation but slightly for portrait oriented ones, too. This is because although the implicit calculation of the fourth polynomial parameter tries to keep the image at the same size, this is only possible at the radius '''r_src''' = 1.0.

Outside this radius, especially in the image corners, the size and hence the Field of View might differ. Since they are interconnected in this way, you should always allow the optimization for FoV too, if you optimize for '''a''', '''b''' and '''c''' with more than one image. (You cannot optimize for FoV with only one image). As noted above you need a full 360 degree panorama in order to get an accurate measure of the [[field of view]].

The '''a''' and '''c''' parameters control more complex forms of distortion. In most cases it will be enough to optimize for the '''b''' parameter only, which is good at correcting normal [[barrel distortion]] and [[pincushion distortion]].

If you want to see how changing the parameters influences distortion correction go to http://www.4pi.org/downloads/ and get '''abc.xls'''. Don't deactivate macros on loading.

See also [http://www.path.unimelb.edu.au/~dersch/barrel/barrel.html Helmut Dersch's barrel distortion page].

There's an excellent tutorial on how to optimize by John Houghton: [http://homepage.ntlworld.com/j.houghton/optitute.htm]

=== Tools to correct barrel and pincushion distortion ===

* The original [[PTStitcher]] can be scripted to batch process images with known a, b & c parameters. It can also be operated with one of the [[GUI front-ends]].

* [[nona]] or [[nona_gui]] (both part of the [[hugin]] distribution) can be used identically to [[PTStitcher]].

* The [[Panorama_Tools_Plugins#Radial_Shift|Correct Radial Shift]] filter in the [[Panorama Tools Plugins]] for the [[gimp]] or [[photoshop]] uses the same a, b & c parameters as [[PTStitcher]]. Note that it doesn't know about d & e shift parameters and uses 'd' as an overall scaling factor instead, which should be d = 1-(a+b+c) to keep the image roughly the same size. If you need to shift the correction center like with the d & e parameter you must combine it with [[Panorama_Tools_Plugins#Vertical_Shift_.26_Horizontal_Shift|Vertical Shift]] and/or [[Panorama_Tools_Plugins#Vertical_Shift_.26_Horizontal_Shift|Horizontal Shift]].

* [[PTLens]] is a [[Photoshop]] plugin and a stand-alone Windows tool that uses the same a, b & c parameters and comes with a database of popular lenses.

* [[Clens]] is a command line version of [[PTLens]].

* [[fulla]] is a command-line tool that uses the same a, b, c & d parameters to correct [[barrel distortion]]. It can also correct [[chromatic aberration]] and [[vignetting]] at the same time.

* [[PTShift]] determines different a, b & c parameters for the three color channels in order to correct for [[Chromatic aberration]] with the [[Panorama_Tools_Plugins#Radial_Shift|Correct Radial Shift]] filter.

* [[Gimp wideangle plugin]] uses a different formula altogether to correct distortion.

* [[Gimp phfluuh plugin]] is another tool that corrects lens distortion using yet another formula.

* [[CamChecker]] is a tool for automatically determining lens distortion and generates a different set of parameters from everything else.

* [[zhang_undistort]] is a tool distributed with [[hugin]] that uses [[CamChecker]] parameters to actually correct distortion.

* [[Distortion Remove]] uses a completely different approach with a distortion matrix. Page in german only: http://www.stoske.de/digicam/Artikel/verzeichnung.html

[[Category:Glossary]]

Lens correction model

2006-08-15T10:17:44Z

Dedalus: /* Lens distortion a, b & c parameters */ formula using <math>

== Lens correction model ==

The panorama tools have a very flexible model to correct for typical geometrical lens errors. Even better, it can often even estimate the correction parameters directly from the images in a panorama.

There are a total of 6 parameters that have to do with lens correction.
* First of all there is the lens [[Field of View]] (FoV) - not exactly an error, but a parameter that determines the image perspective distortion.
* The actual lens correction parameters '''a''', '''b''' and '''c''' which are used to correct for [[barrel distortion]], [[pincushion distortion]] and even [[wavy distortion]].
* The lens shift parameters '''d''' and '''e''' that correct for the lens [[optical axis]] not being in the image center.

Two more parameters correct for image errors that are not induced by the lens but by a scanner or scanning camera for example. These are the shear parameters '''f''' and '''g'''.

=== Field of View ===

The [[Focal Length]] is a physical property of the lens. Together with the effective sensor or film size and the focusing distance it approximates the image [[Field of view]] (there are other factors that influence it). '''Caution''': Cropping the image changes the Field of View. If you need to crop your source images for a panorama, crop them all to the same size!

The Field of View together with the lens projection ([[Rectilinear Projection|rectilinear]], [[Fisheye Projection|fisheye]] or [[Cylindrical Projection|cylindrical]] for swing lens cameras) determine the image [[perspective distortion]]. Perspective distortion is less with a smaller Field of View. See Helmut Dersch page [http://www.path.unimelb.edu.au/~dersch/perspective/Wide_Angle_Perspective.html] for details about different wide angle perspectives.

=== Lens distortion a, b & c parameters ===

For perfect [[Rectilinear Projection|rectilinear]] camera optics, all you would need to know is the field of view. Perfect results could be achieved by simply mapping pixels in the image to the [[tangent plane]]. Real lenses deviate from this perfect tangent plane projection. The deviations push and pull fixed points in the scene away from where they would have fallen. Luckily, rather than arbitrary pushes and pulls, almost all deviations occur radially, towards or away from some common center, and luckily the deviation amount is almost the same at a given radius around that center. Hence a model that corrects for this deviation based on the radius gives pretty good results.

The [[lens distortion]] '''a''', '''b''' and '''c''' parameters correspond to a third degree polynomial describing radial lens distortion: <pre>r_src = (a*r_dest^3 + b*r_dest^2 + c*r_dest + d) * r_dest</pre>

:<math>
r_{src} = ({a}r_{dest}^3+{b}r_{dest}^2+{c}r_{dest}+d)r_{dest}
</math>

where '''r_dest''' and '''r_src''' refer to the normalized radius of an image pixel. The center point of this radius is where the [[optical axis]] hits the image - normally the image center. Normalized means here that the largest circle that completely fits into an image is said to have radius=1.0 . (In other words, radius=1.0 is half the smaller side of the image.) A perfect lens would have '''a'''='''b'''='''c'''=0.0 and '''d'''=1.0 which resolves into '''r_src'''='''r_dest'''.

Sometimes the above formula is written as <pre>r_src = a*r_dest^4 + b*r_dest^3 + c*r_dest^2 + d*r_dest</pre> which is essentially the same.

Usual values for '''a''', '''b''' and '''c''' are below 1.0, in most cases below 0.01. Too high values suggest that you chose a wrong lens type, f.e. fisheye instead of rectilinear or vice versa. This refers to the absolute values of course since '''a''', '''b''' and '''c''' can be positive or negative (f.e. both 4.5 and -4.5 are considered too high values).

The fourth parameter ('''d''') is only available in the [[Panorama Tools Plugins#Radial_Shift|Correct, Radial Shift]] filter of the [[Panorama Tools Plugins]]. It controls the result image size and is calculated implicitly by [[pano12]] (used by PTOptimizer, PTStitcher and the GUIs) in order to keep the same image size: <pre>d = 1-(a+b+c)</pre> Hence it is not available in the different [[GUI front-ends]] (you can see it in the PTOptimizer result script).

Unfortunately a different parameter also named '''d''' refers to image shift in PTStitcher and PTOptimizer scripts and the GUIs. This sometimes causes confusion. (See more discussion below.)

This polynomial approach is never exact, but can give a pretty good approximation to the real behaviour of a given lens. If you need better correction you must use a distortion matrix, as used by '''Distortion Remove''' (see link below).

==== Lens distortion and fisheyes ====

Unlike rectilinear lenses, fish-eye lenses do not follow the tangent-plane geometry, but instead have ''built-in'' distortions designed to achieve wide fields of view. The radial lens distortion parameters are used the same way for rectilinear lenses and [[Fisheyes|fisheye lenses]], but they should never be used to attempt to remap a fisheye to a rectilinear image. This is done by selecting the proper source and destination projection. Fisheye geometry follows a rapidly-changing trigonometric function which can hardly be approximated by a third degree polynomial.

For fisheyes, the lens correction parameters correct for the deviation between a real lens and the [[Fisheye Projection|ideal fisheye geometry]].

=== Lens or image shift d & e parameters ===

Sometimes a lens and image sensor might not be centered with respect to each other. In this case the [[optical axis]] doesn't fall on the image center. This is particularly the case for scanned images where you never can say whether the film is centered on the scanner or not.

If the above lens correction algorithm is used on such images both lens correction and perspective correction work on the wrong center point. The lens shift parameters '''d''' (horizontal shift) and '''e''' (vertical shift) compensate for that problem. They contain values in pixel units which determine how far the center for radial correction is shifted outside the geometrical image center.

=== Image shear f & g parameters ===

Image shear is not a [[lens distortion]] but nevertheless is part of the panotools lens correction model. It corrects for a distortion induced by scanners or scanning cameras that causes a rectangular image being sheared to the form of a parallelogram (one side of the images is shifted parallel to the opposite side)

=== Determine lens correction ===

'''a''', '''b''', '''c''' and '''FoV''' are physical properties of a lens/camera-combination at a given focus distance. If you always shoot at the same focus setting, f.e. infinity or the [[Depth of Field#Hyperfocal_distance|hyperfocal distance]], then you can safely reuse the parameters. At different focus settings, '''FoV''' will change noticeably, but usually it is fineto reuse '''a''', '''b''', and '''c''' even then.

There are a number of ways to determine the a, b, c and [[field of view|fov]]
parameters for a particular lens/camera combination:

* Taking a single photograph of a subject containing straight lines, defining one or more sets of [[straight line control points]] (types t3, t4, etc.), and optimising for just a, b, c. You need to set the output format to [[Rectilinear Projection]] for this technique to work. This method is used by the author of [[PTLens]].

* Taking a single photograph of a rectangular object, selecting lots of [[horizontal control points|horizontal]] and [[vertical control points]], then optimising [[roll]], [[pitch]], [[yaw]], [[field of view|fov]], a, b & c. You need to set the output format to [[Rectilinear Projection]] for this technique to work. The process is similar to this [http://hugin.sourceforge.net/tutorials/architectural/ hugin architectural tutorial]:

* Taking two or more overlapping photographs and selecting lots of normal control points, then optimising [[roll]], [[pitch]], [[yaw]], [[field of view|fov]], a, b & c. This technique works with any output [[Projections|projection format]] but requires [[parallax]] free images shot exactly from the [[Nodal Point]]. Note that to get a precise measure of the [[field of view]], you have to take a full 360 degree panorama.

* Using a tool such as [[PTLens]] or [[clens]] to read the [[JPEG]] [[EXIF]] data and correct the image automatically by looking up the lens in an existing database.

=== Optimize for lens correction ===

If you optimize for lens correction in order to calibrate your lens you should keep some facts in mind:

Since lens correction parameters are determined by evaluating the distortion at different radius values you should provide enough control points at a large range of radii from the image center.
* If you use a rectangular pattern or straight lines for that task, make sure you set control points in all distances from the center.
* If you use two or more images make sure you overlap regions with large potential distortion (f.e. the corners) with regions with low possible distortion (f.e. the center). An only horizontal overlap would do, but use at least 50% in order to overlap the image center of one image with the border of the other.

'''a''', '''b''' and '''c''' parameters influence [[Field of View]], especially for images in landscape orientation but slightly for portrait oriented ones, too. This is because although the implicit calculation of the fourth polynomial parameter tries to keep the image at the same size, this is only possible at the radius '''r_src''' = 1.0.

Outside this radius, especially in the image corners, the size and hence the Field of View might differ. Since they are interconnected in this way, you should always allow the optimization for FoV too, if you optimize for '''a''', '''b''' and '''c''' with more than one image. (You cannot optimize for FoV with only one image). As noted above you need a full 360 degree panorama in order to get an accurate measure of the [[field of view]].

The '''a''' and '''c''' parameters control more complex forms of distortion. In most cases it will be enough to optimize for the '''b''' parameter only, which is good at correcting normal [[barrel distortion]] and [[pincushion distortion]].

If you want to see how changing the parameters influences distortion correction go to http://www.4pi.org/downloads/ and get '''abc.xls'''. Don't deactivate macros on loading.

See also [http://www.path.unimelb.edu.au/~dersch/barrel/barrel.html Helmut Dersch's barrel distortion page].

There's an excellent tutorial on how to optimize by John Houghton: [http://homepage.ntlworld.com/j.houghton/optitute.htm]

=== Tools to correct barrel and pincushion distortion ===

* The original [[PTStitcher]] can be scripted to batch process images with known a, b & c parameters. It can also be operated with one of the [[GUI front-ends]].

* [[nona]] or [[nona_gui]] (both part of the [[hugin]] distribution) can be used identically to [[PTStitcher]].

* The [[Panorama_Tools_Plugins#Radial_Shift|Correct Radial Shift]] filter in the [[Panorama Tools Plugins]] for the [[gimp]] or [[photoshop]] uses the same a, b & c parameters as [[PTStitcher]]. Note that it doesn't know about d & e shift parameters and uses 'd' as an overall scaling factor instead, which should be d = 1-(a+b+c) to keep the image roughly the same size. If you need to shift the correction center like with the d & e parameter you must combine it with [[Panorama_Tools_Plugins#Vertical_Shift_.26_Horizontal_Shift|Vertical Shift]] and/or [[Panorama_Tools_Plugins#Vertical_Shift_.26_Horizontal_Shift|Horizontal Shift]].

* [[PTLens]] is a [[Photoshop]] plugin and a stand-alone Windows tool that uses the same a, b & c parameters and comes with a database of popular lenses.

* [[Clens]] is a command line version of [[PTLens]].

* [[fulla]] is a command-line tool that uses the same a, b, c & d parameters to correct [[barrel distortion]]. It can also correct [[chromatic aberration]] and [[vignetting]] at the same time.

* [[PTShift]] determines different a, b & c parameters for the three color channels in order to correct for [[Chromatic aberration]] with the [[Panorama_Tools_Plugins#Radial_Shift|Correct Radial Shift]] filter.

* [[Gimp wideangle plugin]] uses a different formula altogether to correct distortion.

* [[Gimp phfluuh plugin]] is another tool that corrects lens distortion using yet another formula.

* [[CamChecker]] is a tool for automatically determining lens distortion and generates a different set of parameters from everything else.

* [[zhang_undistort]] is a tool distributed with [[hugin]] that uses [[CamChecker]] parameters to actually correct distortion.

* [[Distortion Remove]] uses a completely different approach with a distortion matrix. Page in german only: http://www.stoske.de/digicam/Artikel/verzeichnung.html

[[Category:Glossary]]