PanoTools.org Wiki - User contributions [en]

Main Page

2010-06-29T17:22:26Z

Dezen: Undo revision 12468 by MariaDonaldson (Talk) spam link removed

__NOTOC__
== Welcome to the PanoTools wiki ==

The [[Wiki History|wiki]] that aims to show you what you can do with the [[panorama tools]] and how to use them the best way.

The panorama tools are mainly used to build [[PanoRama|panoramic images]] from a set of overlapping images.
The usability extends beyond "just" building panoramas by far though. You can, for instance, use them to render an average of multiple images to broaden the [[dynamic range]] of the images or average out noise. You can also build object movies with them, morph between images and much more. See [[panorama tools applications]] for an extensive list.

We hope you'll find this knowledge base interesting and useful. And if you feel something is missing, please feel free to add your knowledge. All pages on this wiki are editable by you. Let the [[FAQ]] page help you on your way. If you are not up to adding something yourself, please add a description of what you think is missing to the [[requested pages]] page, or maybe just add a comment to an article's ''discussion'' tab. However, you need an account and you need to [[Special:Userlogin|login]] to edit.

Please see [[Contribute|how to contribute]] for details. There is a list of [[articles that need enhancement]].

The links below may be helpful to easily find the topic you are looking for.

==== Site overviews ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| width=20% | [[SiteMap|Site Map]] || The contents of this wiki in a structured view
|-
| width=20% | [[Special:Allpages|All Pages]] || An alphabetic list of all pages on this wiki
|-
| width=20% | [[Special:Categories|Categories]] || A categorized overview of the contents of this wiki
|}

==== Working with the Panorama Tools ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| width=20% | [[Getting started]] || An introduction to the Panorama Tools and links to tutorials.
|-
| width=20% | [[Panorama formats]] || Panoramas come in various shapes and sizes. This page describes the differences between them.
|-
| width=20% | [[Panorama tools applications]] || Applications of the panorama tools that go beyond panorama stitching.
|-
| width=20% | [[Software]] || A comprehensive overview of all software category pages grouped by platform.
|-
| width=20% | [[Hardware]] || Computers, Cameras, Tripods - everything that is hardware related.
|-
| width=20% | [[Tutorials]] || Step by step guides to solutions and tasks.
|-
| width=20% | [[Glossary]] || An explanation of odd words and terms.
|}

==== Our community ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| width=20% | [[PanoToolsNG]] || Some information on our mailing list and possibilities to read.
|-
| width=20% | [[Searching the archives]] || What to do when Google and Yahoo don't find what you need.
|-
| width=20% | [[People]] || Lists of People that use or develop [[Panorama tools]]
|-
| width=20% | [[License]] || All the contents of this wiki are licensed
|-
| width=20% | [[Contribute]] || Help keep PanoTools a valuable immersive imaging resource.
|}

==== Recent activity ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| '''New Tutorials'''
| '''Recent Additions'''
| '''Recent Changes'''
|-
|<DPL>
category=Tutorial:Basic_need|Tutorial:Nice_to_know|Tutorial:Specialised
namespace=|PanoTools
notcategory=Draft
ordermethod=firstedit
order=descending
addeditdate=false
count=5
</DPL>
|<DPL>
namespace=|PanoTools
notcategory=Tutorial
ordermethod=firstedit
order=descending
addeditdate=false
count=5
</DPL>
|<DPL>
namespace=|PanoTools
ordermethod=lastedit
order=descending
addeditdate=false
count=5
</DPL>
|-
|}

==== Wiki Help ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| width=20% | [[Help:FAQ|Frequently Asked Questions]] regarding this wiki
|-
| width=20% | [[Help|Help pages]]
|-
|-
| width=20% | [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide]
|-
|-
| with=20% | [http://meta.wikimedia.org/wiki/Help:Editing#The_wiki_markup The wiki markup]
|}

[[Category:Info]]

Hugin SDK (MSVC 2008)

2010-06-14T08:46:39Z

Dezen: Undo revision 12437 by Vsimon213 (Talk) Spam link removed

Hugin depends on different components like libraries and tools, which are not available on a common Windows system. All these components can be combined to a Hugin Software Developmant Kit (SDK). This article gives step-by-step instructions to build such SDK for Hugin using Microsoft Visual C++ 2008 (MSVC 2008) Express Edition and precompiled dependencies.

While this article is designed for developing a native 32-bit version, adidtional instructions are provided so that a 64-bit version of the Hugin SDK can be compiled. When appropriate, steps that only apply to the 32-bit or 64-bit versions will be noted as (32-bit) or (64-bit), and you can safely ignore them if you are not targeting that particular version. In order to compile a 64-bit version of the Hugin SDK, one does not need a 64-bit computer. However, if they wish to test or debug the binaries, or for some projects (such as OpenEXR) which execute compiled binaries as part of their build step, this will not necessarily be possible on Win32.

First of all an overview is given over the contents of the SDK and the tools that are necessary to build the SDK.

The build steps for each component are written like a walkthrough and annotated on the end of each section.

Maybe some of the described tools and packages, especially those fetched from Subversion (SVN) repository, will change over time and/or become obsolete. Hence it is likely that some steps will become invalid or won't work any more.

The SDK is structured, that each component resides in its own subdirectory. This approach is different to other platforms like Linux, where some common directories are available to store include files, libraries and applications. The files of a component are spread over all these directories. Both approaches to structure the files in a file system have its assets and drawbacks.

The base directory of the SDK is denoted as <tt><SDKHOME></tt> in this article. Replace <tt><SDKHOME></tt> by directory name where you store the SDK on your system. In the examples <tt><SDKHOME></tt> is replaced by the directory name <tt>D:\usr\src\SDK</tt>.

== Prerequisites ==

To build the SDK some tools are required that are listed in the table below. Download the tools and install them. The destination directory of each tool is arbitrary. If you are uncertain, choose the default given in the setup dialog of each tool.

{| class="wikitable" width="100%"
|- valign="top"
! style="padding:5px; text-align:left" width="30%" | Tool
! style="padding:5px; text-align:left" | Description
|- valign="top"
| style="padding:5px; text-align:left" | Microsoft Visual C++ 2008 Express Edition
| style="padding:5px; text-align:left" | Compiler, Debugger and IDE Visit [http://www.microsoft.com/express/vc/ Download page] If compiling for 64-bit, you will need to [http://jenshuebel.wordpress.com/2009/02/12/visual-c-2008-express-edition-and-64-bit-targets/ enable Express Edition to compile 64-bit projects].
|- valign="top"
| style="padding:5px; text-align:left" | (x64 Only) Microsoft Windows SDK for Windows Server 2008 and .NET Framework 3.5
| style="padding:5px; text-align:left" | x64 Compiler, Libraries, and Headers Visit [http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-9BE5-FA919850BDBF] When installing, make sure to include the Visual C++ compilers for x64 (under Developer Tools) and the Header Files and x64 libraries (under Windows Headers and Libraries). Optionally consider installing all of the SDK, as it makes compiling generally easier.
|- valign="top"
| style="padding:5px; text-align:left" | CMake 2.6.4 (2009-05-05)
| style="padding:5px; text-align:left" | Generator of solution and project files for MSVC 2008 Visit [http://www.cmake.org/cmake/resources/software.html#latest Download page] or download [http://www.cmake.org/files/v2.6/cmake-2.6.4-win32-x86.exe <tt>cmake-2.6.4-win32-x86.exe</tt>]
|- valign="top"
| style="padding:5px; text-align:left" | TortoiseSVN 1.6.1.16129 (2009-02-13)
| style="padding:5px; text-align:left" | Tool to handle source codes in Subversion repositories Visit [http://tortoisesvn.net/downloads Download page] or download [http://downloads.sourceforge.net/tortoisesvn/TortoiseSVN-1.6.1.16129-win32-svn-1.6.1.msi <tt>TortoiseSVN-1.6.1.16129-win32-svn-1.6.1.msi (32-bit)</tt>] or [http://downloads.sourceforge.net/tortoisesvn/TortoiseSVN-1.6.1.16129-x64-svn-1.6.1.msi <tt>TortoiseSVN-1.6.1.16129-x64-svn-1.6.1.msi (64-bit)</tt>]
|- valign="top"
| style="padding:5px; text-align:left" | TortoiseHg 1.0.4 (2010-06-11)
| style="padding:5px; text-align:left" | Tool to handle source codes in Mercurial repositories Visit [http://tortoisehg.bitbucket.org/ Download page] 
|- valign="top"
| style="padding:5px; text-align:left" | 7-Zip 4.65 (2009-02-03)
| style="padding:5px; text-align:left" | Tool to decompress the source packages Visit [http://www.7-zip.org/download.html Download page] or download [http://downloads.sourceforge.net/sevenzip/7z465.exe <tt>7z465.exe (32-bit)</tt>] or [http://downloads.sourceforge.net/sevenzip/7z465-x64.msi <tt>7z465-x64.msi (64-bit)</tt>]
|- valign="top"
| style="padding:5px; text-align:left" | Java SE Development Kit 6 Update 13
| style="padding:5px; text-align:left" | Java Development Kit (JDK) Visit [http://java.sun.com/javase/downloads/index.jsp Download page]
|}

== Contents of the Hugin SDK ==

=== Precompiled Version (32-bit only) ===

For those who want to avoid to build the whole SDK from scratch a precompiled SDK is available.

{| class="wikitable" width="100%"
|- valign="top"
! style="padding:5px; text-align:left" | Precompiled Hugin SDK (Win32)
|- valign="top"
| style="padding:5px; text-align:left" | [http://hugin.panotools.org/sdk/MSVC/Hugin-SDK-20090509-win32.exe <tt>Hugin-SDK-20090509-win32.exe </tt>] (76 MiB, 2009-05-09)
|}

=== Building from Source ===
The contents of the Hugin SDK is shown in the following table. Download the packages, except the packages fetched from Subversion repository.

{| class="wikitable" width="100%"
|- valign="top"
! style="padding:5px; text-align:left" width="30%" | Directory
! style="padding:5px; text-align:left" | Description (Website) Download package (Date of the package)
|- valign="top"
| style="padding:5px; text-align:left" | <tt>autopano-sift-C</tt>
| style="padding:5px; text-align:left" | Autopano-SIFT-C (http://hugin.sourceforge.net/) Subversion repository <tt>https://hugin.svn.sourceforge.net/svnroot/hugin/autopano-sift-C/trunk</tt>
|- valign="top"
| style="padding:5px; text-align:left" | <tt>boost_1_39_0</tt>
| style="padding:5px; text-align:left" | Boost C++ libraries 1.39.0 (http://www.boost.org/) [http://downloads.sourceforge.net/boost/boost_1_39_0.7z <tt>boost_1_39_0.7z</tt>] (2009-02-09) [http://downloads.sourceforge.net/boost/boost-jam-3.1.17-1-ntx86.zip <tt>boost-jam-3.1.17-1-ntx86.zip</tt>] (2008-11-29)
|- valign="top"
| style="padding:5px; text-align:left" | <tt>Deploy</tt> <tt>OpenEXR</tt>
| style="padding:5px; text-align:left" | OpenEXR library 1.6.1 and IlmBase libraries 1.0.1 (http://www.openexr.com/) [http://download.savannah.nongnu.org/releases/openexr/ilmbase-1.0.1.tar.gz <tt>ilmbase-1.0.1.tar.gz</tt>] (2007-10-22) [http://download.savannah.nongnu.org/releases/openexr/openexr-1.6.1.tar.gz <tt>openexr-1.6.1.tar.gz</tt>] (2007-10-22)
|- valign="top"
| style="padding:5px; text-align:left" | <tt>enblend-enfuse-3.2</tt>
| style="padding:5px; text-align:left" | Enblend 3.2 and Enfuse 3.2 (http://enblend.sourceforge.net/) 
{| class="wikitable"
|- valign="top"
! style="padding:5px; text-align:left" | 32-Bit
! style="padding:5px; text-align:left" | 64-Bit
|- valign="top"
| style="padding:5px; text-align:left" | [http://downloads.sourceforge.net/enblend/enblend-enfuse-3.2.zip <tt>enblend-enfuse-3.2.zip</tt>] (2008-09-09)
| style="padding:5px; text-align:left" | [http://downloads.sourceforge.net/enblend/enblend-enfuse-3.2.tar.gz <tt>enblend-enfuse-3.2.tar.gz</tt>] (2008-09-09)
|}
|- valign="top"
| style="padding:5px; text-align:left" | <tt>exiftool</tt>
| style="padding:5px; text-align:left" | ExifTool 7.74 (http://www.sno.phy.queensu.ca/~phil/exiftool) [http://www.sno.phy.queensu.ca/~phil/exiftool/exiftool-7.74.zip <tt>exiftool-7.74.zip</tt>] (2009-02-17)
|- valign="top"
| style="padding:5px; text-align:left" | <tt>exiv2-0.18.1</tt>
| style="padding:5px; text-align:left" | Exiv2 C++ library 0.18 (http://www.exiv2.org/) [http://www.exiv2.org/exiv2-0.18.1.tar.gz <tt>exiv2-0.18.1.tar.gz</tt>] (2009-04-06)
|- valign="top"
| style="padding:5px; text-align:left" | <tt>expat-2.0.1</tt>
| style="padding:5px; text-align:left" | Expat XML Parser library 2.0.1 (http://sourceforge.net/projects/expat/) [http://downloads.sourceforge.net/expat/expat-2.0.1.tar.gz <tt>expat-2.0.1.tar.gz</tt>] (2007-06-05)
|- valign="top"
| style="padding:5px; text-align:left" | <tt>gettext</tt>
| style="padding:5px; text-align:left" | GNU gettext 0.13.1 and iconv library 1.9.1 (http://www.gnu.org/) 
{| class="wikitable"
|- valign="top"
! style="padding:5px; text-align:left" | 32-Bit
! style="padding:5px; text-align:left" | 64-Bit
|- valign="top"
| style="padding:5px; text-align:left" | <ul><li>[http://ftp.gnu.org/gnu/gettext/gettext-runtime-0.13.1.bin.woe32.zip <tt>gettext-runtime-0.13.1.bin.woe32.zip</tt>] (2004-01-20)</li><li>[http://ftp.gnu.org/gnu/gettext/gettext-tools-0.13.1.bin.woe32.zip <tt>gettext-tools-0.13.1.bin.woe32.zip</tt>] (2004-01-20)</li><li>[http://ftp.gnu.org/gnu/libiconv/libiconv-1.9.1.bin.woe32.zip <tt>libiconv-1.9.1.bin.woe32.zip</tt>] (2004-01-20)</li></ul>
| style="padding:5px; text-align:left" | <ul><li> [http://ftp.gnu.org/gnu/libiconv/libiconv-1.9.1.tar.gz libiconv-1.9.1.tar.gz] (2003-05-27)</li><li>[http://ftp.gnu.org/gnu/gettext/gettext-0.13.1.tar.gz gettext-0.13.1.tar.gz] (2003-12-17)</li></ul>
|}
|- valign="top"
| style="padding:5px; text-align:left" | <tt>glew</tt>
| style="padding:5px; text-align:left" | OpenGL Extension Wrangler Library (GLEW) 1.5.1 (http://glew.sourceforge.net/) [http://downloads.sourceforge.net/glew/glew-1.5.1-src.zip <tt>glew-1.5.1-src.zip</tt>] (2008-11-03)
|- valign="top"
| style="padding:5px; text-align:left" | <tt>libpano\pano13</tt>
| style="padding:5px; text-align:left" | Panorama Tools and pano13 library (http://panotools.sourceforge.net/) Subversion repository <tt>https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/libpano</tt>
|- valign="top"
| style="padding:5px; text-align:left" | <tt>libxml2-2.7.3</tt>
| style="padding:5px; text-align:left" | XML C parser and toolkit (http://www.xmlsoft.org/) [ftp://xmlsoft.org/libxml2/libxml2-sources-2.7.3.tar.gz <tt>libxml2-sources-2.7.3.tar.gz</tt>] (2009-01-18)
|- valign="top"
| style="padding:5px; text-align:left" | <tt>UnxUtils</tt>
| style="padding:5px; text-align:left" | GNU utilities ported to win32 platform (http://sourceforge.net/projects/unxutils/) [http://downloads.sourceforge.net/unxutils/UnxUtils.zip <tt>UnxUtils.zip</tt>] (2007-03-01)
|- valign="top"
| style="padding:5px; text-align:left" | <tt>wxWidgets-2.8.10</tt>
| style="padding:5px; text-align:left" | wxWidgets cross-platform GUI C++ framework 2.8.10 (http://www.wxwidgets.org/) [http://downloads.sourceforge.net/wxwindows/wxMSW-2.8.10.zip <tt>wxMSW-2.8.10.zip</tt>] (2009-03-17)
|- valign="top"
! colspan="2" | Additional files only necessary for building a 64-bit SDK
|- valign="top"
! style="padding:5px; text-align:left" width="30%" | Directory
! style="padding:5px; text-align:left" | Description (Website) Download package (Date of the package)
|- valign="top"
| style="padding:5px; text-align:left" | <tt>(64-bit) libxmi-1.2-1</tt>
| style="padding:5px; text-align:left" | GNU libxmi 2-D rasterization library (Win32 port) (http://gnuwin32.sourceforge.net) [http://downloads.sourceforge.net/gnuwin32/libxmi-1.2-1-src.zip <tt>libxmi-1.2-1-src.zip</tt>] (2004-04-16) 
|- valign="top"
| style="padding:5px; text-align:left" | <tt>(64-bit) STLport-5.2.1</tt>
| style="padding:5px; text-align:left" | STLport Standard Library (http://stlport.sourceforge.net/) [http://downloads.sourceforge.net/stlport/STLport-5.2.1.tar.gz <tt>STLport-5.2.1.tar.gz</tt>] (2008-12-10) 
|- valign="top"
| style="padding:5px; text-align:left" | <tt>(64-bit) lcms-1.18a</tt>
| style="padding:5px; text-align:left" | LittleCms Color management library (http://www.littlecms.com) [http://www.littlecms.com/lcms-1.18a.zip <tt>lcms-1.18a.zip</tt>] (2009-04-19) 
|}

In the following subsections each component is discussed in detail. The order of the subsections seems random, but I applied the approach to describe the precompiled packages first, followed by the big packages, where some of the small packages depend on.

The decompress step of each component contains seemingly inconsistent namings of destination directories, because in some components a subdirectory is specified as destination directory and in some steps only the base directory. This is due to the fact that some package archives contain a base directory and some not. To check the right locations each result section of every component's description contains a summary of the expected files.

The SDK is currently outdated. The following changes are necessary to build Hugin:

{| class="wikitable" width="100%"
|- valign="top"
! style="padding:5px; text-align:left" width="30%" | Directory
! style="padding:5px; text-align:left" | Description (Website) Download package
|- valign="top"
| style="padding:5px; text-align:left" | <tt>freeglut_2.6.0</tt>
| style="padding:5px; text-align:left" | Freeglut (http://freeglut.sourceforge.net/index.php) [http://prdownloads.sourceforge.net/freeglut/freeglut-2.6.0.tar.gz?download <tt>freeglut-2.6.0.tar.gz</tt>]
|- valign="top"
| style="padding:5px; text-align:left" | <tt>make_3.81</tt>
| style="padding:5px; text-align:left" | GNU make 3.81 (http://www.gnu.org/software/make/) [http://ftp.gnu.org/pub/gnu/make/make-3.81.tar.gz <tt>make-3.81.tar.gz</tt>] This package replaces UnxUtils.
|}

==== Diff Files ====
In order to make compilation simple, a series of patch files are included below that contain all the necessary changes, not only to compile the SDK, but to optionally compile an x64 version of the SDK. When directed, you will need to apply the patch file specified. If you are compiling for x64, there may be additional patches you need to apply.

The download link for the patches is [http://sourceforge.net/tracker/?func=detail&aid=2789320&group_id=77506&atid=550443 http://sourceforge.net/tracker/?func=detail&aid=2789320&group_id=77506&atid=550443]

In order to apply a patch, you will first have needed to follow directions for the [[#UnxUtils|UnxUtils]] step. You cannot apply any patches before that step. To apply a patch, follow these directions:
<ol>
<li>Start a Command Prompt by choosing Start -> Run and typing in "cmd.exe"</li>
<li>On the Command Prompt, change directory to <tt><SDKHOME></tt> 
'''Example'''
<pre>
C:\Program Files\Microsoft\Windows SDK\v6.1>d:

D:>cd \usr\src\SDK

D:\usr\src\SDK>
</pre></li>
<li>On the command prompt, enter the following commands without any line breaks and press the Return/Enter key, substituting <SDKHOME> where appropriate: 
<pre>
set PATH=%PATH%;<SDKHOME>\UnxUtils\usr\local\wbin
</pre>
</li>
<li>On the command prompt, enter the following commands without any line breaks and press the Return/Enter key, substituting <PATCHFILE> with the name of the patch file to apply: 
<pre>
patch -p 0 -i <PATCHFILE>
</pre>
'''NOTE:''' On Vista and later systems, the filename "patch.exe" is a protected file name which will always result in a UAC prompt if the file does not include a manifest (which UnxUtils version does not). This can be worked around by copying the file <tt><SDKHOME>\UnxUtils\usr\local\wbin\patch.exe</tt> to another file not containing the name, such as <tt><SDKHOME>\UnxUtils\usr\local\wbin\apply_diff.exe</tt>. Then substitute the command <tt>'patch'</tt> in the above command with <tt>'apply_diff'</tt>
</li>
</ol>

'''Result'''

If everything worked, you should see a list of filenames that were patched.
'''Example'''
<pre>
D:\usr\src\SDK>patch -p 0 -i libiconv-1.9.1.diff
patching file 'libiconv-1.9.1/srclib/error.c'

D:\usr\src\SDK>
</pre>

If there was an error, you may wish to consult the [[Hugin SDK (MSVC 2008) Patches]] page for instructions on what changes were contained in the patch.

=== UnxUtils ===

<ol>
<li>Create the directory <tt><SDKHOME>\UnxUtils</tt></li>
<li>Decompress the file <tt>UnxUtils.zip</tt> to created directory <tt><SDKHOME>\UnxUtils</tt></li>
</ol>

'''Result'''

The applications reside in
<tt><SDKHOME>\UnxUtils\bin</tt> and
<tt><SDKHOME>\UnxUtils\usr\local\wbin</tt>

=== ExifTool ===

<ol>
<li>Create the directory <tt><SDKHOME>\exiftool</tt></li>
<li>Decompress the file <tt>exiftool-7.74.zip</tt> to <tt><SDKHOME>\exiftool</tt></li>
<li>Rename the file <tt>exiftool(-k).exe</tt> to <tt>exiftool.exe</tt></li>
</ol>

'''Result'''

The application resides in
<tt><SDKHOME>\exiftool</tt>

=== GetText ===
{| class="wikitable"
|- valign="top"
! style="padding:5px; text-align:left" | 32-Bit Directions
! style="padding:5px; text-align:left" | 64-Bit Directions
|- valign="top"
| style="padding:5px; text-align:left" | <ol>
<li>Create the directory <tt><SDKHOME>\gettext</tt></li>
<li>Decompress the following files to created directory <tt><SDKHOME>\gettext</tt>
<ul>
<li><tt>gettext-runtime-0.13.1.bin.woe32.zip</tt></li>
<li><tt>gettext-tools-0.13.1.bin.woe32.zip</tt></li>
<li><tt>libiconv-1.9.1.bin.woe32.zip</tt></li>
</ul>
</li>
</ol>
| style="padding:5px; text-align:left" | <ol>
<li>Create the directory <tt><SDKHOME>\gettext</tt></li>
<li>Decompress the following files into the directory <tt><SDKHOME></tt>
<ul>
<li><tt>gettext-0.13.1.tar.gz</tt></li>
<li><tt>libiconv-1.9.1.tar.gz</tt></li>
</ul>
After decompress, there should be two new folders in <tt><SDKHOME></tt>: <tt><SDKHOME>\gettext-0.13.1</tt> and <tt><SDKHOME>\libiconv-1.9.1</tt>
</li>
<li>Apply the <tt>libiconv-1.9.1.diff</tt> patch</li>
<li>Apply the <tt>gettext-0.13.1.diff</tt> patch</li>
<li>Open a Windows SDK prompt by choosing Start -> Programs -> Microsoft Windows SDK v6.1 -> CMD Shell</li>
<li>On the command prompt, enter the following command without any line breaks and press the Return/Enter key: 
<pre>
setenv /Release /x64 /xp
</pre>
It should now refresh and say
<pre>
Setting SDK environment relative to <path where you installed the SDK>
Targeting Windows XP x64 RELEASE
</pre></li>
<li>On the command prompt, change directory to <SDKHOME>\libiconv-1.9.1 
'''Example'''
<pre>
C:\Program Files\Microsoft\Windows SDK\v6.1>d:

D:>cd \usr\src\SDK\libiconv-1.9.1

D:\usr\src\SDK\libiconv-1.9.1>
</pre></li>
<li>On the command prompt, enter the following commands without any line breaks and press the Return/Enter key, substituting <SDKHOME> where appropriate: 
<pre>
nmake -f Makefile.msvc NO_NLS=1 MFLAGS=-MT
nmake -f Makefile.msvc NO_NLS=1 MFLAGS=-MT install PREFIX=<SDKHOME>\gettext
cd ..\gettext-0.13.1
nmake -f Makefile.msvc MFLAGS=-MT PREFIX=<SDKHOME>\gettext
nmake -f Makefile.msvc MFLAGS=-MT install PREFIX=<SDKHOME>\gettext
cd ..\libiconv-1.9.2-src
nmake -f Makefile.msvc NO_NLS=1 MFLAGS=-MT distclean
nmake -f Makefile.msvc MFLAGS=-MT PREFIX=<SDKHOME>\gettext
nmake -f Makefile.msvc MFLAGS=-MT install PREFIX=<SDKHOME>\gettext
</pre></li>
<li>Close the Windows SDK command prompt window</li>
</ol>
|}
'''Result'''

The applications reside in
<tt><SDKHOME>\gettext\bin</tt>

The include files reside in
<tt><SDKHOME>\gettext\include</tt>

The libraries reside in
<tt><SDKHOME>\gettext\lib</tt>
=== STLport (64-bit Only) ===
<ol>
<li>Decompress the file <tt>STLport-5.2.1.tar.gz</tt> to directory <tt><SDKHOME></tt></li>
<li>Open a Windows SDK prompt by choosing Start -> Programs -> Microsoft Windows SDK v6.1 -> CMD Shell</li>
<li>On the command prompt, enter the following command without any line breaks and press the Return/Enter key: 
<pre>
setenv /Release /x64 /xp
</pre>
It should now refresh and say
<pre>
Setting SDK environment relative to <path where you installed the SDK>
Targeting Windows XP x64 RELEASE
</pre></li>
<li>On the command prompt, change directory to <SDKHOME>\STLport-5.2.1 
'''Example'''
<pre>
C:\Program Files\Microsoft\Windows SDK\v6.1>d:

D:>cd \usr\src\SDK\STLport-5.2.1

D:\usr\src\SDK\STLport-5.2.1>
</pre></li>
<li>On the command prompt, enter the following commands without any line breaks and press the Return/Enter key: 
<pre>configure msvc9 --with-static-rtl
cd build/lib
nmake clean install</pre>
</li>
<li>Close the Windows SDK command prompt window</li>
</ol>

'''Result'''

The libraries reside in <tt><SDKHOME>\STLport-5.2.1\lib</tt>

=== lcms-1.18 (64-bit Only) ===
<ol>
<li>Decompress the file <tt>lcms-1.18a.tar.gz</tt> to directory <tt><SDKHOME></tt></li>
<li>Apply the <tt>lcms-1.18.diff</tt> patch</li>
<li>Open the file <tt><SDKHOME>\lcms-1.18\Projects\VC2008\lcms.sln</tt></li>
<li>Select "Release" in the Solution Configuration pull-down menu. Select "x64" in the Solution Platform pull-down menu</li>
<li>Select project lcms in Solution Explorer, and then choose Build > Project Only > Build Only lcms</li>
<li>Close Visual Studio C++ 2008 Express Edition</li>
</ol>

'''Result'''

The library resides in <tt><SDKHOME>\lcms-1.18\Lib\MS</tt>

{| class="wikitable" width="100%"
|-
! style="padding:5px; text-align:left" | Note
|-
| style="padding:5px; text-align:left" | During build process temporary object files are stored in following directories
<ul>
<li><tt><SDKHOME>\lcms-1.18\Projects\VC2008\LibDebug</tt></li>
<li><tt><SDKHOME>\lcms-1.18\Projects\VC2008\LibRelease</tt></li>
</ul>
Both directories may be deleted to save disk space.
|}

=== libxmi-1.2.1 (64-bit Only) ===
<ol>
<li>Open the file <tt>libxmi-1.2-1.src.zip</tt> in 7-Zip</li>
<li>Open the "src" folder by double-clicking</li>
<li>Open the "libxmi" folder by double-clicking</li>
<li>Open the "1.2" folder by double-clicking</li>
<li>Extract "libxmi-1.2" to the directory <tt><SDKHOME></tt></li>
<li>Apply the <tt>libxmi-1.2.diff</tt> patch</li>
</ol>

'''Result'''

The libxmi-1.2 sources now reside in <tt><SDKHOME>\libxmi-1.2</tt>
=== wxWidgets ===
<ol>
<li>Decompress the file <tt>wxMSW-2.8.10.zip</tt> to directory <tt><SDKHOME></tt></li>
<li>Rename the directory <tt><SDKHOME>\wxMSW-2.8.10</tt> to <tt><SDKHOME>\wxWidgets-2.8.10</tt></li>
<li>Apply the <tt>wxWidgets-2.8.10.diff</tt> patch [[Hugin SDK (MSVC 2008) Patches#wxWidgets]]</li>
<li>
{| class="wikitable" width="100%"
|- valign="top"
! style="padding:5px; text-align:left" width="50%" | 32-Bit Directions
! style="padding:5px; text-align:left" | 64-Bit Directions
|- valign="top"
| style="padding:5px; text-align:left" | To open a Visual Studio command prompt choose Start > Programs > Microsoft Visual C++ 2008 Express Edition > Visual Studio Tools > Visual Studio 2008 Command Prompt
| style="padding:5px; text-align:left" | <ol>
<li>Open a Windows SDK prompt by choosing Start -> Programs -> Microsoft Windows SDK v6.1 -> CMD Shell</li>
<li>On the command prompt, enter the following command without any line breaks and press the Return/Enter key: 
<pre>
setenv /Release /x64 /xp
</pre>
It should now refresh and say
<pre>
Setting SDK environment relative to <path where you installed the SDK>
Targeting Windows XP x64 RELEASE
</pre></li>
</ol>
|}</li>

<li>On command prompt change directory to <tt><SDKHOME>\wxWidgets-2.8.10\build\msw</tt> 
'''Example'''
<pre>
C:\Program Files\Microsoft Visual Studio 9.0\VC>d:

D:\>cd \usr\src\SDK\wxWidgets-2.8.10\build\msw

D:\usr\src\SDK\wxWidgets-2.8.10\build\msw>
</pre>
</li>
<li>Enter each of the following two commands without any line break and press the Return key
{| class="wikitable"
|- valign="top"
! style="padding:5px; text-align:left" | 32-Bit Directions
! style="padding:5px; text-align:left" | 64-Bit Directions
|- valign="top"
| style="padding:5px; text-align:left" | <pre>
nmake -f makefile.vc BUILD=debug UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static
nmake -f makefile.vc BUILD=release UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static
</pre>
| style="padding:5px; text-align:left" | <pre>
nmake -f makefile.vc BUILD=debug TARGET_CPU=AMD64 UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static
nmake -f makefile.vc BUILD=release TARGET_CPU=AMD64 UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static
</pre>
|}
</li>
<li>Close the Windows SDK command prompt window</li>
<li>(64-bit Only)Rename the folder <tt><SDKHOME>wxWidgets-2.8.10\lib\vc_amd64_lib</tt> to <tt><SDKHOME>wxWidgets-2.8.10\lib\vc_lib</tt></li>
</ol>

'''Result'''

The include files reside in
<tt><SDKHOME>\wxWidgets-2.8.10\include</tt> and its subdirectories

Additional Hugin depends on following files
<ul>
<li><tt><SDKHOME>\wxWidgets-2.8.10\src\jpg\*.h</tt></li>
<li><tt><SDKHOME>\wxWidgets-2.8.10\src\jpg\jconfig.vc</tt></li>
<li><tt><SDKHOME>\wxWidgets-2.8.10\src\png\*.h</tt></li>
<li><tt><SDKHOME>\wxWidgets-2.8.10\src\tiff\*.h</tt></li>
<li><tt><SDKHOME>\wxWidgets-2.8.10\src\zlib\*.h</tt></li>
</ul>

The libraries reside in
<tt><SDKHOME>\wxWidgets-2.8.10\lib\vc_lib</tt>

{| class="wikitable"
|-
! style="padding:5px; text-align:left" | Note
|-
| style="padding:5px; text-align:left" | During build process temporary object files are stored in following directories
{| class="wikitable" width="100%"
|- valign="top"
! style="padding:5px; text-align:left" | 32-Bit
! style="padding:5px; text-align:left" | 64-Bit
|- valign="top"
| style="padding:5px; text-align:left" | <ul>
<li><tt><SDKHOME>\wxWidgets-2.8.10\build\msw\vc_mswu</tt></li>
<li><tt><SDKHOME>\wxWidgets-2.8.10\build\msw\vc_mswud</tt></li>
</ul>
| style="padding:5px; text-align:left" |
<ul>
<li><tt><SDKHOME>\wxWidgets-2.8.10\build\msw\vc_mswu_amd64</tt></li>
<li><tt><SDKHOME>\wxWidgets-2.8.10\build\msw\vc_mswud_amd64</tt></li>
</ul>
|}
Both directories may be deleted to save disk space.
|}

=== Boost ===

<ol>
<li>Decompress the file <tt>boost_1_39_0.7z</tt> to directory <tt><SDKHOME></tt></li>
<li>Decompress the file <tt>boost-jam-3.1.17-1-ntx86.zip</tt> to an arbitrary directory and copy the application <tt>bjam.exe</tt> to <tt><SDKHOME>\boost_1_39_0</tt></li>
<li>To open a Windows command prompt choose Start > Run, then enter <tt>cmd.exe</tt> and click OK.</li>
<li>On command prompt change directory to <tt><SDKHOME>\boost_1_39_0</tt> 
'''Example'''
<pre>
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Dokuments and Settings\Guido>d:

D:\>cd \usr\src\SDK\boost_1_39_0

D:\usr\src\SDK\boost_1_39_0>
</pre>
</li>
<li>Enter the following command without line breaks and press Return key 
{| class="wikitable"
|- valign="top"
! style="padding:5px; text-align:left" | 32-Bit Directions
! style="padding:5px; text-align:left" | 64-Bit Directions
|- valign="top"
| style="padding:5px; text-align:left" | <pre>
bjam --with-date_time --with-thread toolset=msvc variant=debug variant=release link=static threading=multi runtime-link=static stage
</pre>
After <tt>bjam.exe</tt> finished a statement like the following should be printed in the command prompt window
<pre>
...updated 56 targets...

d:\usr\src\SDK\boost_1_39_0>
</pre>
| style="padding:5px; text-align:left" | <pre>
bjam --with-date_time --with-thread toolset=msvc variant=debug variant=release link=static threading=multi runtime-link=static address-model=64 stage
</pre>
After <tt>bjam.exe</tt> finished a statement like the following should be printed in the command prompt window
<pre>
...updated 26 targets...
</pre>
|}</li>

<li>Close the Windows command prompt window</li>
</ol>

'''Result'''

The include files reside in
<tt><SDKHOME>\boost_1_39_0</tt> and its subdirectory <tt>boost</tt>

The libraries reside in
<tt><SDKHOME>\boost_1_39_0\stage\lib</tt>

{| class="wikitable" width="100%"
|-
! style="padding:5px; text-align:left" | Notes
|-
|<ul>
<li>During build process temporary files are generated in <tt><SDKHOME>\boost_1_39_0\bin.v2</tt>. This directory may be deleted to save disk space.
</li>
<li>Hugin needs only the two Boost libraries <tt>date_time</tt> and <tt>thread</tt>, thus only these two libraries have to be built. 
If you want to build all Boost libraries enter following command on the Windows command prompt instead of the command described above and press Return key.
<pre>
bjam -–build-type=complete toolset=msvc stage
</pre>
There are about 7GB disc space needed during build of all libraries (3.5GB for libraries and the same amount for the temporary files).
</li>
<li>The Boost include files are typically included by a statement like 
<tt>#include "boost/whatever.hpp"</tt> 
Therefore the base directory of the Boost include files is <tt><SDKHOME>\boost_1_39_0</tt>
</li>
<li>Only the following libraries are needed to build a release version of Hugin:
<ul>
<li><tt>libboost_date_time-vc90-mt-s-1_39.lib</tt></li>
<li><tt>libboost_thread-vc90-mt-s-1_39.lib</tt></li>
</ul>
The files with "<tt>gd</tt>" in the filename, e.g. <tt>libboost_thread-vc90-mt-sgd-1_39.lib</tt>, are the debug libraries.
The library files without "<tt>-1_39</tt>" suffix are automatically generated copies of the libraries with version suffix. They are used by CMake to detect the library directory.
</li>
</ul>
|}

=== OpenEXR ===

OpenEXR depends on following SDK component:
<ul>
<li>wxWidgets</li>
</ul>
Prepare this component before OpenEXR.

<ol>
<li>Create the directory <tt><SDKHOME>\OpenEXR</tt></li>
<li>Decompress the file <tt>ilmbase-1.0.1.tar.gz</tt> to created directory <tt><SDKHOME>\OpenEXR</tt> 
<li>Decompress the file <tt>openexr-1.6.1.tar.gz</tt> to the same directory <tt><SDKHOME>\OpenEXR</tt> 
After decompress there should only exist the two directories <tt>ilmbase-1.0.1</tt> and <tt>openexr-1.6.1</tt> in <tt><SDKHOME>\OpenEXR</tt></li>
<li>Apply the <tt>OpenEXR.diff</tt> patch [[Hugin SDK (MSVC 2008) Patches#OpenEXR]]</li>
<li>Open solution file <tt><SDKHOME>\OpenEXR\ilmbase-1.0.1\vc\vc8\IlmBase\IlmBase.sln</tt></li>
<li>Select Debug in Solutions Configuration pull-down menu, and then choose Build > Build Solution</li>
<li>Select Release in Solutions Configuration pull-down menu, and then choose Build > Build Solution</li>
<li>Open solution file <tt><SDKHOME>\OpenEXR\openexr-1.6.1\vc\vc8\OpenEXR\OpenEXR.sln</tt></li>
<li>Choose Build > Batch Build</li>
<li>Select Build for Project IlmImf with Solution Config 
{| class="wikitable"
|- valign="top"
! style="padding:5px; text-align:left" | 32-Bit
! style="padding:5px; text-align:left" | 64-Bit
|- valign="top"
| style="padding:5px; text-align:left" | Solution Config: "Debug" with Platform: "Win32" 
Solution Config: "Release" with Platform: "Win32"
| style="padding:5px; text-align:left" | Solution Config: "Debug" with Platform: "x64" 
Solution Config: "Release" with Platform: "x64"
|}</li>
<li>Click Build</li>
<li>Close Visual C++ 2008 Express Edition</li>
</ol>

'''Result'''

The include files reside in
<tt><SDKHOME>\Deploy\include</tt>

The libraries reside in
<tt><SDKHOME>\Deploy\lib\Debug</tt> and
<tt><SDKHOME>\Deploy\lib\Release</tt>

=== Enblend and Enfuse ===
{| class="wikitable"
|- valign="top"
! style="padding:5px; text-align:left" | 32-Bit Directions
! style="padding:5px; text-align:left" | 64-Bit Directions
|- valign="top"
| style="padding:5px; text-align:left" | <ol>
<li>Decompress the file <tt>enblend-enfuse-3.2.zip</tt> to directory <tt><SDKHOME></tt></li>
</ol>
| style="padding:5px; text-align:left" | Enblend & Enfuse depend on the following SDK components:
<ul>
<li>wxWidgets</li>
<li>OpenEXR</li>
<li>lcms</li>
<li>STLport</li>
<li>boost</li>
<li>libxmi</li>
</ul>
Prepare these components before Enblend & Enfuse.

<ol>
<li>Decompress the file <tt>enblend-enfuse-3.2.tar.gz</tt> to directory <tt><SDKHOME></tt> 
After decompression, you should now have a folder <tt><SDKHOME>\enblend-enfuse-3.2</tt></li>
<li>Apply the <tt>enblend-enfuse-3.2.diff</tt> patch [[Hugin SDK (MSVC 2008) Patches#Enblend/Enfuse/libxmi]]</li>
<li>Open the file <tt><SDKHOME>\enblend-enfuse-3.2\enblend_msvc2008.sln</tt></li>
<li>Select Release in Solutions Configuration pull-down menu, choose x64 in the Solutions Platform pull-down menu, and then choose Build > Build Solution</li>
<li>Close Visual C++ 2008 Express Edition</li>
</ol>
|}
'''Result'''

The applications reside in <tt><SDKHOME>\enblend-enfuse-3.2</tt>

=== Expat ===

<ol>
<li>Decompress the file <tt>expat-2.0.1.tar.gz</tt> to directory <tt><SDKHOME></tt></li>
<li>Apply the <tt>expat-2.0.1.diff</tt> patch [[Hugin SDK (MSVC 2008) Patches#expat]]</li>
<li>Open the file <tt><SDKHOME>\expat-2.0.1\Source\expat.sln</tt></li>
<li>Choose Build > Batch Build</li>
<li>Select Build for Project expat_static with 
{| class="wikitable"
|- valign="top"
! style="padding:5px; text-align:left" | 32-Bit
! style="padding:5px; text-align:left" | 64-Bit
|- valign="top"
| style="padding:5px; text-align:left" | Solution Config: "Debug" with Platform: "Win32" 
Solution Config: "Release" with Platform: "Win32"
| style="padding:5px; text-align:left" | Solution Config: "Debug" with Platform: "x64" 
Solution Config: "Release" with Platform: "x64"
|}</li>
<li>Click Build</li>
<li>Close Visual C++ 2008 Express Edition</li>
</ol>

'''Result'''

The include files reside in
<tt><SDKHOME>\expat-2.0.1\lib</tt>

The libraries reside in
<tt><SDKHOME>\expat-2.0.1\win32\bin\Debug</tt> and
<tt><SDKHOME>\expat-2.0.1\win32\bin\Release</tt>

=== Exiv2 ===

Exiv2 depends on following SDK components:
<ul>
<li>wxWidgets</li>
<li>GetText</li>
<li>Expat</li>
</ul>
Prepare these components before Exiv2.

<ol>
<li>Decompress the file <tt>exiv2-0.18.1.tar.gz</tt> to directory <tt><SDKHOME></tt></li>
<li>Apply the <tt>exiv2-0.18.1.diff</tt> patch [[Hugin SDK (MSVC 2008) Patches#exiv2]]</li>
<li>(64-bit Only)Apply the <tt>exiv2-0.18.1.x64.diff</tt> patch</li>
<li>Open solution file <tt><SDKHOME>\exiv2-0.18.1\msvc\exiv2.sln</tt></li>
<li>In the Solution Explorer, select "exiv2lib"</li>
<li>Select Debug in Solutions Configuration pull-down menu and your platform in the Solution Platform pull-down menu, and then choose Build > Build exiv2lib</li>
<li>Select Release in Solutions Configuration pull-down menu and your platform in the Solution Platform pull-down menu, and then choose Build > Build exiv2lib</li>
<li>Close Visual C++ 2008 Express Edition</li>
<li>Create the directory <tt><SDKHOME>\exiv2-0.18.1\msvc\lib</tt></li>
<li>Copy the following files to this directory and rename them as specified in Destination column.

{| class="wikitable"
|- valign="top"
! style="padding:5px; text-align:left" | Source
! style="padding:5px; text-align:left" | Destination
|-
| style="padding:5px; text-align:left" | <tt><SDKHOME>\exiv2-0.18.1\msvc\bin\Debug\exiv2.lib</tt>
| style="padding:5px; text-align:left" | <tt><SDKHOME>\exiv2-0.18.1\msvc\lib\''exiv2d''.lib</tt>
|-
| style="padding:5px; text-align:left" | <tt><SDKHOME>\exiv2-0.18.1\msvc\bin\Release\exiv2.lib</tt>
| style="padding:5px; text-align:left" | <tt><SDKHOME>\exiv2-0.18.1\msvc\lib\exiv2.lib</tt>
|-
| style="padding:5px; text-align:left" | <tt><SDKHOME>\expat-2.0.1\win32\bin\Debug\libexpatMT.lib</tt>
| style="padding:5px; text-align:left" | <tt><SDKHOME>\exiv2-0.18.1\msvc\lib\''libexpatd''.lib</tt>
|-
| style="padding:5px; text-align:left" | <tt><SDKHOME>\expat-2.0.1\win32\bin\Release\libexpatMT.lib</tt>
| style="padding:5px; text-align:left" | <tt><SDKHOME>\exiv2-0.18.1\msvc\lib\''libexpat''.lib</tt>
|}
</li>
</ol>

'''Comment'''

When using exiv2 0.19 (which works better with bigger files), copy and rename also the following files:

{| class="wikitable"
|- valign="top"
! style="padding:5px; text-align:left" | Source
! style="padding:5px; text-align:left" | Destination
|-
| style="padding:5px; text-align:left" | <tt><SDKHOME>\exiv2-0.19\msvc\xmpsdk\Debug\xmpsdk.lib</tt>
| style="padding:5px; text-align:left" | <tt><SDKHOME>\exiv2-0.19\msvc\lib\''xmpsdkd''.lib</tt>
|-
| style="padding:5px; text-align:left" | <tt><SDKHOME>\exiv2-0.19\msvc\xmpsdk\Release\xmpsdk.lib</tt>
| style="padding:5px; text-align:left" | <tt><SDKHOME>\exiv2-0.19\msvc\lib\xmpsdk.lib</tt>
|}

'''Result'''

The include files reside in
<tt><SDKHOME>\exiv2-0.18.1\msvc\include</tt>

The libraries reside in
<tt><SDKHOME>\exiv2-0.18.1\msvc\lib</tt>

=== GLEW ===

<ol>
<li>Decompress the file <tt>glew-1.5.1-src.zip</tt> to directory <tt><SDKHOME></tt></li>
<li>Apply the <tt>glew.diff</tt> patch [[Hugin SDK (MSVC 2008) Patches#glew]]</li>
<li>Open the file <tt><SDKHOME>\glew\build\vc6\glew.sln</tt></li>
<li>Choose Build > Batch Build</li>
<li>Select Build for Project glew_static with Solution Config 
{| class="wikitable"
|- valign="top"
! style="padding:5px; text-align:left" | 32-Bit
! style="padding:5px; text-align:left" | 64-Bit
|- valign="top"
| style="padding:5px; text-align:left" | Solution Config: "Debug" with Platform: "Win32" 
Solution Config: "Release" with Platform: "Win32"
| style="padding:5px; text-align:left" | Solution Config: "Debug" with Platform: "x64" 
Solution Config: "Release" with Platform: "x64"
|}</li>
<li>Click Build</li>
<li>Close Visual C++ 2008 Express Edition</li>
</ol>

'''Result'''

The include files reside in
<tt><SDKHOME>\glew\include</tt>

The libraries reside in
<tt><SDKHOME>\glew\lib</tt>

{| class="wikitable" width="100%"
|-
! style="padding:5px; text-align:left" | Note
|-
| style="padding:5px; text-align:left" | The GLEW include files are typically included by a statement like <tt>#include "GL/glew.h"</tt> Therefore the base directory of the GLEW include files is <tt><SDKHOME>\glew\include</tt>
|}

=== Panorama Tools ===

Panorama Tools depends on following SDK component:
<ul>
<li>wxWidgets</li>
</ul>
Prepare this component before Panoroma Tools.

<ol>
<li>Set two windows environment variables:
<ul>
<li>Set variable <tt>WXWIDGETS_HOME</tt> to wxWidgets base folder <tt><SDKHOME>\wxWidgets-2.8.10</tt></li>
<li>Set variable <tt>JDK_HOME</tt> to Java SE Development Kit's destination directory name. This directory name was shown during the setup, e.g. <tt>C:\Program Files\Java\jdk1.6.0_13</tt></li>
</ul>
To take effect on changes of environment variables you may have to logout and login.
</li>
<li>Create the directory <tt><SDKHOME>\libpano\pano13</tt></li>
<li>In explorer right-click on created directory <tt><SDKHOME>\libpano\pano13</tt></li>, and then choose SVN Checkout from the shortcut menu. The Checkout dialog appears.</li>
<li>In "URL of repository" field enter following address:
<pre>
https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/libpano
</pre>
</li>
<li>Click OK</li>
<li>After checkout has finished click OK</li>
<li>Apply the <tt>libpano.diff</tt> patch [[Hugin SDK (MSVC 2008) Patches#Panorama Tools]]</li>
<li>Open solution file <tt><SDKHOME>\libpano\pano13\libpano.sln</tt></li>
<li>Select your platform in the Solution Platform pull-down menu</li>
<li>Select "Debug LIB CMD" in Solution Configuration pull-down menu</li>
<li>Select project pano13 in Solution Explorer, and then choose Build > Project Only > Build Only pano13</li>
<li>Select "Release LIB CMD" in Solution Configuration pull-down menu, and then choose Build > Build Solution</li>
<li>Close Visual C++ 2008 Express Edition</li>
</ol>

'''Result'''

The applications reside in
<tt><SDKHOME>\libpano\pano13\tools\Release</tt>

The include files reside in
<tt><SDKHOME>\libpano\pano13</tt>

The libraries reside in
"<tt><SDKHOME>\libpano\pano13\Debug LIB CMD</tt>" and
"<tt><SDKHOME>\libpano\pano13\Release LIB CMD</tt>"

{| class="wikitable" width="100%"
|- valign="top"
! style="padding:5px; text-align:left" | Note
|- valign="top"
| style="padding:5px; text-align:left" | The applications have to be built in release version only. Therefore only pano13 library has to be built in Debug configuration.
|}

=== libxml2 ===

<ol>
<li>Decompress the file <tt>libxml2-sources-2.7.3.tar.gz</tt> to directory <tt><SDKHOME></tt></li>
<li>
{| class="wikitable"
|- valign="top"
! style="padding:5px; text-align:left" | 32-Bit Directions
! style="padding:5px; text-align:left" | 64-Bit Directions
|- valign="top"
| style="padding:5px; text-align:left" | <ol><li>To open a Visual Studio command prompt choose Start > Programs > Microsoft Visual C++ 2008 Express Edition > Visual Studio Tools > Visual Studio 2008 Command Prompt</li></ol>
| style="padding: 5px; text-align:left" | <ol>
<li>Open a Windows SDK prompt by choosing Start -> Programs -> Microsoft Windows SDK v6.1 -> CMD Shell</li>
<li>On the command prompt, enter the following command without any line breaks and press the Return/Enter key: 
<pre>
setenv /Release /x64 /xp
</pre>
It should now refresh and say
<pre>
Setting SDK environment relative to <path where you installed the SDK>
Targeting Windows XP x64 RELEASE
</pre></li>
</ol>
|}
</li>

<li>On command prompt change directory to <tt><SDKHOME>\libxml2-2.7.3\win32</tt> 
'''Example'''
<pre>
Setting environment for using Microsoft Visual Studio 2008 x86 tools.

C:\Program Files\Microsoft Visual Studio 9.0\VC>d:

D:\>cd \usr\src\SDK\libxml2-2.7.3\win32

D:\usr\src\SDK\libxml2-2.7.3\win32>
</pre>

<li>Enter each of the following two commands without any line break and press the Return key.
<pre>
cscript configure.js ftp=no http=no iconv=no cruntime=/MT
nmake -f makefile.msvc libxmla
</pre>
</li>
</ol>

'''Result'''

The include files reside in
<tt><SDKHOME>\libxml2-2.7.3\include</tt>

The libraries reside in
<tt><SDKHOME>\libxml2-2.7.3\win32\bin.msvc</tt>

{| class="wikitable" width="100%"
|-
! style="padding:5px; text-align:left" | Notes
|-
| style="padding:5px; text-align:left" | <ul>
<li>During build process temporary object files are generated in directory
<tt><SDKHOME>\libxml2-2.7.3\win32\int.a.msvc</tt>.
This directories may be deleted to save disc space.</li>
<li>Hugin does not depend on libxml2 library, but autopano-sift-C. Therefore it is included in this SDK.</li>
</ul>
|}

=== autopano-sift-C ===

Autopano-SIFT-C depends on following SDK components:
<ul>
<li>libxml2</li>
<li>Panorama Tool's pano13 library</li>
<li>wxWidgets</li>
</ul>
Prepare these components before Autopano-SIFT-C.

<ol>
<li>Create the directory <tt><SDKHOME>\autopano-sift-C-trunk</tt></li>
<li>In explorer right-click on created directory <tt><SDKHOME>\autopano-sift-C-trunk</tt>, and then choose SVN Checkout from the shortcut menu. The Checkout dialog appears.</li>
<li>In "URL of repository" field enter following address:
<pre>
https://hugin.svn.sourceforge.net/svnroot/hugin/autopano-sift-C/trunk
</pre>
</li>
<li>Click OK</li>
<li>After checkout has finished click OK</li>
<li>Start CMake (cmake-gui). The CMake dialog appears.</li>
<li>In "Where is the source code" field enter
<pre>
<SDKHOME>\autopano-sift-C-trunk
</pre>
Alternatively click Browse Source to point to this directory</li>
<li>In "Where to build the binaries" field enter
<pre>
<SDKHOME>\autopano-sift-C
</pre>
</li>
<li>Click Configure 
If a dialog appears, which asks to create the build directoy, click Yes. 
A dialog appears, where you can specify the generator for the project.</li>
<li>
{| class="wikitable"
|- valign="top"
! style="padding:5px; text-align:left" | 32-Bit Directions
! style="padding:5px; text-align:left" | 64-Bit Directions
|- valign="top"
| style="padding:5px; text-align:left" | Select "Visual Studio 9 2008" and select option "Use default native compilers"
| style="padding:5px; text-align:left" | Select "Visual Studio 9 2008 Win64" and select option "Use default native compilers"
|}</li>
<li>Click Finish 
In the Name and Value list the entries are shown with red background.</li>
<li>Click Configure</li>
<li>Click Generate</li>
<li>Close CMake</li>
<li>Open solution file <tt><SDKHOME>\autopano-sift-C\autopano-sift-C.sln</tt></li>
<li>Select Release in Solution Configuration pull-down menu, and then choose Build > Build Solution</li>
<li>Select project INSTALL in Solution Explorer, and then choose Build > Project Only > Build Only INSTALL</li>
<li>Close Visual C++ 2008 Express Edition</li>
<li>
Copy the directories <tt>bin</tt> and <tt>shared</tt> from <tt><SDKHOME>\autopano-sift-C\INSTALL\FILES</tt> to <tt><SDKHOME>\autopano-sift-C</tt></li>
</ol>

'''Result'''

The applications reside in
<tt><SDKHOME>\autopano-sift-C\bin</tt>

The manual pages reside in
<tt><SDKHOME>\autopano-sift-C\shared</tt>

{| class="wikitable" width="100%"
|- valign="top"
! style="padding:5px; text-align:left" | Note
|- valign="top"
| style="padding:5px; text-align:left" | To save disk space you may delete all files and directories in <tt><SDKHOME>\autopano-sift-C</tt>, except the subdirectories <tt>bin</tt> and <tt>shared</tt>.
|}

=== Freeglut ===
<ol>
<li>Decompress the file <tt>freeglut-2.6.0.tar.gz</tt> to directory <tt><SDKHOME></tt></li>
<li>Open the file <tt><SDKHOME>\freeglut-2.6.0\VisualStudio2008Static\freeglut.sln</tt></li>
<li>Select "Debug" in the Solution Configuration pull-down menu. </li>
<li>Select project freeglut in Solution Explorer, and then choose Build > Project Only > Build Only freeglut</li>
<li>Select "Release" in the Solution Configuration pull-down menu. </li>
<li>Select project freeglut in Solution Explorer, and then choose Build > Project Only > Build Only freeglut</li>
<li>Close Visual Studio C++ 2008 Express Edition</li>
</ol>

'''Result'''

The library resides in <tt><SDKHOME>\freeglut-2.6.0\VisualStudio2008Static\Debug</tt> and <tt><SDKHOME>\freeglut-2.6.0\VisualStudio2008Static\Release</tt>

=== GNU Make ===
<ol>
<li>Decompress the file <tt>make-3.81.tar.gz</tt> to directory <tt><SDKHOME></tt></li>
<li>Open the file <tt><SDKHOME>\make-3.81\make_msvc_net2003.sln</tt> (Confirm convertion.)</li>
<li>Select "Release" in the Solution Configuration pull-down menu. </li>
<li>Select project make_msvc.net2003 Solution Explorer, and then choose Build > Project</li>
<li>Close Visual Studio C++ 2008 Express Edition</li>
<li>Rename the file <tt><SDKHOME>\make-3.81\Release\make_msvc.net2003.exe</tt> to <tt><SDKHOME>\make-3.81\Release\make.exe</tt>
</ol>

'''Result'''

The executable make.exe resides in <tt><SDKHOME>\make-3.81\Release\</tt>

(All other files in this directory can be deleted to save space.)

[[User:Ryansleevi|Ryan Sleevi]] 17:00, 9 May 2009 (UTC)

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

Hardware

2010-02-13T20:55:09Z

Dezen: /* Popular fisheye lenses */ new samyang review added

Almost any type of computer is usable, as long as it is running some version of Windows, Mac OS, Mac OS X or Linux. We recommend you to use a reasonably fast computer, since re-warping images and blending them are quite CPU intensive. A slower computer just means a longer wait, though.

== Memory ==

While a fast processor will speed up the creation of digital panoramas, memory seems to be the single most important hardware requirement. I've stitched 6 and 8 frame panorama's together with as little as 512MB when I had a 3MPix camera, but with my new 8MPix, I can't process more than 3 images with 512 MB. Jumping up to 1 GB of RAM let's me build and manipulate huge digital files. Remember, image manipulation software nearly always stores images in memory uncompressed, so my 3MPix images (2048 x 1536) take up 24MB of RAM. [[User:Jeff|Jeff]] 21:33, 7 Dec 2004 (EST)

However, if you have a large enough hard disk 1 GB of RAM seems enough for all tasks. Both [[Photoshop]] and [[PTStitcher]] use the hard disk heavily. I managed to stitch a 30 layer [[Full 16 bit workflow|16 bit]] 4,000x50,000 pixel panorama on my 1GB Athlon 1400 machine. It took forever and a day not only to stitch but to load into Photoshop, too. Photoshop used 23 GB of scratch disk but work was suprisingly smooth. [[User:Erik Krause|Erik Krause]] 05:51, 30 Apr 2005 (EDT)

One caveat - dual hard drives can markedly improve performance, at least in MS Windows machines. If the windows swap file is located on the same drive as the application scratch file, say photoshop, then Windows and Photoshop are battling over hard drive access. Locating your scratch disk on a different PHYSICAL hard drive helps considerably. If you have three drives, that's even better. One for Windows and software, one for your scratch disk (and more software, or storage) and a third for your working files. You can have a performance increase of 20% or more. --[[User:Add360.com|Add360.com]] 03:09, 7 Nov 2005 (EST)

== Cameras ==
Currently content still on [[Camera Kits]] and [[Cameras]] pages

An interesting alternative for cheap fisheye photography: [http://shop.lomography.com/fisheyecamera/ Lomo Fisheye Camera]: 35mm film camera with a 170° fisheye lens

== Camera Memory ==
Long gone are the days with the 1 meg memory card that came with my first digital camera. Heck, the 64 meg card that came with my last Nikon is now next to useless! I find myself with a collection of cards, from 512 meg up to 1 gig, and I'm looking at the 2 gig cards. With my Coolpix 8700 in Raw mode, the 1 gig card holds around 65 photos! So plan accordingly. You also need to consider memory card speed. A slow card can take several seconds to save a high quality image, compared to a higher speed card taking under a second. Just remember: faster card = higher cost. For situations where you can afford to wait while an image saves, save 25% and get a slower card. But if you need faster save times, you'll be happier with the faster speed cards. Also see Personal Storage Devices at the bottom of this page. --[[User:Add360.com|Add360.com]] 03:10, 7 Nov 2005 (EST)

== Lenses ==
Narrow angle lenses (field of view < 90 degrees) are often used to create high quality panoramas for print. Fisheye lenses are more often used to create comparatively lower quality panoramas for web display, etc., although with a typical digital SLR and the popular Nikkor 10.5mm or Sigma 8mm lens it is common to produce stitched images from 8,000 to 12,000 pixels wide 
With wider angles of view fewer shots are needed to capture a complete scene. Fisheye lenses are typically used for creating immersive 'spherical' panoramas, whereas longer focal length lenses are more normally used to create cylindrical panoramas as it is much harder to assemble the large numbers of tiled shots these require to cover the zenith and nadir (top and bottom) of a complete spherical panorama image.
 In order to assist with setting up your lens and camera there is a [[Entrance Pupil Database]] with relevant dimensions.

=== Popular narrow angle lenses ===
Any fixed focal length lens would be best for maximum quality. Most zoom lenses suffer from non-standard edge light fall-off ([[vignetting]]) and from heavy lens flare. Consumer zoom lenses often perform badly in terms of contrast, sharpness, maximum aperture and [[chromatic aberration]].

=== Popular wide angle lenses ===
{|
| [http://www.sigmaphoto.com/lenses/lenses_all_details.asp?id=3236&navigator=1 Sigma 12-24mm f4.5-5.6] || Super wide-angle zoom lens with a 84-122 degree field of view on film SLR cameras
|-
| [http://www.nikonusa.com/template.php?cat=1&grp=5&productNr=2144 Nikkor 12-24mm f/4 DX] || Super wide-angle zoom lens with a 61-99 degree field of view for Nikon mount DSLR cameras
|}

=== Popular fisheye lenses ===
{|
| [http://www.nikonusa.com/template.php?cat=1&grp=5&productNr=2148 Nikkor 10.5mm f/2.8 DX] || full frame fisheye (180 degrees diagnonally) for Nikon mount DSLR cameras
|-
| [http://peleng8.com Peleng 8mm/f3.5] || fisheye lens covering a 180 degrees field of view
|-valign="top"
| [http://www.syopt.co.kr/eng/product/8mm.asp Samyang 8mm/f.3.5] ||(also known as Bower 8mm, Falcon 8mm, Polar 8mm, Rokinon 8mm, Walimex 8mm and Vivitar 7mm) full frame fisheye lens with manual focus, 180° diagonal field of view with APS-C sensor: Nikon, Pentax, Sony; 167° diagonal field of view with Canon APS-C sensor [http://www.syopt.co.kr/common/pdf/f=8mm.pdf Datasheet] [http://www.versacorp.com/vlink/jcreview/sy8rv9jc.pdf Review by Jeffrey R. Charles [PDF]]
[http://michel.thoby.free.fr/SAMYANG/Early%20test%20report.html Review including panoramic issues by Michel Thoby] 
[http://www.lenstip.com/index.php?test=obiektywu&test_ob=160 Distributor´s review]
|-
| [http://www.sigma-photo.com/lenses/lenses_all_details.asp?id=3336&navigator=6 Sigma 4.5mm/f2.8] || The first 180 deg. Circular Fisheye Lens exclusively for use with APS-C size digital SLR cameras.
|-
| [http://www.sigma-photo.com/lenses/lenses_all_details.asp?id=3319&navigator=4 Sigma 8mm/f3.5] || fisheye lens covering a 180 degrees field of view
|-
| [http://www.rugift.com/photocameras/zenitar_m_fisheye_lens.htm Zenitar 16mm f/2.8] || full frame fisheye (180 degrees diagnonally for 35mm film or full frame sensor) for various SLR and DSLR cameras (manual operation)
|}

=== Fisheye conversion lenses ===
{|
| [http://raynox.co.jp/english/dcr/dcrcf185pro/index.htm Raynox DCR-CF185PRO] || 180 degrees field of view with a standard lens at 35mm
|-
| [http://nikonimaging.com/global/products/accessory/converter/fc-e9/ Nikon FC-E9] || ~185-190 degrees field of view with a standard lens at 35mm (this is '''not''' only for Nikon, I used this with my Canon PS A75.. you need a [http://www.hama.de/portal/articleId*5592/action*2563 52mm >> 46mm adapter ring].. with that it works great with Canon or whatever you want) An [http://nikonimaging.com/global/products/accessory/converter/list.htm adapter ring] is required for ALL Nikon cameras, and can make the setup rather large [[:Image:Fce9.jpg|(almost a foot long!)]]
|-
| [http://nikonimaging.com/global/products/accessory/converter/fc-e8/ Nikon FC-E8] || ~180 degrees field of view with a standard lens at 35mm. [http://nikonimaging.com/global/products/accessory/converter/list.htm adapter ring required]
|}

There are also many small and cheap semi fisheye conversion lenses available from [http://raynox.co.jp Raynox] if you have a small digital camera and quality is not the most important issue:
{|
| [http://raynox.co.jp/english/video/egvideoindex.htm Raynox video camera index] || Look for the 0.3x versions
|}

== Filters ==

== Tripods / Monopods ==
My current favorite tripod for shooting panoramas is the manfrotto 755b.

The tripod is extremely strong, tall, and incorporates a ball head that can be used to quickly level a head - though this does require somewhat of a 'knack' to get the hang of.

Essentially, for just over $200 you can get a really large, strong tripod, with levelling feature. Only downside for me is the weight, but I cannot justify spending 3x the price to get a carbon fibre version!

Stu

Monopods have a couple of advantages. One advantage: Height - many have several sections. They are most popular with one-shot lens users. You can extend the monopod fully, set the self timer on the camera, and position the camera 10' off the ground (held at arms length above your head.) Takes practice, but it works. You'll want to invest in a monopod level. These attach to the monopod leg, kind of like the level used on 4x4' when you build a deck. Another advantage is portability, plus some monopods serve double duty as trekking poles. They are difficult to use for multiple shots, as one can wobble the monopod left, right, back, and forth between shots. It's just like mounting your camera on top of a giant joy-stick! --[[User:Add360.com|Add360.com]] 03:14, 7 Nov 2005 (EST)

== Panoramic Heads ==
When combining multiple images, it is critical that each image be captured from the same point of view. This [[Nodal Point|optical center]] of the lens is commonly called the nodal point, although it is more correctly referred to as the entrance pupil. The nodal point is located inside the lens; in the wide angle lenses used for panoramic imaging, the entrance pupil tends to be near the front of the lens.

A standard tripod mount rotates the camera around the mounting screw in the camera; the simplest [[nodal point adapters|nodal point adapter]] simply shifts the camera back to move the lens's nodal point over the axis of rotation. [[Heads|More complicated brackets]] allow the camera to rotate vertically around the nodal point around the nodal point as well as horizontally.

== Stitching Adapters ==
With lenses that produce a large image circle, it is possible to capture a number of DSLR frames for stitching into a large panorama. Typical lenses that can be used for this purpose come from Medium Format, and Large Format (4x5) camera systems. A stitching adapter is typically used on a Large Format camera to provide precise XY positioning of the DSLR camera, so that all the image tiles are taken in the plane of focus.

In this type of system, since the capture device (DSLR Camera) is moved, but the lens is not; there is no requirement for determining the lens nodal point. However the panorama must be stitched as an orthographic projection.

== Flashes ==
Have a look at [http://www.isitemedia.com.au/developement/flash.htm iSiteMedia's Pano flash] - made from an old studio flash and an opal garden light.

== Miscellaneous ==

== Portable Storage Devices ==
These come in several varieties, a broad price range, and with varying options. Kind of like purchasing a VW Beetle vs a Porsche - either can get you from point A to point B. Basically all models perform the same function: automatically move images from your memory card to the storage device. Just stick in the card and like a digital vacuum, it sucks the images from the card to the device. That is the BASIC function. The type of cards it reads, hard drive space, battery life, simple LCD display vs full color display - the features go on and on. You can preview images on some models, display them on TV via built-in jacks, watch movies, play music. It all depends on your budget! Google "Portable Storage Device" or search on Amazon or eBay. You'll get an idea what's available. Not to long ago there were only a couple of models available. Now you can find dozens! Bottom line: If you take a lot of photos, you'll eventually need one of these! --[[User:Add360.com|Add360.com]] 03:11, 7 Nov 2005 (EST)
 
 NOTE that by now (Dec 2008) the cost of flash memory cards has dropped so much that these portable storage devices are now a rather expensive solution in comparison to buying a few more memory cards. This plus their need for battery power (which can be problematic if you're not near power sources) means that they are no longer the wishlist item they used to be.

Click to see an alphabetical list of panorama related [[hardware manufacturers]].

[[Category:Hardware]]

{{Outdated|Talk}}

Hardware

2010-01-17T20:13:07Z

Dezen: /* Popular fisheye lenses */ alphabetically reordered, samayang lens added

Almost any type of computer is usable, as long as it is running some version of Windows, Mac OS, Mac OS X or Linux. We recommend you to use a reasonably fast computer, since re-warping images and blending them are quite CPU intensive. A slower computer just means a longer wait, though.

== Memory ==

While a fast processor will speed up the creation of digital panoramas, memory seems to be the single most important hardware requirement. I've stitched 6 and 8 frame panorama's together with as little as 512MB when I had a 3MPix camera, but with my new 8MPix, I can't process more than 3 images with 512 MB. Jumping up to 1 GB of RAM let's me build and manipulate huge digital files. Remember, image manipulation software nearly always stores images in memory uncompressed, so my 3MPix images (2048 x 1536) take up 24MB of RAM. [[User:Jeff|Jeff]] 21:33, 7 Dec 2004 (EST)

However, if you have a large enough hard disk 1 GB of RAM seems enough for all tasks. Both [[Photoshop]] and [[PTStitcher]] use the hard disk heavily. I managed to stitch a 30 layer [[Full 16 bit workflow|16 bit]] 4,000x50,000 pixel panorama on my 1GB Athlon 1400 machine. It took forever and a day not only to stitch but to load into Photoshop, too. Photoshop used 23 GB of scratch disk but work was suprisingly smooth. [[User:Erik Krause|Erik Krause]] 05:51, 30 Apr 2005 (EDT)

One caveat - dual hard drives can markedly improve performance, at least in MS Windows machines. If the windows swap file is located on the same drive as the application scratch file, say photoshop, then Windows and Photoshop are battling over hard drive access. Locating your scratch disk on a different PHYSICAL hard drive helps considerably. If you have three drives, that's even better. One for Windows and software, one for your scratch disk (and more software, or storage) and a third for your working files. You can have a performance increase of 20% or more. --[[User:Add360.com|Add360.com]] 03:09, 7 Nov 2005 (EST)

== Cameras ==
Currently content still on [[Camera Kits]] and [[Cameras]] pages

An interesting alternative for cheap fisheye photography: [http://shop.lomography.com/fisheyecamera/ Lomo Fisheye Camera]: 35mm film camera with a 170° fisheye lens

== Camera Memory ==
Long gone are the days with the 1 meg memory card that came with my first digital camera. Heck, the 64 meg card that came with my last Nikon is now next to useless! I find myself with a collection of cards, from 512 meg up to 1 gig, and I'm looking at the 2 gig cards. With my Coolpix 8700 in Raw mode, the 1 gig card holds around 65 photos! So plan accordingly. You also need to consider memory card speed. A slow card can take several seconds to save a high quality image, compared to a higher speed card taking under a second. Just remember: faster card = higher cost. For situations where you can afford to wait while an image saves, save 25% and get a slower card. But if you need faster save times, you'll be happier with the faster speed cards. Also see Personal Storage Devices at the bottom of this page. --[[User:Add360.com|Add360.com]] 03:10, 7 Nov 2005 (EST)

== Lenses ==
Narrow angle lenses (field of view < 90 degrees) are often used to create high quality panoramas for print. Fisheye lenses are more often used to create comparatively lower quality panoramas for web display, etc., although with a typical digital SLR and the popular Nikkor 10.5mm or Sigma 8mm lens it is common to produce stitched images from 8,000 to 12,000 pixels wide 
With wider angles of view fewer shots are needed to capture a complete scene. Fisheye lenses are typically used for creating immersive 'spherical' panoramas, whereas longer focal length lenses are more normally used to create cylindrical panoramas as it is much harder to assemble the large numbers of tiled shots these require to cover the zenith and nadir (top and bottom) of a complete spherical panorama image.
 In order to assist with setting up your lens and camera there is a [[Entrance Pupil Database]] with relevant dimensions.

=== Popular narrow angle lenses ===
Any fixed focal length lens would be best for maximum quality. Most zoom lenses suffer from non-standard edge light fall-off ([[vignetting]]) and from heavy lens flare. Consumer zoom lenses often perform badly in terms of contrast, sharpness, maximum aperture and [[chromatic aberration]].

=== Popular wide angle lenses ===
{|
| [http://www.sigmaphoto.com/lenses/lenses_all_details.asp?id=3236&navigator=1 Sigma 12-24mm f4.5-5.6] || Super wide-angle zoom lens with a 84-122 degree field of view on film SLR cameras
|-
| [http://www.nikonusa.com/template.php?cat=1&grp=5&productNr=2144 Nikkor 12-24mm f/4 DX] || Super wide-angle zoom lens with a 61-99 degree field of view for Nikon mount DSLR cameras
|}

=== Popular fisheye lenses ===
{|
| [http://www.nikonusa.com/template.php?cat=1&grp=5&productNr=2148 Nikkor 10.5mm f/2.8 DX] || full frame fisheye (180 degrees diagnonally) for Nikon mount DSLR cameras
|-
| [http://peleng8.com Peleng 8mm/f3.5] || fisheye lens covering a 180 degrees field of view
|-valign="top"
| [http://www.syopt.co.kr/eng/product/8mm.asp Samyang 8mm/f.3.5] ||(also known as Bower, Polar, Rokinon, Walimex and Falcon) full frame fisheye with manual focus, 180° diagonally with APS-C sensor: Nikon, Pentax, Sony; 167° diagonally with Canon APS-C sensor [http://www.syopt.co.kr/common/pdf/f=8mm.pdf Datasheet] 
[http://michel.thoby.free.fr/SAMYANG/Early%20test%20report.html 1.review incl. panoramic issues], [http://www.lenstip.com/index.php?test=obiektywu&test_ob=160 2.review, note: it´s written by the distributor of the lens]
|-
| [http://www.sigma-photo.com/lenses/lenses_all_details.asp?id=3336&navigator=6 Sigma 4.5mm/f2.8] || The first 180 deg. Circular Fisheye Lens exclusively for use with APS-C size digital SLR cameras.
|-
| [http://www.sigma-photo.com/lenses/lenses_all_details.asp?id=3319&navigator=4 Sigma 8mm/f3.5] || fisheye lens covering a 180 degrees field of view
|-
| [http://www.rugift.com/photocameras/zenitar_m_fisheye_lens.htm Zenitar 16mm f/2.8] || full frame fisheye (180 degrees diagnonally for 35mm film or full frame sensor) for various SLR and DSLR cameras (manual operation)
|}

=== Fisheye conversion lenses ===
{|
| [http://raynox.co.jp/english/dcr/dcrcf185pro/index.htm Raynox DCR-CF185PRO] || 180 degrees field of view with a standard lens at 35mm
|-
| [http://nikonimaging.com/global/products/accessory/converter/fc-e9/ Nikon FC-E9] || ~185-190 degrees field of view with a standard lens at 35mm (this is '''not''' only for Nikon, I used this with my Canon PS A75.. you need a [http://www.hama.de/portal/articleId*5592/action*2563 52mm >> 46mm adapter ring].. with that it works great with Canon or whatever you want) An [http://nikonimaging.com/global/products/accessory/converter/list.htm adapter ring] is required for ALL Nikon cameras, and can make the setup rather large [[:Image:Fce9.jpg|(almost a foot long!)]]
|-
| [http://nikonimaging.com/global/products/accessory/converter/fc-e8/ Nikon FC-E8] || ~180 degrees field of view with a standard lens at 35mm. [http://nikonimaging.com/global/products/accessory/converter/list.htm adapter ring required]
|}

There are also many small and cheap semi fisheye conversion lenses available from [http://raynox.co.jp Raynox] if you have a small digital camera and quality is not the most important issue:
{|
| [http://raynox.co.jp/english/video/egvideoindex.htm Raynox video camera index] || Look for the 0.3x versions
|}

== Filters ==

== Tripods / Monopods ==
My current favorite tripod for shooting panoramas is the manfrotto 755b.

The tripod is extremely strong, tall, and incorporates a ball head that can be used to quickly level a head - though this does require somewhat of a 'knack' to get the hang of.

Essentially, for just over $200 you can get a really large, strong tripod, with levelling feature. Only downside for me is the weight, but I cannot justify spending 3x the price to get a carbon fibre version!

Stu

Monopods have a couple of advantages. One advantage: Height - many have several sections. They are most popular with one-shot lens users. You can extend the monopod fully, set the self timer on the camera, and position the camera 10' off the ground (held at arms length above your head.) Takes practice, but it works. You'll want to invest in a monopod level. These attach to the monopod leg, kind of like the level used on 4x4' when you build a deck. Another advantage is portability, plus some monopods serve double duty as trekking poles. They are difficult to use for multiple shots, as one can wobble the monopod left, right, back, and forth between shots. It's just like mounting your camera on top of a giant joy-stick! --[[User:Add360.com|Add360.com]] 03:14, 7 Nov 2005 (EST)

== Panoramic Heads ==
When combining multiple images, it is critical that each image be captured from the same point of view. This [[Nodal Point|optical center]] of the lens is commonly called the nodal point, although it is more correctly referred to as the entrance pupil. The nodal point is located inside the lens; in the wide angle lenses used for panoramic imaging, the entrance pupil tends to be near the front of the lens.

A standard tripod mount rotates the camera around the mounting screw in the camera; the simplest [[nodal point adapters|nodal point adapter]] simply shifts the camera back to move the lens's nodal point over the axis of rotation. [[Heads|More complicated brackets]] allow the camera to rotate vertically around the nodal point around the nodal point as well as horizontally.

== Stitching Adapters ==
With lenses that produce a large image circle, it is possible to capture a number of DSLR frames for stitching into a large panorama. Typical lenses that can be used for this purpose come from Medium Format, and Large Format (4x5) camera systems. A stitching adapter is typically used on a Large Format camera to provide precise XY positioning of the DSLR camera, so that all the image tiles are taken in the plane of focus.

In this type of system, since the capture device (DSLR Camera) is moved, but the lens is not; there is no requirement for determining the lens nodal point. However the panorama must be stitched as an orthographic projection.

== Flashes ==
Have a look at [http://www.isitemedia.com.au/developement/flash.htm iSiteMedia's Pano flash] - made from an old studio flash and an opal garden light.

== Miscellaneous ==

== Portable Storage Devices ==
These come in several varieties, a broad price range, and with varying options. Kind of like purchasing a VW Beetle vs a Porsche - either can get you from point A to point B. Basically all models perform the same function: automatically move images from your memory card to the storage device. Just stick in the card and like a digital vacuum, it sucks the images from the card to the device. That is the BASIC function. The type of cards it reads, hard drive space, battery life, simple LCD display vs full color display - the features go on and on. You can preview images on some models, display them on TV via built-in jacks, watch movies, play music. It all depends on your budget! Google "Portable Storage Device" or search on Amazon or eBay. You'll get an idea what's available. Not to long ago there were only a couple of models available. Now you can find dozens! Bottom line: If you take a lot of photos, you'll eventually need one of these! --[[User:Add360.com|Add360.com]] 03:11, 7 Nov 2005 (EST)
 
 NOTE that by now (Dec 2008) the cost of flash memory cards has dropped so much that these portable storage devices are now a rather expensive solution in comparison to buying a few more memory cards. This plus their need for battery power (which can be problematic if you're not near power sources) means that they are no longer the wishlist item they used to be.

Click to see an alphabetical list of panorama related [[hardware manufacturers]].

[[Category:Hardware]]

{{Outdated|Talk}}

Entrance Pupil Database

2009-12-31T11:48:32Z

Dezen: /* Number of pics for 360° */ four third lenses reordered

Wouldn't it be great if everyone entered their values for their [[No-parallax point| NPP / Nodal Point / Entrance Pupil]] for lens and camera combinations.
Some searching on the web will find a lot of people saying they want to start to create a database of some kind, but have not seen anything substantial so far (correct me if I am wrong).

Please enter your own values if they are not listed.

Thanks,
--[[User:Korffr|Richard Korff]] 11:12, 13 May 2005 (EDT)

To cater for all the different camera bodies and lenses, the tables have been split into 3 parts:

*The '''[[#Tripod Mount Measurements|first table]]''' shows the position of the tripod mount in relation to the lens axis. This is easy to measure and is dependent only on the camera body.
*The '''[[#Entrance Pupil Measurements|second table]]''' shows the actual entrance pupil distance which is only dependent on the lens itself. Note that the [[No-parallax point|NPP]] for [[Special issues with fisheye lenses|fisheye]] lenses is not constant over the image circle's [[Field of View|FoV]], so you will sometimes find different NPP values depending on the angle where your images overlap.
*The '''[[#Number of pics for 360°|third table]]''' shows the number if pics neccessay for a full 360° coverage and the rotation angle between shots.

Use as much as possible actual measurements rather than the reading on your [[panorama head]], unless your are sure these are the same.

To enter a line for your combination, edit the page by clicking edit at the top of the screen (you may need to create an account or sign-in first), and edit the table below.

== Tripod Mount Measurements ==

{| border="1" cellpadding="5" cellspacing="0" align="left" valign="top" class="wikitable sortable"
|+
! Style="background:#e0e0e0;" width="25%" | '''Camera'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount off-center (C)'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount height (H)'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount length (L1)'''
|-style="vertical-align:top;"
|<div style="width: 200px; height:150px"> </div><hr>Use the correct name of your camera. For digital camera's, please use the name as mentioned at [http://www.dpreview.com/reviews/specs.asp dpreview]. || [[Image:EPDB-off-center.jpg|Tripod mount off-center]]<hr>Looking at the bottom of the camera, the distance between the the middle of the tripod mount to the lens axis (0 if the tripod mount is over the centre of the lens) || [[Image:EPDB-height.jpg|Tripod mount height]]<hr>Facing the camera, the distance from the base of the camera to the center of the lens || [[Image:EPDB-length1.jpg|Tripod mount length]]<hr>Looking at the bottom of the camera, the distance between the middle of the tripod mount to the base of the lens base, or base for adaptor tube. For fixed lens camera's which do not allow use of adaptors this column is not applicable.
|-class="sortbottom"
|Canon EOS 5D MKII || align="center" | 0 mm || align="center" | 43.5 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 20D || align="center" | 0 mm || align="center" | 40 mm || align="center" | 36.5 mm
|-class="sortbottom"
|Canon EOS 40D || align="center" | 0 mm || align="center" | 42 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 400D || align="center" | 0 mm || align="center" | 37 mm || align="center" | 39 mm
|-class="sortbottom"
|Canon EOS 400D with BG-E3 || align="center" | 0 mm || align="center" | 81 mm || align="center" | 33 mm
|-class="sortbottom"
|Canon EOS 300D / Digital Rebel (EOS Digital Rebel) || align="center" | 0 mm || align="center" |40 mm || align="center" | 40 mm
|-class="sortbottom"
|Canon EOS 300D / Digital Rebel || align="center" | 0 mm || align="center" |40 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 350D / Digital Rebel XT || align="center" | 0 mm || align="center" | 37.5 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 450D / Digital Rebel XSi || align="center" | 0 mm || align="center" | 35 mm || align="center" | 39 mm
|-class="sortbottom"
|Canon EOS 500D / Digital Rebel X1i || align="center" | 0 mm || align="center" | 38.5 mm || align="center" | 39 mm

|-class="sortbottom"
|Canon G9 || align="center" | 12 mm || align="center" | 29 mm || align="center" | N/A
|-class="sortbottom"
|Canon PowerShot A630 || align="center" | 15 mm || align="center" | 28 mm || align="center" | 0 mm (fixed lens)
|-class="sortbottom"
|Fujifilm FinePix S7000 || align="center" | 0 mm || align="center" | 32.8 mm || align="center" | 69mm + 37mm(Adapt.Tube)=106mm
|-class="sortbottom"
|Nikon C8800 || align="center" | 19.1 mm || align="center" | 67.9 mm || align="center" | N/A
|-class="sortbottom"
|Nikon D2H (+D2Hs/D2X/D2Xs?) || align="center" | 0 mm || align="center" | 79 mm || align="center" | 29.5 mm
|-class="sortbottom"
|Nikon D40 (+D40x?) || align="center" | 0 mm || align="center" | 36 mm || align="center" | 42 mm
|-class="sortbottom"
|Nikon D60 || align="center" | 0 mm || align="center" | 42 mm || align="center" | 36 mm
|-class="sortbottom"
|Nikon D70 || align="center" | 0 mm || align="center" | 52 mm || align="center" | 36 mm
|-class="sortbottom"
|Nikon D80 || align="center" | 0 mm || align="center" | 42.8 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D90 || align="center" | 0 mm || align="center" | 42.8 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D100 with MB-D100 || align="center" | 0 mm || align="center" | 93 mm || align="center" | 33.5 mm
|-class="sortbottom"
|Nikon D200 || align="center" | 0 mm || align="center" | 47 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D200 with MB-D200 || align="center" | 0 mm || align="center" | 93 mm || align="center" | ~33 mm
|-class="sortbottom"
|Nikon D300 || align="center" | 0 mm || align="center" | 47.6 mm || align="center" | 42.4 mm
|-class="sortbottom"
|Nikon D300 with MB-D10 || align="center" | 0 mm || align="center" | 90.2 mm || align="center" | 31.4 mm
|-class="sortbottom"
|Pentax K10D/K20D || align="center" | 0 mm || align="center" | 41.6 mm || align="center" | 37.2 mm
|-class="sortbottom"
|Sony Alpha A100 || align="center" | 0 mm || align="center" | 37 mm || align="center" | 35 mm
|}

 
 
 
 
 
 

== Entrance Pupil Measurements ==

{| border="1" cellpadding="5" cellspacing="0" align="center" class="wikitable sortable"
|+
! style="background:#e0e0e0;" width="25%" | '''Lens'''
! style="background:#e0e0e0;" width="25%" | '''Focal Length'''
! style="background:#e0e0e0;" width="50%" | '''Entrance Pupil Length (L2)'''
|-valign="top"
|<div style="height:150px;"> </div><hr>Enter the exact lens name, or if you are using a camera with a fixed lens the name of your camera as mentioned at [http://www.dpreview.com/reviews/specs.asp dpreview].||<div style="height:150px;"> </div><hr> ||[[Image:EPDB-length2.jpg|Entrance Pupil Length]]<hr>Facing the side of the lens, the distance from the base of the lens to the Entrance Pupil. A negative value means the entrance pupil is before the lens base. (not sure if this makes sense in a theoretical way)
|-class="sortbottom"
| EF-S 10-22mm || align="center" | 10mm || align="center" | 66mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 18mm || align="center" | 47mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 24mm || align="center" | 23mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 35mm || align="center" | 45mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 55mm || align="center" | 55mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 17mm || align="center" | 71mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 28mm || align="center" | 69mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 40mm || align="center" | 72mm
|-class="sortbottom"
| Canon 50mm f/1.8 II || align="center" | 50mm || align="center" | 23mm
|-class="sortbottom"
| Canon 35mm f/2 || align="center" | 35mm || align="center" | 12.5mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 70mm || align="center" | 83mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 85mm || align="center" | 70mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 100mm || align="center" | 45mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 135mm || align="center" | -30mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 200mm || align="center" | -30mm
|-class="sortbottom"
| Nikkor AF-S DX 18-55mm II|| align="center" | 18mm || align="center" | 70mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 18mm || align="center" | 51mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 24mm || align="center" | 44mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 35mm || align="center" | 33.5mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 50mm || align="center" | 24.5mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 70mm || align="center" | -6.5mm
|-class="sortbottom"
| Nikkor AF DX 10.5mm || align="center" | 10.5mm || align="center" | 45.5mm
|-class="sortbottom"
| Nikkor AF DX 10.5mm || align="center" | 10.5mm || align="center" | 46mm
|-class="sortbottom"
| Nikkor AF-S DX 35mm/1.8G || align="center" | 35mm || align="center" | 18mm
|-class="sortbottom"
| Sigma 10mm f/2.8 EX DC HSM Fisheye (60° stops) || align="center" | 10mm || align="center" | 50mm
|-class="sortbottom"
| Sigma 8mm F4.0 EX || align="center" | 8mm || align="center" | 47.5mm / 49mm / 51mm - which one is it?
|-class="sortbottom"
| Sigma 8mm F3.5 EX || align="center" | 8mm || align="center" |
|-class="sortbottom"
| Nikon C8800 at Wide inf. (is this at the widest setting ?) || align="center" | 8.9mm ?? || align="center" | 75mm center of tripod mtg screw to Ent Pupil
|-class="sortbottom"
| Peleng-N 8mm F3.5 || align="center" | 8mm || align="center" | 44mm
|-class="sortbottom"
| Opteka 0.22X UHD II FishEye || align="center" | 0.22X - 8mm || align="center" | 35.75mm
|-class="sortbottom"
| Tamron 90mm F2.8 Di2 Macro || align="center" | 90mm || align="center" | 34mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 10mm || align="center" | 62mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 14mm || align="center" | 64mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 20mm || align="center" | 68mm
|-class="sortbottom"
| Sigma 30mm F1.4 EX DC || align="center" | 30mm || align="center" | 26.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 11mm || align="center" | 58.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 14mm || align="center" | 59.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 18mm || align="center" | 62.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 17mm || align="center" | 56.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 24mm || align="center" | 48mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 35mm || align="center" | 40.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 50mm || align="center" | 31.5mm
|-class="sortbottom"
| Tamron 28-75mm F2.8 XR DI || align="center" | 28-75mm || align="center" | 58.8mm
|-class="sortbottom"
| Tokina 12-24mm f4 DX || align="center" | 12mm || align="center" | 60mm
|-class="sortbottom"
| Carl Zeiss Jena Flektogon 20mm f/4 || align="center" | 20mm || align="center" | 17.5mm
|-class="sortbottom"
| Raynox DCR-CF185PRO || align="center" | Conversion lens || align="center" | 80mm
|-class="sortbottom"
| Canon PowerShot A630 || align="center" | 35mm (wide open) || align="center" | 31mm
|-class="sortbottom"
| Canon G9 || align="center" | 7.4mm (wide) || align="center" | 33.7mm from tripod screw
|-class="sortbottom"
| Canon G9 || align="center" | 44.4mm (tight) || align="center" | -10mm from tripod screw
|-class="sortbottom"
| Zenitar 2,8/16 || align="center" | 16mm || align="center" | 36mm
|-class="sortbottom"
| Pentax smc DA 10-17mm F3.5-4.5 Fisheye zoom || align="center" | 10mm || align="center" | 57.8mm
|-class="sortbottom"
| <Manufacturer / Lens> || align="center" | <Focal Length> || align="center" | <Entrance Pupil Length>
|}

 

*To calculate the Entrance pupil distance add the Tripod Mount Length (L1) from the camera and the Entrance Pupil Length (L2) from the lens. So for example for a Canon 300d and a 10-22mm at 10mm, the total Entrance pupil distance from the tripod mount is 40mm + 66mm = 106mm

*For these '''''Focal Length''''' values the actual focus is set to infinity (<math>\infty</math>)

== Number of pics for 360° ==

{| border="1" cellpadding="5" cellspacing="0" align="left"
|+
! style="background:#e0e0e0;" rowspan="3" | '''Focal Length Lens Type'''
! style="background:#e0e0e0;" colspan="4" | '''crop factor 1.5/1.6 '''
! style="background:#e0e0e0;" colspan="4" | '''Full Frame'''
|-
! style="background:#e0e0e0;" colspan="2" | '''Portrait '''
! style="background:#e0e0e0;" colspan="2" | '''Landscape'''
! style="background:#e0e0e0;" colspan="2" | '''Portrait '''
! style="background:#e0e0e0;" colspan="2" | '''Landscape'''
|-
|style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate ||style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate
|style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate ||style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate
|-
||8mm fisheye
||4||90°|| ||
||3||120°||3||120°
|-
||10.5mm fisheye
||6||60°|| ||
||4||90°|| ||
|-
||16mm fisheye
|| || || ||
||6||60°||4||90°
|-
||10mm rectilinear
||6||60°||4||90°
|| || || ||
|-
||14mm rectilinear
||8||45°||6||60°
|| || || ||
|-
||18mm rectilinear
||10||36°||8||45°
|| || || ||
|-
||24mm rectilinear
||12||30°||8||45°
||8||45°||6||60°
|-
||28mm rectilinear
||15||24°||10||36°
||12-8||30°-40°||8-6||40°-60°
|-
||35mm rectilinear
||18||20°||12||30°
||18-12||20°-30°||12-8||30°-40°
|-
||50mm rectilinear
||24||15°||18||20°
||18||20°||12||30°
|-
||70mm rectilinear
||36||10°||24||15°
||24||15°||15||24°
|}
{{clr}}

{| border="1" cellpadding="5" cellspacing="0" align="left"
|+
! style="background:#e0e0e0;" rowspan="3" | '''Focal Length'''
! style="background:#e0e0e0;" colspan="4" | '''(Micro-) Four Thirds (crop factor 2.0)'''
|-
! style="background:#e0e0e0;" colspan="2" | '''Portrait '''
! style="background:#e0e0e0;" colspan="2" | '''Landscape'''
|-
|style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate ||style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate
|-
||8mm fisheye
||4||90°||3||120°
|-
||7mm rectilinear
||5||72°||4||90°
|-
||9mm rectilinear
||6||60°||5||72°
|-
||11mm rectilinear
||7||51,5°||6||60°
|-
||12mm rectilinear
||8||45°||6||60°
|-
||14mm rectilinear
||9||40°||7||51,5°
|-
||17mm rectilinear
||11||33°||8||45°
|-
||18mm rectilinear
||11||33°||9||40°
|-
||25mm rectilinear
||15||24°||12||30°
|-
||35mm rectilinear
||21||17°||16||22,5°
|-
||40mm rectilinear
||24||15°||18||20°
|}
{{clr}}

== Related Resources ==

* VRwave lens database - http://www.vrwave.com/panoramic/photography/lens_database.html
* Panoramic Resolution by Ken Turkowski - http://www.worldserver.com/turk/quicktimevr/panores.html
* Panoramic Calculator by Frank van der Pol - http://www.frankvanderpol.nl/fov_pan_calc.htm
* Panoramic calculator by Sean T. McHugh (at the very bottom) http://www.cambridgeincolour.com/tutorials/image-projections.htm
* Olympus E-System specific data (german)
** http://olypedia.de/Nodalpunkte_E_System tripod mount and entrance pupil measurements
** http://olypedia.de/Nodalpunkte_E-300_/_E-500 entrance pupil measurements with different lenses
** http://olypedia.de/Nodalpunkte_E-1 entrance pupil measurements for E-1 with different lenses
[[Category:Hardware]]

{{Incomplete|Talk}}

Entrance Pupil Database

2009-12-30T23:33:14Z

Dezen: /* Number of pics for 360° */ an extra tabel for Four Thirds Lenses added, as most focal lengths did no fit due to the crop factor

Wouldn't it be great if everyone entered their values for their [[No-parallax point| NPP / Nodal Point / Entrance Pupil]] for lens and camera combinations.
Some searching on the web will find a lot of people saying they want to start to create a database of some kind, but have not seen anything substantial so far (correct me if I am wrong).

Please enter your own values if they are not listed.

Thanks,
--[[User:Korffr|Richard Korff]] 11:12, 13 May 2005 (EDT)

To cater for all the different camera bodies and lenses, the tables have been split into 3 parts:

*The '''[[#Tripod Mount Measurements|first table]]''' shows the position of the tripod mount in relation to the lens axis. This is easy to measure and is dependent only on the camera body.
*The '''[[#Entrance Pupil Measurements|second table]]''' shows the actual entrance pupil distance which is only dependent on the lens itself. Note that the [[No-parallax point|NPP]] for [[Special issues with fisheye lenses|fisheye]] lenses is not constant over the image circle's [[Field of View|FoV]], so you will sometimes find different NPP values depending on the angle where your images overlap.
*The '''[[#Number of pics for 360°|third table]]''' shows the number if pics neccessay for a full 360° coverage and the rotation angle between shots.

Use as much as possible actual measurements rather than the reading on your [[panorama head]], unless your are sure these are the same.

To enter a line for your combination, edit the page by clicking edit at the top of the screen (you may need to create an account or sign-in first), and edit the table below.

== Tripod Mount Measurements ==

{| border="1" cellpadding="5" cellspacing="0" align="left" valign="top" class="wikitable sortable"
|+
! Style="background:#e0e0e0;" width="25%" | '''Camera'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount off-center (C)'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount height (H)'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount length (L1)'''
|-style="vertical-align:top;"
|<div style="width: 200px; height:150px"> </div><hr>Use the correct name of your camera. For digital camera's, please use the name as mentioned at [http://www.dpreview.com/reviews/specs.asp dpreview]. || [[Image:EPDB-off-center.jpg|Tripod mount off-center]]<hr>Looking at the bottom of the camera, the distance between the the middle of the tripod mount to the lens axis (0 if the tripod mount is over the centre of the lens) || [[Image:EPDB-height.jpg|Tripod mount height]]<hr>Facing the camera, the distance from the base of the camera to the center of the lens || [[Image:EPDB-length1.jpg|Tripod mount length]]<hr>Looking at the bottom of the camera, the distance between the middle of the tripod mount to the base of the lens base, or base for adaptor tube. For fixed lens camera's which do not allow use of adaptors this column is not applicable.
|-class="sortbottom"
|Canon EOS 5D MKII || align="center" | 0 mm || align="center" | 43.5 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 20D || align="center" | 0 mm || align="center" | 40 mm || align="center" | 36.5 mm
|-class="sortbottom"
|Canon EOS 40D || align="center" | 0 mm || align="center" | 42 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 400D || align="center" | 0 mm || align="center" | 37 mm || align="center" | 39 mm
|-class="sortbottom"
|Canon EOS 400D with BG-E3 || align="center" | 0 mm || align="center" | 81 mm || align="center" | 33 mm
|-class="sortbottom"
|Canon EOS 300D / Digital Rebel (EOS Digital Rebel) || align="center" | 0 mm || align="center" |40 mm || align="center" | 40 mm
|-class="sortbottom"
|Canon EOS 300D / Digital Rebel || align="center" | 0 mm || align="center" |40 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 350D / Digital Rebel XT || align="center" | 0 mm || align="center" | 37.5 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 450D / Digital Rebel XSi || align="center" | 0 mm || align="center" | 35 mm || align="center" | 39 mm
|-class="sortbottom"
|Canon EOS 500D / Digital Rebel X1i || align="center" | 0 mm || align="center" | 38.5 mm || align="center" | 39 mm

|-class="sortbottom"
|Canon G9 || align="center" | 12 mm || align="center" | 29 mm || align="center" | N/A
|-class="sortbottom"
|Canon PowerShot A630 || align="center" | 15 mm || align="center" | 28 mm || align="center" | 0 mm (fixed lens)
|-class="sortbottom"
|Fujifilm FinePix S7000 || align="center" | 0 mm || align="center" | 32.8 mm || align="center" | 69mm + 37mm(Adapt.Tube)=106mm
|-class="sortbottom"
|Nikon C8800 || align="center" | 19.1 mm || align="center" | 67.9 mm || align="center" | N/A
|-class="sortbottom"
|Nikon D2H (+D2Hs/D2X/D2Xs?) || align="center" | 0 mm || align="center" | 79 mm || align="center" | 29.5 mm
|-class="sortbottom"
|Nikon D40 (+D40x?) || align="center" | 0 mm || align="center" | 36 mm || align="center" | 42 mm
|-class="sortbottom"
|Nikon D60 || align="center" | 0 mm || align="center" | 42 mm || align="center" | 36 mm
|-class="sortbottom"
|Nikon D70 || align="center" | 0 mm || align="center" | 52 mm || align="center" | 36 mm
|-class="sortbottom"
|Nikon D80 || align="center" | 0 mm || align="center" | 42.8 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D90 || align="center" | 0 mm || align="center" | 42.8 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D100 with MB-D100 || align="center" | 0 mm || align="center" | 93 mm || align="center" | 33.5 mm
|-class="sortbottom"
|Nikon D200 || align="center" | 0 mm || align="center" | 47 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D200 with MB-D200 || align="center" | 0 mm || align="center" | 93 mm || align="center" | ~33 mm
|-class="sortbottom"
|Nikon D300 || align="center" | 0 mm || align="center" | 47.6 mm || align="center" | 42.4 mm
|-class="sortbottom"
|Nikon D300 with MB-D10 || align="center" | 0 mm || align="center" | 90.2 mm || align="center" | 31.4 mm
|-class="sortbottom"
|Pentax K10D/K20D || align="center" | 0 mm || align="center" | 41.6 mm || align="center" | 37.2 mm
|-class="sortbottom"
|Sony Alpha A100 || align="center" | 0 mm || align="center" | 37 mm || align="center" | 35 mm
|}

 
 
 
 
 
 

== Entrance Pupil Measurements ==

{| border="1" cellpadding="5" cellspacing="0" align="center" class="wikitable sortable"
|+
! style="background:#e0e0e0;" width="25%" | '''Lens'''
! style="background:#e0e0e0;" width="25%" | '''Focal Length'''
! style="background:#e0e0e0;" width="50%" | '''Entrance Pupil Length (L2)'''
|-valign="top"
|<div style="height:150px;"> </div><hr>Enter the exact lens name, or if you are using a camera with a fixed lens the name of your camera as mentioned at [http://www.dpreview.com/reviews/specs.asp dpreview].||<div style="height:150px;"> </div><hr> ||[[Image:EPDB-length2.jpg|Entrance Pupil Length]]<hr>Facing the side of the lens, the distance from the base of the lens to the Entrance Pupil. A negative value means the entrance pupil is before the lens base. (not sure if this makes sense in a theoretical way)
|-class="sortbottom"
| EF-S 10-22mm || align="center" | 10mm || align="center" | 66mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 18mm || align="center" | 47mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 24mm || align="center" | 23mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 35mm || align="center" | 45mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 55mm || align="center" | 55mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 17mm || align="center" | 71mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 28mm || align="center" | 69mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 40mm || align="center" | 72mm
|-class="sortbottom"
| Canon 50mm f/1.8 II || align="center" | 50mm || align="center" | 23mm
|-class="sortbottom"
| Canon 35mm f/2 || align="center" | 35mm || align="center" | 12.5mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 70mm || align="center" | 83mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 85mm || align="center" | 70mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 100mm || align="center" | 45mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 135mm || align="center" | -30mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 200mm || align="center" | -30mm
|-class="sortbottom"
| Nikkor AF-S DX 18-55mm II|| align="center" | 18mm || align="center" | 70mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 18mm || align="center" | 51mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 24mm || align="center" | 44mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 35mm || align="center" | 33.5mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 50mm || align="center" | 24.5mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 70mm || align="center" | -6.5mm
|-class="sortbottom"
| Nikkor AF DX 10.5mm || align="center" | 10.5mm || align="center" | 45.5mm
|-class="sortbottom"
| Nikkor AF DX 10.5mm || align="center" | 10.5mm || align="center" | 46mm
|-class="sortbottom"
| Nikkor AF-S DX 35mm/1.8G || align="center" | 35mm || align="center" | 18mm
|-class="sortbottom"
| Sigma 10mm f/2.8 EX DC HSM Fisheye (60° stops) || align="center" | 10mm || align="center" | 50mm
|-class="sortbottom"
| Sigma 8mm F4.0 EX || align="center" | 8mm || align="center" | 47.5mm / 49mm / 51mm - which one is it?
|-class="sortbottom"
| Sigma 8mm F3.5 EX || align="center" | 8mm || align="center" |
|-class="sortbottom"
| Nikon C8800 at Wide inf. (is this at the widest setting ?) || align="center" | 8.9mm ?? || align="center" | 75mm center of tripod mtg screw to Ent Pupil
|-class="sortbottom"
| Peleng-N 8mm F3.5 || align="center" | 8mm || align="center" | 44mm
|-class="sortbottom"
| Opteka 0.22X UHD II FishEye || align="center" | 0.22X - 8mm || align="center" | 35.75mm
|-class="sortbottom"
| Tamron 90mm F2.8 Di2 Macro || align="center" | 90mm || align="center" | 34mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 10mm || align="center" | 62mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 14mm || align="center" | 64mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 20mm || align="center" | 68mm
|-class="sortbottom"
| Sigma 30mm F1.4 EX DC || align="center" | 30mm || align="center" | 26.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 11mm || align="center" | 58.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 14mm || align="center" | 59.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 18mm || align="center" | 62.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 17mm || align="center" | 56.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 24mm || align="center" | 48mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 35mm || align="center" | 40.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 50mm || align="center" | 31.5mm
|-class="sortbottom"
| Tamron 28-75mm F2.8 XR DI || align="center" | 28-75mm || align="center" | 58.8mm
|-class="sortbottom"
| Tokina 12-24mm f4 DX || align="center" | 12mm || align="center" | 60mm
|-class="sortbottom"
| Carl Zeiss Jena Flektogon 20mm f/4 || align="center" | 20mm || align="center" | 17.5mm
|-class="sortbottom"
| Raynox DCR-CF185PRO || align="center" | Conversion lens || align="center" | 80mm
|-class="sortbottom"
| Canon PowerShot A630 || align="center" | 35mm (wide open) || align="center" | 31mm
|-class="sortbottom"
| Canon G9 || align="center" | 7.4mm (wide) || align="center" | 33.7mm from tripod screw
|-class="sortbottom"
| Canon G9 || align="center" | 44.4mm (tight) || align="center" | -10mm from tripod screw
|-class="sortbottom"
| Zenitar 2,8/16 || align="center" | 16mm || align="center" | 36mm
|-class="sortbottom"
| Pentax smc DA 10-17mm F3.5-4.5 Fisheye zoom || align="center" | 10mm || align="center" | 57.8mm
|-class="sortbottom"
| <Manufacturer / Lens> || align="center" | <Focal Length> || align="center" | <Entrance Pupil Length>
|}

 

*To calculate the Entrance pupil distance add the Tripod Mount Length (L1) from the camera and the Entrance Pupil Length (L2) from the lens. So for example for a Canon 300d and a 10-22mm at 10mm, the total Entrance pupil distance from the tripod mount is 40mm + 66mm = 106mm

*For these '''''Focal Length''''' values the actual focus is set to infinity (<math>\infty</math>)

== Number of pics for 360° ==

{| border="1" cellpadding="5" cellspacing="0" align="left"
|+
! style="background:#e0e0e0;" rowspan="3" | '''Focal Length Lens Type'''
! style="background:#e0e0e0;" colspan="4" | '''crop factor 1.5/1.6 '''
! style="background:#e0e0e0;" colspan="4" | '''Full Frame'''
|-
! style="background:#e0e0e0;" colspan="2" | '''Portrait '''
! style="background:#e0e0e0;" colspan="2" | '''Landscape'''
! style="background:#e0e0e0;" colspan="2" | '''Portrait '''
! style="background:#e0e0e0;" colspan="2" | '''Landscape'''
|-
|style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate ||style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate
|style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate ||style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate
|-
||8mm fisheye
||4||90°|| ||
||3||120°||3||120°
|-
||10.5mm fisheye
||6||60°|| ||
||4||90°|| ||
|-
||16mm fisheye
|| || || ||
||6||60°||4||90°
|-
||10mm rectilinear
||6||60°||4||90°
|| || || ||
|-
||14mm rectilinear
||8||45°||6||60°
|| || || ||
|-
||18mm rectilinear
||10||36°||8||45°
|| || || ||
|-
||24mm rectilinear
||12||30°||8||45°
||8||45°||6||60°
|-
||28mm rectilinear
||15||24°||10||36°
||12-8||30°-40°||8-6||40°-60°
|-
||35mm rectilinear
||18||20°||12||30°
||18-12||20°-30°||12-8||30°-40°
|-
||50mm rectilinear
||24||15°||18||20°
||18||20°||12||30°
|-
||70mm rectilinear
||36||10°||24||15°
||24||15°||15||24°
|}
{{clr}}

{| border="1" cellpadding="5" cellspacing="0" align="left"
|+
! style="background:#e0e0e0;" rowspan="3" | '''Focal Length'''
! style="background:#e0e0e0;" colspan="4" | '''(Micro-) Four Thirds (crop factor 2.0)'''
|-
! style="background:#e0e0e0;" colspan="2" | '''Portrait '''
! style="background:#e0e0e0;" colspan="2" | '''Landscape'''
|-
|style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate ||style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate
|-
||8mm fisheye
|| || || ||
|-
||7mm rectilinear
||4||90°||5||72°
|-
||9mm rectilinear
||5||72°||6||60°
|-
||11mm rectilinear
||6||60°||7||51,5°
|-
||12mm rectilinear
||6||60°||8||45°
|-
||14mm rectilinear
||7||51,5°||9||40°
|-
||17mm rectilinear
||8||45°||11||33°
|-
||18mm rectilinear
||9||40°||11||33°
|-
||25mm rectilinear
||12||30°||15||24°
|-
||35mm rectilinear
||16||22,5°||21||17°
|-
||40mm rectilinear
||18||20°||24||15°
|}
{{clr}}

== Related Resources ==

* VRwave lens database - http://www.vrwave.com/panoramic/photography/lens_database.html
* Panoramic Resolution by Ken Turkowski - http://www.worldserver.com/turk/quicktimevr/panores.html
* Panoramic Calculator by Frank van der Pol - http://www.frankvanderpol.nl/fov_pan_calc.htm
* Panoramic calculator by Sean T. McHugh (at the very bottom) http://www.cambridgeincolour.com/tutorials/image-projections.htm
* Olympus E-System specific data (german)
** http://olypedia.de/Nodalpunkte_E_System tripod mount and entrance pupil measurements
** http://olypedia.de/Nodalpunkte_E-300_/_E-500 entrance pupil measurements with different lenses
** http://olypedia.de/Nodalpunkte_E-1 entrance pupil measurements for E-1 with different lenses
[[Category:Hardware]]

{{Incomplete|Talk}}

Talk:Entrance Pupil Database

2009-12-10T19:48:00Z

Dezen: /* Tables */

I am confused by the terms "horizontal" and "off-axial" adjustment.

It seems like they should be "horizontal" and "vertical".

And these depend on camera orientation. The distance between camera base and lens axis is "horizontal" only if the camera is in portrait orientation. In landscape, that same distance is "vertical".

Pictures should make this clear.

Perhaps it would be even more clear to refer to these offsets as "basal" and "lateral", or some such.

Is there a standard nomenclature for these things? Where is it defined?

--Rik

------
Rik,

I agree with you. Initially I had x, y and z but that would probably be just as arbitrary.
I have not had the time to take pictures of the setup to show what I mean.
The descriptions I had in mind are based on a portrait setup.

I am not sure if there are standard definition for it. I was not able to find it.
Any help or suggestions would be helpfull.

Richard
------

== Number of picture for 360 / Degrees between picture ==

Peter,

Thanks for adding your measurements.

I have a question. I thought the degrees between the pictures would only be applicable to Fisheye lenses ? Does that also apply to normal lenses ? Or is the difference only noticable in Fisheye lenses, and too small have an impact on normal lenses.

Thanks,

Richard

-- [[User:Korffr|Korffr]] 10:40, 22 May 2005 (EDT)

Hi Richard,

Sorry, I don't know if there is a difference between fisheye and normal lenses. For me it is more an information about the number of pictures needed for 360 degrees with enough overlap. These values are for portrait orientation. Probably we should make a third table with additional things like this then put all the informations in one table, isn't it?

--[[User:Pitdavos|Pitdavos]] 11:31, 22 May 2005 (EDT)

== Tripod Mount Length L1 ==
The text for this measurment includes "For fixed lens camera's this column is not applicable." Is this really true ? A lot of "Fixed" lens cameras do allow the addition of an adaptor tube which then permits the additional lenses to be added - whilst this implies that such cameras are not "Fixed lens" the way it reads now I suspect puts people off inserting a measurment for cameras which include a Fixed lens.

Unless there is another reason I would propose to change the text to read;
"Looking at the bottom of the camera, the distance between the middle of the tripod mount to the base of the lens base, or base for adaptor tube. For fixed lens camera's which do not allow use of adaptors this column is not applicable."

Thoughts ?

Geoff

OK well no comments after several weeks so, changes made and the Fuji S7000 is listed with the length of its adaptor tube as well as an example

Geoff

== Focal Length / # of pics for 360° / Degree between pics ==

The number of pictures for 360° and the angle between two pictures doesn't depend only on focal length... It also depends on the size of the sensor. For instance the angle is roughly the same for 28mm on an EOS 5D (24x36 sensor) and 17mm on an EOS 350D (APS sensor).

I suggest to put this information to a separate table. [[User:JX|JX]] 16:46, 10 April 2008 (CEST)
:Good idea. (When setting up this table there where almost no full frame sensors available. Could you contribute values?--[[User:Erik Krause|Erik Krause]] 18:19, 11 April 2008 (CEST)

:: I will.. when I get time, probably in May. [[User:JX|JX]] 18:13, 14 April 2008 (CEST)

==Enhance==
The Entrance pupil database needs constant enhancement. Please enter the NPP-settings you found for your camera.

== Canon 5d Mark II ==

Does anyone have these measurements for the Canon 5d Mark II? -[[User:Dvmorris|Dvmorris]] 17:29, 11 April 2009 (UTC)

==Tables==
My suggestion would be to, to split the tables or to mark them with a color according to the manufacturer [[User:Dezen|Dezen]] 19:48, 10 December 2009 (UTC)

Talk:Entrance Pupil Database

2009-12-10T19:47:37Z

Dezen:

Entrance Pupil Database

2009-12-10T19:44:41Z

Dezen: /* Number of pics for 360° */ columns for olympus added, data coming soon

Wouldn't it be great if everyone entered their values for their [[No-parallax point| NPP / Nodal Point / Entrance Pupil]] for lens and camera combinations.
Some searching on the web will find a lot of people saying they want to start to create a database of some kind, but have not seen anything substantial so far (correct me if I am wrong).

Please enter your own values if they are not listed.

Thanks,
--[[User:Korffr|Richard Korff]] 11:12, 13 May 2005 (EDT)

To cater for all the different camera bodies and lenses, the tables have been split into 3 parts:

*The '''[[#Tripod Mount Measurements|first table]]''' shows the position of the tripod mount in relation to the lens axis. This is easy to measure and is dependent only on the camera body.
*The '''[[#Entrance Pupil Measurements|second table]]''' shows the actual entrance pupil distance which is only dependent on the lens itself. Note that the [[No-parallax point|NPP]] for [[Special issues with fisheye lenses|fisheye]] lenses is not constant over the image circle's [[Field of View|FoV]], so you will sometimes find different NPP values depending on the angle where your images overlap.
*The '''[[#Number of pics for 360°|third table]]''' shows the number if pics neccessay for a full 360° coverage and the rotation angle between shots.

Use as much as possible actual measurements rather than the reading on your [[panorama head]], unless your are sure these are the same.

To enter a line for your combination, edit the page by clicking edit at the top of the screen (you may need to create an account or sign-in first), and edit the table below.

== Tripod Mount Measurements ==

{| border="1" cellpadding="5" cellspacing="0" align="left" valign="top" class="wikitable sortable"
|+
! Style="background:#e0e0e0;" width="25%" | '''Camera'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount off-center (C)'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount height (H)'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount length (L1)'''
|-style="vertical-align:top;"
|<div style="width: 200px; height:150px"> </div><hr>Use the correct name of your camera. For digital camera's, please use the name as mentioned at [http://www.dpreview.com/reviews/specs.asp dpreview]. || [[Image:EPDB-off-center.jpg|Tripod mount off-center]]<hr>Looking at the bottom of the camera, the distance between the the middle of the tripod mount to the lens axis (0 if the tripod mount is over the centre of the lens) || [[Image:EPDB-height.jpg|Tripod mount height]]<hr>Facing the camera, the distance from the base of the camera to the center of the lens || [[Image:EPDB-length1.jpg|Tripod mount length]]<hr>Looking at the bottom of the camera, the distance between the middle of the tripod mount to the base of the lens base, or base for adaptor tube. For fixed lens camera's which do not allow use of adaptors this column is not applicable.
|-class="sortbottom"
|Canon EOS 5D MKII || align="center" | 0 mm || align="center" | 43.5 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 20D || align="center" | 0 mm || align="center" | 40 mm || align="center" | 36.5 mm
|-class="sortbottom"
|Canon EOS 40D || align="center" | 0 mm || align="center" | 42 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 400D || align="center" | 0 mm || align="center" | 37 mm || align="center" | 39 mm
|-class="sortbottom"
|Canon EOS 400D + BG-E3 (battery grip)|| align="center" | 0 mm || align="center" | 81 mm || align="center" | 33 mm
|-class="sortbottom"
|Canon EOS 300D / Digital Rebel (EOS Digital Rebel) || align="center" | 0 mm || align="center" |40 mm || align="center" | 40 mm
|-class="sortbottom"
|Canon EOS 300D / Digital Rebel (measured by NP) || align="center" | 0 mm || align="center" |40 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 350D / Digital Rebel XT (measured by NP) || align="center" | 0 mm || align="center" | 37.5 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 450D / Digital Rebel XSi || align="center" | 0 mm || align="center" | 35 mm || align="center" | 39 mm
|-class="sortbottom"
|Canon EOS 500D / Digital Rebel X1i || align="center" | 0 mm || align="center" | 38.5 mm || align="center" | 39 mm
|-class="sortbottom"
|Canon EOS 1000D (waiting for Mauro78 measures) || align="center" | x mm || align="center" | x mm || align="center" | x mm
|-class="sortbottom"
|Canon G9 || align="center" | 12 mm || align="center" | 29 mm || align="center" | N/A
|-class="sortbottom"
|Canon PowerShot A630 || align="center" | 15 mm || align="center" | 28 mm || align="center" | 0 mm (fixed lens)
|-class="sortbottom"
|Fujifilm FinePix S7000 || align="center" | 0 mm || align="center" | 32.8 mm || align="center" | 69mm + 37mm(Adapt.Tube)=106mm
|-class="sortbottom"
|Nikon C8800 || align="center" | 19.1 mm || align="center" | 67.9 mm || align="center" | N/A
|-class="sortbottom"
|Nikon D2H (+D2Hs/D2X/D2Xs?) || align="center" | 0 mm || align="center" | 79 mm || align="center" | 29.5 mm
|-class="sortbottom"
|Nikon D40 (+D40x?) || align="center" | 0 mm || align="center" | 36 mm || align="center" | 42 mm
|-class="sortbottom"
|Nikon D60 || align="center" | 0 mm || align="center" | 42 mm || align="center" | 36 mm
|-class="sortbottom"
|Nikon D70 || align="center" | 0 mm || align="center" | 52 mm || align="center" | 36 mm
|-class="sortbottom"
|Nikon D80 || align="center" | 0 mm || align="center" | 42.8 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D90 || align="center" | 0 mm || align="center" | 42.8 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D100 with MB-D100 || align="center" | 0 mm || align="center" | 93 mm || align="center" | 33.5 mm
|-class="sortbottom"
|Nikon D200 || align="center" | 0 mm || align="center" | 47 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D300 || align="center" | 0 mm || align="center" | 47.6 mm || align="center" | 42.4 mm
|-class="sortbottom"
|Nikon D300 + MB-D10 || align="center" | 0 mm || align="center" | 90.2 mm || align="center" | 31.4 mm
|-class="sortbottom"
|Pentax K10D/K20D || align="center" | 0 mm || align="center" | 41.6 mm || align="center" | 37.2 mm
|-class="sortbottom"
|Sony Alpha A100 || align="center" | 0 mm || align="center" | 37 mm || align="center" | 35 mm
|}

 
 
 
 
 
 

== Entrance Pupil Measurements ==

{| border="1" cellpadding="5" cellspacing="0" align="center" class="wikitable sortable"
|+
! style="background:#e0e0e0;" width="25%" | '''Lens'''
! style="background:#e0e0e0;" width="25%" | '''Focal Length'''
! style="background:#e0e0e0;" width="50%" | '''Entrance Pupil Length (L2)'''
|-valign="top"
|<div style="height:150px;"> </div><hr>Enter the exact lens name, or if you are using a camera with a fixed lens the name of your camera as mentioned at [http://www.dpreview.com/reviews/specs.asp dpreview].||<div style="height:150px;"> </div><hr> ||[[Image:EPDB-length2.jpg|Entrance Pupil Length]]<hr>Facing the side of the lens, the distance from the base of the lens to the Entrance Pupil. A negative value means the entrance pupil is before the lens base. (not sure if this makes sense in a theoretical way)
|-class="sortbottom"
| EF-S 10-22mm || align="center" | 10mm || align="center" | 66mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 18mm || align="center" | 47mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 24mm || align="center" | 23mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 35mm || align="center" | 45mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 55mm || align="center" | 55mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 17mm || align="center" | 71mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 28mm || align="center" | 69mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 40mm || align="center" | 72mm
|-class="sortbottom"
| Canon 50mm f/1.8 II || align="center" | 50mm || align="center" | 23mm
|-class="sortbottom"
| Canon 35mm f/2 || align="center" | 35mm || align="center" | 12.5mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 70mm || align="center" | 83mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 85mm || align="center" | 70mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 100mm || align="center" | 45mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 135mm || align="center" | -30mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 200mm || align="center" | -30mm
|-class="sortbottom"
| Nikkor AF-S DX 18-55mm II|| align="center" | 18mm || align="center" | 70mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 18mm || align="center" | 51mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 24mm || align="center" | 44mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 35mm || align="center" | 33.5mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 50mm || align="center" | 24.5mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 70mm || align="center" | -6.5mm
|-class="sortbottom"
| Nikkor AF DX 10.5mm || align="center" | 10.5mm || align="center" | 45.5mm
|-class="sortbottom"
| Nikkor AF DX 10.5mm || align="center" | 10.5mm || align="center" | 46mm
|-class="sortbottom"
| Nikkor AF-S DX 35mm/1.8G || align="center" | 35mm || align="center" | 18mm
|-class="sortbottom"
| Sigma 10mm f/2.8 EX DC HSM Fisheye (60° stops) || align="center" | 10mm || align="center" | 50mm
|-class="sortbottom"
| Sigma 8mm F4.0 EX || align="center" | 8mm || align="center" | 47.5mm / 49mm / 51mm - which one is it?
|-class="sortbottom"
| Sigma 8mm F3.5 EX || align="center" | 8mm || align="center" |
|-class="sortbottom"
| Nikon C8800 at Wide inf. (is this at the widest setting ?) || align="center" | 8.9mm ?? || align="center" | 75mm center of tripod mtg screw to Ent Pupil
|-class="sortbottom"
| Peleng-N 8mm F3.5 || align="center" | 8mm || align="center" | 44mm
|-class="sortbottom"
| Opteka 0.22X UHD II FishEye || align="center" | 0.22X - 8mm || align="center" | 35.75mm
|-class="sortbottom"
| Tamron 90mm F2.8 Di2 Macro || align="center" | 90mm || align="center" | 34mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 10mm || align="center" | 62mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 14mm || align="center" | 64mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 20mm || align="center" | 68mm
|-class="sortbottom"
| Sigma 30mm F1.4 EX DC || align="center" | 30mm || align="center" | 26.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 11mm || align="center" | 58.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 14mm || align="center" | 59.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 18mm || align="center" | 62.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 17mm || align="center" | 56.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 24mm || align="center" | 48mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 35mm || align="center" | 40.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 50mm || align="center" | 31.5mm
|-class="sortbottom"
| Tamron 28-75mm F2.8 XR DI || align="center" | 28-75mm || align="center" | 58.8mm
|-class="sortbottom"
| Carl Zeiss Jena Flektogon 20mm f/4 || align="center" | 20mm || align="center" | 17.5mm
|-class="sortbottom"
| Raynox DCR-CF185PRO || align="center" | Conversion lens || align="center" | 80mm
|-class="sortbottom"
| Canon PowerShot A630 || align="center" | 35mm (wide open) || align="center" | 31mm
|-class="sortbottom"
| Canon G9 || align="center" | 7.4mm (wide) || align="center" | 33.7mm from tripod screw
|-class="sortbottom"
| Canon G9 || align="center" | 44.4mm (tight) || align="center" | -10mm from tripod screw
|-class="sortbottom"
| Zenitar 2,8/16 || align="center" | 16mm || align="center" | 36mm
|-class="sortbottom"
| Pentax smc DA 10-17mm F3.5-4.5 Fisheye zoom || align="center" | 10mm || align="center" | 57.8mm
|-class="sortbottom"
| <Manufacturer / Lens> || align="center" | <Focal Length> || align="center" | <Entrance Pupil Length>
|}

 

*To calculate the Entrance pupil distance add the Tripod Mount Length (L1) from the camera and the Entrance Pupil Length (L2) from the lens. So for example for a Canon 300d and a 10-22mm at 10mm, the total Entrance pupil distance from the tripod mount is 40mm + 66mm = 106mm

*For these '''''Focal Length''''' values the actual focus is set to infinity (<math>\infty</math>)

== Number of pics for 360° ==

{| border="1" cellpadding="5" cellspacing="0" align="left"
|+
! style="background:#e0e0e0;" rowspan="3" | '''Focal Length Lens Type'''
! style="background:#e0e0e0;" colspan="4" | '''crop factor 1.5/1.6 '''
! style="background:#e0e0e0;" colspan="4" | '''Full Frame'''
! style="background:#e0e0e0;" colspan="4" | '''Four Thirds (crop factor 2.0)'''
|-
! style="background:#e0e0e0;" colspan="2" | '''Portrait '''
! style="background:#e0e0e0;" colspan="2" | '''Landscape'''
! style="background:#e0e0e0;" colspan="2" | '''Portrait '''
! style="background:#e0e0e0;" colspan="2" | '''Landscape'''
! style="background:#e0e0e0;" colspan="2" | '''Portrait '''
! style="background:#e0e0e0;" colspan="2" | '''Landscape'''
|-
|style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate ||style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate
|style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate ||style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate
|style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate ||style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate
|-
||8mm fisheye
||4||90°|| ||
||3||120°||3||120°
|| || || ||
|-
||10.5mm fisheye
||6||60°|| ||
||4||90°|| ||
|| || || ||
|-
||16mm fisheye
|| || || ||
||6||60°||4||90°
|| || || ||
|-
||10mm rectilinear
||6||60°||4||90°
|| || || ||
|| || || ||
|-
||14mm rectilinear
||8||45°||6||60°
|| || || ||
|| || || ||
|-
||18mm rectilinear
||10||36°||8||45°
|| || || ||
|| || || ||
|-
||24mm rectilinear
||12||30°||8||45°
||8||45°||6||60°
|| || || ||
|-
||28mm rectilinear
||15||24°||10||36°
||12-8||30°-40°||8-6||40°-60°
|| || || ||
|-
||35mm rectilinear
||18||20°||12||30°
||18-12||20°-30°||12-8||30°-40°
|| || || ||
|-
||50mm rectilinear
||24||15°||18||20°
||18||20°||12||30°
|| || || ||
|-
||70mm rectilinear
||36||10°||24||15°
||24||15°||15||24°
|| || || ||
|}
{{clr}}

== Related Resources ==

* VRwave lens database - http://www.vrwave.com/panoramic/photography/lens_database.html
* Panoramic Resolution by Ken Turkowski - http://www.worldserver.com/turk/quicktimevr/panores.html
* Panoramic Calculator by Frank van der Pol - http://www.frankvanderpol.nl/fov_pan_calc.htm
* Panoramic calculator by Sean T. McHugh (at the very bottom) http://www.cambridgeincolour.com/tutorials/image-projections.htm
* Olympus E-System specific data (german)
** http://olypedia.de/Nodalpunkte_E_System tripod mount and entrance pupil measurements
** http://olypedia.de/Nodalpunkte_E-300_/_E-500 entrance pupil measurements with different lenses
** http://olypedia.de/Nodalpunkte_E-1 entrance pupil measurements for E-1 with different lenses
[[Category:Hardware]]

{{Incomplete|Talk}}

Entrance Pupil Database

2009-12-10T19:39:07Z

Dezen: /* Related Resources */ pano calculator link

Wouldn't it be great if everyone entered their values for their [[No-parallax point| NPP / Nodal Point / Entrance Pupil]] for lens and camera combinations.
Some searching on the web will find a lot of people saying they want to start to create a database of some kind, but have not seen anything substantial so far (correct me if I am wrong).

Please enter your own values if they are not listed.

Thanks,
--[[User:Korffr|Richard Korff]] 11:12, 13 May 2005 (EDT)

To cater for all the different camera bodies and lenses, the tables have been split into 3 parts:

*The '''[[#Tripod Mount Measurements|first table]]''' shows the position of the tripod mount in relation to the lens axis. This is easy to measure and is dependent only on the camera body.
*The '''[[#Entrance Pupil Measurements|second table]]''' shows the actual entrance pupil distance which is only dependent on the lens itself. Note that the [[No-parallax point|NPP]] for [[Special issues with fisheye lenses|fisheye]] lenses is not constant over the image circle's [[Field of View|FoV]], so you will sometimes find different NPP values depending on the angle where your images overlap.
*The '''[[#Number of pics for 360°|third table]]''' shows the number if pics neccessay for a full 360° coverage and the rotation angle between shots.

Use as much as possible actual measurements rather than the reading on your [[panorama head]], unless your are sure these are the same.

To enter a line for your combination, edit the page by clicking edit at the top of the screen (you may need to create an account or sign-in first), and edit the table below.

== Tripod Mount Measurements ==

{| border="1" cellpadding="5" cellspacing="0" align="left" valign="top" class="wikitable sortable"
|+
! Style="background:#e0e0e0;" width="25%" | '''Camera'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount off-center (C)'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount height (H)'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount length (L1)'''
|-style="vertical-align:top;"
|<div style="width: 200px; height:150px"> </div><hr>Use the correct name of your camera. For digital camera's, please use the name as mentioned at [http://www.dpreview.com/reviews/specs.asp dpreview]. || [[Image:EPDB-off-center.jpg|Tripod mount off-center]]<hr>Looking at the bottom of the camera, the distance between the the middle of the tripod mount to the lens axis (0 if the tripod mount is over the centre of the lens) || [[Image:EPDB-height.jpg|Tripod mount height]]<hr>Facing the camera, the distance from the base of the camera to the center of the lens || [[Image:EPDB-length1.jpg|Tripod mount length]]<hr>Looking at the bottom of the camera, the distance between the middle of the tripod mount to the base of the lens base, or base for adaptor tube. For fixed lens camera's which do not allow use of adaptors this column is not applicable.
|-class="sortbottom"
|Canon EOS 5D MKII || align="center" | 0 mm || align="center" | 43.5 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 20D || align="center" | 0 mm || align="center" | 40 mm || align="center" | 36.5 mm
|-class="sortbottom"
|Canon EOS 40D || align="center" | 0 mm || align="center" | 42 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 400D || align="center" | 0 mm || align="center" | 37 mm || align="center" | 39 mm
|-class="sortbottom"
|Canon EOS 400D + BG-E3 (battery grip)|| align="center" | 0 mm || align="center" | 81 mm || align="center" | 33 mm
|-class="sortbottom"
|Canon EOS 300D / Digital Rebel (EOS Digital Rebel) || align="center" | 0 mm || align="center" |40 mm || align="center" | 40 mm
|-class="sortbottom"
|Canon EOS 300D / Digital Rebel (measured by NP) || align="center" | 0 mm || align="center" |40 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 350D / Digital Rebel XT (measured by NP) || align="center" | 0 mm || align="center" | 37.5 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 450D / Digital Rebel XSi || align="center" | 0 mm || align="center" | 35 mm || align="center" | 39 mm
|-class="sortbottom"
|Canon EOS 500D / Digital Rebel X1i || align="center" | 0 mm || align="center" | 38.5 mm || align="center" | 39 mm
|-class="sortbottom"
|Canon EOS 1000D (waiting for Mauro78 measures) || align="center" | x mm || align="center" | x mm || align="center" | x mm
|-class="sortbottom"
|Canon G9 || align="center" | 12 mm || align="center" | 29 mm || align="center" | N/A
|-class="sortbottom"
|Canon PowerShot A630 || align="center" | 15 mm || align="center" | 28 mm || align="center" | 0 mm (fixed lens)
|-class="sortbottom"
|Fujifilm FinePix S7000 || align="center" | 0 mm || align="center" | 32.8 mm || align="center" | 69mm + 37mm(Adapt.Tube)=106mm
|-class="sortbottom"
|Nikon C8800 || align="center" | 19.1 mm || align="center" | 67.9 mm || align="center" | N/A
|-class="sortbottom"
|Nikon D2H (+D2Hs/D2X/D2Xs?) || align="center" | 0 mm || align="center" | 79 mm || align="center" | 29.5 mm
|-class="sortbottom"
|Nikon D40 (+D40x?) || align="center" | 0 mm || align="center" | 36 mm || align="center" | 42 mm
|-class="sortbottom"
|Nikon D60 || align="center" | 0 mm || align="center" | 42 mm || align="center" | 36 mm
|-class="sortbottom"
|Nikon D70 || align="center" | 0 mm || align="center" | 52 mm || align="center" | 36 mm
|-class="sortbottom"
|Nikon D80 || align="center" | 0 mm || align="center" | 42.8 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D90 || align="center" | 0 mm || align="center" | 42.8 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D100 with MB-D100 || align="center" | 0 mm || align="center" | 93 mm || align="center" | 33.5 mm
|-class="sortbottom"
|Nikon D200 || align="center" | 0 mm || align="center" | 47 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D300 || align="center" | 0 mm || align="center" | 47.6 mm || align="center" | 42.4 mm
|-class="sortbottom"
|Nikon D300 + MB-D10 || align="center" | 0 mm || align="center" | 90.2 mm || align="center" | 31.4 mm
|-class="sortbottom"
|Pentax K10D/K20D || align="center" | 0 mm || align="center" | 41.6 mm || align="center" | 37.2 mm
|-class="sortbottom"
|Sony Alpha A100 || align="center" | 0 mm || align="center" | 37 mm || align="center" | 35 mm
|}

 
 
 
 
 
 

== Entrance Pupil Measurements ==

{| border="1" cellpadding="5" cellspacing="0" align="center" class="wikitable sortable"
|+
! style="background:#e0e0e0;" width="25%" | '''Lens'''
! style="background:#e0e0e0;" width="25%" | '''Focal Length'''
! style="background:#e0e0e0;" width="50%" | '''Entrance Pupil Length (L2)'''
|-valign="top"
|<div style="height:150px;"> </div><hr>Enter the exact lens name, or if you are using a camera with a fixed lens the name of your camera as mentioned at [http://www.dpreview.com/reviews/specs.asp dpreview].||<div style="height:150px;"> </div><hr> ||[[Image:EPDB-length2.jpg|Entrance Pupil Length]]<hr>Facing the side of the lens, the distance from the base of the lens to the Entrance Pupil. A negative value means the entrance pupil is before the lens base. (not sure if this makes sense in a theoretical way)
|-class="sortbottom"
| EF-S 10-22mm || align="center" | 10mm || align="center" | 66mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 18mm || align="center" | 47mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 24mm || align="center" | 23mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 35mm || align="center" | 45mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 55mm || align="center" | 55mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 17mm || align="center" | 71mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 28mm || align="center" | 69mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 40mm || align="center" | 72mm
|-class="sortbottom"
| Canon 50mm f/1.8 II || align="center" | 50mm || align="center" | 23mm
|-class="sortbottom"
| Canon 35mm f/2 || align="center" | 35mm || align="center" | 12.5mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 70mm || align="center" | 83mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 85mm || align="center" | 70mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 100mm || align="center" | 45mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 135mm || align="center" | -30mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 200mm || align="center" | -30mm
|-class="sortbottom"
| Nikkor AF-S DX 18-55mm II|| align="center" | 18mm || align="center" | 70mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 18mm || align="center" | 51mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 24mm || align="center" | 44mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 35mm || align="center" | 33.5mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 50mm || align="center" | 24.5mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 70mm || align="center" | -6.5mm
|-class="sortbottom"
| Nikkor AF DX 10.5mm || align="center" | 10.5mm || align="center" | 45.5mm
|-class="sortbottom"
| Nikkor AF DX 10.5mm || align="center" | 10.5mm || align="center" | 46mm
|-class="sortbottom"
| Nikkor AF-S DX 35mm/1.8G || align="center" | 35mm || align="center" | 18mm
|-class="sortbottom"
| Sigma 10mm f/2.8 EX DC HSM Fisheye (60° stops) || align="center" | 10mm || align="center" | 50mm
|-class="sortbottom"
| Sigma 8mm F4.0 EX || align="center" | 8mm || align="center" | 47.5mm / 49mm / 51mm - which one is it?
|-class="sortbottom"
| Sigma 8mm F3.5 EX || align="center" | 8mm || align="center" |
|-class="sortbottom"
| Nikon C8800 at Wide inf. (is this at the widest setting ?) || align="center" | 8.9mm ?? || align="center" | 75mm center of tripod mtg screw to Ent Pupil
|-class="sortbottom"
| Peleng-N 8mm F3.5 || align="center" | 8mm || align="center" | 44mm
|-class="sortbottom"
| Opteka 0.22X UHD II FishEye || align="center" | 0.22X - 8mm || align="center" | 35.75mm
|-class="sortbottom"
| Tamron 90mm F2.8 Di2 Macro || align="center" | 90mm || align="center" | 34mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 10mm || align="center" | 62mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 14mm || align="center" | 64mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 20mm || align="center" | 68mm
|-class="sortbottom"
| Sigma 30mm F1.4 EX DC || align="center" | 30mm || align="center" | 26.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 11mm || align="center" | 58.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 14mm || align="center" | 59.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 18mm || align="center" | 62.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 17mm || align="center" | 56.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 24mm || align="center" | 48mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 35mm || align="center" | 40.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 50mm || align="center" | 31.5mm
|-class="sortbottom"
| Tamron 28-75mm F2.8 XR DI || align="center" | 28-75mm || align="center" | 58.8mm
|-class="sortbottom"
| Carl Zeiss Jena Flektogon 20mm f/4 || align="center" | 20mm || align="center" | 17.5mm
|-class="sortbottom"
| Raynox DCR-CF185PRO || align="center" | Conversion lens || align="center" | 80mm
|-class="sortbottom"
| Canon PowerShot A630 || align="center" | 35mm (wide open) || align="center" | 31mm
|-class="sortbottom"
| Canon G9 || align="center" | 7.4mm (wide) || align="center" | 33.7mm from tripod screw
|-class="sortbottom"
| Canon G9 || align="center" | 44.4mm (tight) || align="center" | -10mm from tripod screw
|-class="sortbottom"
| Zenitar 2,8/16 || align="center" | 16mm || align="center" | 36mm
|-class="sortbottom"
| Pentax smc DA 10-17mm F3.5-4.5 Fisheye zoom || align="center" | 10mm || align="center" | 57.8mm
|-class="sortbottom"
| <Manufacturer / Lens> || align="center" | <Focal Length> || align="center" | <Entrance Pupil Length>
|}

 

*To calculate the Entrance pupil distance add the Tripod Mount Length (L1) from the camera and the Entrance Pupil Length (L2) from the lens. So for example for a Canon 300d and a 10-22mm at 10mm, the total Entrance pupil distance from the tripod mount is 40mm + 66mm = 106mm

*For these '''''Focal Length''''' values the actual focus is set to infinity (<math>\infty</math>)

== Number of pics for 360° ==

{| border="1" cellpadding="5" cellspacing="0" align="left"
|+
! style="background:#e0e0e0;" rowspan="3" | '''Focal Length Lens Type'''
! style="background:#e0e0e0;" colspan="4" | '''crop factor 1.5/1.6 '''
! style="background:#e0e0e0;" colspan="4" | '''Full Frame'''
|-
! style="background:#e0e0e0;" colspan="2" | '''Portrait '''
! style="background:#e0e0e0;" colspan="2" | '''Landscape'''
! style="background:#e0e0e0;" colspan="2" | '''Portrait '''
! style="background:#e0e0e0;" colspan="2" | '''Landscape'''
|-
|style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate ||style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate
|style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate ||style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate
|-
||8mm fisheye
||4||90°|| ||
||3||120°||3||120°
|-
||10.5mm fisheye
||6||60°|| ||
||4||90°|| ||
|-
||16mm fisheye
|| || || ||
||6||60°||4||90°
|-
||10mm rectilinear
||6||60°||4||90°
|| || || ||
|-
||14mm rectilinear
||8||45°||6||60°
|| || || ||
|-
||18mm rectilinear
||10||36°||8||45°
|| || || ||
|-
||24mm rectilinear
||12||30°||8||45°
||8||45°||6||60°
|-
||28mm rectilinear
||15||24°||10||36°
||12-8||30°-40°||8-6||40°-60°
|-
||35mm rectilinear
||18||20°||12||30°
||18-12||20°-30°||12-8||30°-40°
|-
||50mm rectilinear
||24||15°||18||20°
||18||20°||12||30°
|-
||70mm rectilinear
||36||10°||24||15°
||24||15°||15||24°
|}
{{clr}}

== Related Resources ==

* VRwave lens database - http://www.vrwave.com/panoramic/photography/lens_database.html
* Panoramic Resolution by Ken Turkowski - http://www.worldserver.com/turk/quicktimevr/panores.html
* Panoramic Calculator by Frank van der Pol - http://www.frankvanderpol.nl/fov_pan_calc.htm
* Panoramic calculator by Sean T. McHugh (at the very bottom) http://www.cambridgeincolour.com/tutorials/image-projections.htm
* Olympus E-System specific data (german)
** http://olypedia.de/Nodalpunkte_E_System tripod mount and entrance pupil measurements
** http://olypedia.de/Nodalpunkte_E-300_/_E-500 entrance pupil measurements with different lenses
** http://olypedia.de/Nodalpunkte_E-1 entrance pupil measurements for E-1 with different lenses
[[Category:Hardware]]

{{Incomplete|Talk}}

Entrance Pupil Database

2009-12-10T19:36:43Z

Dezen: /* Related Resources */ olympus data links added

Wouldn't it be great if everyone entered their values for their [[No-parallax point| NPP / Nodal Point / Entrance Pupil]] for lens and camera combinations.
Some searching on the web will find a lot of people saying they want to start to create a database of some kind, but have not seen anything substantial so far (correct me if I am wrong).

Please enter your own values if they are not listed.

Thanks,
--[[User:Korffr|Richard Korff]] 11:12, 13 May 2005 (EDT)

To cater for all the different camera bodies and lenses, the tables have been split into 3 parts:

*The '''[[#Tripod Mount Measurements|first table]]''' shows the position of the tripod mount in relation to the lens axis. This is easy to measure and is dependent only on the camera body.
*The '''[[#Entrance Pupil Measurements|second table]]''' shows the actual entrance pupil distance which is only dependent on the lens itself. Note that the [[No-parallax point|NPP]] for [[Special issues with fisheye lenses|fisheye]] lenses is not constant over the image circle's [[Field of View|FoV]], so you will sometimes find different NPP values depending on the angle where your images overlap.
*The '''[[#Number of pics for 360°|third table]]''' shows the number if pics neccessay for a full 360° coverage and the rotation angle between shots.

Use as much as possible actual measurements rather than the reading on your [[panorama head]], unless your are sure these are the same.

To enter a line for your combination, edit the page by clicking edit at the top of the screen (you may need to create an account or sign-in first), and edit the table below.

== Tripod Mount Measurements ==

{| border="1" cellpadding="5" cellspacing="0" align="left" valign="top" class="wikitable sortable"
|+
! Style="background:#e0e0e0;" width="25%" | '''Camera'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount off-center (C)'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount height (H)'''
! style="background:#e0e0e0;" width="25%" | '''Tripod mount length (L1)'''
|-style="vertical-align:top;"
|<div style="width: 200px; height:150px"> </div><hr>Use the correct name of your camera. For digital camera's, please use the name as mentioned at [http://www.dpreview.com/reviews/specs.asp dpreview]. || [[Image:EPDB-off-center.jpg|Tripod mount off-center]]<hr>Looking at the bottom of the camera, the distance between the the middle of the tripod mount to the lens axis (0 if the tripod mount is over the centre of the lens) || [[Image:EPDB-height.jpg|Tripod mount height]]<hr>Facing the camera, the distance from the base of the camera to the center of the lens || [[Image:EPDB-length1.jpg|Tripod mount length]]<hr>Looking at the bottom of the camera, the distance between the middle of the tripod mount to the base of the lens base, or base for adaptor tube. For fixed lens camera's which do not allow use of adaptors this column is not applicable.
|-class="sortbottom"
|Canon EOS 5D MKII || align="center" | 0 mm || align="center" | 43.5 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 20D || align="center" | 0 mm || align="center" | 40 mm || align="center" | 36.5 mm
|-class="sortbottom"
|Canon EOS 40D || align="center" | 0 mm || align="center" | 42 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 400D || align="center" | 0 mm || align="center" | 37 mm || align="center" | 39 mm
|-class="sortbottom"
|Canon EOS 400D + BG-E3 (battery grip)|| align="center" | 0 mm || align="center" | 81 mm || align="center" | 33 mm
|-class="sortbottom"
|Canon EOS 300D / Digital Rebel (EOS Digital Rebel) || align="center" | 0 mm || align="center" |40 mm || align="center" | 40 mm
|-class="sortbottom"
|Canon EOS 300D / Digital Rebel (measured by NP) || align="center" | 0 mm || align="center" |40 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 350D / Digital Rebel XT (measured by NP) || align="center" | 0 mm || align="center" | 37.5 mm || align="center" | 38.5 mm
|-class="sortbottom"
|Canon EOS 450D / Digital Rebel XSi || align="center" | 0 mm || align="center" | 35 mm || align="center" | 39 mm
|-class="sortbottom"
|Canon EOS 500D / Digital Rebel X1i || align="center" | 0 mm || align="center" | 38.5 mm || align="center" | 39 mm
|-class="sortbottom"
|Canon EOS 1000D (waiting for Mauro78 measures) || align="center" | x mm || align="center" | x mm || align="center" | x mm
|-class="sortbottom"
|Canon G9 || align="center" | 12 mm || align="center" | 29 mm || align="center" | N/A
|-class="sortbottom"
|Canon PowerShot A630 || align="center" | 15 mm || align="center" | 28 mm || align="center" | 0 mm (fixed lens)
|-class="sortbottom"
|Fujifilm FinePix S7000 || align="center" | 0 mm || align="center" | 32.8 mm || align="center" | 69mm + 37mm(Adapt.Tube)=106mm
|-class="sortbottom"
|Nikon C8800 || align="center" | 19.1 mm || align="center" | 67.9 mm || align="center" | N/A
|-class="sortbottom"
|Nikon D2H (+D2Hs/D2X/D2Xs?) || align="center" | 0 mm || align="center" | 79 mm || align="center" | 29.5 mm
|-class="sortbottom"
|Nikon D40 (+D40x?) || align="center" | 0 mm || align="center" | 36 mm || align="center" | 42 mm
|-class="sortbottom"
|Nikon D60 || align="center" | 0 mm || align="center" | 42 mm || align="center" | 36 mm
|-class="sortbottom"
|Nikon D70 || align="center" | 0 mm || align="center" | 52 mm || align="center" | 36 mm
|-class="sortbottom"
|Nikon D80 || align="center" | 0 mm || align="center" | 42.8 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D90 || align="center" | 0 mm || align="center" | 42.8 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D100 with MB-D100 || align="center" | 0 mm || align="center" | 93 mm || align="center" | 33.5 mm
|-class="sortbottom"
|Nikon D200 || align="center" | 0 mm || align="center" | 47 mm || align="center" | 40 mm
|-class="sortbottom"
|Nikon D300 || align="center" | 0 mm || align="center" | 47.6 mm || align="center" | 42.4 mm
|-class="sortbottom"
|Nikon D300 + MB-D10 || align="center" | 0 mm || align="center" | 90.2 mm || align="center" | 31.4 mm
|-class="sortbottom"
|Pentax K10D/K20D || align="center" | 0 mm || align="center" | 41.6 mm || align="center" | 37.2 mm
|-class="sortbottom"
|Sony Alpha A100 || align="center" | 0 mm || align="center" | 37 mm || align="center" | 35 mm
|}

 
 
 
 
 
 

== Entrance Pupil Measurements ==

{| border="1" cellpadding="5" cellspacing="0" align="center" class="wikitable sortable"
|+
! style="background:#e0e0e0;" width="25%" | '''Lens'''
! style="background:#e0e0e0;" width="25%" | '''Focal Length'''
! style="background:#e0e0e0;" width="50%" | '''Entrance Pupil Length (L2)'''
|-valign="top"
|<div style="height:150px;"> </div><hr>Enter the exact lens name, or if you are using a camera with a fixed lens the name of your camera as mentioned at [http://www.dpreview.com/reviews/specs.asp dpreview].||<div style="height:150px;"> </div><hr> ||[[Image:EPDB-length2.jpg|Entrance Pupil Length]]<hr>Facing the side of the lens, the distance from the base of the lens to the Entrance Pupil. A negative value means the entrance pupil is before the lens base. (not sure if this makes sense in a theoretical way)
|-class="sortbottom"
| EF-S 10-22mm || align="center" | 10mm || align="center" | 66mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 18mm || align="center" | 47mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 24mm || align="center" | 23mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 35mm || align="center" | 45mm
|-class="sortbottom"
| Canon 18-55mm || align="center" | 55mm || align="center" | 55mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 17mm || align="center" | 71mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 28mm || align="center" | 69mm
|-class="sortbottom"
| Canon 17-40mm || align="center" | 40mm || align="center" | 72mm
|-class="sortbottom"
| Canon 50mm f/1.8 II || align="center" | 50mm || align="center" | 23mm
|-class="sortbottom"
| Canon 35mm f/2 || align="center" | 35mm || align="center" | 12.5mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 70mm || align="center" | 83mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 85mm || align="center" | 70mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 100mm || align="center" | 45mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 135mm || align="center" | -30mm
|-class="sortbottom"
| Sigma70-300 || align="center" | 200mm || align="center" | -30mm
|-class="sortbottom"
| Nikkor AF-S DX 18-55mm II|| align="center" | 18mm || align="center" | 70mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 18mm || align="center" | 51mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 24mm || align="center" | 44mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 35mm || align="center" | 33.5mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 50mm || align="center" | 24.5mm
|-class="sortbottom"
| Nikkor AF-S DX 18-70mm || align="center" | 70mm || align="center" | -6.5mm
|-class="sortbottom"
| Nikkor AF DX 10.5mm || align="center" | 10.5mm || align="center" | 45.5mm
|-class="sortbottom"
| Nikkor AF DX 10.5mm || align="center" | 10.5mm || align="center" | 46mm
|-class="sortbottom"
| Nikkor AF-S DX 35mm/1.8G || align="center" | 35mm || align="center" | 18mm
|-class="sortbottom"
| Sigma 10mm f/2.8 EX DC HSM Fisheye (60° stops) || align="center" | 10mm || align="center" | 50mm
|-class="sortbottom"
| Sigma 8mm F4.0 EX || align="center" | 8mm || align="center" | 47.5mm / 49mm / 51mm - which one is it?
|-class="sortbottom"
| Sigma 8mm F3.5 EX || align="center" | 8mm || align="center" |
|-class="sortbottom"
| Nikon C8800 at Wide inf. (is this at the widest setting ?) || align="center" | 8.9mm ?? || align="center" | 75mm center of tripod mtg screw to Ent Pupil
|-class="sortbottom"
| Peleng-N 8mm F3.5 || align="center" | 8mm || align="center" | 44mm
|-class="sortbottom"
| Opteka 0.22X UHD II FishEye || align="center" | 0.22X - 8mm || align="center" | 35.75mm
|-class="sortbottom"
| Tamron 90mm F2.8 Di2 Macro || align="center" | 90mm || align="center" | 34mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 10mm || align="center" | 62mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 14mm || align="center" | 64mm
|-class="sortbottom"
| Sigma 10-20mm F4-5.6 EX DC || align="center" | 20mm || align="center" | 68mm
|-class="sortbottom"
| Sigma 30mm F1.4 EX DC || align="center" | 30mm || align="center" | 26.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 11mm || align="center" | 58.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 14mm || align="center" | 59.5mm
|-class="sortbottom"
| Tamron 11-18mm F4.5-5.6 || align="center" | 18mm || align="center" | 62.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 17mm || align="center" | 56.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 24mm || align="center" | 48mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 35mm || align="center" | 40.5mm
|-class="sortbottom"
| Tamron 17-50mm F2.8 XR DI II LD ASP || align="center" | 50mm || align="center" | 31.5mm
|-class="sortbottom"
| Tamron 28-75mm F2.8 XR DI || align="center" | 28-75mm || align="center" | 58.8mm
|-class="sortbottom"
| Carl Zeiss Jena Flektogon 20mm f/4 || align="center" | 20mm || align="center" | 17.5mm
|-class="sortbottom"
| Raynox DCR-CF185PRO || align="center" | Conversion lens || align="center" | 80mm
|-class="sortbottom"
| Canon PowerShot A630 || align="center" | 35mm (wide open) || align="center" | 31mm
|-class="sortbottom"
| Canon G9 || align="center" | 7.4mm (wide) || align="center" | 33.7mm from tripod screw
|-class="sortbottom"
| Canon G9 || align="center" | 44.4mm (tight) || align="center" | -10mm from tripod screw
|-class="sortbottom"
| Zenitar 2,8/16 || align="center" | 16mm || align="center" | 36mm
|-class="sortbottom"
| Pentax smc DA 10-17mm F3.5-4.5 Fisheye zoom || align="center" | 10mm || align="center" | 57.8mm
|-class="sortbottom"
| <Manufacturer / Lens> || align="center" | <Focal Length> || align="center" | <Entrance Pupil Length>
|}

 

*To calculate the Entrance pupil distance add the Tripod Mount Length (L1) from the camera and the Entrance Pupil Length (L2) from the lens. So for example for a Canon 300d and a 10-22mm at 10mm, the total Entrance pupil distance from the tripod mount is 40mm + 66mm = 106mm

*For these '''''Focal Length''''' values the actual focus is set to infinity (<math>\infty</math>)

== Number of pics for 360° ==

{| border="1" cellpadding="5" cellspacing="0" align="left"
|+
! style="background:#e0e0e0;" rowspan="3" | '''Focal Length Lens Type'''
! style="background:#e0e0e0;" colspan="4" | '''crop factor 1.5/1.6 '''
! style="background:#e0e0e0;" colspan="4" | '''Full Frame'''
|-
! style="background:#e0e0e0;" colspan="2" | '''Portrait '''
! style="background:#e0e0e0;" colspan="2" | '''Landscape'''
! style="background:#e0e0e0;" colspan="2" | '''Portrait '''
! style="background:#e0e0e0;" colspan="2" | '''Landscape'''
|-
|style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate ||style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate
|style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate ||style="background:#e0e0e0;"| pics/360° ||style="background:#e0e0e0;"| rotate
|-
||8mm fisheye
||4||90°|| ||
||3||120°||3||120°
|-
||10.5mm fisheye
||6||60°|| ||
||4||90°|| ||
|-
||16mm fisheye
|| || || ||
||6||60°||4||90°
|-
||10mm rectilinear
||6||60°||4||90°
|| || || ||
|-
||14mm rectilinear
||8||45°||6||60°
|| || || ||
|-
||18mm rectilinear
||10||36°||8||45°
|| || || ||
|-
||24mm rectilinear
||12||30°||8||45°
||8||45°||6||60°
|-
||28mm rectilinear
||15||24°||10||36°
||12-8||30°-40°||8-6||40°-60°
|-
||35mm rectilinear
||18||20°||12||30°
||18-12||20°-30°||12-8||30°-40°
|-
||50mm rectilinear
||24||15°||18||20°
||18||20°||12||30°
|-
||70mm rectilinear
||36||10°||24||15°
||24||15°||15||24°
|}
{{clr}}

== Related Resources ==

* VRwave lens database - http://www.vrwave.com/panoramic/photography/lens_database.html
* Panoramic Resolution by Ken Turkowski - http://www.worldserver.com/turk/quicktimevr/panores.html
* Panoramic Calculator by Frank van der Pol - http://www.frankvanderpol.nl/fov_pan_calc.htm
* Olympus E-System specific data (german)
** http://olypedia.de/Nodalpunkte_E_System tripod mount and entrance pupil measurements
** http://olypedia.de/Nodalpunkte_E-300_/_E-500 entrance pupil measurements with different lenses
** http://olypedia.de/Nodalpunkte_E-1 entrance pupil measurements for E-1 with different lenses
[[Category:Hardware]]

{{Incomplete|Talk}}

Photography Guidelines

2009-12-10T18:14:11Z

Dezen: some useful keywords linked

For [[Panorama|panoramic images]], first you have to take the photos before you can [[How stitching works|stitch]] them together. Here are a few guidelines when taking the photos.

== Essential Guidelines ==

* '''Rotate camera around non-parallax point'''
The [[no-parallax point]] inside your lense is where you see the aperture when you look into the camera lense. Rotating the camera around this point avoids parallax error. Correcting this error is outside the scope of stitching software (although the software can fudge to make the effects less visible).

* '''Take photos with about 50% overlap'''
This is for the processing software, most importantly to perform the exposure and vignetting correction. For aligning purpose only, some 20-30% overlap would be sufficient. If you use >50% overlap, your photo series is still usable if one photo in between is spoiled (it happens).

* '''Take account of moving objects'''
Photos are taken at different times. Make sure that in the photo overlap there is an area which has not changed, so either you or the software can place the seam there. With moving objects, clouds or walking persons, try to rotate against the flow in order to avoid duplication.

* '''Do NOT use the camera panoramic mode'''
Usually the camera sets the exposure with the first photo, hence you risk to have several photos with blown highlights. These modes typically give you little control over a number of camera features you want to control. For example, you may want to expose "to the right" or set the distance manually.

== Useful Guidelines ==

* '''Use a tripod''', possibly with [[heads | panorama head]], or rest your camera on a firm object.
This is again about the [[no-parallax point]]. But for non-indoor photography carefully taken handheld photos can be perfectly stitchable.

* '''Cover a wider range'''
For a cylindrical panoramic projection (less than 360deg), cover a wider horizontal range than you plan for the panoramic image, as the barrel shape projection shapes tend to limit the vertical field-of-view in the corners.

* '''Set the focus to manual'''
During a photo series you may point your camera in a direction where there are no features for the camera to focus on. Usually the default distance the camera chooses is not what you want.

* '''Use fixed aperture'''
Vignetting correcting varies slightly with aperture, so one vignetting correction setting can be used. And if your lense contains dust spots (it happens), one needs only one dustmap or flatfield for dust removal. If your camera is dust-prone, take a photo of clear sky - this can be processed into a flatfield.

* '''Use optimum aperture'''
Usually one try to reach the maximum [[depth of Field | depth of field]] at the best image quality in the panorama to prevent differently focused areas. This results in using a specific aperture depending on the used lens, but generally starting from f/8, f/11. The better the quality of your lens the smaller the aperture (the larger the [[f-number]]) can be set.

* '''Shoot in RAW Mode'''
Shooting in [[RAW]] Mode allows you to correct the white balance, (to a certain extent) the exposure and some other parameters depending on the used software. Generally speaking the RAW format provides the most flexibility whilst requiring the most disk space.

== no longer necessary ==

Some things that were necessary in the distant past but are no longer:
# avoid rolling the camera (software can accomodate that)
# use special camera panorama mode
## get precise overlap in the camera display
## take sequence at fixed exposure and white balance (still beneficial but can be corrected to a certain amount)

== Next Steps ==

The next step after photography is [[How stitching works|stitching]].

[[Category:Tutorial:Basic need]]

Photography Guidelines

2009-12-10T18:09:00Z

Dezen: /* Useful Guidelines */ 2 useful guidelines added

For [[Panorama|panoramic images]], first you have to take the photos before you can [[How stitching works|stitch]] them together. Here are a few guidelines when taking the photos.

== Essential Guidelines ==

* '''Rotate camera around non-parallax point'''
The non-parallax point inside your lense is where you see the aperture when you look into the camera lense. Rotating the camera around this point avoids parallax error. Correcting this error is outside the scope of stitching software (although the software can fudge to make the effects less visible).

* '''Take photos with about 50% overlap'''
This is for the processing software, most importantly to perform the exposure and vignetting correction. For aligning purpose only, some 20-30% overlap would be sufficient. If you use >50% overlap, your photo series is still usable if one photo in between is spoiled (it happens).

* '''Take account of moving objects'''
Photos are taken at different times. Make sure that in the photo overlap there is an area which has not changed, so either you or the software can place the seam there. With moving objects, clouds or walking persons, try to rotate against the flow in order to avoid duplication.

* '''Do NOT use the camera panoramic mode'''
Usually the camera sets the exposure with the first photo, hence you risk to have several photos with blown highlights. These modes typically give you little control over a number of camera features you want to control. For example, you may want to expose "to the right" or set the distance manually.

== Useful Guidelines ==

* '''Use a tripod''', possibly with panorama head, or rest your camera on a firm object.
This is again about the non-parallax point. But for non-indoor photography carefully taken handheld photos can be perfectly stitchable.

* '''Cover a wider range'''
For a cylindrical panoramic projection (less than 360deg), cover a wider horizontal range than you plan for the panoramic image, as the barrel shape projection shapes tend to limit the vertical field-of-view in the corners.

* '''Set the focus to manual'''
During a photo series you may point your camera in a direction where there are no features for the camera to focus on. Usually the default distance the camera chooses is not what you want.

* '''Use fixed aperture'''
Vignetting correcting varies slightly with aperture, so one vignetting correction setting can be used. And if your lense contains dust spots (it happens), one needs only one dustmap or flatfield for dust removal. If your camera is dust-prone, take a photo of clear sky - this can be processed into a flatfield.

* '''Use optimum aperture'''
Usually one try to reach the maximum [[depth of Field | depth of field]] at the best image quality in the panorama to prevent differently focused areas. This results in using a specific aperture depending on the used lens, but generally starting from f/8, f/11. The better the quality of your lens the smaller the aperture (the larger the [[f-number]]) can be set.

* '''Shoot in RAW Mode'''
Shooting in [[RAW]] Mode allows you to correct the white balance, (to a certain extent) the exposure and some other parameters depending on the used software. Generally speaking the RAW format provides the most flexibility whilst requiring the most disk space.

== no longer necessary ==

Some things that were necessary in the distant past but are no longer:
# avoid rolling the camera (software can accomodate that)
# use special camera panorama mode
## get precise overlap in the camera display
## take sequence at fixed exposure and white balance (still beneficial but can be corrected to a certain amount)

== Next Steps ==

The next step after photography is [[How stitching works|stitching]].

[[Category:Tutorial:Basic need]]

HDR Software overview

2009-12-09T19:51:07Z

Dezen: /* Software overview */ just software versions and some prices corrected

Certainly one of the most interesting upcoming technologies for photographers is High Dynamic Range Imaging (HDRI), allowing work with the full real world levels of illumination. While standard image formats utilizes 8 or 16 bits with applied gamma and color space, the HDR image format extends the bit depth up to 96bit in a linear color space.

On this overview we will focus on the currently available Windows GUI-based software packages that are able to create and process HDR images. I want to thank all authors of the respective software packages for their support during the creation of the overview, especially Geraldine Joffre, Andreas Schömann, Paul Nolan, and Thomas Lock. Aside from the windows based GUI packages Bernhard Vogl has evaluated, command line tools are also available and have been added to the table below.

The following software packages have been tested:

==Software overview==

{| border="1" cellpadding="5"
|- style="background-color: #000000; color: #F5F5F5; font-size: small;"
! Software
! Homepage
! Version
! Platforms
! Price
! Comments
|-
! Artizen
|
[http://www.supportingcomputers.net/ supportingcomputers.net]
| 2.5.17
| Win
| 45 CDN
| -
|-
! EasyHDR Pro
|
[http://www.easyhdr.com easyhdr.com]
| 1.70.3
| Win
| 30 EUR
| -
|-
! FDRTools Basic
|
[http://fdrtools.com/ fdrtools.com]
| 2.3.0
| Win, Mac
| free
| -
|-
! FDRTools Advanced
|
[http://fdrtools.com/ fdrtools.com]
| 2.3.0
| Win, Mac
| 39.00 EUR
| -
|-
! HDRShop
|
[http://gl.ict.usc.edu/HDRShop/ gl.ict.usc.edu/HDRShop]
| 1.0
| Win
| free for non-commercial and educational use (commercial license: HDRShop 2 (399.00 USD))
| no further development, superseded by the commercial version 2.0
|-
! Unified Color HDR PhotoStudio
|
[http://www.unifiedcolor.com/ unifiedcolor.com]
| 2.13.32
| Win
| 149.99 USD
| Advanced HDR merge and edit program. Always works in 32 bit floating point, offers very powerful image adjustment operations (Shadow/Highlight, Color Tone Equalizer, Color Tuning).
|-
! hugin
|
[http://hugin.sf.net/ hugin.sf.net]
|nowrap| 0.7 beta 4
| Linux, Win, Mac
| free, open source
| All in one panorama creation program. See [[hugin]]
|-
! Photogenics HDR
|
[http://www.idruna.com/ idruna.com]
| 7.0
| Win, Linux
| 699.00 USD
| focuses on 3D workflow and film editing
|-
! Photomatix Pro
|
[http://www.hdrsoft.com/ hdrsoft.com]
| 3.2.6
| Win, Mac
| 99.00 USD
| -
|-
! Photoshop
|
[http://www.adobe.com/ adobe.com]
| 11.0 (CS4)
| Win, Mac
| 649.00 USD (US download) 1042.84 EUR (Europe boxed)
| -
|-
! Picturenaut
|
[http://www.hdrlabs.com/picturenaut/ hdrlabs.com/picturenaut/]
| 3
| Win
| free
|
|-
! pfstools
|
[http://www.mpi-sb.mpg.de/resources/pfstools/ mpi-sb.mpg.de]
| 1.8.1
| Unix, Mac, (Win)
| free, open source
| Command line tools and two GUI (pfsview and [http://theplaceofdeadroads.blogspot.com/2006/07/qpfstmo-hdr-tone-mapping-gui-for-linux_04.html qpfstmo]) for creation and processing of hdr images.
|-
! PTGui Pro
|
[http://www.ptgui.com/ ptgui.com]
| 8.3.5
| Win, Mac
| 149 EUR
| All in one panorama creation program. See [[PTGui]]
|-
! Qtpfsgui
|
[http://qtpfsgui.sourceforge.net/ qtpfsgui.sourceforge.net]
| 1.9.3
| Win, Mac, Linux
| free, open-source
| QT based GUI for pfstools, now including an automatic image alignment. See [[Qtpfsgui]]
|}

As you can see,there is a wide variety of fees you have to pay for the different software packages. This is partly justified by the features and the editing functions the various programs offer.

== HDR creation and tonemapping ==

{| border="1" cellpadding="5" style="text-align: center;"
|- style="background-color: #000000; color: #f5f5f5; font-size: small;"
! rowspan="2" | Software
! rowspan="2" | measure camera response curve
! colspan="4" | create HDR from bracketed images
! rowspan="2" | create HDR from camera RAW image (*1)
! colspan="5" | tonemap image to LDR
|- style="background-color: #000000; color: #f5f5f5; font-size: small;"
! single HDR image creation
! batch mode
! LDR image alignment
! ghost removal
! number of different operators
! single image via GUI
! batch mode
! parameters save-/restoreable
! panoramic mapping (correct border and zenith/nadir blending)
|-
! align="left" | Artizen
| <big>○</big> (histogram)
| √
| √
| automatic & freehand & numeric
| ?
| √
| 5+ Builtin Plus 8 more downloadable
| √
| √
| √
| √
|-
! align="left" | EasyHDR
| ?
| √
| √
| manual ?
| ?
| √
| 1
| √
| during creation
| √
| –
|-
! align="left" | FDRTools Basic
| √ & modify-able histogram
| √
| <big>○</big> (via command line)
| √
|
| √
| 2
| √
| <big>○</big> (via command line)
| –
|
|-
! align="left" | FDRTools Advanced
| √ & modify-able histogram
| √
| <big>○</big> (via command line)
| √
| √
| √
| 3 (also supports compression & contrast bracketing)
| √
| <big>○</big> (via command line)
| –
| √
|-
! align="left" | HDRShop
| √
| √
| –
| –
| –
| –
| –
| –
| –
| –
| –
|-
! align="left" | HDR PhotoStudio
| - (merges JPEG/TIFF directly)
| √
| –
| √ (automatic)
| –
| √
| 16
| √
| √ (via recipes)
| √
| –
|-
! align="left" | hugin
| √
| √
| -
| √ (by standard control points)
| -
| -
| -
| -
| -
| -
| -
|-
! align="left" | Photogenics HDR
| –
| √ (relies on EXIF data)
| –
| ?
| ?
| – (tethered shooting with Canon cameras possible)
| 3
| √
| –
| –
| –
|-
! align="left" | Photomatix Pro
| √ (selectable)
| √
| √
| √ (selectable)
| √
| √
| 2 + 2 LDR blending methods
| √
| √
| √
| <big>○</big> (no zenith/nadir possible)
|-
! align="left" | Photoshop
| √ (supposedly automatic)
| √ (relies on EXIF data)
| –
| √ (selectable)
| ?
| –
| 4
| √
| –
| √
| –
|-
! align="left" | Picturenaut
| √ (selectable)
| √
| <big>○</big> (via command line)
| √ (selectable)
| ?
| –
| 2
| √
| command line (HDRI2LDRI - adaptive logarithmic only)
| √/– (can read MKHDRI-curves)
| not necessary, global operator
|-
! align="left" | pfstools
| √ (pfscalibration, pfstmo with qpfstmo GUI)
| √
| <big>○</big> (via command line)
| -
| -
| √
| 7
| √ (qpfstmo)
| √
| -/– (command line)
| –
|-
! align="left" | PTGui Pro
| √
| √
| √ (via Batch Stitcher)
| √ (by standard control points)
| -
| -
| 1
| √
| √ (via Batch Stitcher)
| √
| √
|-
! align="left" | Qtpfsgui
| <big>○</big> pfstools calibration can be used
| √
| √
| √
| √
| √
| 8
| √
| √
| √
| –
|}

<nowiki>*1</nowiki>: Most software relies on DCRaw for RAW conversion. Some cameras with extended DR capabilities are not converted correctly (e.g. Fuji's S3 camera: Although DCRaw could theoretically read all photosensors, it would need one conversion call for every photosite which is not implemented in the tested software packages.)

== HDR image manipulation ==

There are basically 3 types of appications available:
* Converter software: This type of software will assist you in generating and tonemapping HDR images
* Image editors: These are full-flagged image manipulation programs that will also give you the possibility of HDR generation and tonemapping
* Panorama creation programs with the additional possibility of HDR generation and tonemapping

{| border="1" cellpadding="5" style="font-size: small;"
|- style="background-color: #000000; color: #f5f5f5;"
! rowspan="2" | Software
! File formats (*1) EXR/HDR: 96bit TIFF: 32bit
! rowspan="2" | software type
! rowspan="2" | full image editing capabilities
! colspan="2" | manipulation essentials
! rowspan="2" | no. of builtin panoramic transformations
! colspan="3" | filters
! rowspan="2" | plugins possible
|- style="background-color: #000000; color: #f5f5f5;"
! read/write
! resize, crop, rotate
! white balance
! approx number
! HDR capable
! scriptable
|-
! align="left" | Artizen
| EXR, HDR, TIFF, PFM
| image editor, converter and creator
| √
| √
| <big>○</big> (color adjust)
| 4
| >40
| √
| √
| Tone Mapping Operator SDK included
|-
! align="left" | EasyHDR
| HDR, TIFF
| converter
| –
| –
| √
| –
| –
| –
| –
| –
|-
! align="left" | FDRTools Basic
| EXR, HDR, TIFF
| converter
| –
| –
| –
| –
| –
| –
| –
| –
|-
! align="left" | FDRTools Advanced
| EXR, HDR, TIFF
| converter
| –
| –
| –
| –
| –
| –
| –
| –
|-
! align="left" | HDRShop
| HDR, TIFF
| converter
| –
| √
| √
| 6 (+ 3D rotation)
| ~15
| √
| –
| √
|-
! align="left" | HDR PhotoStudio
| BEF, EXR, HDR (read), TIFF
| HDR merge, image editor
| √
| √
| √
| -
| 16
| √
| √
| -
|-
! align="left" | hugin
| EXR, HDR, TIFF
| panorama creation program
| –
| <big>○</big> (panorama related transformations and cropping)
| –
| 12
| -
| -
| -
| n/a
|-
! align="left" | Photogenics HDR
| EXR, HDR, TIFF
| image editor
| √
| √
| <big>○</big> (color adjust)
| 4
| >40
| √
| –
| √ (beta)
|-
! align="left" | Photomatix Pro
| EXR, HDR, TIFF
| converter
| –
| √
| –
| 1
| –
| –
| –
| –
|-
! align="left" | Photoshop
| EXR, HDR, TIFF (always assumes 32bit)
| image editor
| √
| √
| <big>○</big> (white point adjust)
| –
| >40
| ~15
| √
| √
|-
! align="left" | Picturenaut
| HDR, TIFF
| converter
| –
| √ (resize)
| –
| –
| –
| –
| –
| HDRShop plugins
|-
! align="left" | pfstools
| EXR, HDR, JPEG-HDR (read only), PFM, TIFF
| converter
| –
| √
| –
| 4
| ~11
| √
| √
| n/a
|-
! align="left" | PTGui Pro
| EXR, HDR
| panorama creation program
| –
| <big>○</big> (panorama related transformations and cropping)
| –
| 10
| -
| -
| -
| n/a
|-
! align="left" | Qtpfsgui
| JPEG, PNG, PPM, PBM, TIFF, EXR, HDR, PFS
| converter
| –
| √
| –
| 4
| ~11
| √
| -
| n/a
|}

<nowiki>*1</nowiki>: TIFF: 32 bit floating point TIFF. Please note that the TIFF file format is an abstract container for various encoding methods. This may result in incompatibility when exchanging TIFF files between various applications. This is also true to some extent for .hdr files. Though, all applications in this overview use the most recent file format.

== UI functionality and large image processing ==

The best HDR software is not of much use if it lacks of an intuitive user interface. We will now have a look on some key functionality and UI design. We will also have a look if the applications utilize a clever memory management. The test file is a HDR panorama stitched by Hugin with a size of 8000x4000 pixels (32 Mpix), converted to the Radiance (.hdr) format. (This is tested using a standard Windows XP setup w. 1GB of RAM, swapping to HDD allowed)

{| border="1" cellpadding="5" style="text-align: center;"
|- style="background-color: #000000; color: #f5f5f5; font-size: small;"
! rowspan="2" | Software
! colspan="2" | drag & drop operation from operating system possible
! colspan="2" | large image processing
|- style="background-color: #000000; color: #f5f5f5; font-size: small;"
! drop JPEG LDR images → generate HDR image
! drop HDR image
! load 32Mpix HDR file
! tone map 32Mpix image
|-
! align="left" | Artizen
| yes / yes
| yes
| √
| √
|-
! align="left" | EasyHDR
| no / no
| no
| runtime error
| –
|-
! align="left" | FDRTools Basic
| no / no
| no
| √
| <big>○</big> (very slow)
|-
! align="left" | FDRTools Advanced
| no / no
| no
| √
| <big>○</big> (very slow)
|-
! align="left" | HDRShop
| yes / no (will open multiple images for editing)
| yes
| √
| n/a
|-
! align="left" | HDR PhotoStudio
| yes / yes
| yes
| √ (in 64-bit version)
| √ (in 64-bit version)
|-
! align="left" | hugin
| no / no
| yes
| √
| -
|-
! align="left" | Photogenics HDR
| yes / no (will open multiple images for editing)
| yes
| √
| <big>○</big> (very slow)
|-
! align="left" | Photomatix Pro
| yes / yes
| yes
| √
| √ (only in batch mode)
|-
! align="left" | Photoshop
| yes / no (will open multiple images for editing)
| yes
| √
| √
|-
! align="left" | Picturenaut
| yes / no (will open multiple images for editing)
| yes
| √
| √
|-
! align="left" | pfstools
| no / no
| no
| n/a (no GUI)
| √ (depends on algorithm)
|-
! align="left" | PTGui Pro
| no / no
| yes
| √
| √
|-
! align="left" | Qtpfsgui
| yes / yes
| yes
| √
| √ (depends on algorithm)
|}

== See Also ==

* [[HDR and Tonemapping dialogs in detail]]

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

{{Outdated|Talk}}

User:Dezen

2009-12-06T17:16:53Z

Dezen: Created page with 'dezen is my nickname. Panoramic photographing beginner. *[http://www.flickr.com/photos/41657588@N06/ My Flickr Account]'

dezen is my nickname. Panoramic photographing beginner.
*[http://www.flickr.com/photos/41657588@N06/ My Flickr Account]

Talk:HDR and Tonemapping dialogs in detail

2009-12-06T17:07:12Z

Dezen:

==Enhance==
I fear this article needs constant updating. Please anybody using any of the mentioned software, provide the new information! Sorry for the inconvenient table layout - I'm looking for a table wiki editor... --[[User:Erik Krause|Erik Krause]] 22:48, 21 September 2008 (CEST)

Hello, what about splitting the whole page into sections? Editing would become easier perhaps. --[[User:Dezen|Dezen]] 17:07, 6 December 2009 (UTC)

Talk:Photography Guidelines

2009-12-06T17:02:53Z

Dezen:

Hello all, I hope I got the balance right, providing a concise explanation to each bullet point. Obviously any bullet point can become a link to a page that explains that issue in more detail. -- [[User:Klaus|Klaus]] 18:43, 2 May 2008 (CEST)

Hello, what about adding "Shoot in RAW format if possible"? As you are able to set the white balance and the exposure (to a certain level) afterwards. --[[User:Dezen|Dezen]] 17:02, 6 December 2009 (UTC)

Main Page

2009-12-06T16:48:37Z

Dezen: Undo revision 12006 by Dezen (Talk)

__NOTOC__
== Welcome to the PanoTools wiki ==

The [[Wiki History|wiki]] that aims to show you what you can do with the [[panorama tools]] and how to use them the best way.

The panorama tools are mainly used to build [[PanoRama|panoramic images]] from a set of overlapping images.
The usability extends beyond "just" building panoramas by far though. You can, for instance, use them to render an average of multiple images to broaden the [[dynamic range]] of the images or average out noise. You can also build object movies with them, morph between images and much more. See [[panorama tools applications]] for an extensive list.

We hope you'll find this knowledge base interesting and useful. And if you feel something is missing, please feel free to add your knowledge. All pages on this wiki are editable by you. Let the [[FAQ]] page help you on your way. If you are not up to adding something yourself, please add a description of what you think is missing to the [[requested pages]] page. However, you need an account and you need to [[Special:Userlogin|login]] to edit.

Please see [[Contribute|how to contribute]] for details. There is a list of [[articles that need enhancement]]

To find the topic you are looking for quick, the links below may be helpful

==== Site overviews ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| width=20% | [[SiteMap|Site Map]] || The contents of this wiki in a structured view
|-
| width=20% | [[Special:Allpages|All Pages]] || An alphabetic list of all pages on this wiki
|-
| width=20% | [[Special:Categories|Categories]] || A categorized overview of the contents of this wiki
|}

==== Working with the Panorama Tools ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| width=20% | [[Getting started]] || An introduction to the Panorama Tools and links to tutorials.
|-
| width=20% | [[Panorama formats]] || Panoramas come in various shapes and sizes. This page describes the differences between them.
|-
| width=20% | [[Panorama tools applications]] || Applications of the panorama tools that go beyond panorama stitching.
|-
| width=20% | [[Software]] || A comprehensive overview of all software category pages grouped by platform.
|-
| width=20% | [[Hardware]] || Computers, Cameras, Tripods - everything that is hardware related.
|-
| width=20% | [[Tutorials]] || Step by step guides to solutions and tasks.
|-
| width=20% | [[Glossary]] || An explanation of odd words and terms.
|}

==== Our community ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| width=20% | [[PanoToolsNG]] || Some information on our mailing list and possibilities to read.
|-
| width=20% | [[Searching the archives]] || What to do when Google and Yahoo don't find what you need.
|-
| width=20% | [[People]] || Lists of People that use or develop [[Panorama tools]]
|-
| width=20% | [[License]] || All the contents of this wiki are licensed
|-
| width=20% | [[Contribute]] || Help keep PanoTools a valuable immersive imaging resource.
|}

==== Recent activity ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| '''New Tutorials'''
| '''Recent Additions'''
| '''Recent Changes'''
|-
|<DPL>
category=Tutorial:Basic_need|Tutorial:Nice_to_know|Tutorial:Specialised
namespace=|PanoTools
notcategory=Draft
ordermethod=firstedit
order=descending
addeditdate=false
count=5
</DPL>
|<DPL>
namespace=|PanoTools
notcategory=Tutorial
ordermethod=firstedit
order=descending
addeditdate=false
count=5
</DPL>
|<DPL>
namespace=|PanoTools
ordermethod=lastedit
order=descending
addeditdate=false
count=5
</DPL>
|-
|}

==== Wiki Help ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| width=20% | [[Help:FAQ|Frequently Asked Questions]] regarding this wiki
|-
| width=20% | [[Help|Help pages]]
|-
|-
| width=20% | [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide]
|-
|-
| with=20% | [http://meta.wikimedia.org/wiki/Help:Editing#The_wiki_markup The wiki markup]
|}

[[Category:Info]]

Main Page

2009-12-06T16:47:34Z

Dezen: /* Welcome to the PanoTools wiki */ "requested pages" now links to Special:WantedPages

__NOTOC__
== Welcome to the PanoTools wiki ==

The [[Wiki History|wiki]] that aims to show you what you can do with the [[panorama tools]] and how to use them the best way.

The panorama tools are mainly used to build [[PanoRama|panoramic images]] from a set of overlapping images.
The usability extends beyond "just" building panoramas by far though. You can, for instance, use them to render an average of multiple images to broaden the [[dynamic range]] of the images or average out noise. You can also build object movies with them, morph between images and much more. See [[panorama tools applications]] for an extensive list.

We hope you'll find this knowledge base interesting and useful. And if you feel something is missing, please feel free to add your knowledge. All pages on this wiki are editable by you. Let the [[FAQ]] page help you on your way. If you are not up to adding something yourself, please add a description of what you think is missing to the [[Special:WantedPages | requested pages]] page. However, you need an account and you need to [[Special:Userlogin|login]] to edit.

Please see [[Contribute|how to contribute]] for details. There is a list of [[articles that need enhancement]]

To find the topic you are looking for quick, the links below may be helpful

==== Site overviews ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| width=20% | [[SiteMap|Site Map]] || The contents of this wiki in a structured view
|-
| width=20% | [[Special:Allpages|All Pages]] || An alphabetic list of all pages on this wiki
|-
| width=20% | [[Special:Categories|Categories]] || A categorized overview of the contents of this wiki
|}

==== Working with the Panorama Tools ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| width=20% | [[Getting started]] || An introduction to the Panorama Tools and links to tutorials.
|-
| width=20% | [[Panorama formats]] || Panoramas come in various shapes and sizes. This page describes the differences between them.
|-
| width=20% | [[Panorama tools applications]] || Applications of the panorama tools that go beyond panorama stitching.
|-
| width=20% | [[Software]] || A comprehensive overview of all software category pages grouped by platform.
|-
| width=20% | [[Hardware]] || Computers, Cameras, Tripods - everything that is hardware related.
|-
| width=20% | [[Tutorials]] || Step by step guides to solutions and tasks.
|-
| width=20% | [[Glossary]] || An explanation of odd words and terms.
|}

==== Our community ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| width=20% | [[PanoToolsNG]] || Some information on our mailing list and possibilities to read.
|-
| width=20% | [[Searching the archives]] || What to do when Google and Yahoo don't find what you need.
|-
| width=20% | [[People]] || Lists of People that use or develop [[Panorama tools]]
|-
| width=20% | [[License]] || All the contents of this wiki are licensed
|-
| width=20% | [[Contribute]] || Help keep PanoTools a valuable immersive imaging resource.
|}

==== Recent activity ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| '''New Tutorials'''
| '''Recent Additions'''
| '''Recent Changes'''
|-
|<DPL>
category=Tutorial:Basic_need|Tutorial:Nice_to_know|Tutorial:Specialised
namespace=|PanoTools
notcategory=Draft
ordermethod=firstedit
order=descending
addeditdate=false
count=5
</DPL>
|<DPL>
namespace=|PanoTools
notcategory=Tutorial
ordermethod=firstedit
order=descending
addeditdate=false
count=5
</DPL>
|<DPL>
namespace=|PanoTools
ordermethod=lastedit
order=descending
addeditdate=false
count=5
</DPL>
|-
|}

==== Wiki Help ====
{| cellspacing="5" style="border: 1px solid #ff3030; color: #000; background-color: #f7f7f7" width=100%
|-
| width=20% | [[Help:FAQ|Frequently Asked Questions]] regarding this wiki
|-
| width=20% | [[Help|Help pages]]
|-
|-
| width=20% | [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide]
|-
|-
| with=20% | [http://meta.wikimedia.org/wiki/Help:Editing#The_wiki_markup The wiki markup]
|}

[[Category:Info]]

Perspective correction

2009-12-06T16:44:02Z

Dezen: /* Camera panned, tilted and rotated */ non existing link "focal length" changed to "Focal Length"

==Intro==
This tutorial has no direct relevance to panorama creation. However, perspective correction is an issue for panorama creation as well, if you shoot your images tilted up or down. But please note that it is not necessary to correct the images prior to stitching - this is done in one go with alignment and stitching.

Falling lines can be annoying not only in architectural photography. In former times photographers used shift lenses (some times called [http://en.wikipedia.org/wiki/Perspective_correction Perspective Correction] lenses) to correct for that. These lenses usually are pretty expensive, not available in all needed focal lengths and limited to a certain amount of correction.

Panotools are able to simulate a shift lens in terms of geometry (obviously they can't simulate it in terms of [[Depth of Field]]). There are some easy and straightforward techniques to achieve perspective correction depending on the direction the camera was tilted.

==Prerequisites==
This tutorial uses [[PTGui]], but any of the [[GUI front-ends]] would do. The usage of these programs is more or less identical although names differ sometimes a bit and some fields are in different locations. For hugin see tutorials on [http://hugin.sourceforge.net/tutorials/architectural/en.shtml Simulating an architectural projection] and [http://hugin.sourceforge.net/tutorials/perspective/en.shtml Perspective correction]

In all cases you start a new project and add the image you want to correct by pressing the '''Add''' button.

Go to '''Lens parameters''' tab and choose your lens type (presumable '''normal (rectilinear)'''). Enter the approximate '''Field of View''' if not already read from [[EXIF]] data (it's not necessary to have it exact). If you already have lens correction parameters enter them in the '''a''', '''b''' and '''c''' fields else enter 0.0 for each.

In '''Panorama settings''' tab choose '''Rectilinear ('flat')''' as output.

===Warning===

Newer PTGui versions require you to allow optimization for Roll and Pitch when using the internal optimizer together with horizontal or vertical control points. Use the '''Panorama Tools Optimizer''' in this case.

== Camera tilted up or down ==
Using a shift lens this would have been shot with camera level and the lens shifted up or down. The respective parameter to simulate this in panotools is '''Pitch'''.

=== Camera level to the horizon ===
{| border="0" cellpadding="2" cellspacing="0" align="right"
|valign="top"|[[Image:PC_img01.jpg|thumb|100px|right|Falling lines example © Daniela Dürbeck]]
|valign="top"|[[Image:PC_img02.jpg|thumb|100px|right|corrected image in Panorama Editor]]
|}
If the camera was level to the horizon, one pair of [[vertical control points]] is enough to correct for falling lines. Go to '''Control points''' tab and set one point to the top of something vertical in your image in the left pane and one point at the bottom of the same vertical structure in the right pane. This vertical structure must not go through or near the image center. Be sure to choose '''Vertical line''' as control point type.

On '''Optimizer''' tab check '''Interface: Advanced'''. Check '''Pitch''' and '''Use control points of:''' for '''Image 0'''. All other fields are unchecked. Then press '''Run Optimizer''' and confirm the following dialog.

Once you're done proceed as described under [[#Adjust output|Adjust output]].

In the example image I set one point at the middle light at the top of the tower, another approximately in the middle as far down as possible. Click the thumbs to enlarge.
{{clr}}

=== Camera tilted and rotated ===
{| border="0" cellpadding="2" cellspacing="0" align="right"
|valign="top"|[[Image:PC_img03.jpg|thumb|100px|right|Falling lines example 2 © Erik Krause]]
|valign="top"|[[Image:PC_img04.jpg|thumb|100px|right|Image in Control Point Editor]]
|-
|valign="top"|[[Image:PC_img05.jpg|thumb|100px|right|Corrected image in Panorama Editor]]
|}
If the camera was rotated you need at least two vertical lines control point pairs. Go to '''Control points''' tab and set two point pairs on some vertical structures well apart from each other. For each line set a point in one pane at the bottom and in the other pane at the top of the same vertical structure. Be sure to choose '''Vertical line''' as control point type.

If there is no second vertical structure you can use a horizontal one with a [[horizontal control points]] pair instead.

In order to correct for perspective and image rotation you must optimize '''Pitch''' and '''Roll'''.

On '''Optimizer''' tab check '''Interface: Advanced'''. Check '''Pitch''' '''Roll''' and '''Use control points of:''' for '''Image 0'''. All other fields are unchecked. Then press '''Run Optimizer''' and confirm the following dialog.

Once you're done proceed as described under [[#Adjust output|Adjust output]].

In the example image I set one point pair at top and bottom of the leftmost edge of the altar and one point pair at the rightmost edge. Click the thumbs to enlarge.
{{clr}}

== Camera panned sideways ==
{| border="0" cellpadding="2" cellspacing="0" align="right"
|valign="top"|[[Image:PC_img06.jpg|thumb|100px|right|Panned camera example © Tom! Striewisch]]
|valign="top"|[[Image:PC_img07.jpg|thumb|100px|right|corrected image]]
|}
Using a shift lens this would have been shot with camera film or sensor parallel to the subject and the lens shifted right or left. The respective parameter to simulate this in panotools is '''Yaw'''.

It is not often necessary to correct for a panned camera since we are used to horizontal perspective distortion. One use is to shoot a mirror without the camera beeing mirrored.

If the camera was level to the horizon, one pair of [[horizontal control points]] is enough to correct for horizontal perspective distortion. Go to '''Control points''' tab and set one point to the left of something horizontal in your image in the left pane and one point at the rigth of the same horizontal structure in the rigth pane. This horizontal structure must not go through or near the image center. Be sure to choose '''Horizontal line''' as control point type.

On '''Optimizer''' tab check '''Interface: Advanced'''. Check '''Yaw''' and '''Use control points of:''' for '''Image 0'''. All other fields are unchecked. Then press '''Run Optimizer''' and confirm the following dialog.

Once you're done proceed as described under [[#Adjust output|Adjust output]].

In the example image I set one point at the top border of the mirror at the left and right end. Click the thumbs to enlarge.

=== Camera panned and rotated ===
If the camera was rotated during shooting you need at least two horizontal control point pairs or one horizontal and one vertical. Proceed in an analogous manner as for rotated camera if [[#Camera tilted and rotated|tilted upwards]]
{{clr}}

== Camera panned, tilted and rotated ==
{| border="0" cellpadding="2" cellspacing="0" align="right"
|valign="top"|[[Image:PC_img08.jpg|thumb|100px|right|Tight spaces example © Bruno Postle]]
|valign="top"|[[Image:PC_img09.jpg|thumb|100px|right|corrected image]]
|}
Using a shift lens (provided you get one with a short enough [[Focal Length | focal length]]) this would have been shot with camera level and film or sensor parallel to the subject and the lens shifted diagonally. The respective parameters to simulate this in panotools are '''Yaw, Pitch''' and '''Roll'''.

Sometimes you have to shoot in very tight spaces but would like to show the image in a frontal view.

In this case two vertical pairs and two horizontal pairs are needed. Go to '''Control points''' tab and set two point pairs to the left and right of something horizontal in your image. Be sure to choose '''Horizontal line''' as control point type for these two and to set the lines as distant as possible.

Set two point pairs to the top and bottom of some vertical structure in your image. Be sure to choose '''Vertical line''' as control point type for these two. These two lines should be as distant as possible, too. There is no problem if horizontal and vertical lines cross.

On '''Optimizer''' tab check '''Interface: Advanced'''. Check '''Yaw, Pitch, Roll''' and eventually '''Field of View''' and '''Use control points of:''' for '''Image 0'''. In this case it is possibly necessary to optimize Field of View as well, because the optimizer won't find a good solution if it is wrong. All other fields are unchecked. Then press '''Run Optimizer''' and confirm the following dialog.

Once you're done proceed as described under [[#Adjust output|Adjust output]].

In the example image I set the lines at the vertical and horizontal edges between the slabs. Click the thumbs to enlarge. There is an excellent [[hugin]] tutorial available on how to correct this image: [http://hugin.sourceforge.net/tutorials/perspective/en.shtml]
{{clr}}

== Summary ==
Only few control point pairs are needed to correct for perspective distortion.
* Camera level. To correct for
** falling lines (vertical perspective distortion) - set one pair to a vertical structure off center. Optimize for '''Pitch''' only.
** horizontal perspective distortion - set one pair to a horizontal structure off center. Optimize for '''Yaw''' only.
* Camera rotated. To correct for
** falling lines (vertical perspective distortion) - set at least one pair of vertical points to a vertical structure plus either one vertical pair apart from the other vertical one or a horizontal pair on a horizontal structure. Optimize for '''Pitch''' and '''Roll''' only.
** horizontal perspective distortion - set at least one pair of horizontal points to a horizontal structure plus either one horizontal pair apart from the other horizontal one or a vertical pair on a vertical structure. Optimize for '''Yaw''' and '''Roll''' only.
* Camera tilted, panned and rotated - set two pairs to two different vertical structures apart from each other and two pairs to different horizontal structures apart from each other. Optimize for '''Yaw, Pitch, Roll''' and eventually '''Field of View'''.

==Adjust output==
In any case you should get an average control point distance of almost 0.0. And in any case the image will be shifted in some direction, hence the output image will be larger. The width and height of the output image can be adjusted, but it is not possible to crop either side individually in PTGui.

Open '''Panorama Editor''' (Ctrl+E) and press the '''Fit panorama''' (Ctrl+F or menu: Edit -> Fit panorama) button. This will automatically adjust the output area to fit the corrected image.

You should see the image shifted in some direction with the empty space filled with black. You can adjust the width and heigth of the frame using the small sliders at the bottom and right side of the window (actually you adjust the output [[Field of View]]). The additional black space must be cropped in some image editor.

== Save ==
As a last step go to '''Create Panorama''' tab page and press '''Set optimum size'''. Choose either [[TIFF]], [[JPEG|JPG]] (and quality) or [[PNG]] as output and enter an appropriate file name. There should be a checkmark under '''Include Images'''. Then press '''Create Panorama'''.

== Batch process ==
If you want to batch process some equally sized images with the same correction values (only possible if you shot them all from a tripod without moving the camera) you can simply add them to the project on '''Source Images''' tab.

To correct them all for same '''Pitch''' and '''Roll''' (falling lines) you simply check the '''Link''' box on '''Optimizer''' tab for either parameter.

If you want to correct them all for '''Yaw''' too select the '''Yaw''' field on '''Image parameters''' tab and press Ctrl+C twice. Then hold down the shift key and press the down arrow until all '''Yaw''' field are selected. Press Ctrl+V twice to paste the value to all '''Yaw''' fields (same works for '''Pitch''' and '''Roll''' fields, too)

On '''Create Panorama''' tab page select '''Multi image TIFF''' for output. You get the images saved with the base name and a four digit number appended.

--[[User:Erik Krause|Erik Krause]] 18:38, 23 Jul 2005 (EDT)

[[Category:Tutorial:Basic need]]

No-parallax point

2009-12-06T16:42:33Z

Dezen: non existing link "focal length" changed to "Focal Length"

{{Glossary|The special point that you have to rotate your camera around, to avoid parallax errors. Commonly (and falsely) referred to as the [[Nodal Point]].}}
If you rotate your camera around some randomly chosen point, your images may show [[parallax]] and be difficult to stitch.

With most lenses, there is one special point around which you can rotate your camera and get no parallax. This special "'''no-parallax point'''" is the center of the lens's '''entrance pupil''', a virtual aperture within the lens. In the panorama photography community, this special point is often called the "'''nodal point'''", but it is in fact unrelated to the actual nodal points of the lens.[[#References|1]],[[#References|2]] The actual nodal points are other points on the optical path, which are of no significance to most photographers. The no-parallax point is also the "center of perspective", but this term is not commonly used and does not describe why the no-parallax point is important.

The entrance pupil is the image of the limiting aperture or diaphragm, as seen through the front of the lens. The image seen may be magnified by the effect of the lens elements in front of it, and the image is displaced from the actual position of the aperture. It is the center of this image about which the camera must be rotated to avoid parallax. Interestingly, the entrance pupil is important in another way: the [[f-number]] of a lens is actually the ratio of the [[Focal Length |focal length ]] to the diameter of the entrance pupil, not to the diameter of the physical aperture inside the camera.

Everything considered, the best term for the no-parallax point may be (surprise!) the "no-parallax point". "Entrance pupil" is correct although a bit imprecise to a geometry purist; it makes a good term for searching the literature and would be preferred in formal writing. "Nodal point" is commonly-used, but incorrect and leads to confusion. It should be avoided when writing and interpreted with caution in reading the literature.

Regardless of what you call the no-parallax point, it is easily found by trial and error. Just adjust the rotation point so that foreground and background points stay lined up.

Some lenses, notably fisheyes, do not have a single no-parallax point. Instead, they have a range of what we might call "least-parallax points" that depend on the angle away from the lens axis. Such lenses can be recognized easily — just look into the front of the lens and observe that the location of the entrance pupil moves forward or backward as you rotate the lens off-axis. With such lenses, it is good to pick one angle at which you like to stitch, and rotate your camera around a point that gives no parallax at that angle.

To facilitate finding the no-parallax point for other people, please fill the measurements you have found for your Camera / Lens / Focal Length combination in the [[Entrance Pupil Database]]

==See also==
*[[Nodal point adapters]]
*[[Entrance Pupil Database]]

==References==
#Kerr, Douglas A. "[http://doug.kerr.home.att.net/pumpkin/Pivot_Point.pdf The Proper Pivot Point for Panoramic Photography]" ''The Pumpkin'' (2005). Accessed [[2007-01-14]].
#van Walree, Paul "[http://www.vanwalree.com/optics/misconceptions.html#m6 Misconceptions in photographic optics]", Item #6. Accessed [[2007-01-14]].

== Links ==
*Rik Littlefield, [http://www.janrik.net/PanoPostings/NoParallaxPoint/TheoryOfTheNoParallaxPoint.pdf Theory of the "No-Parallax" Point in Panorama Photography]
*Big Ben's Panorama Tutorials, [http://www.path.unimelb.edu.au/~bernardk/tutorials/360/photo/nodal.html Determining the Nodal Point of a Lens].
*Kaidan, [http://www.kaidan.com/nodalpoint.html How to Find Your Camera's Nodal Point].
*Alain Hamblenne, [http://www.outline.be/quicktime/tuto/ The Grid]
*[http://michel.thoby.free.fr/ Michel Thoby], especially [http://michel.thoby.free.fr/SIGMA8mm/Alpha%20test%20300D/Nodal%20point%20of%20SIGMA%208mm.html Nodal point location for the SIGMA 8mm f:4 lens], which describes an interesting approach using a laser pointer.
[[Category:Glossary]]

Lightprobe

2009-12-06T16:04:38Z

Dezen:

Lightprobe image is a spherical panorama made of several blended exposures containing high dynamic range.
The panorama itself is usually made with the well-known methods:

*photographing and stitching
*photographing a mirrored ball once or optionally photographing a mirrored ball more times and stitching

The image is usually saved in Radiance .hdr image format as

*angular map (reflection mapping?)
*vertical cross cube

The main purpose consists in simulating environmental light and reflections in rendering software using the radiosity method. Usually a sphere is created around the main scene, the sphere gets as texture/material the lightprobe image. Besides that the sphere´s material gets a "luminocity" property which allows to simulate light sources depending on the lightprobe´s color information. As the lightprobe contains high dynamic range it allows rather realistic but time consuming renderings.
The method with photographing a mirrored ball (usually delivering quite poor overall image quality as you need a nearly perfect sphere) is nevertheless popular for especially shooting light probes, as light information here is more important than the image or its resolution, the lightprobe usually is not seen in the final rendering.

More Information:
*[http://gl.ict.usc.edu/HDRShop/tutorial/tutorial5.html Creating light probe]
*[http://www.dma.ufg.ac.at/app/link/Grundlagen%3A3D-Grafik/module/9933?step=0#chapter Creating light probe (german)]
*[http://www.debevec.org/probes/ General Information and downloadable light probes by Paul Debevec]
*[http://www.debevec.org/IBL2003/ HDRI and Image-Based Lighting SIGGRAPH 2003 Course]
*[http://www.debevec.org/Research/IBL/ Demonstration of lighting]
*[http://gl.ict.usc.edu/HDRShop/tutorial/tutorial4.html Converting lightporbe with HDRShop]

Lightprobe

2009-12-06T15:46:23Z

Dezen:

Lightprobe image is a spherical panorama made of several blended exposures containing high dynamic range.
The panorama itself is usually made with the well-known methods:

*photographing and stitching
*photographing a mirrored ball once or optionally photographing a mirrored ball more times and stitching

The image is usually saved in Radiance .hdr image format as

*angular map (reflection mapping?)
*vertical cross cube

The main purpose consists in simulating environmental light and reflections in rendering software using the radiosity method. Usually a sphere is created around the main scene, the sphere gets as texture/material the lightprobe image. Besides that the sphere´s material gets a "luminocity" property which allows to simulate light sources depending on the lightprobe´s color information. As the lightprobe contains high dynamic range it allows rather realistic but time consuming renderings.
The method with photographing a mirrored ball (usually delivering quite poor overall image quality as you need a nearly perfect sphere) is nevertheless popular for especially shooting light probes, as light information here is more important than the image or its resoslution, the lightprobe usually is not seen in the final rendering.

More Information:
*[http://gl.ict.usc.edu/HDRShop/tutorial/tutorial5.html Creating light probe]
*[http://www.debevec.org/probes/ General Information and downloadable light probes by Paul Debevec]
*[http://www.debevec.org/Research/IBL/ Demonstration of lighting]
*[http://gl.ict.usc.edu/HDRShop/tutorial/tutorial4.html Converting lightporbe with HDRShop]

Lightprobe

2009-12-06T15:45:50Z

Dezen:

Lightprobe image is a spherical panorama made of several blended exposures containing high dynamic range.
The panorama itself is usually made with the well-known methods:

*photographing and stitching
*photographing a mirrored ball once or optionally photographing a silver ball more times and stitching

The image is usually saved in Radiance .hdr image format as

* angular map (reflection mapping?)
*vertical cross cube

The main purpose consists in simulating environmental light and reflections in rendering software using the radiosity method. Usually a sphere is created around the main scene, the sphere gets as texture/material the lightprobe image. Besides that the sphere´s material gets a "luminocity" property which allows to simulate light sources depending on the lightprobe´s color information. As the lightprobe contains high dynamic range it allows rather realistic but time consuming renderings.
The method with photographing a mirrored ball (usually delivering quite poor overall image quality as you need a nearly perfect sphere) is nevertheless popular for especially shooting light probes, as light information here is more important than the image or its resoslution, the lightprobe usually is not seen in the final rendering.

More Information:
*[http://gl.ict.usc.edu/HDRShop/tutorial/tutorial5.html Creating light probe]
*[http://www.debevec.org/probes/ General Information and downloadable light probes by Paul Debevec]
*[http://www.debevec.org/Research/IBL/ Demonstration of lighting]
*[http://gl.ict.usc.edu/HDRShop/tutorial/tutorial4.html Converting lightporbe with HDRShop]

Lightprobe

2009-12-06T15:44:04Z

Dezen: Created page with 'Lightprobe image is a spherical panorama made of several blended exposures containing high dynamic range. The panoram itself is usually made with the well-known methods: * phot...'

Lightprobe image is a spherical panorama made of several blended exposures containing high dynamic range.
The panoram itself is usually made with the well-known methods:

* photographing and stitching
* photographing a mirrored ball once or optionally photographing a silver ball more times and stitching

The image is usually saved in Radiance .hdr image format as

* angular map (reflection mapping?)
* vertical cross cube

The main purpose consists in simulating environmental light and reflections in rendering software using the radiosity method. Usually a sphere is created around the main scene, the sphere gets as texture/material the lightprobe image. Besides that the sphere´s material gets a "luminocity" property which allows to simulate light sources depending on the lightprobe´s color information. As the lightprobe contains high dynamic range it allows rather realistic but time consuming renderings.
The method with photographing a mirrored ball (usually delivering quite poor overall image quality as you need a nearly perfect sphere) is nevertheless popular for especially shooting light probes, as light information here is more important than the image or its resoslution, the lightprobe usually is not seen in the final rendering.

More Information:
*[http://gl.ict.usc.edu/HDRShop/tutorial/tutorial5.html Creating light probe]
*[http://www.debevec.org/probes/ General Information and downloadable light probes by Paul Debevec]
*[http://www.debevec.org/Research/IBL/ Demonstration of lighting]
*[http://gl.ict.usc.edu/HDRShop/tutorial/tutorial4.html Converting lightporbe with HDRShop]

Panorama scripting in a nutshell

2009-12-05T21:24:21Z

Dezen:

This is a short document describing the various Open Source tools and techniques available for working with panoramas in a non-GUI environment. The examples are based on Linux experience, but most of them should work on OS X or Windows with minor modifications at most.

This document is also useful for understanding what happens 'under the hood' in [[hugin]] itself and recommended reading for anyone looking to work with the hugin sourcecode.

= Why would you do that? =

Creating and manipulating panoramas is something that should obviously be done in a [[GUI front-ends|graphical tool]]. This is true, but perhaps you find that you are spending more time operating a computer than being a photographer. This is an indication that something is wrong - The computer exists to do the boring work and scripting is one way to make this happen.

= PanoTools 'Scripting' =

The file format first used in Helmut Dersch's [[Panorama tools]] is often referred to as a 'script', but a 'PanoTools' script is really a data file describing a 'panorama stitching project'.

Although these original PanoTools are obsolete, the file format is alive and well with several variations used as project files by [[PTGui]], [[PTAssembler]], [[hugin]] and related tools. These files are simple plain-text, sometimes it is useful to modify them directly with a text editor - Further on we will introduce various methods for manipulating them via the 'programming' kind of scripts.

= Simple command-line stitching =

Lets start with a basic but common use case: Photographers with quality [[Nodal point adapters|panoramic tripod heads]] can reproduce identical sets of photos every time, in this situation there is no need to create a new stitching project for every panorama, it is enough to use a single project as a template.

This example takes a pre-existing project called template.pto, created with three photos. It uses [[nona]] for remapping, and [[enblend]] for blending the remapped photos into a finished [[TIFF]] image:

nona -o out -m TIFF_m template.pto DSC_1234.JPG DSC_1235.JPG DSC_1236.JPG
enblend -o finished.tif out0000.tif out0001.tif out0002.tif

The first [[nona]] command creates three remapped [[TIFF]] images called out0000.tif, out0001.tif etc... the list of input images can be substituted with any set of identically sized photos. The second [[enblend]] command uses these TIFF files as input and merges them to a file called finished.tif.

= Creating hugin projects on the command-line =

The entire panorama creation process can be performed on the command-line, and therefore scripted, doing this involves a series of steps similar to the workflow in a GUI tool.

== Generating control points ==

There are a number of tools available for generating [[control points]] from groups of photos, such as [[autopano-sift]], [[autopano-sift-c]], [[panomatic]] and [[match-n-shift]]. Here is an example using autopano-sift-c:

autopano-sift-c --projection 0,50 project.pto DSC_1234.JPG DSC_1235.JPG DSC_1236.JPG

This will create a .pto project with [[control points]] (if any) linking the three photos, note that the [[projections|projection]] format (f0, [[Rectilinear Projection|rectilinear]]) of the input photos and approximate horizontal [[Field of View|angle of view]] (v50, 50 degrees) have to be specified.

== Pruning control points ==

This still isn't a finished panorama, at the very least this involves [[optimization|optimising]] the camera positions and then rendering the output.

You could go ahead and [[optimization|optimise]] this project file straight away, but this can be a bit hit and miss. First it is a good idea to clean up the [[control points]]. There are currently two useful tools for cleaning control points: [[Using Celeste with hugin|celeste]] removes points from areas of sky and [[ptoclean]] removes points with large error distances, first [[celeste_standalone]]:

celeste_standalone -i project.pto -o project.pto

Then [[ptoclean]]:

ptoclean -v --output project.pto project.pto

Note that in both cases we are overwriting the input project.pto file with the cleaned output. If you want you can create intermediate temporary files and keep each step in case you need to backtrack.

(Other control point cleaners are [[ptscluster]] and the new [[cpclean]])

== Optimising positions and geometry ==

Up to now, the project file simply contains an image list and [[control points]], the images are not yet aligned, you can do this by [[optimization|optimising]] geometric parameters with the [[autooptimiser]] tool:

autooptimiser -a -l -s -o project.pto project.pto

Now you could just skip ahead and render the output if photometric [[optimization|optimisation]] isn't required.

([[PToptimizer]] is an alternative geometrical optimiser)

== Optimising photometric parameters ==

Photos have photometric exposure variables which can be [[optimization|optimised]] in much the same way as aligning positions. Doing this can remove brightness, [[white balance]] and [[vignetting]] differences between photos, giving better blending or allowing creation of [[HDR]] images.

[[vig_optimize]] does the equivalent job for photometric parameters as [[autooptimiser]] does for geometric parameters. It doesn't have an equivalent of the autooptimiser -a 'auto' mode, so you need to indicate in the .pto project which parameters are 'variables', use a tool such as [[ptovariable]]:

ptovariable --vignetting --response --exposure project.pto
vig_optimize -o project.pto project.pto

= Stitching hugin projects on the command-line =

== Rendering images ==

The [[hugin]] tool for remapping and distorting the photos into the final panorama frame is [[nona]], it uses the .pto project file as a set of instructions:

nona -m TIFF_m -o project project.pto

This [[nona]] command creates one remapped [[TIFF]] image for each of the input photos, these will be named project0000.tif, project0001.tif, project0002.tif etc...

([[PTblender]] is an alternative renderer to [[nona]])

== Blending ==

[[nona]] can do rudimentary assembly of the remapped images, but a much better tool for this is [[enblend]], feed it the images, it will pick seam lines and blend the overlapping areas:

enblend -o project.tif project0000.tif project0001.tif project0002.tif ...

Finally this produces the stitched panorama: project.tif

= ''Makefile'' stitching system =

This simple stitching process works well on the command-line, but it gets increasingly complicated when dealing with [[bracketing|bracketed]] stacks of photos, these are necessary for exposure blending with [[enfuse]] or [[HDR]] creation with [[hugin_hdrmerge]].

Luckily [[hugin]] understands about stacks and is capable of breaking-up a project into each of the stitching tasks: rendering, assembling stacks and blending. These targets are written to a standard ''Makefile'' formatted file whenever a project is saved or stitched, e.g when you save project.pto using the hugin GUI, project.pto.mk is saved also. Stitching is then performed not by the hugin GUI, but by GNU ''make'' which processes the targets in the ''Makefile'', resulting in the final stitched panorama.

== Creating ''Makefile''s with pto2mk ==

This functionality is also available for use with any .pto project with the command-line [[pto2mk]] tool:

pto2mk -o project.pto.mk -p project project.pto
make -f project.pto.mk

One of the advantages of using ''make'' on the command-line is that re-running this command will only redo necessary work. If none of the input files have changed, then ''make'' will finish immediately; however if one of the input or intermediate files has changed, say by modifying an [[alpha channel]], then only the tasks necessary to integrate that image into the final panorama will be redone.

== ''make'' options ==

''make'' supports multiple targets, by default [[hugin]] creates an 'all', it also creates a 'clean' target that deletes intermediate files. So you can clean up afterwards like so:

make -f project.pto.mk clean

Internal variables can be overriden by environment variables using the '-e' flag, so to stitch using the alternative [[nona-mask]] tool instead of [[nona]], use something like this:

NONA=nona-mask make -e -f project.pto.mk

Alternatively variables can be simply appended to the end of any ''make'' command, this does exactly the same thing:

make -f project.pto.mk NONA=nona-mask

In a shell such as bash, setting the environment will modify internal variables for the rest of the session:

export ENFUSE='enfuse -l 29'

(note that this will override any existing useful [[enfuse]] options)

== Parallel ''make'' ==

''make'' supports parallel processing for machines with multiple cores/processors with the '-j' parameter, so for a 16 core system this command will stitch using 16 parallel processes:

make -j 16 -f project.pto.mk NONA='nona -t 1'

(note that by default [[nona]] uses all available cores, in this case it needs to be limited to one thread so that 16 instances of nona can run at the same time)

== Stitching queues ==

Processing a series of projects one after another is simple enough, this command will stitch all the projects in a folder:

for file in *.pto.mk; do make -f $file; done

For more advanced command-line stitching, a tool like [http://distmake.sourceforge.net/ distmake] will manage a queue of ''Makefile'' stitching jobs, and even load-balance multiple machines over a network.

== ''Makefile'' plugins ==

A ''Makefile'' can be extended with additional targets by creating a second ''Makefile'' that includes the original [[hugin]] .pto.mk ''Makefile''. For instance a plugin ''Makefile'' called 'Makefile.psd.mk' might define a new target called 'ldr_psd' that assembles a multilayer [[PSD]] file for manual blending in a tool such as the [[Gimp]]:

include $(PTO).mk
ldr_psd : $(LDR_LAYERS) $(LDR_BLENDED)
PTtiff2psd -o $(LDR_REMAPPED_PREFIX_SHELL)_layered.psd \
$(LDR_LAYERS_SHELL) $(LDR_BLENDED_SHELL)

You can then use this plugin by calling the ldr_psd target and supplying the name of the relevant .pto project:

make -f Makefile.psd.mk ldr_psd PTO=project.pto

Hugin installs with an example Makefile.equirect.mk plugin with some common add-on tasks such as creating basic [[QTVR]], [[PanoSalado]] and [[SPi-V]] files.

== Useful ''Makefile'' variables ==

Each filesystem PATH in this table has a matching PATH_SHELL version with special characters escaped - This is the version that should be used in the 'command' part of each ''Makefile'' rule.

{|
| $(INPUT_IMAGES) || list of input files
|-
| $(INPUT_IMAGE_1) || first input file
|-
| $(PROJECT_FILE) || .pto project file
|-
| ||
|-
| $(HUGIN_PROJECTION) || output [[projections|projection]] type in panotools numeric format
|-
| $(HUGIN_HFOV) || output horizontal [[Field of View|angle of view]] in degrees
|-
| $(HUGIN_WIDTH) || output width in pixels
|-
| $(HUGIN_HEIGHT) || output height in pixels
|-
| ||
|-
| $(DO_LDR_BLENDED) || set if 'normal' stitching with no exposure blending set
|-
| $(DO_LDR_STACKED_BLENDED) || set if stitching with 'exposure blending' set
|-
| $(DO_HDR_BLENDED) || set if [[HDR]] merging set
|-
| ||
|-
| $(LDR_REMAPPED_PREFIX) || normal blended output prefix
|-
| $(LDR_EXPOSURE_REMAPPED_PREFIX) || exposure blended output prefix
|-
| $(HDR_STACK_REMAPPED_PREFIX) || [[HDR]] merged output prefix
|-
| ||
|-
| $(LDR_BLENDED) || normal blended output file
|-
| $(LDR_STACKED_BLENDED) || exposure blended output file
|-
| $(HDR_BLENDED) || [[HDR]] merged output file
|-
| ||
|-
| $(LDR_LAYERS) || list of normal unblended output files
|-
| $(LDR_STACKS) || list of exposure blended stack files
|-
| $(LDR_EXPOSURE_LAYERS) || list of blended exposure layers
|-
| $(HDR_STACKS) || list of [[HDR]] merged stack files
|}

= Holding it all together with panostart =

The .pto.mk ''Makefile'' helps with the stitching at the end of the process, but doesn't help with the bits at the beginning such as: identifying which photos go in which panorama, generating [[control points]], pruning and [[optimization|optimising]].

[[panostart]] is a prototype tool that does it all. Given a list of photos in a folder, it identifies likely panoramas by comparing [[EXIF]] timestamps and writes a meta-''Makefile'' containing: rules for generating .pto projects with [[match-n-shift]], rules for generating corresponding .pto.mk ''Makefile''s with [[pto2mk]], rules for stitching the projects with ''make'', plus some other rules for creating useful distributable output.

A typical [[panostart]] command for dealing with a folder full of photos taken with a pocket point-and-shoot camera on auto-exposure might look like this:

panostart --output Makefile --projection 0 --fov 50 --nostacks --loquacious *.JPG

Processing this ''Makefile'' is simple:

make

Some of the resulting panoramas will have position, cropping and stitching errors. Fix these by editing the relevant .pto projects in [[hugin]] or another tool, when you type ''make'' again on the command-line, only those projects that have changed will be restitched.

Another advantage of doing things this way is reproducibility: delete all the (enormous) [[TIFF]] output panoramas and all you need to keep permanently are the photos, the meta-''Makefile'' and the associated .pto projects. If you ever need to recreate the TIFF panoramas in the future, just type ''make''. If you know the name of the TIFF file you want, just type 'make project.tif' and only a single panorama will be processed.

= Panotools::Script for manipulating project files =

The name is a historical mistake, [[Panotools_Script|Panotools::Script]] is a perl library for working with [[hugin]] .pto projects, though it could be extended in the future to cover any of the related file formats. Many of the command-line tools described in this document are written with this library.

Here is a trivial script, all it does is open and save a .pto project, it also resets the output ('p' Panorama line) [[Field of View|angle of view]] to 360 degrees (v360), the [[projections|projection]] format to [[equirectangular Projection|equirectangular]] (f2) and the output pixel size to 4096x2048 pixels (w4096 h2048):

#!/usr/bin/perl
use Panotools::Script;
my $pto = new Panotools::Script;
$pto->Read ($ARGV[0]);
$pto->Panorama->Set (v => 360, f => 2, w => 4096, h = 2048);
$pto->Write ($ARGV[0]);

Here's slightly more complex script, this iterates over the input images and increments the [[white balance]] making the panorama slightly 'warmer':

#!/usr/bin/perl
use Panotools::Script;
my $pto = new Panotools::Script;
$pto->Read ($ARGV[0]);
for my $image (@{$pto->Image})
{
my $Er_new = $image->{Er} * 100 / 95; # red value
my $Eb_new = $image->{Eb} * 95 / 100; # blue value
$image->Set (Er => $Er_new, Eb => $Eb_new);
}
$pto->Write ($ARGV[0]);

= Full list of command-line tools =

== Control point generation ==

* [[autopano-sift-c]] - All in one keypoint generator and matcher
* [[match-n-shift]] - All in one wrapper around [[align_image_stack]] and [[autopano-sift-c]]
* [[panomatic]] - All in one alternative to [[autopano-sift-c]]
* [[align_image_stack]] - Generates [[control points]] for stacked photos

* generatekeys - Keypoint generator
* matchpoint - Keypoint generator
* autopano - Keypoint matcher, part of [[autopano-sift-c]] and not to be confused with autopano

== Project file modification ==

* ptoset - Change global parameters and project options
* [[ptovariable]] - Set typical [[optimization|optimisation]] variables
* ptsed - Set any project parameter, convert .pto into PanoTools format
* [[ptosort]] - Sort [[control points]] or images, remove duplicate control points
* ptopath - Remove file paths in project files
* [[transform-pano]] - [[Roll]], [[pitch]] and [[yaw]] rotation of .pto projects
* ptocentre - Rotate projects to put images in panorama centre

* [[ptomerge]] - Join two or more projects
* [[ptosplit]] - Extract subsets of images from a project into a new project

== Control point pruning ==

* ptscluster - Clean 'bad' [[control points]] based on distances and position
* [[celeste_standalone]] - Clean sky [[control points]]
* [[ptoclean]] - Clean 'bad' [[control points]] based on standard deviation error
* [[cpclean]] - An improved version of [[ptoclean]], part of the [[hugin]] project

== Optimisation ==

* [[autooptimiser]] - [[optimization|Optimise]] geometry of .pto projects
* [[PToptimizer]] - [[optimization|Optimize]] geometry of PanoTools format projects
* [[vig_optimize]] - [[optimization|Optimise]] photometric parameters of .pto projects

== Rendering ==

* [[nona]] - Default [[hugin]] rendering engine
* [[nona-mask]] - Wrapper around [[nona]] for using external bitmap masks
* [[PTmender]] - Render PanoTools format projects

* [[PTAInterpolate]] - Create intermediate images from PanoTools projects

== Blending ==

* [[enblend]] - Merge partially overlapping images with multiresolution splines
* [[enfuse]] - Merge overlapping images with exposure fusion
* PTroller - Merge partially overlapping images with no seaming
* PTmasker - Compute stitching masks for input by PTroller
* enblend-mask - Wrapper around [[enblend]] for using external bitmap masks
* enfuse-mask - Wrapper around [[enfuse]] for using external bitmap masks
* [[hugin_hdrmerge]] - Merge [[bracketing|bracketed]] images for [[HDR]] generation
* enblend-svg - Wrapper around [[enblend]] for specifying input images via SVG files

* process-masks - Allow 'positive' masking in external masks for [[enblend]]
* tif2svg - Assemble multiple [[TIFF]] images into SVG files for enblend-svg
* [[PTblender]] - Correct colour and brightness of overlapping images

== Misc ==

* [[panostart]] - All-in-one panorama workflow via ''Makefile''s
* [[pto2mk]] - Create platform specific ''Makefile'' for stitching a project
* [[ptodummy]] - Generate missing input photos to debug .pto projects
* [[calibrate_lens]] - Automatic lens calibration using straight-line detection

== Chromatic aberration ==

* [[fulla]] - Correct lens distortion and [[chromatic aberration]]
* [[tca_correct]] - Calculate [[chromatic aberration]] in a photo

== Querying ==

* ptograph - Draw undirected graphs of projects
* ptoget - Query any project parameter
* ptoinfo - Generate a report on a project file
* PTinfo - Display info about a panotools generated [[TIFF]] file
* [[panoinfo]] - Display information about installed [[libpano13]] library

== TIFF files ==

* PTtiff2psd - Join multiple [[TIFF]] images into a multilayer [[PSD]] file
* PTtiffdump - Compare two TIFF files
* PTcrop - Remove unwanted empty space in [[TIFF]] files and replace with offsets
* PTuncrop - Replace offsets in [[TIFF]] files with empty pixels

== Output formats ==

* [[qtvr2img]] - Extract six cubefaces from a cubic [[QTVR]]
* cubic2erect - Render six cubefaces into a single [[equirectangular Projection|equirectangular]] image
* qtvr2erect - Render a cubic [[QTVR]] into a single [[equirectangular Projection|equirectangular]] image
* jpeg2qtvr - Assemble six [[JPEG]] cubefaces into a cubic [[QTVR]]
* [[erect2qtvr]] - Render a single [[equirectangular Projection|equirectangular]] image into a cubic [[QTVR]]

* erect2cubic - Create a .pto project for extracting cube faces from an [[equirectangular Projection|equirectangular]] image
* erect2planet - Create a .pto project for extracting a 'little planet' from an [[equirectangular Projection|equirectangular]] image
* erect2mercator - Create a .pto project for extracting a mercator view from an [[equirectangular Projection|equirectangular]] image

== Older tools ==

Helmut Dersch's [[PTOptimizer]] and [[PTStitcher]] were the original command-line tools. These are not really recommendable any more as they require an older, buggier version of the [[libpano12]] library, they are closed source so don't work on modern systems such as OS X or 64bit Linux, and are lacking in features compared to modern replacements such as [[autooptimiser]] and [[nona]].

= Useful Image processing tools =

* [[ImageMagick]] - Many utilities for converting, manipulating and resizing images
* GraphicsMagick - A fork of ImageMagick with many improvements
* libtiff - Supplied with useful tools such as tiffcp for joining and recompression, and tifficc for adding ICC colour profiles
* [[exiftool]] - All purpose reading, setting and copying of [[EXIF]] data
* exiv2 - [[EXIF]] manipulation, useful for setting the file modification date from the EXIF date
* jpegtran - Lossless rotation of [[JPEG]] images
* ufraw-batch - Command-line [[RAW]] processing
* [[dcraw]] - Command-line [[RAW]] processing

[[Category:Software:Platform:Windows]]
[[Category:Software:Platform:Linux]]
[[Category:Software:Platform:Mac OS X]]
[[Category:Software:Hugin]]
[[Category:Tutorial:Specialised]]

--[[User:Bruno|Bruno]] 21:23, 2 May 2009 (UTC)