PanoTools.org Wiki - User contributions [en]

Discussion lists

2013-04-08T07:26:43Z

Zarl: /* Mailing lists */ users of

Finding yourself out of the loop? Perhaps you are not subscribed to enough panotools related mailing lists and forums? Confused? you will be.

== Mailing lists ==

* '''proj-imim''', [[Helmut Dersch]]'s original mailing list no longer exists, though the membership was transferred relatively smoothly to the panotools list in early 2003.

* '''[http://groups.yahoo.com/group/PanoToolsNG/ PanoTools NG]''', the main discussion list for users of panorama tools and related GUI tools. (More on [[Mailing list]])

* '''[http://groups.yahoo.com/group/Panotools-List/ panotools-list]''', a meta-list for discussion of management of the main panotools list.

* '''[https://lists.sourceforge.net/lists/listinfo/panotools-devel panotools-devel]''', a list for developers of panotools and the pano12 library in particular.

* '''[http://groups.yahoo.com/group/panotools-meeting/ panotools-meeting]''', a list for planning the annual [http://www.panotools-meeting.com/ panotools meeting].

* '''[https://lists.sourceforge.net/lists/listinfo/panotools-cvs panotools-cvs]''', not a discussion list, a read only archive of every change to the panotools sourcecode.

* '''[http://groups.google.com/group/hugin-ptx hugin-ptx]''', discussion of Linux and Unix related panorama software and [[hugin]] in particular (note August 2006: After four years and 5400 messages, the old ptx list has successfully migrated from email-lists.org to google groups, all are welcome at the new hugin-ptx address).

* '''[https://lists.sourceforge.net/lists/listinfo/freepv-devel freepv-devel]''', a list related to development of the [[freepv]] open source viewer for panorama content.

* '''[http://lists.apple.com/mailman/listinfo/quicktime-vr QuickTime-VR]''', Apple's mailing list for users of QuickTime VR.

* '''[http://www.ivrpa.org/iqtvra/docs/en/ iqtvra]''', the [[IVRPA|International VR Photography Association]] have a mailing list for members only, this is in addition to web boards (see below).

* '''[http://groups.yahoo.com/group/wwp/ wwp]''', the list for the [http://worldwidepanorama.org World Wide Panorama] event held every three months.

* '''[http://groups.yahoo.com/group/PanoramicPhotography-ns/ PanoramicPhotography-ns]''', another Yahoo list, 'Panoramic Photography without the Spam' it says in the description. Almost no activity.

* '''[http://groups.yahoo.com/group/panorama-stitching/ panorama-stitching]''', yet another Yahoo list. Almost no activity.

* '''[http://groups.google.com/group/ptgui PTGui users list]''', PTGui list

== Forum resources and web boards ==

* '''[http://www.tawbaware.com/forum2/index.php ptassembler]''', message boards related to [[PTAssembler]].

* '''[http://www.kekus.com/forum/archive/index.php/ kekus digital]''', various message boards related to [[PTMac]].

* '''[http://ivrpa.org/forum/ ivrpa forums]''', the [[IVRPA|International VR Photography Association]] have some message boards.

* '''[http://www.panoguide.com/forums/ panoguide]''', message boards on the [http://www.panoguide.com/ panoguide] site.

* '''[http://www.360rage.com/panorama-forum/ 360 rage]''', message boards on the [http://www.360rage.com/ 360rage] site.

* '''[http://www.panolab.com/index.php?action=forum panolab]''', panolab forum.

* '''[http://fieldofview.com/spv-dev/forum SPi-V dev]''', forums for users of the [[SPi-V]] panorama viewer.

* '''[http://www.pano2qtvr.com/forum/ Pano2QTVR]''', forums for users of the [[Pano2QTVR]] tool.

* '''[http://www.devalvr.com/forum/viewforum.php?f=2 DevalVR support]''', forum for users of [[DevalVR]].

== other resources ==

* '''[http://www.panoramas.dk/ panoramas.dk]''', panoramas tutorials, software listing
* '''[http://www.johnhpanos.com/tuts.htm johnpanos.com]''', John Houghton's panorama tutorials
* '''[http://www.vrmag.org/ vrmag.org]''', news about virtual reality
* '''[http://www.path.unimelb.edu.au/~bernardk/tutorials/360/ Big Ben's Panorama Tutorials]'''
* '''[http://www.worldserver.com/turk/ Ken Turkowski]''', QuickTime VR Authoring Tricks
* '''[http://www.philohome.com/ Philo's Home Page]''' - Tutorials, Lego, Home of the [[Philopod]]

== non-english resources ==

* '''[http://www.panorama-community.net/index.php Panorama-Community]''', german-speaking panoramic photography forum

* '''[http://fr.groups.yahoo.com/group/photopanorama/ photopanorama]''', French Panorama list

[[Category:Community]]

Mac software

2013-03-21T13:34:22Z

Zarl: /* Viewers */ linked to dedicated "Viewers" article

== Basic Library ==

The original library on Mac Classic is the [[pano12|pano12.lib]] which was placed in the System extensions folder. This library hasn't been updated since version 2.6b1 and does not include the fast transformation or multi processor support. The OS X version supplied by Kekus Digital to run with [[PTMac]] is called PanoTools.bundle and has many updates including fast transform by default, multi-processor support, improved optimizer (including Altivec optimizations), etc.

The current version of [[Panorama Tools]] on [http://panotools.sf.net/ Sourceforge] builds on OS X and is basically the same as the version supplied by Kekus Digital, this provides the main library (the [[pano12|libpano12.dylib]] file), [[PTOptimizer]] and [[panoinfo]].

== Stitching Software ==

There are two [[Panorama Tools]] front-end applications available for OS X, these are [[Hugin]] (Open Source) and [[PTMac]] (shareware).

== Helper ==

[[clens]], [[Autopano|autopano-sift]], [[PTOptimizer]], [[nona]], [[nona_gui]], [[Enblend]] and [[panoglview]] are all available for OS X as part of the [[Hugin]] bundle.

=== Quicktime VR conversion tools ===

There are two tools for converting equirectangular images into cubic Quicktime VR .mov files:

[[CubicConverter]] from ClickHere Design is Mac OSX-native and offers a variety of tools for conversion, editing of cube faces, setting various QuickTimeVR viewing and compression parameters.

[[MakeCubic]] is a Classic application provided free by Apple for basic conversion of equirectangular sources to QuicktimeVR cubic movies. MakeCubic is available on Apple's [http://developer.apple.com/quicktime/quicktimeintro/tools/index.html Quicktime developers tools page].

== Photoshop ==

=== Plug-ins ===

* [[How to install plug-ins in Photoshop]]
* The [[Panorama Tools Plugins]] are part of the original [[Panorama tools]] distribution by [[Helmut Dersch]]. There is a version for Mac OSX available from [http://www.kekus.com/plugin/index.html Kekus.com]

* [[PTLens]] free lens distortion correction.

=== Actions ===

* [[How to install actions in Photoshop]]
* [[Contrast Masking Actions]] lightens shadows and darkens highlights.
* [[Contrast Blending Actions]] combine a bracketed series of images to extend dynamic range.

== Plugins for the Gimp ==

The [[Gimp]] is a sophisticated image editor similar to [[Photoshop]].

There are several [[Gimp#Panoramic_photography_related_gimp_plugins|panoramic photography related gimp plugins]] that can be used to manipulate panoramas.

== Viewers ==
* [[Quicktime]]
* [[CubicNavigator]]
* [[PanoPreviewer]]
See also [[Panorama Viewers]].

== Non-Panoramic use ==

[[PTShift]] [[chromatic aberration]] correction

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

== External Links ==

* [http://www.mac-how.net/ Install and Configure FileZilla on Mac OS]. Interesting and helpful articles about Mac OS.

Hardware

2013-03-18T12:57:18Z

Zarl: Reverted edits by Katesuttonncm (talk) to last revision by Erik Krause

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)

== Automatic shutter releases ==
See [[Extended bracketing control]] on how to extend the limited bracketing capabilities of your camera.

== 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 [[No-parallax-point|optical center]] of the lens is commonly called the nodal point, although it is more correctly referred to as the entrance pupil or no-parallax-point. The no-parallax-point is usually 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 [[NPP adapters|no-parallax-point adapter]] simply shifts the camera back to move the lens's no-parallax-point over the axis of rotation. [[Heads|More complicated brackets]] allow the camera to rotate vertically around the no-parallax-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 no-parallax-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}}

Hugin Optimizer tab

2013-03-05T15:34:13Z

Zarl: now with TOC (__NOTOC__ deleted)

{| style="margin: 1em auto 1em 1em;background:#FFFF99;color:#FF0000;text-align:left;border: solid #FF3300;"
|-valign="top"
! '''2013-01-01:'''
! These are the wiki pages belonging to hugin versions up to and including 2012.0.0
|}

[[hugin]] uses a photo alignment scheme where it adjusts image orientation and lens settings of source photos
until the [[control points]] line-up. This process is called ''optimisation'' and the '''hugin Optimizer tab''' is where it is controlled in detail. You actually ''create'' individual '''control points''' in the [[hugin Control Points tab|Control Points tab]], and ''manage'' them in the [[hugin Photos tab|Photos tab]] and [[hugin Control Points table|Control Points table]].

So to align two or more photos we need to connect them with some control points. A general rule is that optimising more parameters requires more control points.

== Quick Optimizer ==

Use the '''Optimize''' combo box to pick one of several pre-set optimisation schemes, then click the '''Optimize now!''' button to calculate the best available fit. For a spherical panorama, which is where each image is taken from the same position, you should not optimise translation. For a [[linear panorama]], where you take pictures from different locations of the same flat surface, you must optimise translation.

One valid technique is to try each optimisation scheme in turn, starting at the top, and skipping the ones with translation if you are making a spherical panorama, until you are satisfied with the results.

The '''Optimisation result''' tells you how good the alignment is, large control point error distances indicate one of several things:

* Some '''control points''' are in the wrong place, look at the list in the [[hugin Control Points table|Control Points table]] and identify points with large distances and check they are set properly.
* If points are set correctly, there may be [[parallax]] errors caused by camera movement between shots. If so it may be necessary to decide which objects in the scene are important to have aligned and delete unrelated control points in the [[hugin Control Points tab|Control Points tab]].
* Otherwise you may not be optimising enough parameters. For example, the [[EXIF]] data retrieved from a [[JPEG]] file may not give a very accurate starting [[Field of View]], in this case you should optimise '''view (v)'''.

'''Use only control points between images selected in preview window.''' allows you to work on just a few
of the images in the current project rather than all of them. Use the buttons along the top of the
[[Hugin FastPreview window|Fast Preview window]] to enable and disable source photos. When optimising with the
[[Hugin Optimizer tab|Optimizer tab]], all the hidden images will be ignored.

The following pre-set optimisation schemes are provided:

=== Positions (incremental, starting from anchor) ===

This is the simplest setting, and is probably sufficient for a lot of purposes. Only the relative orientation of images are optimised, lens parameters are left untouched, this works best if either of the following is true:

* The lens has minimal [[barrel distortion]] and the photo [[EXIF]] information supplies an accurate [[Field of View]].
or
* [[Lens calibration]] has already been performed, saved to a file and loaded into the current project via the [[Hugin Photos tab|Photos tab]].

Note that to align any pair of photos, there should be at least two pairs of [[control points]] connecting them.

=== Positions (y,p,r) ===

This is exactly the same as the ''incremental'' setting above except that the parameters are optimised at once, this may confuse the optimiser if the images are not already roughly in the right place. Don't use this setting.

=== Positions and View (y,p,r,v) ===

This is the same as optimising '''Positions''' except that the lens [[Field of View]] is optimised too - Use this if you don't trust the Field of View calculated from the photo's [[EXIF]] data.

Note that for this too work you need at least three well-spaced pairs of [[control points]] between any pair of photos. With a 360 degree panorama it is usually beneficial to optimise the '''Field of View''', even if you have already calibrated this beforehand.

=== Positions and Barrel Distortion (y,p,r,b) ===

This is the same as optimising '''Positions''' except that an attempt is made to discover the lens [[barrel distortion]] at the same time. Only the '''b''' parameter of the full [[lens correction model]] is varied by this optimisation scheme, as this is a reasonable approximation of the distortion of a typical lens. You should trust the field of view if you use this.

Again you need at least three well-placed pairs of [[control points]] between any pair of photos.

=== Positions, View and Barrel (y,p,r,v,b) ===

As the name suggests this optimises positions, [[Field of View]] and [[barrel distortion]] all at once.

=== Everything without translation ===

This optimises image orientation and all geometric parameters in the full [[lens correction model]]. It includes more lens distortion parameters. The x shift and y shift (d and e) parameters account for the centre of the projection not being in the centre of the image. This is quite common, and gets very bad if an image is the cropped corner of another image.

You will need many control points, the more the better, and preferably a full spherical panorama (360 by 180 degrees) to get the best correction. You should also use a calibrated [[Heads|panoramic head]]. If the control points are bad (either there are not enough or some are in the wrong place), or your images were not taken around the [[no-parallax point]], this could produce bizarre results.

However, if you do this well, you will accurately perform [[lens calibration]]. You can save and reuse this lens information on the [[Hugin Camera and Lens tab]].

=== Positions and Translations (y,p,r,x,y,z) ===

This will optimise image orientation and the translation you get when moving the camera for a linear panorama. This is great for stitching images of the same flat surface taken from different places, for example when you couldn't fit a painting or the front of a building into one picture. Again it isn't ideal if the lens information such as the field of view is wrong.

=== Positions, Translation and View (y,p,r,x,y,z,v) ===

This is similar to '''Positions and Translations''', except you can use it when you don't trust the [[Field of View]] from the [[EXIF]] data.

=== Positions, Translation and Barrel (y,p,r,x,y,z,b) ===

This is the same as optimising '''Positions''' and '''Translation''' except that an attempt is made to discover the lens [[barrel distortion]] at the same time. Only the '''b''' parameter of the full [[lens correction model]] is varied by this optimisation scheme, as this is a reasonable approximation of the distortion of a typical lens. You should trust the field of view if you use this.

=== Positions, Translation, View and Barrel (y,p,r,x,y,z,b,b) ===

This is useful when you are optimising a linear panorama, don't trust the field of view, and want to correct barrel distortion.

=== The Custom parameters below ===

The pre-set optimisation options are useful for most situations, but often it is necessary to switch to '''Custom parameters'''.

For example, when shooting hand-held panoramas, some of the position variation between shots can be resolved by using different '''d''' and '''e''' '''Image Center Shift''' parameters for each shot. Select '''The Custom parameters below''' and pick the '''d''' and '''e''' parameters for optimisation. Note that by default, lens settings are shared for all photos in the project, go to the [[hugin Camera and Lens tab]] and ''uncheck'' the '''link''' box for any you want to have different values in each photo.

Similarly, the translation parameters could be used to correct a wonky shot. However, they were meant for linear panoramas which expand to infinite distance at 180 degrees field of view, so you must make sure any images with non-zero translation (X, Y, or Z parameters) are in the middle of the panorama (y and p should all be around zero, and the field of view shouldn't be large enough to make them expand more than 180 degrees). This can be used to patch in the floor after you have removed the tripod that was obscuring it. You can take a shot of the floor where the tripod was at an angle (therefore you can avoid casting a shadow on the image in most cases). You can then optimise X,Y,Z on only this image. However, the floor must be flat for this to work, and this shot must be in the middle of the panorama. You can make down the middle by rotating the panorama on either of the previews.

==== Image Orientation ====

The '''Image Orientation''' section shows the photo number and [[roll]], [[pitch]] and [[yaw]] rotation/orientation values for all input photos (in parenthesis), and the X, Y, and Z translation parameters. The ''check'' mark indicates parameters that will be optimised. The translation parameters should all be 0 on a spherical panorama.

==== Lens Parameters ====

The '''Lens Parameters''' section shows the lens number and the [[lens correction model]] parameters (in parenthesis) for each of the distinct lenses in the project. Only parameters that are '''linked''' in the [[hugin Camera and Lens tab]] are shown in parenthesis.

Note that normally all the photos in a project have the same lens, so there is usually only one row here.

==== edit script before optimizing ====

[[hugin]] actually creates a [[PTOptimizer]] script file which it passes to the panorama tools library for optimisation, select '''edit script before optimizing''' and you can tweak this file for each optimisation run.

This is something you would only do in obscure cases such as:

* Linking the positions of input photos. For example photos in a multi-row panorama taken with tripod can all be assumed to have the same [[roll]], similarly photos in each row can be assumed to have the same [[pitch]] - This will help when there are few details available for setting [[control points]].
* Optimising the '''g''' or '''t''' shear parameters of the [[lens correction model]] for scanned images is only possible by editing the script file.

[[Category:Software:Hugin]]

Getting started

2013-03-04T18:24:52Z

Zarl: /* A basic understanding of the techniques */ terribly important link was missing

== What do I need to get started ==
=== A decent computer with any of the following Operating Systems: BSD, Linux, Windows or a Macintosh. ===
Stitching panoramas is quite CPU intensive, so having a decent computer with enough memory is sure to be in your favor.
See the [[Hardware]] page for more info.

=== A camera ===
A simple camera is enough to get started. If it's not a digital one, you can scan your images or you can have your photo store digitize them and put them on compact disc.
If you want better quality, more comfort or more degrees of view you can step up to a camera with a wide angle lens or even a system that shoots a full 360 degrees panorama in one go. Visit the [[Hardware]] page for more information..

=== Software ===
There are many different software solutions to assemble panoramas these days, but we focus on the [[Panorama tools|panorama tools]].
They are free to use (under the GPL license), very flexible and will give you the most professional results.
See the [[software]] page for more info.

=== A scenery and some light ===
You'll probably manage to find such a spot on your own.
=== A basic understanding of the techniques ===
And that is not as hard as you may think (others also make [[Common idiot errors|mistakes]], so don't give up too quickly). To learn some basic steps, go to the [[tutorials]] section and look for the tutorials marked with one rating star: [[Image:RatingStar_001.jpg]]

== Where do I get help ==
=== Here ===
First, search the Wiki. To look for terms you don't understand, go to the [[glossary]]. If you don't find the term but feel it should be there, log in and add it to the glossary (don't create a page) Someone who knows something about will create a page.

Use the search facility in the left column. If you press the 'Go' button, you get directly to a page where the title contains the search term. If you press 'Search' or if Go didn't succeed you get a list with pages where the search term is either in the title or in the body.

Web browsers like [http://mozilla.com/en-US/ Firefox] or [http://caminobrowser.org/ Camino] allow you to add this wiki to their list of search engines. Just click on the icon in the search bar and look at the bottom of the drop down list for something like "Add panotools.org Wiki (en)".

=== The Web ===
Use your favorite search engine to search for more info. There are lots of tutorials on the web that are not yet listed here. Feel free to add a link to the appropriate wiki page if you found a good resource not already listed (search the wiki first).

=== The mailing list ===
You're welcome to join the [[mailing list]] and ask your question there if you don't find a satisfactory answer here or on the web.

[[Category:Tutorial:Basic need]]

Zenith and Nadir editing overview

2013-02-20T14:31:22Z

Zarl: Reverted edits by ShannonHart (talk) to last revision by Zarl

{{RatingStarSystem}}
== Intro ==
One of the most problematic points when shooting spherical panoramas is the view straight down also called the [[Nadir]] view. Either the tripod is visible or there may be alignment or color mismatches if shooting handheld.

Unfortunately neither the nadir nor the zenith (straight above) area can be edited directly in the [[equirectangular]] image since it is very distorted. For this task we need to either extract a partial view pointing straight up or down or we can cover the relevant section by something else - a mirror ball or a logo f.e.

You find several pages that describe how to do that. This one is intended to give an overview of the different techniques.

== Patching Nadir ==
There are several reasons why you want to patch [[Nadir]] and retouch it such, that nothing of the photographer and his equipment is seen any more. One is that it is somehow annoying if you view a full screen spherical pano and feel very immersed and something not belonging to the scene like a logo pops into sight.

The easiest way to achieve this is to simply shoot nadir. Step aside and shoot roughly from the same position straight down. This gets complicated if the floor is not even or if there are details in different heights because you get [[parallax]] errors. You will need to use a special stitching workflow to get this right. See [[Stitching Nadir Shots]] for details.

If you need to patch [[Nadir]] after shooting you need to either move it to a location where it can be edited or extract a view for editing.

=== Moving Nadir ===
This technique remaps the whole panorama such that [[Nadir]] is on the equator and hence almost undistorted. [[Zenith]] can be edited in the same image. The disadvantage is that if you have regular patterns on the floor that you could use for filling the hole they are distorted the further away from the hole they are. Hence this technique seems to be good for small nadir holes or floor with irregular patterns like sand, grass or leaves only:

* [[Edit zenith and nadir in one go with PTGui]] [[Image:RatingStar_002.jpg]]
* [[Edit zenith and nadir in one go with Adjust filter]] [[Image:RatingStar_002.jpg]]
* [[How to use enblend for patching zenith and nadir images]] [[Image:RatingStar_002.jpg]]

=== Extracting and Inserting Nadir ===
Not as convenient as moving nadir is to extract a rectilinear view, patch it and insert it back into the panorama. This way straight patterns like rectangular stones or wooden planks stay straight and equal spaced, hence it is very easy to patch the floor.

There is a comprehensive overview in [[Extracting and inserting rectilinear Views]] [[Image:RatingStar_001.jpg]] and a special tutorial on [[How to use PTEditor]] [[Image:RatingStar_001.jpg]] for that task.

=== Patching techniques ===
In both cases you need a technique to patch Nadir. One of the most powerful requires an image editor capable of using layers. Here a workflow for [[Photoshop]]:
* Open image to patch
* Keep the layers palette open
* Create layer from background by double clicking it in the layers palette.
* In the layers palette duplicate layer by dragging the layer thumbnail to the 'Create new layer' icon in the footer line.
* Add a mask to the top layer by clicking the 'Add vector mask' icon in the footer line
* Make bottom layer invisible by clicking on it's eye symbol
* Make the mask the painting destination by clicking it in the layers palette.
* Choose a soft brush and black as painting color.
* Paint the mask black where you want to retouch the image - this should result in a hole in the image
* Switch the bottom layers visibility on again.
* Click the bottom layers thumbnail to make it painting destination
* Choose the Move Tool and move the layer by dragging in the image to place some other parts of the floor in the hole in the upper layer
* Edit seams of the mask to your need.
* Once you're done flatten and save.

There are numerous other techniques to patch an image, including using the patch tool (which requires the area to be patched having similar color and brightness as the surroundings) or the clone stamp. A very nice one that is capable of blending the patched area with equalization of color is described in [[Using enblend to fill the "Hole in the floor"]] [[Image:RatingStar_002.jpg]]

== Replacing Nadir ==
The easiest way to cover a tripod head or a hole is to place something else over it. This can be a logo or f.e. a mirror ball. The latter is nice, because it doesn't affect the 'immersive feeling' that much - it could well be part of the scene:

* [[Adding a nadir cap (mirror ball)]] [[Image:RatingStar_002.jpg]]
* [[Adding a nadir logo with text]] [[Image:RatingStar_003.jpg]]

==See also==
* [http://www.photoslareunion.com/OmbreTrepied/TripodShadow.html Erasing the tripod shadow in a panoramic photography with bracketing exposure sets] - Tutorial by Romuald Vareuse

[[Category:Tutorial:Basic need]]

Enfuse

2012-12-18T12:42:13Z

Zarl: Reverted edits by Ipodsoft (talk) to last revision by Erik Krause

[[Image:2125768589_b.jpg|thumb|[[:Image:2125768589_b.jpg|Four exposure panorama blended with enfuse]]]]
[[Image:Lamp_enfuse.jpg|thumb|[[:Image:Lamp_enfuse.jpg|17 EV image blended with enfuse - (c) Jacek Zagaja]]]]
Enfuse is {{glossary|a command-line program used to merge different exposures of the same scene to produce an image that looks very much like a [[Tone_mapping|tonemapped]] image (without the [[Halo|halos]]) but requires no creation of an [[HDR]] image|1}}. Therefore it is much simpler to use and allows the creation of very large multiple exposure panoramas.

Enfuse is based on a paper by Tom Mertens, Jan Kautz and Frank Van Reeth: [http://research.edm.uhasselt.be/~tmertens/papers/exposure_fusion_reduced.pdf "Exposure fusion"] The implementation was done by Andrew Mihal (developer of [[Enblend]]) and the [[hugin]] team around [[User:Pablo|Pablo d'Angelo]]

An extended documentation could be found on [[Enfuse reference manual]]

Other programs using Exposure Fusion: [http://www.tawbaware.com/tufuse.htm tufuse] and [[PTGui]] Pro

== State of development ==
On 8 September 2008 the first official version of enfuse has been released together with enblend.
Enfuse/enblend can be downloaded from [http://enblend.sourceforge.net/ enblend.sourceforge.net]. On that site you will find the 3.2 version source code as well as precompiled windows binaries.

Beta (development) releases can be downloaded from
*[http://panorama.dyndns.org/index.php?lang=en&subject=Hugin&texttag=Hugin panorama.dyndns.org] (scroll down on that page) for MacOSX
*and also from [http://hugin.panotools.org/testing/hugin/ hugin.panotools.org]

=== Known bugs ===
(This section needs to be updated) 
This is a list of known bugs in the current version as linked above. For a list of bugs in previous versions please refer to an [http://wiki.panotools.org/Enfuse?oldid=10011 older version of this page]

* If contrasty structures are near [[zenith]] or [[nadir]] in an [[equirectangular]] image, there might be an artifact (vortex) in the resulting pano.
: Workaround: use on zenith and nadir images separately and stitch them in the resulting pano afterwards.
:: - unknown, whether could be fixed easily

== Description ==
Enfuse merges overlapping images using the Mertens-Kautz-Van Reeth exposure fusion algorithm. This is a quick way to blend differently exposed images into a nice output image, without producing intermediate [[HDR]] images that are then tonemapped to a viewable image. This simplified process often works much better than the currently known tonemapping algorithms.

Enfuse can also be used to build extended [[Depth_of_Field|DOF]] images, by blending a focus stack.

=== Basics ===
The basic idea is that pixels in the input images are weighted according to qualities such as proper exposure, good contrast, and high saturation. These weights determine how much a given pixel will contribute to the final image.

This idea is not quite new. F.e. Ardeshir Goshtasby proposed a [http://www.humanfactors.wright.edu/~agoshtas/IMAVIS4.27.Paper.pdf technique to select and blend only well exposed blocks] and Erik Krause provided a [http://www.erik-krause.de/blending photoshop action] to smart mask badly exposed areas. Many such "DRI" or "Exposure Blending" solutions exist.

The problem of all this techniques was to find good transitions between the areas taken from differently exposed images. There always was a risk of getting banding or even reversed gradients within areas where the brightness gradually changed.

Enfuse solves this problem by using the multi resolution spline blending technique well known from [[enblend]] and [[smartblend]] - and it is actually this step which is responsible for the wonderful results. The technique is described detailed [http://enblend.sourceforge.net/details.htm for enblend] and it works almost the same for enfuse, with the exception that instead of the initial seam line a mask is created according to the given criteria.

Enfuse uses three different criteria to judge the quality of a pixel: Exposure, saturation, and contrast.
* The exposure criteria favors pixels with luminance close to the middle of the range. These pixels are considered better-exposed than those with high or low luminance levels.
* The saturation criteria favors highly-saturated pixels.
* The contrast criteria favors high-contrast pixels. The local gray or color value standard deviation is used as a contrast measure. The Mertens-Kautz-Van Reeth paper suggest using a laplacian filter, but the standard deviation produces much better results for differently focused images.

=== Adjustments ===
You can adjust how much importance is given to each criteria by setting the weight parameters on the command line. For example, if you set --wExposure=1.0 and --wSaturation=0.5, Enfuse will favor well-exposed pixels over highly-saturated pixels when blending the source images. The impact of these parameters on the final result will not always be clear. The quality of the result is subject to your artistic interpretation. Playing with the weights may or may not give you a more pleasing result. I encourage you to experiment (perhaps using downsized images for speed).

Enfuse allows each input image to have an alpha channel. By setting the alpha values of pixels to zero, users can manually remove those pixels from consideration when blending. If an input image lacks an alpha channel, Enfuse will print a warning and continue assuming all pixels should be processed for final output. Any alpha value other than zero is interpreted as "this pixel should should be considered for the final image".

== Usage ==
The usage below refers to the CVS version of the 21 Dec 2007. Use enfuse as follows:
enfuse <options> <input files>.
Input files can be a list of files or a wildcard (on windows f.e. <code>IMG*.jpg</code> for all jpg images that begin with IMG.

=== Common options ===
-h
Print information on the available options.
-l num
Use exactly this many levels for pyramid blending. A low number trades off quality of results for faster execution time and lower memory usage. The default is to use as many levels as possible given the source image size. However, recent versions don't seem to do that hence it might be useful to specify an arbitrary high number (f.e. -l 20) for best results. If you specify a high number Enfuse may still use a smaller number of levels if the geometry of the images demands it.
-o output-file
Required. Specify the name of the output file.
-v
Verbose output.
-w
Blend around the -180/+180 boundary. Useful for full-360 panoramas. Enfuse currently does not blend the zenith or the nadir, so you may still see some seams in these areas.
--compression=COMP
Write a compressed output file. Valid values are [[w:NONE|NONE]], [[w:PACKBITS|PACKBITS]], [[w:LZW|LZW]] and [[w:DEFLATE|DEFLATE]] for TIFF files, and numbers from 0-100 for JPEG files.

=== Extended options ===

-b kilobytes
Set the block size for Enfuse's image cache. This is the amount of data that Enfuse will move to and from the disk in one go. The default is 2 MiB which should be good for most systems.
-c
Use the CIECAM02 color appearance model for blending colors. Your input TIFF files should have embedded ICC profiles. If no ICC profile is present, Enfuse will assume that image uses the sRGB color space. The difference between using this option and Enfuse's default color blending algorithm is very slight, and will be most noticeable when you need to blend areas of different primary colors together.
-g
Gimp (ver. < 2) and Cinepaint exhibit unusual behaviors when loading images with unassociated alpha channels. Use the -g flag to work around this. With this flag Enfuse will create the output image with the associated alpha tag set, even though the image is really unassociated alpha.
-f WIDTHxHEIGHT+x0+y0
Set the size and position of the output image manually. This is useful when the input images are cropped TIFF files, such as those produced by Nona.
-m megabytes
Set the size of Enfuse's image cache. This is the amount of RAM (in megabytes) Enfuse will use for storing image data before swapping to disk. The default is 1024 MB.

=== Fusion options ===
<code>W</code> is a number between 0 (no weight) and 1 (full weight)
--wExposure=W
Sets the relative weight of the well-exposedness criterion. Increasing this weight relative to the others will make well-exposed pixels contribute more to the final output.
--wSaturation=W
Sets the relative weight of high-saturation pixels. Increasing this weight makes pixels with high saturation contribute more to the final output.
--wContrast=W
Sets the relative weight of high-contrast pixels. Increasing this weight makes pixels with neighboring differently colored pixels contribute more to the final output. Particularly useful for focus stacks.
--wMu=mu
Mean of the gaussian weighting function (from 0 to 1) for the exposure criterion only. default value: 0.5. This moves the peak of the curve towards the brighter or darker end of the [[histogram]]. Higher values pick more brighter pixels from the source images, lower values more darker ones.
--wSigma=sigma
Standard deviation of the gaussian weighting function (from 0) for the exposure criterion only. default value: 0.2. Higher values cause a wider curve and more pixels to be taken from a particular image (possibly including under- and over-exposed ones). A lower value causes a narrower curve and less pixels to be taken, possibly resulting in banding.
--HardMask
Force hard blend masks on the finest scale. This avoids averaging of fine details (only), at the expense of increasing the noise. This improves the sharpness of focus stacks considerably.

=== Expert options ===

--ContrastWindowSize=s
Window size for local contrast analysis. Values larger than 5 might result in increased computation times. Values in the range of 3 to 7 have given good results on focus stacks. The impact on the result quality is not easy to define. You will have to experiment.

--GrayProjector=OPERATOR
Apply grayscale projection OPERATOR, where OPERATOR is one of "average", "l-star", "lightness", "value", "luminance", or "channel-mixer:RED-WEIGHT:GREEN-WEIGHT:BLUE-WEIGHT". Default: "average"

--EdgeScale=EDGESCALE[:LCESCALE[:LCEFACTOR]]
Scale on which to look for edges. Positive LCESCALE switches on local contrast enhancement by LCEFACTOR (EDGESCALE, LCESCALE, LCEFACTOR >= 0). 
Append "%" to LCESCALE for values relative to EDGESCALE; 
append "%" to LCEFACTOR for relative value. Defaults: 0:0:0

--MinCurvature=CURVATURE
Minimum CURVATURE for an edge to qualify. Append "%" for relative values. Default: 0.

--debug
Output intermediate images for debugging.

== External Links ==
=== Command line ===
Another implementation of the enfuse algorithm is TuFuse from Max Lyons, which features automatic [[Depth_of_Field|DOF]] fusion (from a focus stack) and exposure fusion in one go as well as some additional options: http://www.tawbaware.com/tufuse.htm (freeware, windows only)

=== GUIs ===
enfuse has triggered the development of some GUIs.

==== Multi platform ====

* The recent release of [[hugin]] has integrate enfuse fully. Get it from http://hugin.sourceforge.net (open source).

* [[PTGui]] Pro since version 7.7 has a built in image fusion tool which features the exposure criterion only but has extended adjustment possibilities.

* LR/Enfuse is a Lightroom plugin for blending exposures directly from within Lightroom using Enfuse. It works on Mac and PC. Get it from http://photographers-toolbox.com/products/lrenfuse.php

==== Linux ====

* [http://panorama.dyndns.org/index.php?lang=en&subject=KImageFuser&texttag=KImagefuser KImageFuser] by Harry van der Wolf is an enfuse/align_image_stack Gui for Linux (free GPL V3). It has a preview function and batch options. It is written in the graphical script environment [http://kommander.kdewebdev.org/ kommander] and can run on any linux platform. Dependencies are: kdewebdev-3.5.9 or newer, [http://enblend.sourceforge.net enfuse], align_image_stack (from [http://hugin.sourceforge.net Hugin]), convert ([http://www.imagemagick.org ImageMagick]). Not a dependendency but highly recommended: [http://www.sno.phy.queensu.ca/~phil/exiftool/ Exiftool] to be able to copy all relevant exif data (ImageDescription, Make, Model, Artist, WhitePoint, Copyright, GPS:all, DateTimeOriginal, CreateDate, UserComment, ColorSpace, OwnerName, SerialNumber, all IPTC, all JFIF, XResolution, YResolution, ResolutionUnit, Lens, FocalLengthIn35mmFormat and FocalLength) to the new image. All dependencies are available in the main linux distributions. Note also that at least one KDE theme should be available like e.g. the famous (and default) "bluecurve" theme. KImageFuser has also been added to the [https://hugin.svn.sourceforge.net/svnroot/hugin/ Hugin svn] in it's own project [https://hugin.svn.sourceforge.net/svnroot/hugin/KImageFuser KImageFuser] tree.
* [http://www.digikam.org/ digiKam] can use enfuse to blend bracketed images.

==== Windows ====
* The droplets by Erik Krause are contained in the [[hugin]] windows package from http://hugin.sourceforge.net and installed ready to use. A group of image files or an entire folder can be dragged and dropped on a droplet. In case of a folder the user can specify the number of images in a bracketed series, hence multiple series can be enfused in one go. The droplets copy relevant EXIF data to the result image such that camera and lens data isn't lost f.e. for subsequent stitching. Another droplet version does automatic alignment in order to allow for handheld bracketed series. (open source)

* [http://software.bergmark.com/enfuseGUI/ EnfuseGUI] by Ingemar Bergmark is a graphical user interface (free).

*[http://www.tawbaware.com/tufusepro.htm TuFuse Pro] by Max Lyons is a nice graphical user interface to his own [http://www.tawbaware.com/tufuse.htm tufuse] free command line application (commercial)

* [http://www.tawbaware.com/forum2/viewtopic.php?t=4966 Tufusion] is a free GUI for Max Lyons' tufuse, developed by TuFuse forum user "entropy". It's not as sophisticated as TuFuse Pro, but it surely makes life a lot easier, compared to using the command line application.

==== Mac OSX ====

* [http://pangeasoft.net/pano/bracketeer/ Bracketeer] (commercial) by ''Brian Greenstone'' is a graphical user interface with preview function for OS X 10.4 and higher.

* [http://software.bergmark.com/enfuseGUI/ EnfuseGUI] (donationware) by ''Ingemar Bergmark'' is a graphical user interface for OS X 10.4 and higher.

* [http://panorama.dyndns.org/index.php?lang=en&subject=ImageFuser&texttag=ImageFuser ImageFuser] ([http://groups.google.com/group/hugin-ptx/browse_thread/thread/711ec6caf975785e Open Source]) by ''Harry van der Wolf'' is a graphical user interface for enfuse and [[align_image_stack]] with preview function for OS X 10.4 and higher.

* [http://www.kekus.com/legacy_products.html XFuse] (free) by ''Kevin Kratzke'' is a graphical user interface that allows for batch processing and works on OS X 10.4 and higher. Development of this application is discontinued, last downloadable version is 0.5 as of Feb. 8, 2008.

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

Install Panotools-Script on Windows

2012-12-18T08:10:15Z

Zarl: Reverted edits by Tonyguards (talk) to last revision by Mpetroff

'''Panotools::Script''' is a framework for scripting various panorama
operations using the command-line tools shipped with [[hugin]], it has some
[http://search.cpan.org/dist/Panotools-Script/ Documentation on CPAN].

== Simplified Method ==
=== Install Panotools::Script ===
#Install required software:
#* Install Strawberry Perl from http://strawberryperl.com/.
#* Install ImageMagick (Win32 dynamic at 16 bits-per-pixel) from http://www.imagemagick.org/script/binary-releases.php.
#Install Perl scripts:
#* Open: Start Menu -> Strawberry Perl -> Tools -> CPAN Client
#* Run the following commands:
#*:<pre>
#*:notest install Panotools::Script Image::Magick
#*:exit
#*:</pre>

The latest version of '''Panotools::Script''' should now be installed. These packages will work fine on the computer on which they were built, but .exe tools may be desired in order to run on computers without Perl installed.

=== Build .exe Tools (Optional) ===
#Install required Perl scripts:
#* Open: Start Menu -> Strawberry Perl -> Tools -> CPAN Client
#* Run the following commands:
#*:<pre>
#*:notest install PAR::Packer
#*:exit
#*:</pre>
#Build .exe tools:
#* Open: Start Menu -> Strawberry Perl -> Perl (Command Line)
#* Change directory to install directory:
#*:<pre>
#*:cd <STRAWBERRY-PERL-HOME>\perl\site\bin
#*:</pre>
#* Build desired .exe tools (replace <PACKAGE> with name of package):
#*:<pre>
#*:pp -o <PACKAGE>.exe <PACKAGE>
#*:</pre>

== Perl ==

'''Panotools::Script''' is a ''Perl module'', so for Windows you need to
[http://www.activestate.com/store/activeperl/download/ download and install ActiveState Perl]
first, I got the MSI installer for ActivePerl-5.8.8.822.

For some reason, the installer doesn't set the PATH correctly for manually
built modules, so go to '''Explorer''' -> '''My Computer''' -> '''right-click'''
-> '''Properties''' -> '''Advanced''' -> '''Environment Variables''' ->
'''System variables'''. Scroll to '''Path''', click '''edit''', and add this path
to the front of the existing list of paths:

C:\Perl\site\bin;

=== Image::ExifTool, Image::Size and Module::Build ===

You need three extra ''modules'' that are not installed by default. So in the Activestate
part of the ''Start menu'', run the Perl Package Manager (PPM). This can be used to
install pre-built add-on modules, in this case you want to install ''Image-ExifTool'', ''Image-Size''
and ''Module-Build''. Reboot after installing Module-Build, remember this ''is'' windows.

== ImageMagick ==

[[ImageMagick]] is a general purpose command-line image manipulation suite,
'''Panotools::Script''' uses it for various purposes such as resizing and playing
with alpha channels. I downloaded the ''Win32 dynamic at 16 bits-per-pixel'' version
[http://www.imagemagick.org/script/binary-releases.php#windows from the ImageMagick site].

== hugin ==

Install [[hugin]] from the
[http://sourceforge.net/project/showfiles.php?group_id=77506 sourceforge download area]
if you haven't already. You need to fix the PATH again, add the hugin installation
location the same as you did for ''Perl'' above:

C:\Program Files\hugin\bin;

== autotrace ==

Autotrace is a tool for converting bitmap images to vector graphics, only
install this if you plan on editing enblend masks in [http://inkscape.org/ Inkscape].

[http://autotrace.sourceforge.net/index.html#download Download autotrace from here].
You need to manually extract and install this one, put the folder containing
the various DLLs and EXE files somewhere like '''C:\Program Files\autotrace''' and
add this to your PATH as you did for Perl and hugin.

== Panotools::Script ==

[http://search.cpan.org/dist/Panotools-Script/ Download the latest source-code for Panotools::Script].
This is a ''gzipped tar archive'', so you will need something like
[http://www.7-zip.org/ 7-zip] to extract it.

=== Download nmake ===

''make'' is required to build and install Perl modules, [http://download.microsoft.com/download/vc15/patch/1.52/w95/en-us/nmake15.exe download nmake from Microsoft]
and double-click it to extract. Copy NMAKE.EXE and NMAKE.ERR to the directory where you extracted the
'''Panotools::Script''' sources.

=== Test and install ===

Open a ''command window'': Click '''Start''' -> '''Run...''' -> '''cmd''' -> '''OK'''.

Change to the directory where you extracted the sources:

cd Desktop\Panotools-Script-0.09

Then run the tests:

perl Makefile.PL
nmake test

The tests will produce lots of output and warnings, but at the end it should
report 100% success. Finally install everything:

nmake install

== Creating .exe tools ==

This step isn't necessary if you have perl installed, but may be useful to make the tools
usable on systems without perl. The right tool for this is PAR::Packer, I couldn't get it
to work with this version of perl (please update this HOWTO if you know), so I installed
''App-Packer'' using Perl Package Manager (PPM).

If you are lucky then you can just create the .exe files with the ''make_exe.pl'' script:

perl bin\make_exe.pl

I wasn't so lucky and had an error from a standard perl module ''bytes_heavy.pl'', which
I fixed by pasting this code into ''C:\Perl\lib\bytes_heavy.pl''

<source lang="pl">
sub import {
return unless $Have_Bytes;
shift;
unshift @_, 'bytes';
goto &bytes::import;
}
</source>

Finally, you should be able to run the resulting .exe files on other
Windows systems, though you will also need the copy the ''perl58.dll''
file to the same destination.

== Infrastructure to build the .exe tools - the new way ==

this is highly experimental. it has been tested on PAR::Packer 0.980 released May 14, 2008. Works for 0.982 / July 29, 2008 as well.

# Install MinGW - MSVC 2008 EE is not supported
#* Download MinGW-5.1.4.exe from http://www.mingw.org/
#* Follow default install, but add g++ to the mix, i.e. just click "Next" as often as needed, but on the screen where you can tick boxes to choose what to install, check the box with g++ (and leave anything else as is. It will be installed in C:\MinGW
#* Run the now installed C:\MinGW\MinGW-5.1.4.exe to ensure you get the latest updates.
# Install ActiveState Perl 5.10.0 build 1002 (other versions may also work, this is the one that worked for me)
# start the Perl Package Manager (PPM), search and install the following packages
#* Getopt-ArgvFile (>=1.07)
#* Module-ScanDeps (>=0.78)
#* PAR-Dist (>=0.22)
#* Parse-Binary (>=0.10)
# Download dmake from http://search.cpan.org/dist/dmake/
# Extract dmake to C:\MinGW so that you have a folder called C:\MinGW\dmake
# Make yourself an environment batch file, call it perl.bat, with the following content:
#:<pre>
#:set MINGW_PATH=C:\MinGW
#:set PERL_PATH=C:\Perl
#:set PATH=%MINGW_PATH%\bin;%MINGW_PATH%\mingw32\bin;%MINGW_PATH%\dmake;
#:set PATH=%PATH%C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;
#:set LIB=%MINGW_PATH%\lib;
#:set INCLUDE=%MINGW_PATH%\include;
#:set PATH=%PERL_PATH%\site\bin;%PERL_PATH%\bin;%PATH%
#:cmd /K
#:</pre>
# install manually Win32-exe, Par and Par-Packer.
#* get them from:
#** [http://search.cpan.org/~smueller/PAR-Packer-0.980/lib/PAR/Packer.pm PAR-packer]
#** [http://search.cpan.org/~smueller/Win32-Exe-0.11/lib/Win32/Exe.pm Win-Exe]
#** [http://search.cpan.org/~smueller/PAR-1.002/lib/PAR.pm PAR]
#* extract them to a temporary folder
#* doubleclick on perl.bat to start a CLI
#* in the CLI, run the following commands
#*:<pre>
#*: > perl Makefile.PL
#*: > dmake
#*: > dmake test
#*: > dmake install
#*:</pre>
# test your installation
#* create a file test.pl with the following content:
#*:<pre>
#*: #!/usr/bin/perl
#*: print "hello world!\n";
#*:</pre>
#* in the CLI, check it works
#*:<pre>
#*: perl test.pl
#*:</pre>
#* compile it
#*:<pre>
#*: pp -o test.exe test.pl
#*:</pre>
#* test it
#*:<pre>
#*: test.exe
#*:</pre>
#contribute back! If you have come so far, it is because volunteers have helped you. Those volunteers need your help in turn.
#* Subscribe to the PAR::Packer [http://lists.cpan.org/showlist.cgi?name=par mailing list].
#* From time to time there will be a request like [http://www.nntp.perl.org/group/perl.par/2008/07/msg3649.html this] one.
#* when you see the request, download the latest packages and repeat the above step 7.
#* when processing the PAR-packer temporary folder, after dmake test, issue a
#*:<pre>
#*: dmake par
#*:</pre>
#* In the temporary folder there should now be a file named '''PAR-Packer-0.980-MSWin32-x86-multi-thread-5.10.0.par''' or something similar. Upload that file somewhere and announce it to the mailing list.
#* if you want to intall the latest PAR-Packer, continue with dmake install.

The perl58.dll is no longer required.


[[User:Yuval|Yuval]] 23:09, 15 May 2008 (CEST) with help from Mark Dootson and the PAR::Packer community


[[Category:Tutorial:Nice to know]]

Hugin translation guide

2012-11-14T13:27:09Z

Zarl: /* Website / Release Notes */ updated links

== Introduction ==

This page intends to provide guidance to translators of the Hugin project. Some terminology is very specific or used in a specific way in hugin, making it hard to find a close translation that fits the context of hugin in another language than English.

== Getting Started on translations ==

*1. Get your language file
:Each language version of hugin uses a different *.po file (just like "fr.po" for French or "ja.po" for Japanese) containing all the translated strings. The country codes use the [http://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-1] naming convention.
:In general, you need the latest *.po file, usually the one for the language you want to modify. You can download it from the [http://hugin.hg.sourceforge.net/hgweb/hugin/hugin/file/default/src/translations Mercurial repository]: in this list of files navigate to your *.po file, click on the file name and then use the link "raw" in the navigation bar to save the file (right click or ctrl-click: Save Link as...) to your local hard disk.
:If there is yet no translation file for your language you can use the file hugin.pot and rename that using the above naming convention or just ask the [http://groups.google.com/group/hugin-ptx developers list] for assistance.

*2. Edit your *.po file
:To edit the *.po or *.pot files, use [http://sourceforge.net/projects/poedit/ poedit] (it is a cross-platform PO files editor which runs on Mac OS X, Unix and Windows) or [http://kbabel.kde.org/ kbabel] (it runs on any KDE platform). Note that you don't have to translate everything if you don't have time or knowledge to do it all. Also [[Hugin_translation_guide#Do_not_translate:|check below]] for things that shouldn't be translated (like software names) or for some explanations on specific words.
:Note: When using a version of Poedit before 1.4.3, editing comments directly in the right pane doesn't work, the text isn't saved into the .po file. To edit comments, use the "edit comment" dialogue from the menu. With Poedit 1.4.3 and later, please note that to see the comment window you have to check "View / Show comment window", and to be able to modify the comment you must go to "File / Preferences..." and check "Comment window is editable" in the "Editor" tab.
:Messages marked as '''fuzzy''' are actually not used in the GUI, their English counterparts are used instead. This seems to be an automagic suggestion which naturally often fails, so compare a fuzzy translation with the original phrase.

*3. Verify your translation
:In order to test your new translation and as well save some time for the developers who apply your file to trunk it's recommanded to [http://wiki.panotools.org/Hugin_translation_guide#How_to_check_the_translated_file_for_syntax_errors check] your newly translated po file for syntax errors. It's also a good idea to [http://wiki.panotools.org/Hugin_translation_guide#Use_your_new_translation_file temporarily load] your new translation file into the latest available hugin build.

*4. Submit your *.po file, or even better, commit your changes through Mercurial
**You can submit your edited translation via hugin's [https://bugs.launchpad.net/hugin/ tracker] on launchpad (you'll need a launchpad account to log in). Add the tags "translation" and "hugin" and attach your file.
**'''An even better solution''', but which the first time takes you a few more minutes to set everything up, is to use Hugin's revision control system. For more information see [http://wiki.panotools.org/Hugin_translation_guide#Become_a_Power_Translator Become a Power Translator] below.

== How to check the translated file for syntax errors ==
The best way to check if your newly translated XX.po file hasn't any error, is to run the following command in a terminal (if you are under linux)
msgfmt -c --statistics XX.po
(you will need to install the gettext package to use the msgfmt command)

If you get as output the number of translated, unstranslated and fuzzy strings the file is ok. Else you get error messages indicating the line where the errors resides. Open the po file in a text editor, look for the line where the error lives and fix it. Finally run again the above command until you get no errors.

Note: if you use Poedit, it gives you warning when the po file you are trying to save contains errors. In the error message read the line where the error is listed then close poedit and open the file in a text editor and look for errors in the specific line.

=== Common mistakes ===
* Remember that the first line in a po file need to be commented as shown here (note the # sign at the beggining of the line)
# French translations for hugin package.
# Copyright (C) 2004 Pablo dAngelo
# This file is distributed under the same license as the hugin package.
# Jean-Luc Coulon (f5ibh) <jean-luc.coulon@wanadoo.fr>, 2004-2009, 2010.

* Watch carefully for retaining placeholders:
:If you take the following string:
Open "%s" file
:the %s must remain the same in the translated string because it is a formatting placeholder where the code will display a variable (e.g. a filename, a number etc...) at run time. For example %s is a string and %0.3f is a number with three post-comma digits.

* Watch out for the new line (\n) indicator at the end of the string. For example in the string:
This is a test for a new line string\n
:The \n symbol must remain at the end of the translated string

* Watch out for quotation marks ". They must be quoted as \"

== Use your new translation file ==

poedit updates your PO file and creates a MO file for your language. You can rename your MO file into hugin.mo and replace the hugin.mo file from your current installation (don't forget to make a backup of the original MO file, just in case).

*On '''Windows''' the MO file is in your hugin directory, in <tt>share\locale\''XX''\LC_MESSAGES\hugin.mo</tt>, where ''XX'' is your language.
*On '''Linux''' the MO file is under <tt>/usr/local/share/locale/XX/LC_MESSAGES/hugin.mo</tt>
*On '''Mac OS X''' the MO file is inside the hugin bundle: just click on Hugin.app and from the context menu choose "Show package contents", from there it's under <tt>Contents/Resources/''XX''.lproj/locale/hugin.mo</tt> (<tt>''XX''</tt> is your language code).

If you want to you can also rebuild hugin (doesn't have to be a heavy job when you only changed the .po file, the process only updates that part).

== Contribute your Translation ==

The preferred way is for translations to be contributed via the [https://bugs.launchpad.net/hugin/ tracker]. If you don't want to use the tracker you can also post it as attachment to the mailing list, but the mailing list has a short memory and your hard work may be forgotten.

To use the tracker, you need a [http://wiki.panotools.org/Hugin_Trackers#Launchpad_Account Launchpad Account].

You can submit our translation via the web or via email.

=== Web ===

* Log on with your Launchpad account.
* Start reporting a [https://bugs.launchpad.net/hugin/+filebug new ticket].
* Enter a title/summary (e.g. German Translation).
* Launchpad will look for duplicates. This is good for bug reports, but for updated translations you can ignore it, scroll down to the bottom of the page and hit the "No, I need to report a new bug".
* On the reporting form, enter a description in the "Further Information" field, then scroll to the bottom and hit the link "Extra options".
* There you will find an Attachment field. Hit it and browse to the .po file. When the bug tracker asks you if this is a patch: click yes, even though technically it isn't one. In this case it will help make developers aware of a file that needs to be reviewed and added to the codebase.
* Click the "Submit Bug Report" button.

=== eMail ===

Reporting a new ticket by email works too, but there are some critical conditions:
* Your email account must be registered with Launchpad.
* You must have an OpenPGP key associated with it and known to Launchpad.
* You must craft your email carefully. A misplaced space or a typo can doom your report.
* To be safe, use TEXT email, not HTML -- a good habit anyway. In most email client you recognize the TEXT mode by the lack of a formatting toolbar).

The message:
* From: your Launchpad-registered email address
* To: new@bugs.launchpad.net
* Subject: title of the bug
* Body: description + carefully crafted commands. Commands are usually at the end of the body. One per line. Each command line starts with a single space.
* Enter the command " affects hugin" to assign the report to Hugin.
* Enter the command " tag translation" to tag the report as being a translation.
* Attach the file(s) to the email.
* Send. It takes about five minutes to process and you get an email back with the result.

== Become a Power Translator ==

After adding your po file to Hugin's [https://bugs.launchpad.net/hugin/ tracker], the developers still need to integrate it, which is not easy as it means dealing with conflicting version (but how should a developer know which one of two conflicting sentences in a foreign language is the right one?). Thus using the same Mercurial approach to translation reduces considerably the burden on the rest of the team and is very much appreciated. Translation is a development too!

So '''instead of adding your po file to the tracker''', you can integrate it yourself. You'll first need a '''Sourceforge user account''' ([http://sourceforge.net/account/registration/ register here] if you don't have one yet. Then tell the developers on the [http://groups.google.com/group/hugin-ptx/ mailing list] what your user account is, so that they can '''grant you access to Mercurial''', the revision control system (you'll need this before following the next steps).

=== The first time ===

'''For Windows users'''

*1. Get and install [http://tortoisehg.bitbucket.org/ TortoiseHg].
*2. In the explorer create a new folder, e.g. hugin-hg. Then do a right click on the created folder and select "Clone" in the "TortoiseHG" submenu. Select the repository http://hugin.hg.sourceforge.net:8000/hgroot/hugin/hugin as source path and select "Clone".
*3. Now select "Repository Settings" in the "TortoiseHG" context menu of the folder. In the section "Synchronize" add a new setting with an alias/name e.g. "writeRepo" and the URL ssh://YOUR-SOURCEFORGE-USERNAME@hugin.hg.sourceforge.net/hgroot/hugin/hugin , close the settings dialog. (This needs to be done only once.)
*4. You can commit your (partial) results anytime: right-click on the folder and select in the context menu "Hg Commit..." - enter a short text describing what you did (e.g.: "updated French translation"), check that only your modified .po file is selected and click OK. Note that you can select only the "translation" folder instead of "hugin-trunk" if you modified only files within "translation".
*5. Open the folder context menu, open "TortoiseHG/Synchronize". Select your in step 2 created setting in the combobox and select "Push". (Or you can also push from the "Repository Explorer".)

'''For Linux/Unix/OSX'''
*1. Get and install [http://mercurial.selenic.com/ Mercurial]. (<pre>apt-get install mercurial</pre> on Ubuntu/Debian,<pre>yum install mercurial</pre> on Fedora, <pre>emerge mercurial</pre> on Gentoo)
*2. Get the full Hugin source code.
<pre>
hg clone http://hugin.hg.sourceforge.net:8000/hgroot/hugin/hugin hugin
</pre>
*3. Do your translation work inside the folder src/translations
*4. You can commit your (partial) results anytime by running the commands
<pre>
hg pull
hg commit TRANSLATEDFILE.po -m "updated LANGUAGE translation"
hg push ssh://YOUR-SOURCEFORGE-USERNAME@hugin.hg.sourceforge.net/hgroot/hugin/hugin
</pre>

'''Important:''' committed changes are only on your local disk. You must push them to SourceForge to make them available to the project.

=== The following times ===
The next time you want to work on the translations, you'll have first to '''retrieve the latest version of the files''' (as someone else might have modified something in the meantime) before working on it and then commiting it again.

;For Windows users
:Simply right-click your "hugin" folder and select "Synchronize" in the "TortoiseHG" menu. In the dialog select "Update" in the combobox "After pull" (You can select in the settings under "Synchronize" that this is the default setting). Now select "Pull".

;For Linux/Unix/OSX
:change into the folder with the files and execute
<pre>
hg pull
hg up -c
</pre>
and then you can continue from step 3 above.

=== Extra perk - Build the latest Hugin ===
:If you're already here, you may want to also build and enjoy the latest Hugin. Some of the current contributors to the build, distribution and code of Hugin have learned this way. You are just a few clicks away from building your own bleeding edge Hugin. Find your platform in [http://wiki.panotools.org/Development_of_Open_Source_tools#Build_your_Own_Test_Builds Build your Own Test Builds] section of the wiki and follow the instructions.
:Welcome to the club!

== Translation guide for specific terms ==

'''Note to translators, please add your language variant to the term on a new line in the same format as NL= Also add your own difficult terms that are not mentioned here.'''

'''Note to developers, please check and enhance the meanings of these terms if they are unclear or incorrect.'''

; Aligning versus Finding control points
: Problem= they appear to be similar or the same, can they be interchanged?

; Anchor
: Meaning=Reference
: NL=referentie (was anker)

; bundle
: Meaning=A technique for distributing OS X software as a single file.
: NL=bundle (bundel?)

; bundled version
: Meaning=? Any packaged software will contain multiple files, these files are said to be 'bundled' (not just OS X)
: NL=ingebouwde versie (gebundelde versie?)

; button
: DE=Schaltfläche

; Camera response (C. r. curve)
: Meaning=it corresponds with photo-electrical transfer function, and I am not sure can I translate it to "opto-electic curve of camera" in my language, because stright tranlation of "camera response" statement sounds trivial and not clear.
: PL=krzywa optoelektryczna aparatu?

; control points
: Meaning=corresponding areas in two images (or the same image for horizontal and vertical control points)
: ET=juhtpunktid
: NL=ijkpunten (was controle punten), IJkpunten bij hoofdletters

; Crop factor
: Meaning=The physical size of a CCD sensor relative to a 35mm frame.

; Cropped (images)
: Meaning=image cut smaller than the original size
: Discussion=Should this be translated? Like Blend, this is jargon, may be clearer when untranslated?
: ET=kärbitud (pildid)
: NL=uitgesneden (afbeeldingen)

; Custom parameters
: Meaning=parameters other than standard (+context???)
: NL=aangepaste parameters

; Estimate (position, FoV, etc.)
: Meaning=? in my book, estimate means an educated guess. I get the impression that a more exact term is intended for hugin. Where can this term be replaced with "calculate" or "determine"?
: ET=määratlema
: NL=bepalen (eng:determine), bereken (eng:calculate) alternative suggestion: Schatten (eng:estimate)

; Exposure blending (or Exposure fusion)
: Meaning=Taking a bracketed photo stack and picking the best bits to create a new image. Hugin tries to use the phrase 'Exposure fusion' rather than 'blending' as the tool for this is [[enfuse]].
: NL=Belichtings lagen samenvoegen (Note: enblend = samenvoegen; enfuse = belichtings lagen samenvoegen?)

; Field of View
: Meaning=Horizontal Angle of view
: ET=vaateväli
: NL=beeldhoek

; flatfield
: Meaning=An astronomical technique, using a photo taken with the lens covered or of an even white surface to calibrate normal photos
: NL=flatfield (astrofoto jargon, ook in NL gebruikt)

; flatfile
: Meaning=?
: NL=?

; grayscale
: Meaning=monochrome colourspace. Typically grayscale images can have many shades of gray as well as black and white.
: ET=halltoonid
: NL=grijsschaal (kan beter!)

; High Dynamic Range (HDR)
: Meaning=Luminance values are within a large numeric range (typically floating point with a linear response)
: NL=Hoog Dynamisch Bereik (HDR)

; image
: Meaning=photo, scan, ....
: ET=pilt
: NL=afbeelding
: DE=Bild

; keypoint
: Meaning=
: DE=Merkmalspunkt (see [http://de.wikipedia.org/wiki/Scale-invariant_feature_transform Article about SIFT] in the German Wikipedia)

; Low Dynamic Range (LDR)
: Meaning=Luminance values are within a small numeric range (typically 8-bit or 16bit integer with a non-linear response curve).
: NL=Laag Dynamisch Bereik (LDR)

; mapping
: Meaning=render and distort an image to a different projection?
: NL=translatie, afbeelding, vervorming, projectie?

; Num. Transf.
: Meaning=Numerical Transform. Rotation of panorama roll, pitch and yaw by manually entering numbers.
: NL=Num. Transf.

; Photometric Alignment
: Meaning=Determining relative exposure, camera response and vignetting
: ET=fotomeetriline joondamine
: NL=fotometrische uitlijning (beter?: fotometrische afstemming)

; Photometric Optimisation
: Meaning=Optimisation of non-mapping image parameters, such as 'Camera response', Vignetting and Exposure.
: ET=fotomeetriline optimeerimine
: NL=fotometrische optimalisatie

; pyramid image
: Meaning=This is the practice of creating a stack of successively smaller versions of an image, useful for many image manipulation tasks.
: NL=piramidale afbeelding

; Seam blending
: Meaning=Taking two or more partially overlapping photos and blending then with a seam down the middle of the overlap. The tool typically used for this is [[enblend]]

; Stitcher (the tab)
: Meaning= Where the actual combining of the images is done
: ET=Ühendaja
: NL=Samenvoegen (alt: Combineren, Naaien?)

; Vertical or Horizontal guide
: Meaning=Horizontal or Vertical "control points"
: NL=h/v hulp (suggestie: ijklijnen)?

=== Do not translate: ===

* Autopano (program name)
* Autopano-SIFT (program name)
* Deflate (zip method)
* Enblend (program name)
* EXR (HDR file type)
* JPEG (file type)
* LZW (zip method)
* Nona (program name)
* Packbits (zip method)
* PTStitcher (program name)

== Technical translation issues ==

Some strings don't appear to be translated, they are apparently generated by the GUI toolkit or the operating system. Most likely they will be in the same language as hugin, because very few people, other than translators, start a program with a specific language other than that of the environment.

The file <tt>src/translations/ignored-entries.txt</tt> contains a list of ignored entries from the xrc files (which are used to declare most of the hugin UI). If you need to translate a sentence which is there, remove the line from the file and run the extract-messages.sh script to update the .po files.

If you find a source term that isn't correct, spelling or meaning, probably best to bring it up with Pablo d'Angelo or on the hugin mailinglist: [http://groups.google.com/group/hugin-ptx]

=== List of source string problems ===

* calculate highest sensible width. (uses every image pixel)
: I can translate this literally, but is this even helpful in English? (this is a tooltip for the size calc button in the Stitcher tab)

== Tips and Tricks ==

=== Running hugin in a specific language ===

If you want to run hugin in another language than the default, use the following command (Linux with UTF8):

$ LANG=nl_NL.utf8 hugin

This will start hugin in dutch. Other languages have different names of course, try looking in <tt>/usr/share/i18n/locales/</tt>.

== Developer info ==

=== Adding new strings ===

After adding new strings, translators need to find them in the .pot and .po files otherwise they won't get translated.

Hugin has a script to extract the messages from both the .xrc files and the .cpp source code and insert them into the hugin.pot and .po files. New strings are added and unused strings are marked as obsolete.

Before running the script, make sure you have wxrc installed. On older Ubuntu, run <code>sudo apt-get install wxrc</code>. On Ubuntu 10.4 it is <code>sudo apt-get install wx-common</code>.

Then, add the new strings:

<pre>
hg pull
hg up
cd src/translations
./extract-messages.sh
hg ci
hg push ssh://YOUR-SOURCEFORGE-USERNAME@hugin.hg.sourceforge.net/hgroot/hugin/hugin
</pre>

=== Applying a contributed .po file ===

You could just overwrite the original and commit, but this assumes the file is correctly formatted and hasn't lost any strings. Better to use '''msgmerge''' to merge the contributed .po file with the existing. Hugin has a script to test what will happen. Use '''msgfmt''' for a quick sanity check too:

src/translations/diff_po.pl src/translations/zh_CN.po /tmp/zh_CN.contributed.po
msgmerge -o zh_CN.merged.po /tmp/zh_CN.contributed.po src/translations/zh_CN.po
msgfmt -c --statistics zh_CN.merged.po
msgfmt -c --statistics src/translations/zh_CN.po
mv zh_CN.merged.po src/translations/zh_CN.po
hg ci zh_CN.po -m 'Edited chinese translation'
hg push ssh://YOUR-SOURCEFORGE-USERNAME@hugin.hg.sourceforge.net/hgroot/hugin/hugin

=== Statistics ===

msgfmt --statistics eo_XX.po

=== Issues That Need Work ===

* There are more than 1000 strings in the hugin.pot file. The main translation problem we have now is that many of these strings are in the sourcecode, but not in bits that are used - i.e. there are strings that are being translated unnecessarily (the panodruid for example).
* The .po files headers are inconsistent. Ideally they would all feature the same license and copyright notice; and they would list all contributors.

== Website / Release Notes ==

Some translators contribute also translated release notes. These are published on the web at http://hugin.sourceforge.net/releases/ . Usually the release manager will draft the release notes in English early on in the release process. Even if they are not linked, you can find them in the repository at http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/file/tip/releases

'''Important''': make sure you translate the file from the [http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/file/tip/releases repository] and not the resulting file displayed on the web, e.g. for 2012.0.0 translate the ''raw'' version of
http://hugin.hg.sourceforge.net/hgweb/hugin/hugin-web/file/4894a12dc2ea/releases/2012.0.0/en.shtml and not the current one from http://hugin.sourceforge.net/releases/ - the former is the source for the page while the latter is the resulting page after server side includes and other server side transformations.

Thanks for your contributions!

[[category:Software:Hugin]]

FJPG

2012-10-24T11:24:00Z

Zarl: Reverted edits by Bevmorguson (talk) to last revision by Erik Krause

'''FJPG''' {{Glossary|is a JPEG flavor that supports display of high dynamic range ([[HDR]]) images for [[PTViewer]] 3.x|1}} introduced by Helmut Dersch. A FJPG file stores an additional block of data containing exponent values for each 8x8 pixel block of the normal [[JPEG]] image. This way JPEG is extended into a good compressed albeit a bit coarse HDR image format.

A conversion program, a technical paper and [[PTViewer]] 3.1.2 which uses this file format for display of adaptive [[dynamic range]] panoramas and images can be found on Helmut Dersch's page: [http://webuser.fh-furtwangen.de/~dersch/]
[[Category:Glossary]]

PTV

2012-10-24T11:23:31Z

Zarl: Reverted edits by Bevmorguson (talk) to last revision by Erik Krause

{{Glossary|PTViewer [[Image format]], supported by [[PTViewer]] version 2.8L from [[Fulvio Senore]]|1}}

Main Page

2012-10-12T08:39:46Z

Zarl: Reverted edits by RaleighRhoades (talk) to last revision by Zarl

__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]]

Pro photographers

2012-10-10T17:09:14Z

Zarl: /* V */

Please add the entry alphabetically to the list.

{{CompactTOC}}

== A ==

== B ==
[http://www.visoog.be] Visoog virtual tour of Ghent, Belgium by Beamhunter

== C ==
[http://www.patrickcheatham.com Patrick Cheatham 360° Photography & Interactives] - San Francisco/Oakland, Ca, USA

== D ==

== E ==

== F ==
Fink, Mark - New Paltz, NY USA www.northernlight.net markdfink@northernlight.net

== G ==
[http://GoVIRTUAL360.com GoVIRTUAL360.com] Virtual tours & panoramic photography in the Corpus Christi, TX area. Patrick Born 361-813-8293

[http://www.globalvision.ch/en/360/panorama-pictures.html GlobalVision Communication] 360° immersive video creation and virtual tours in Europe and Asia

== H ==

== I ==
[http://pano.1drey.com] Andrey Ilyin, Moscow VR Service

== J ==

== K ==

== L ==

== M ==
[http://www.MLSphotos.com MLSphotos.com] Real Estate Photography and Virtual Tours in Southern California and Houston, Texas

== N ==

== O ==

== P ==
Prince Photo Imaging - Denver - 303.520.1528 Full Screen VR - See a sample at:http://www.ehomeparade.com/qtvr/blackforestbb/interface.html

[http://www.PhotoSpherix.com PhotoSpherix]360 Product photography and Panoramic Images
== Q ==

== R ==

== S ==
[http://www.southern-digital.com Southern Digital Solutions] Panoramic and immersive photography by Sacha Griffin

[http://www.sitetraffic.com Sitetraffic]

[http://www.studioargento.com Studio Argento] Architectural and immersive photography by Toni Garbasso

== T ==
[http://www.360days.com 360days: life panoramas] a sandbox by mickael therer, european based photographer

== U ==

== V ==
[http://www.virtualtours360.co.za Virtual Tour South Africa] - Virtual Tour South Africa create 360 photos in to virtual tours

van der Lande Jean-Pierre

[http://www.panograph.hu PanoGraph] by Tamas D.Varga

== W ==

== X ==

== Y ==

== Z ==

== 0 - 9 ==

[http://www.360texas.com 360Texas.com] Fort Worth, Texas

== others ==

[[Category:Community:People]]

Pro photographers

2012-10-10T17:07:44Z

Zarl: Reverted edits by Zarl (talk) to last revision by Corswors

Please add the entry alphabetically to the list.

{{CompactTOC}}

== A ==

== B ==
[http://www.visoog.be] Visoog virtual tour of Ghent, Belgium by Beamhunter

== C ==
[http://www.patrickcheatham.com Patrick Cheatham 360° Photography & Interactives] - San Francisco/Oakland, Ca, USA

== D ==

== E ==

== F ==
Fink, Mark - New Paltz, NY USA www.northernlight.net markdfink@northernlight.net

== G ==
[http://GoVIRTUAL360.com GoVIRTUAL360.com] Virtual tours & panoramic photography in the Corpus Christi, TX area. Patrick Born 361-813-8293

[http://www.globalvision.ch/en/360/panorama-pictures.html GlobalVision Communication] 360° immersive video creation and virtual tours in Europe and Asia

== H ==

== I ==
[http://pano.1drey.com] Andrey Ilyin, Moscow VR Service

== J ==

== K ==

== L ==

== M ==
[http://www.MLSphotos.com MLSphotos.com] Real Estate Photography and Virtual Tours in Southern California and Houston, Texas

== N ==

== O ==

== P ==
Prince Photo Imaging - Denver - 303.520.1528 Full Screen VR - See a sample at:http://www.ehomeparade.com/qtvr/blackforestbb/interface.html

[http://www.PhotoSpherix.com PhotoSpherix]360 Product photography and Panoramic Images
== Q ==

== R ==

== S ==
[http://www.southern-digital.com Southern Digital Solutions] Panoramic and immersive photography by Sacha Griffin

[http://www.sitetraffic.com Sitetraffic]

[http://www.studioargento.com Studio Argento] Architectural and immersive photography by Toni Garbasso

== T ==
[http://www.360days.com 360days: life panoramas] a sandbox by mickael therer, european based photographer

== U ==

== V ==
[http://www.virtualtours360.co.za Virtual Tour South Africa]-Virtual Tour South Africa create 360 photo,s in to virtual tours

Van der Lande Jean-Pierre

[http://www.panograph.hu PanoGraph] by Tamas D.Varga

== W ==

== X ==

== Y ==

== Z ==

== 0 - 9 ==

[http://www.360texas.com 360Texas.com] Fort Worth, Texas

== others ==

[[Category:Community:People]]

Pro photographers

2012-10-10T17:06:28Z

Zarl: Reverted edits by Corswors (talk) to last revision by Aopchuck

Please add the entry alphabetically to the list.

{{CompactTOC}}

== A ==

== B ==
[http://www.visoog.be] Visoog virtual tour of Ghent, Belgium by Beamhunter

== C ==
[http://www.patrickcheatham.com Patrick Cheatham 360° Photography & Interactives] - San Francisco/Oakland, Ca, USA

== D ==

== E ==

== F ==
Fink, Mark - New Paltz, NY USA www.northernlight.net markdfink@northernlight.net

== G ==
[http://GoVIRTUAL360.com GoVIRTUAL360.com] Virtual tours & panoramic photography in the Corpus Christi, TX area. Patrick Born 361-813-8293

[http://www.globalvision.ch/en/360/panorama-pictures.html GlobalVision Communication] 360° immersive video creation and virtual tours in Europe and Asia

== H ==

== I ==
[http://pano.1drey.com] Andrey Ilyin, Moscow VR Service

== J ==

== K ==

== L ==

== M ==
[http://www.MLSphotos.com MLSphotos.com] Real Estate Photography and Virtual Tours in Southern California and Houston, Texas

== N ==

== O ==

== P ==
Prince Photo Imaging - Denver - 303.520.1528 Full Screen VR - See a sample at:http://www.ehomeparade.com/qtvr/blackforestbb/interface.html

[http://www.PhotoSpherix.com PhotoSpherix]360 Product photography and Panoramic Images
== Q ==

== R ==

== S ==
[http://www.southern-digital.com Southern Digital Solutions] Panoramic and immersive photography by Sacha Griffin

[http://www.sitetraffic.com Sitetraffic]

[http://www.studioargento.com Studio Argento] Architectural and immersive photography by Toni Garbasso

== T ==
[http://www.360days.com 360days: life panoramas] a sandbox by mickael therer, european based photographer

== U ==

== V ==
van der Lande Jean-Pierre

----
[http://www.panograph.hu PanoGraph] by Tamas D.Varga

== W ==

== X ==

== Y ==

== Z ==

== 0 - 9 ==

[http://www.360texas.com 360Texas.com] Fort Worth, Texas

== others ==

[[Category:Community:People]]

Talk:Main Page

2012-08-30T11:08:48Z

Zarl: Reverted edits by Yasemin (talk) to last revision by Zarl

Just a quick usability note from an absolute NOOB to the site. This is a great resource for info ''about'' PanoTools, but not much help for beginners who want to find software. I just spent about 45 minutes reading through various parts of the site trying to figure out how to get a copy of the PTRemap plugin for CS3 (MacOS). The only actual download link I could find was a link to libPano in Sourceforge (for *nix) systems. Perhaps some links on the [[Getting started]] page? [[User:RAMilewski|RAMilewski]]
:Many thanks for the hint. Unfortunately we get very little help from newbies and hence don't know what exactly is missing. If you have ideas how to improve the structure you are very welcome to edit any page you think! The Panotools Plugins download link is indeed a bit difficult to find. It's on [[Panorama_Tools_Plugins#Updates]]. --[[User:Erik Krause|Erik Krause]] 19:46, 16 May 2010 (UTC)

----

I apologize for re-inserting the Platform neutral link to the main page. If the Panorama Tools community thinks that there's no platform neutral "category" it's fine with me. I will then add a link to the <strike>[[Remallax]]</strike> project from both the Windows and Mac page.

Happy editing and community sharing!... [[User:Remallax|Remallax]] :-)

----

there is no such thing as "platform neutral" software. categorizing software under "platform neutral" does not help user choose software for their platform nor does it help them choosing a platform based on the functionality offered. I will leave the entry until we discuss this out, but please discussion in the yahoo group or in direct emails as the wiki is very new and not many in the community have accessed it yet.

Yuval

----

I think it's useful to add a "<nowiki>~~~~</nowiki>" to each comment of a discussion, which includes the author and a date. So others know who wrote what and when.

[[User:Smensch01|Smensch01]] 02:07, 4 Dec 2004 (EST)

== "Categories" ==

What about software for more than one platform? Like C++/Qt software both for Windows XP/Mac OS X? And what about plugins? Do we need a "Photoshop platform"? And finally what about the difference between Mac OS 9 and Mac OS X? They are very different platforms. Please see the Wikipedia link about [http://en.wikipedia.org/wiki/Mac_OS_history Mac OS history].

These question show me that the "categorization" into platforms is not optimal.

Why do I put "category" into double quotes? Mediawiki offers categorization of pages but we aren't using this feature. Please see [http://meta.wikimedia.org/wiki/Category Mediawiki Help:Category].

Happy community sharing! [[User:Remallax|Remallax]] 05:25, 4 Dec 2004 (EST)

(By the way, interwiki linking doesn't work here. I used external links. I am trying to find out, what is missing....)

----

So we could just have one single "Software" link on the main page and show the different categorizations there? The Hugin page for example would then be in "Windows", "Linux" and "PanoTools GUIs". I don't really know if this would not be too confusing but it's worth a try.

[[User:Smensch01|Smensch01]] 05:45, 4 Dec 2004 (EST)

----

A Photohop "platform" f.e. is no good idea. There are photoshop actions that run on any OS, there are true plugins (filters, extensions) that ar OS dependent, there are scripts that require a certain version of photoshop but may be OS dependent (AppleScript, VBScript) or not (JavaScript)...

[[User:Erik Krause|Erik Krause]] 15:46, 4 Dec 2004 (EST)

== Throw out the platform sections ==

We should throw out the platform sections. The user just goes to the software she wants.
This is simpler and provides more information immediately.

Let's create a [[Software]] page and merge the [[Windows software]], [[Mac software]],
[[Unix software]] and [[Java software]] pages to it!

Why? Let's take a Mac OS X or Linux user looking for the pano dynamic library. In the [[Software]] page he
finds information about Windows' pano12.dll and a link to the
[http:/panotools.sf.net Panorama Tools Sourceforge page] and discovers compilation
instructions. He decides to update the wiki with a summary for Mac OS X or Linux. This is a lot more in the
spirit of the wiki than seeing stubs not helping him because this information is in another platform,
namely in the [[Windows software]] page.

[[User:Remallax|Remallax]] 14:03, 4 Dec 2004 (EST)

== The home page of the wiki looks intimidating ==

It's nice to see some content growing here.

I'd like to opt for a different approach on the home page of the wiki though.
It's starting to look like a table and that tends to scare people away.

Three or four clicks should be enough to get to the section you are interested in.
Endlessly scrolling a long page to get there in one click is handy, but messy.

shouldn't we place all the sections (software, equipment, etc) on subpages and make
the home page something more readable?

IMHO a good way to start off is to pretend someone hitting the page is interested in
making a panorama and knows nothing about software. Let alone he/she knows the PanoTools.
And ofcourse panotools is about more things than making panoramas

The chronological way then would be
* a short description of all things panotools can do for you with clickable links to each thing (like stitching panoramas, lining up 3d shots, barrel correcting, making object movies, morphing, etc.)
* then switch the story to panorama building, because it's the main thing we're all about.
* Explain "What makes a panorama a panorama"
* explain what do you need to make a panorama (and what is optional)
* explain why panotools is so good at it (free, full featured, active community, etc)
* explain how to get started with links to some other page that chronologically describes all things you should learn (how to rotate your camera, what camera settings to use to prevent exposure differences, what software to download, etc.

This way people can ease into it. The panorama tools are very intimidating when you first encounter them.
You can also lay down some sort of framework to prevent 20 pages describing what the nodal point (or entrance pupil) is.

[[User:Serge|Serge]] 18:08, 5 Dec 2004 (EST)

(b.t.w., the clock on the server is way off!)

----

'''Summary''': I proposed to drop the platform sections from the main page. Smensch suggested to insert just one link to a software page on the home page. Serge said that the main page looks intimidating.

I suggest that I create a Software page and create the sections Basic Library, Stitching Software, Helpers, Photoshop plug-ins, Gimp plug-ins, Viewers, Non-Panoramic use, Printing. The software is not partitioned into platforms. I propose Windows_software and other <Platform>_software for deletion. I simplify the Software section and add some text like:

Interested in learning about software working with panoramas like panorama stitching, Photoshop plugins and other useful tools? Go to the Software page.

Do you agree with this step? It's a big refactoring...

Someone else should simplify the other sections of the Main Page.

[[User:Remallax|Remallax]] 05:41, 6 Dec 2004 (EST)

== Wikipedia ==

Administrators need to do some more work setting up this site and removing '''Wikipedia''' that appears everywhere. I don't know how to do it or would offer my assistance. But for some examples of MediaWiki customization see [http://meta.wikimedia.org/wiki/Sites_using_MediaWiki Sites using MediaWiki].

[[User:209.102.125.95|209.102.125.95]] 20:14, 6 Dec 2004 (EST)

----
This has been corrected. PanoTools is now the "Site Name".

[[User:John Spikowski|67.168.155.83]] 23:24, 6 Dec 2004 (EST)

A VERY INTERESTING SITE.
Our company is about to embark on an exciting era of entertainment which uses fisheye imaging to create some outstanding immersion experiences for theme parks and the military.
If anyone reading this knows of or is a software author with a considerable amount of experience writing conversions algorithms for circular fisheye images, please feel free to contact me at kmm@infocusmp.com.
We are looking for your input. This site has been great in helping me to formulate the technologies available as well as the software.
Thanks
Mac

Main Page

2012-08-30T11:08:29Z

Zarl: Reverted edits by Yasemin (talk) to last revision by Zarl

User talk:Anyareal

2012-07-06T10:13:44Z

Zarl: deleted some useless information

User talk:WalkerDsa

2012-06-30T00:16:58Z

Zarl: come on...

User talk:PaulineOce

2012-06-24T14:14:53Z

Zarl: less spam here...

User talk:Dglkkhnrdi

2012-06-23T23:03:03Z

Zarl: spam removed

User talk:BobetteWatson1972

2012-06-22T08:03:29Z

Zarl: removed spam

User talk:Adultdating 587

2012-06-21T06:34:34Z

Zarl: removed spam

User talk:FixToolbox

2012-06-10T09:04:29Z

Zarl: spam deleted

User talk:TIaYRVZ7Y

2012-05-31T12:14:13Z

Zarl: No thanks.

User talk:RepairToolbox

2012-05-31T07:14:47Z

Zarl: Yet another spammer's hard work deleted...

User talk:Calanloo

2012-05-29T16:33:37Z

Zarl: Spam deleted

User talk:Dlendsi

2012-05-27T07:32:10Z

Zarl: deleted spam

User talk:BLT111

2012-05-25T11:32:45Z

Zarl: Spam deleted

User talk:Janeyoung123

2012-05-23T12:03:29Z

Zarl: deleted redirect

User talk:Travel vietnam

2012-05-23T12:02:11Z

Zarl: Spam deleted

User talk:PressRTbox

2012-05-23T08:19:24Z

Zarl: Spam...

Talk:SiteMap

2012-04-19T08:41:26Z

Zarl: holy Spam...

Talk:Main Page

2012-04-19T08:37:40Z

Zarl: Reverted edits by Yiyuan (Talk) to last version by Erik Krause

Talk:Camera Kits

2012-04-19T07:09:33Z

Zarl: strange article, but maybe useful for a list of fisheyes

== Title (and content) ==
I'm not sure about the purpose of this article but anyway: does it make sense to rename the title to something like ''camera / lens combinations'' so it can be used to e.g. shed some light on special fisheye lenses? Or just move the content to [[Hardware]] (where there's already a [[Hardware#Cameras|link]] that leads to this strange page...). --[[User:Zarl|Carl]] 07:09, 19 April 2012 (UTC)

Hugin Assistant tab

2012-04-19T06:39:22Z

Zarl: /* Settings */ some more details... :-)

The [[hugin]] assistant automates nearly everything needed to create
a panorama, just follow these three steps:

= 1. Load images... =

Click on the '''Load images...''' button to select the photos you want to use in your panorama.

This tries to identify the [[field of view]] of your photos by looking at (EXIF) information stored by
the camera itself. If this fails you need to enter the '''field of view''' manually, or let [[hugin]] calculate it from the [[Focal Length]] and [[crop factor|Focal length multiplier]].

Also select a [[Hugin_Camera_and_Lens_tab#Lens|matching ''Lens type'']] from the drop-down list. If you are unsure try the default '''Normal (rectilinear)'''.

= 2. Align... =

Click on '''Align...''' will use an automatic tool (the one set as ''Default'' in the [[Hugin Preferences#Control_Point_Detectors|Control Point Detectors tab]] of the Preferences) to match images, then use the internal [[hugin]] optimiser to align them, correct exposure and white balance.

The result will appear in the [[hugin Preview window]]. If this looks good proceed with the third step (the '''Create panorama...''' button), otherwise you will need to make some changes to the project in the other tabs of the [[hugin Main window]].

= 3. Create panorama... =

Finally, use '''Create panorama...''' to stitch the panorama to an image file with standard
quality settings.

= Settings =
A tab in the ''Preferences'' dialog (available from the menu) allows you to customise some [[Hugin Preferences#Assistant|settings]] of the assistant.

__NOTOC__
[[Category:Software:Hugin]]

Hugin Assistant tab

2012-04-19T06:35:38Z

Zarl: link to Preferences, __NOTOC__ added

The [[hugin]] assistant automates nearly everything needed to create
a panorama, just follow these three steps:

= 1. Load images... =

Click on the '''Load images...''' button to select the photos you want to use in your panorama.

This tries to identify the [[field of view]] of your photos by looking at (EXIF) information stored by
the camera itself. If this fails you need to enter the '''field of view''' manually, or let [[hugin]] calculate it from the [[Focal Length]] and [[crop factor|Focal length multiplier]].

Also select a [[Hugin_Camera_and_Lens_tab#Lens|matching ''Lens type'']] from the drop-down list. If you are unsure try the default '''Normal (rectilinear)'''.

= 2. Align... =

Click on '''Align...''' will use an automatic tool (the one set as ''Default'' in the [[Hugin Preferences#Control_Point_Detectors|Control Point Detectors tab]] of the Preferences) to match images, then use the internal [[hugin]] optimiser to align them, correct exposure and white balance.

The result will appear in the [[hugin Preview window]]. If this looks good proceed with the third step (the '''Create panorama...''' button), otherwise you will need to make some changes to the project in the other tabs of the [[hugin Main window]].

= 3. Create panorama... =

Finally, use '''Create panorama...''' to stitch the panorama to an image file with standard
quality settings.

= Settings =
Some [[Hugin Preferences#Assistant|settings]] allow you to customise the assistant.

__NOTOC__
[[Category:Software:Hugin]]

Hugin Main window

2012-04-19T06:34:14Z

Zarl: __NOTOC__ deleted

= Tabs =

Although there are many other uses, [[hugin]] is primarily a
tool for assembling multiple photos and creating a 'seamless' panorama.

This process is completely automatic if you use the [[hugin Assistant tab]],
but '''hugin''' also allows full manual control of every stage.
So '''hugin''' divides up the various stages and presents them as ''tabs''
in the main window. These ''tabs'' are roughly in the order of panorama
creation from left to right, though in practice fine-tuning a project can
involve some jumping around between tabs.

This is a quick overview of this ''tab'' system, it isn't a step by step tutorial,
you can find these on the [http://hugin.sourceforge.net/tutorials/ hugin website].

== Assistant ==

The [[hugin Assistant tab]] is the fully automatic part of [[hugin]], here you can
load images, align them and ''stitch'' them into a panorama without having to use
any of the other tabs.

Alternatively, you can use this '''Assistant''' as the first step in creating a
project that will involve the use some or all of the other tabs:

== Images ==

In the [[hugin Images tab]] you can add or remove photos to and from your project.
The table in the middle also shows the positions in the final scene for each the
images, these positions are actually angles for [[roll]], [[pitch]] and [[yaw]].

Although you could enter these positions manually here, you are more likely to
create [[control points]] in the [[hugin Control Points tab]] and then use the
''optimiser'' in the [[hugin Optimizer tab]] to position your images for you.

== Camera and Lens ==

Photos have properties that need to be known in order to assemble them
seamlessly, notably geometric properties such as [[field of view]] or
[[barrel distortion]], plus photometric properties such as [[vignetting]]
or '''exposure'''.

Again, although you could enter parameters for these properties here in the
[[hugin Camera and Lens tab]]; '''hugin''' can estimate the '''field of view'''
from data stored in the photo by the camera, it can also use the ''optimisers''
in the [[hugin Optimizer tab]] to calculate the geometric distortion, and in the
[[hugin Exposure tab]] to calculate photometric corrections.

== Crop ==

Often photos contain parts that you don't want to be used. Typically
[[fisheye Projection]] images have a circular area in the middle with
a useless black area outside. Scanned images have edges that need to
be ''cropped'' away.

The [[hugin Crop tab]] allows you to apply simple masks to ignore these
areas from your photos.

== Mask ==

Often photos contain parts which should not be used in the final panorama (e.g. moving objects),
alternatively you may need to specifically include a distinctive feature (e.g. persons) in the final panorama.

The [[Hugin Mask tab]] allows you to mask these areas for inclusion or exclusion from the stitched panorama.

== Control Points ==

[[hugin]] stitches panoramas by matching identical features in different
photos, these features are defined by ''pairs'' of [[control points]].
The [[hugin Control Points tab]] shows two photos at a time and allows
you to manually create and edit any pair of '''control points'''.

In addition to the '''Control Points tab''' the [[hugin Control Points table]]
is used to manage pairs of '''control points'''.

'''control points''' can be created automatically in the '''Align''' section
of the [[hugin Assistant tab]] or with the '''Feature Matching''' section
of the [[hugin Images tab]].

== Optimizer ==

[[hugin]] uses a photo alignment scheme where it adjusts image orientation
and lens settings of source photos until the [[control points]] line-up,
this process is called ''optimisation'' and the '''hugin Optimizer tab'''
is where it is controlled. You actually ''create'' individual
'''control points''' in the [[hugin Control Points tab]], and ''manage''
them in the [[hugin Images tab]] and [[hugin Control Points table]].

== Exposure ==

Photos in a project can have differences in exposure or white balance, either because of
natural changes in lighting or from settings in the camera itself.

The [[hugin Exposure tab]] corrects these ''photometric'' variations by looking
at pairs of overlapping photos and modelling a system of [[camera response curve]],
'''exposure''', '''white balance''' and [[vignetting]] that fits the photos.

So for this to work, the photos in the project have to be already aligned. Align
photos by managing control points in the [[hugin Control Points tab]] and optimising
geometric image parameters in the [[hugin Optimizer tab]].

== Stitcher ==

The end result of a [[hugin]] project is an image file containing a panorama. The
final [[hugin Stitcher tab]] is where size and quality are set and where this output
file is created.

= Menus =

== File ==

* '''New''', discard the current project and start a new empty project.
* '''Open''' an existing [[hugin]], [[PTGUI]], [[PTAssembler]], [[autopano]] or [[autopano-sift]] project file.
* '''Save''' the current project as a hugin ''pto'' file.
* '''Save as''' a ''pto'' file with a different name.
* '''Write PTStitcher script''', saves a simplified project file suitable for batch stitching with [[PTStitcher]], [[nona]] or [[PTmender]]. Note that [[nona]] can stitch a [[hugin]] project file directly, so this step is unnecessary when using '''nona'''.
* '''Most recently used projects''', shows a list of recent Hugin projects.
* '''Send to batch''', adds the current project to the [[Hugin Batch Processor]] stitching queue.
* '''Run Batch Processor''', launches the [[Hugin Batch Processor]] GUI queue manager, note that the queue won't be processed unless this queue manager is running.
* '''Merge project''', can be used to merge another project with the current project: new photos will be added to the list of images, for duplicate photos only the control points are merged.
* '''Apply Template''', assigns parameters from an existing ''pto'' project to the current set of photos. Only position and [[Lens correction model|lens parameters]] are transferred, [[control points]] are ignored.
* '''Preferences''' opens the [[hugin Preferences]] window.
* '''Quit''' hugin.

== Edit ==

* '''Undo''', undoes the most recent change to the current project.
* '''Redo''', redoes an undo.

* '''Fine-tune all Points''' does the same as '''Fine-tune''' in the [[hugin Control Points tab]] except that all [[control points]] in the project are adjusted. Fine tune settings are set in the [[hugin Preferences]].
* '''Remove control points in masks''' removes all control points in regions which are masked on the [[Hugin Mask tab]].

* '''Optimize''', re-optimises the current project. This has exactly the same effect as clicking '''Optimize Now!''' in the [[hugin Optimizer tab]].
* '''Add Image''' to the current project.

== View ==

* '''Full Screen''' shows this '''Hugin Main window''' using as much screen space as possible without any window decorations. Note that the [[Hugin Fast Preview window]] can also be set as full screen.
* '''Control point table''' shows the [[Hugin Control Points table]].
* '''Preview window''' shows the [[Hugin Preview window]].
* '''Fast Preview window''' shows the [[Hugin Fast Preview window]].
* '''Assistant''' shows the [[Hugin Assistant tab]].
* '''Images''' shows the [[Hugin Images tab]].
* '''Camera and Lens''' shows the [[Hugin Camera and Lens tab]].
* '''Crop''' shows the [[Hugin Crop tab]].
* '''Mask''' shows the [[Hugin Mask tab]].
* '''Control Points''' shows the [[Hugin Control Points tab]].
* '''Optimizer''' shows the [[Hugin Optimizer tab]].
* '''Exposure''' shows the [[Hugin Exposure tab]].
* '''Stitcher''' shows the [[Hugin Stitcher tab]].

== Help ==

* '''Help''' opens the [[hugin]] manual.
* '''Tip of the day'''
* '''Keyboard Shortcuts'''
* '''FAQ''', hugin [[hugin FAQ|Frequently asked questions]].
* '''About''' shows the [[Hugin About window]].
* '''Donate''' opens the Hugin donation page, there is no obligation to donate. Any donations are used for travel and promotion costs related to Hugin development.

= Buttons =

Above the row of tabs are a series of buttons for common commands:

== [[Image:Hugin_filenew.png]] New project ==

Discards the current project and starts a new empty project.

== [[Image:Hugin_fileopen.png]] Open project ==

Opens an existing [[hugin]], [[PTGUI]], [[PTAssembler]], [[autopano]] or [[autopano-sift]] project file.

== [[Image:Hugin_filesave.png]] Save project ==

Saves the current project as a hugin .pto file.

== [[Image:Hugin_filesaveas.png]] Save project as ==

Saves as a .pto file with a different name.

== [[Image:Hugin_undo.png]] Undo ==

Undoes the most recent change to the current project.

== [[Image:Hugin_redo.png]] Redo ==

Redoes an undo.

== [[Image:Hugin_edit_add.png]] Add image ==

Adds an image or photo to the current project.

== [[Image:Hugin_optimize.png]] Re-optimize ==

Re-optimises the current project. This has exactly the same effect as clicking '''Optimize Now!''' in the [[hugin Optimizer tab]].

== [[Image:Gl_preview.png]] Fast Preview panorama ==

Shows the [[hugin Fast Preview window]].

== [[Image:Hugin_preview.png]] Preview panorama ==

Shows the [[hugin Preview window]].

== [[Image:Hugin_list.png]] Show control points ==

Shows the [[hugin Control Points table]].

== [[Image:Hugin_info.png]] About Hugin ==

Shows the hugin '''About''' pop-up window, this displays the current version and a list of contributors.

[[Category:Software:Hugin]]

Hugin Assistant tab

2012-04-19T06:27:03Z

Zarl: /* 2. Align... */ rephrased

Hugin Assistant tab

2012-04-19T06:23:03Z

Zarl: /* 2. Align... */ preferences mentioned instead of autopano-sift

The [[hugin]] assistant automates nearly everything needed to create
a panorama, just follow these three steps:

= 1. Load images... =

Click on the '''Load images...''' button to select the photos you want to use in your panorama.

This tries to identify the [[field of view]] of your photos by looking at (EXIF) information stored by
the camera itself. If this fails you need to enter the '''field of view''' manually, or let [[hugin]] calculate it from the [[Focal Length]] and [[crop factor|Focal length multiplier]].

Also select a [[Hugin_Camera_and_Lens_tab#Lens|matching ''Lens type'']] from the drop-down list. If you are unsure try the default '''Normal (rectilinear)'''.

= 2. Align... =

Click on '''Align...''' will use an automatic tool (the one set as ''Default'' in the [[Hugin Preferences#Control_Point_Detectors|Control Point Detectors tab]] of the Preferences) to match images, then use the internal [[hugin]] optimiser to align them, correct exposure and white balance.

The result will appear in the [[hugin Preview window]], if this looks good then click the next '''Create panorama...''' button. Otherwise you will need to make some changes to the project in the other tabs of the [[hugin Main window]].

= 3. Create panorama... =

Finally, use '''Create panorama...''' to stitch the panorama to an image file with standard
quality settings.

[[Category:Software:Hugin]]

Hugin Optimizer tab

2012-04-19T06:16:34Z

Zarl: rephrased

[[hugin]] uses a photo alignment scheme where it adjusts image orientation and lens settings of source photos
until the [[control points]] line-up. This process is called ''optimisation'' and the '''hugin Optimizer tab''' is where it is controlled in detail. You actually ''create'' individual '''control points''' in the [[hugin Control Points tab]], and ''manage'' them in the [[hugin Images tab]] and [[hugin Control Points table]].

So to align two or more photos we need to connect them with some control points. A general rule is that optimising more parameters requires more control points.

== Quick Optimizer ==

Use the '''Optimize''' combo box to pick one of several pre-set optimisation schemes, then click the '''Optimize now!''' button to calculate the best available fit. For a spherical panorama, which is where each image is taken from the same position, you should not optimise translation. For a [[linear panorama]], where you take pictures from different locations of the same flat surface, you must optimise translation.

One valid technique is to try each optimisation scheme in turn, starting at the top, and skipping the ones with translation if you are making a spherical panorama, until you are satisfied with the results.

The '''Optimisation result''' tells you how good the alignment is, large control point error distances indicate one of several things:

* Some '''control points''' are in the wrong place, look at the list in the [[hugin Control Points table]] and identify points with large distances and check they are set properly.
* If points are set correctly, there may be [[parallax]] errors caused by camera movement between shots. If so it may be necessary to decide which objects in the scene are important to have aligned and delete unrelated control points in the [[hugin Control Points tab]].
* Otherwise you may not be optimising enough parameters. For example, the [[EXIF]] data retrieved from a [[JPEG]] file may not give a very accurate starting [[Field of View]], in this case you should optimise '''view (v)'''.

'''Use only control points between images selected in preview window.''' allows you to work on just a few
of the images in the current project rather than all of them. Use the buttons along the top of the
[[Hugin Preview window]] to enable and disable source photos. When optimising with the
[[Hugin Optimizer tab]], all the hidden images will be ignored.

The following pre-set optimisation schemes are provided:

=== Positions (incremental, starting from anchor) ===

This is the simplest setting, and is probably sufficient for a lot of purposes. Only the relative orientation of images are optimised, lens parameters are left untouched, this works best if either of the following is true:

* The lens has minimal [[barrel distortion]] and the photo [[EXIF]] information supplies an accurate [[Field of View]].
or
* [[Lens calibration]] has already been performed, saved to a file and loaded into the current project via the [[hugin Camera and Lens tab]].

Note that to align any pair of photos, there should be at least two pairs of [[control points]] connecting them.

=== Positions (y,p,r) ===

This is exactly the same as the ''incremental'' setting above except that the parameters are optimised at once, this may confuse the optimiser if the images are not already roughly in the right place. Don't use this setting.

=== Positions and View (y,p,r,v) ===

This is the same as optimising '''Positions''' except that the lens [[Field of View]] is optimised too - Use this if you don't trust the Field of View calculated from the photo's [[EXIF]] data.

Note that for this too work you need at least three well-spaced pairs of [[control points]] between any pair of photos. With a 360 degree panorama it is usually beneficial to optimise the '''Field of View''', even if you have already calibrated this beforehand.

=== Positions and Barrel Distortion (y,p,r,b) ===

This is the same as optimising '''Positions''' except that an attempt is made to discover the lens [[barrel distortion]] at the same time. Only the '''b''' parameter of the full [[lens correction model]] is varied by this optimisation scheme, as this is a reasonable approximation of the distortion of a typical lens. You should trust the field of view if you use this.

Again you need at least three well-placed pairs of [[control points]] between any pair of photos.

=== Positions, View and Barrel (y,p,r,v,b) ===

As the name suggests this optimises positions, [[Field of View]] and [[barrel distortion]] all at once.

=== Everything without translation ===

This optimises image orientation and all geometric parameters in the full [[lens correction model]]. It includes more lens distortion parameters. The x shift and y shift (d and e) parameters account for the centre of the projection not being in the centre of the image. This is quite common, and gets very bad if an image is the cropped corner of another image.

You will need many control points, the more the better, and preferably a full spherical panorama (360 by 180 degrees) to get the best correction. You should also use a calibrated [[Heads|panoramic head]]. If the control points are bad (either there are not enough or some are in the wrong place), or your images were not taken around the [[no-parallax point]], this could produce bizarre results.

However, if you do this well, you will accurately perform [[lens calibration]]. You can save and reuse this lens information on the [[Hugin Camera and Lens tab]].

=== Positions and Translations (y,p,r,x,y,z) ===

This will optimise image orientation and the translation you get when moving the camera for a linear panorama. This is great for stitching images of the same flat surface taken from different places, for example when you couldn't fit a painting or the front of a building into one picture. Again it isn't ideal if the lens information such as the field of view is wrong.

=== Positions, Translation and View (y,p,r,x,y,z,v) ===

This is similar to '''Positions and Translations''', except you can use it when you don't trust the [[Field of View]] from the [[EXIF]] data.

=== Positions, Translation and Barrel (y,p,r,x,y,z,b) ===

This is the same as optimising '''Positions''' and '''Translation''' except that an attempt is made to discover the lens [[barrel distortion]] at the same time. Only the '''b''' parameter of the full [[lens correction model]] is varied by this optimisation scheme, as this is a reasonable approximation of the distortion of a typical lens. You should trust the field of view if you use this.

=== Positions, Translation, View and Barrel (y,p,r,x,y,z,b,b) ===

This is useful when you are optimising a linear panorama, don't trust the field of view, and want to correct barrel distortion.

=== The Custom parameters below ===

The pre-set optimisation options are useful for most situations, but often it is necessary to switch to '''Custom parameters'''.

For example, when shooting hand-held panoramas, some of the position variation between shots can be resolved by using different '''d''' and '''e''' '''Image Center Shift''' parameters for each shot. Select '''The Custom parameters below''' and pick the '''d''' and '''e''' parameters for optimisation. Note that by default, lens settings are shared for all photos in the project, go to the [[hugin Camera and Lens tab]] and ''uncheck'' the '''link''' box for any you want to have different values in each photo.

Similarly, the translation parameters could be used to correct a wonky shot. However, they were meant for linear panoramas which expand to infinite distance at 180 degrees field of view, so you must make sure any images with non-zero translation (X, Y, or Z parameters) are in the middle of the panorama (y and p should all be around zero, and the field of view shouldn't be large enough to make them expand more than 180 degrees). This can be used to patch in the floor after you have removed the tripod that was obscuring it. You can take a shot of the floor where the tripod was at an angle (therefore you can avoid casting a shadow on the image in most cases). You can then optimise X,Y,Z on only this image. However, the floor must be flat for this to work, and this shot must be in the middle of the panorama. You can make down the middle by rotating the panorama on either of the previews.

==== Image Orientation ====

The '''Image Orientation''' section shows the photo number and [[roll]], [[pitch]] and [[yaw]] rotation/orientation values for all input photos (in parenthesis), and the X, Y, and Z translation parameters. The ''check'' mark indicates parameters that will be optimised. The translation parameters should all be 0 on a spherical panorama.

==== Lens Parameters ====

The '''Lens Parameters''' section shows the lens number and the [[lens correction model]] parameters (in parenthesis) for each of the distinct lenses in the project. Only parameters that are '''linked''' in the [[hugin Camera and Lens tab]] are shown in parenthesis.

Note that normally all the photos in a project have the same lens, so there is usually only one row here.

==== edit script before optimizing ====

[[hugin]] actually creates a [[PTOptimizer]] script file which it passes to the panorama tools library for optimisation, select '''edit script before optimizing''' and you can tweak this file for each optimisation run.

This is something you would only do in obscure cases such as:

* Linking the positions of input photos. For example photos in a multi-row panorama taken with tripod can all be assumed to have the same [[roll]], similarly photos in each row can be assumed to have the same [[pitch]] - This will help when there are few details available for setting [[control points]].
* Optimising the '''g''' or '''t''' shear parameters of the [[lens correction model]] for scanned images is only possible by editing the script file.

__NOTOC__
[[Category:Software:Hugin]]

Hugin Assistant tab

2012-04-19T05:59:37Z

Zarl: /* 1. Load images... */ rephrase

The [[hugin]] assistant automates nearly everything needed to create
a panorama, just follow these three steps:

= 1. Load images... =

Click on the '''Load images...''' button to select the photos you want to use in your panorama.

This tries to identify the [[field of view]] of your photos by looking at (EXIF) information stored by
the camera itself. If this fails you need to enter the '''field of view''' manually, or let [[hugin]] calculate it from the [[Focal Length]] and [[crop factor|Focal length multiplier]].

Also select a [[Hugin_Camera_and_Lens_tab#Lens|matching ''Lens type'']] from the drop-down list. If you are unsure try the default '''Normal (rectilinear)'''.

= 2. Align... =

Click on '''Align...''' to use an automatic tool such as [[autopano-sift]] to match images,
then use the internal [[hugin]] optimiser to align them, correct exposure and white
balance. The result will appear in the [[hugin Preview window]], if this looks good then
click the next '''Create panorama...''' button. Otherwise you will need to make some
changes to the project in the tabs of the [[hugin Main window]].

= 3. Create panorama... =

Finally, use '''Create panorama...''' to stitch the panorama to an image file with standard
quality settings.

[[Category:Software:Hugin]]

Hugin Camera and Lens tab

2012-04-19T05:46:01Z

Zarl: /* Lens */ more examples

{| cellspacing="0" cellpadding="0" style="clear: right; margin-bottom: .5em; float: right; padding: .5em 0 .8em 1.4em; background: none; width:auto"
| __TOC__
|}
The '''Camera and Lens''' tab looks a lot like the [[hugin Images tab]], except that the lens settings can be edited here.
As in the Images Tab, multi-selection can be used to change the parameters for multiple images.

[[Panorama Tools]] and [[hugin]] allow the usage of images shot with different lenses and settings inside the same project.
Each image is associated with a lens number.
All images that share the same lens number use the same lens type, and may be forced to share the same lens parameters.

The '''Load lens...''' and '''Save lens...''' buttons allow you to keep calibrated lens profiles. Once a set of lens parameters has been obtained through [[lens calibration]] it shouldn't vary much for future projects. The advantage of this is that if only positions are being optimised in the [[hugin Optimizer tab]], then as few as two or three [[control points]] are needed per image pair.

'''Load EXIF''' examines the selected image file and tries to determine the [[Field of View]]
of the photo by reading embedded [[EXIF]] data. The same function is performed when initially adding photos so you only need
this button to reset the '''Field of View''' if it has since changed.

By default, every photo in a project is assigned to ''lens number'' '''0'''. If you are including
pictures taken with a different camera, a different lens or at different zoom settings; then
you need to assign a ''new lens'' for these pictures by clicking the '''New Lens''' button.
Assign additional photos to this ''lens number'' with the '''Change Lens...''' button.

== Geometric ==

The Panorama Tools [[lens correction model]] has enough parameters to model most photographic images, these parameters can be set manually here in the '''hugin Camera and Lens tab''' or calculated automatically in the [[hugin Optimizer tab]].

Note that any or all of these parameters can be changed back to good defaults in the [[Hugin Reset Values window]] reached by clicking the '''Reset...''' button.

=== Lens ===

The most important parameters are the '''[[Field of View|Horizontal field of view]]''' and the '''Lens type'''. Hugin supports the following projections in input images:

* '''[[Rectilinear Projection|Normal (rectilinear)]]''' - The projection used by most ''standard'' cameras. It keeps straight lines straight. The maximum horizontal field of view is 180 degrees (for an image of infinite size, that is). Also [[Cubic Projection|cubes]] (e.g. rendered in a special application) use this type.
* '''[[Cylindrical Projection|Panoramic (cylindrical)]]''' - This type is often simply called ''cylindrical'' projection. Usually used by panoramic cameras, such as the Horizon, Roundshot and Spheron cameras; sometimes output generated with early stitching software such as QTVRAS that only copes with single row panoramas.
* '''[[Fisheye Projection|Circular fisheye]]''' - Used by many fisheye lenses. If the image is circular or the corners of the image are black, use this type of fisheye lens. A circular crop in the [[Hugin Crop tab]] can be used for cutting away the edge borders.
* '''Full frame fisheye''' - Exactly the same projection as the above '''circular fisheye''', but the crop option will crop to a rectangle instead of a circle. This should be used for full frame fisheye images. A typical example for this type is a 15 mm fisheye on a full frame DSLR.
* '''[[Equirectangular Projection|Equirectangular]]''' - A full spherical projection. These are not from real world lenses but generally created as the result of the [[Hugin Stitcher tab|stitching]] process; useful to reload a finished panorama to extract further images.
* '''[[Projections#Orthographic_projection|Orthographic]]''' - A projection that is e.g. used in cartography. A rare example for a fisheye lens that uses this projection is Nikon's early ''10mm f5.6 OP''.
* '''[[Stereographic Projection|Stereographic]]''' - Special fisheye lenses such as the Samyang 8 mm use this projection.
* '''[[Projections#Equisolid_projection|Equisolid]]''' - Try this projection if your image is e.g. the reflection of a mirrorball or from the visor of an astronaut's helmet.
* '''Fisheye Thoby''' is modeling the Nikkor 10.5 mm fisheye lens.

After the lens type has been specified, an estimate for the horizontal [[field of view]] (HFOV) is required. The HFOV specifies the horizontal opening angle of the image in degrees. Since most photographers are more familiar with [[Focal Length]] as a measure for the HFOV, it can be entered into hugin, and hugin will compute the HFOV from it. For this calculation the actual focal length and the [[crop factor]] of the camera are required. If the 35mm film equivalent focal length is known, a crop factor of 1 should be used.

With [[JPEG]] images, hugin can usually automatically calculate the HFOV based on the [[EXIF]] information.

=== Radial Distortion, Image Center Shift and Image Shearing ===

Usually lenses do not project images exactly according to the selected projection type, but suffer from distortions.
In many cases the distortions are acceptable for single image shots, but they need to be corrected when stitching a panorama.
The '''a''', '''b''' and '''c''' parameters are used to remove that distortion.
They are applied radially from the image center, which can be moved by changing the '''d''' and '''e''' parameters.
These '''a''', '''b''', '''c''', '''d''' and '''e''' parameters are the basis of the panotools [[lens correction model]].

Scanned images might also suffer from image [[shearing]]. This can be corrected using the '''g''' and '''t''' parameters.

The distortion parameters usually vary with the focal length, and to a lesser degree with the focus.
The '''link''' checkbox indicates whether the parameter is linked or not.
A linked parameter is forced to the same value for all images with the same lens number.
This is the default for the HFOV and distortion parameters.
If a parameter is not linked each images is allowed to have individual values for the respective parameter.
This is useful if a different zoom or focus setting has been used for some images.
If scanned images are used, they are usually not perfectly centered, and each image should have individual '''d''' and '''e''' parameters.

== Photometric ==

[[hugin]] models the '''photometric''' parameters of a lens/camera combination in a similar way to the [[lens correction model]] for '''Geometric''' parameters. These parameters can be set manually here in the hugin '''Camera and Lens tab''' or calculated automatically in the [[hugin Exposure tab]].

Note that any or all of these parameters can be changed back to good defaults in the [[Hugin Reset Values window]] reached by clicking the '''Reset...''' button.

=== Exposure and Color ===

'''Exposure (EV)''', EV stands for ''Exposure Value'', setting it to ''0'' (zero) will
result in [[hugin]] applying no exposure change to the photo.

EV is a standard photographic scale, each increase or decrease by one unit will change the
exposure by the equivalent of one ''f-stop'' (ie. halving or doubling the exposure).

Very often, different photos in the same project, even those with the same ''lens number'',
will require a different '''Exposure'''. This could be because the photos were taken
with a different shutter-speed or simply because the light changed between shots, if so
uncheck '''Link''' here before optimising exposure in the [[hugin Exposure tab]].

The '''Red multiplier''' and '''Blue multiplier''' settings are used to account for changes
in '''white balance''' (also known as ''colour balance'' or ''colour temperature'') between
photos. Setting them both to ''1'' will result in no ''white balance'' change (the numbers
are relative to the green channel which stays unaltered).

As with exposure, different photos in the same project are quite likely to require different
''white balance''. Typically this will be caused by variations in lighting conditions between
shots - For example a cloudy scene will contain considerably less ''red'' light than the same scene
under direct sunlight, so uncheck '''Link''' here before optimising '''White balance'''
in the [[hugin Exposure tab]].

=== Vignetting ===

[[Vignetting]] is dependent mainly on your lens and the ''aperture''. Usually the
centre of the image is brighter with a falloff towards the edges. The three
numbers here represent a polynomial curve used by [[hugin]] to correct vignetting.

You are not expected to guess these values, they are generally loaded with a lens
profile or calculated from two or more overlapping photos in the [[hugin Exposure tab]].

Set the values to ''0,0,0'' for no vignetting correction.

Usually all photos taken with the same ''lens'' will have the same vignetting, keep
'''Link''' checked to ensure '''hugin''' applies the same vignetting correction to all
photos with the selected lens number.

=== Vignetting Center Shift ===

The centre of [[vignetting]] is rarely the exact centre of the photo. The two numbers
here indicate the position of the vignetting centre. The scale is in pixels, with
''0,0'' indicating the centre of the photo. The values are independent of the '''d'''
& '''e''' parameters which specify the origin for projection and geometric distortion.

As with other lens parameters, this '''Vignetting Center Shift''' can be optimised in
the [[hugin Exposure tab]]. Keep '''Link''' checked to ensure [[hugin]] applies the same
vignetting centre to all photos with the selected lens number.

=== Camera Response ===

The [[camera response curve]] is used both for mapping the images to a linear
colourspace when creating [[HDR]] output, and for normalising the colourspace
for internal vignetting, brightness and colour corrections when creating
'normal' '''LDR''' output.

[[hugin]] uses the [http://www1.cs.columbia.edu/CAVE/projects/rad_cal/rad_cal.php EMoR response model]
from the Computer Vision Lab at Columbia University which simplifies the full
response curve to these five empirical coefficient numbers. You are
not expected to guess these values, they are generally loaded with a lens
profile or calculated from two or more overlapping photos in the [[hugin Exposure tab]].

Set the five numbers to ''0,0,0,0,0'' to use a generic response curve or change the '''Type'''
to '''Linear''' to indicate that your input photos have a ''scene-referred'' or [[HDR]]
response.

Keep '''Link''' checked to ensure '''hugin''' applies the same
response curve to all photos with the selected lens number.

__NOTOC__
[[Category:Software:Hugin]]

Hugin Camera and Lens tab

2012-04-18T15:35:16Z

Zarl: /* Lens */ Examples added

{| cellspacing="0" cellpadding="0" style="clear: right; margin-bottom: .5em; float: right; padding: .5em 0 .8em 1.4em; background: none; width:auto"
| __TOC__
|}
The '''Camera and Lens''' tab looks a lot like the [[hugin Images tab]], except that the lens settings can be edited here.
As in the Images Tab, multi-selection can be used to change the parameters for multiple images.

[[Panorama Tools]] and [[hugin]] allow the usage of images shot with different lenses and settings inside the same project.
Each image is associated with a lens number.
All images that share the same lens number use the same lens type, and may be forced to share the same lens parameters.

The '''Load lens...''' and '''Save lens...''' buttons allow you to keep calibrated lens profiles. Once a set of lens parameters has been obtained through [[lens calibration]] it shouldn't vary much for future projects. The advantage of this is that if only positions are being optimised in the [[hugin Optimizer tab]], then as few as two or three [[control points]] are needed per image pair.

'''Load EXIF''' examines the selected image file and tries to determine the [[Field of View]]
of the photo by reading embedded [[EXIF]] data. The same function is performed when initially adding photos so you only need
this button to reset the '''Field of View''' if it has since changed.

By default, every photo in a project is assigned to ''lens number'' '''0'''. If you are including
pictures taken with a different camera, a different lens or at different zoom settings; then
you need to assign a ''new lens'' for these pictures by clicking the '''New Lens''' button.
Assign additional photos to this ''lens number'' with the '''Change Lens...''' button.

== Geometric ==

The Panorama Tools [[lens correction model]] has enough parameters to model most photographic images, these parameters can be set manually here in the '''hugin Camera and Lens tab''' or calculated automatically in the [[hugin Optimizer tab]].

Note that any or all of these parameters can be changed back to good defaults in the [[Hugin Reset Values window]] reached by clicking the '''Reset...''' button.

=== Lens ===

The most important parameters are the '''[[Field of View|Horizontal field of view]]''' and the '''Lens type'''. Hugin supports the following projections in input images:

* '''[[Rectilinear Projection|Normal (rectilinear)]]''' - The projection used by most cameras. It keeps straight lines straight. The maximum horizontal field of view is 180 degrees (for an image of infinite size, that is).
* '''[[Cylindrical Projection|Panoramic (cylindrical)]]''' - Often used by panoramic cameras, such as the Horizon, Roundshot and Spheron cameras. This projection is also called simply ''cylindrical'' projection.
* '''[[Fisheye Projection|Circular fisheye]]''' - Used by fisheye lenses. If the image is circular or the corners of the image are black, use this type of fisheye lens. A circular crop in the [[Hugin Crop tab]] can be used for cutting away the edge borders.
* '''Full frame fisheye''' - Exactly the same projection as '''circular fisheye''', but the crop option will crop to a rectangle instead of a circle. This should be used for full frame fisheye images.
* '''[[Equirectangular Projection|Equirectangular]]''' - A full spherical projection. These are generally created as the result of the stitching process, but it can be useful to reload a finished panorama to extract further images.
* '''Orthographic''' - A projection that is e.g. used in cartography. A rare example for a fisheye lens that uses this projection is Nikon's early ''10mm f5.6 OP''.
* '''Stereographic''' - Special fisheye lenses such as the Samyang 8 mm use this projection.
* '''Equisolid'''
* '''Fisheye Thoby''' is modeling the Nikkor 10.5 mm fisheye lens

After the lens type has been specified, an estimate for the horizontal [[field of view]] (HFOV) is required. The HFOV specifies the horizontal opening angle of the image in degrees. Since most photographers are more familiar with [[Focal Length]] as a measure for the HFOV, it can be entered into hugin, and hugin will compute the HFOV from it. For this calculation the actual focal length and the [[crop factor]] of the camera are required. If the 35mm film equivalent focal length is known, a crop factor of 1 should be used.

With [[JPEG]] images, hugin can usually automatically calculate the HFOV based on the [[EXIF]] information.

=== Radial Distortion, Image Center Shift and Image Shearing ===

Usually lenses do not project images exactly according to the selected projection type, but suffer from distortions.
In many cases the distortions are acceptable for single image shots, but they need to be corrected when stitching a panorama.
The '''a''', '''b''' and '''c''' parameters are used to remove that distortion.
They are applied radially from the image center, which can be moved by changing the '''d''' and '''e''' parameters.
These '''a''', '''b''', '''c''', '''d''' and '''e''' parameters are the basis of the panotools [[lens correction model]].

Scanned images might also suffer from image [[shearing]]. This can be corrected using the '''g''' and '''t''' parameters.

The distortion parameters usually vary with the focal length, and to a lesser degree with the focus.
The '''link''' checkbox indicates whether the parameter is linked or not.
A linked parameter is forced to the same value for all images with the same lens number.
This is the default for the HFOV and distortion parameters.
If a parameter is not linked each images is allowed to have individual values for the respective parameter.
This is useful if a different zoom or focus setting has been used for some images.
If scanned images are used, they are usually not perfectly centered, and each image should have individual '''d''' and '''e''' parameters.

== Photometric ==

[[hugin]] models the '''photometric''' parameters of a lens/camera combination in a similar way to the [[lens correction model]] for '''Geometric''' parameters. These parameters can be set manually here in the hugin '''Camera and Lens tab''' or calculated automatically in the [[hugin Exposure tab]].

Note that any or all of these parameters can be changed back to good defaults in the [[Hugin Reset Values window]] reached by clicking the '''Reset...''' button.

=== Exposure and Color ===

'''Exposure (EV)''', EV stands for ''Exposure Value'', setting it to ''0'' (zero) will
result in [[hugin]] applying no exposure change to the photo.

EV is a standard photographic scale, each increase or decrease by one unit will change the
exposure by the equivalent of one ''f-stop'' (ie. halving or doubling the exposure).

Very often, different photos in the same project, even those with the same ''lens number'',
will require a different '''Exposure'''. This could be because the photos were taken
with a different shutter-speed or simply because the light changed between shots, if so
uncheck '''Link''' here before optimising exposure in the [[hugin Exposure tab]].

The '''Red multiplier''' and '''Blue multiplier''' settings are used to account for changes
in '''white balance''' (also known as ''colour balance'' or ''colour temperature'') between
photos. Setting them both to ''1'' will result in no ''white balance'' change (the numbers
are relative to the green channel which stays unaltered).

As with exposure, different photos in the same project are quite likely to require different
''white balance''. Typically this will be caused by variations in lighting conditions between
shots - For example a cloudy scene will contain considerably less ''red'' light than the same scene
under direct sunlight, so uncheck '''Link''' here before optimising '''White balance'''
in the [[hugin Exposure tab]].

=== Vignetting ===

[[Vignetting]] is dependent mainly on your lens and the ''aperture''. Usually the
centre of the image is brighter with a falloff towards the edges. The three
numbers here represent a polynomial curve used by [[hugin]] to correct vignetting.

You are not expected to guess these values, they are generally loaded with a lens
profile or calculated from two or more overlapping photos in the [[hugin Exposure tab]].

Set the values to ''0,0,0'' for no vignetting correction.

Usually all photos taken with the same ''lens'' will have the same vignetting, keep
'''Link''' checked to ensure '''hugin''' applies the same vignetting correction to all
photos with the selected lens number.

=== Vignetting Center Shift ===

The centre of [[vignetting]] is rarely the exact centre of the photo. The two numbers
here indicate the position of the vignetting centre. The scale is in pixels, with
''0,0'' indicating the centre of the photo. The values are independent of the '''d'''
& '''e''' parameters which specify the origin for projection and geometric distortion.

As with other lens parameters, this '''Vignetting Center Shift''' can be optimised in
the [[hugin Exposure tab]]. Keep '''Link''' checked to ensure [[hugin]] applies the same
vignetting centre to all photos with the selected lens number.

=== Camera Response ===

The [[camera response curve]] is used both for mapping the images to a linear
colourspace when creating [[HDR]] output, and for normalising the colourspace
for internal vignetting, brightness and colour corrections when creating
'normal' '''LDR''' output.

[[hugin]] uses the [http://www1.cs.columbia.edu/CAVE/projects/rad_cal/rad_cal.php EMoR response model]
from the Computer Vision Lab at Columbia University which simplifies the full
response curve to these five empirical coefficient numbers. You are
not expected to guess these values, they are generally loaded with a lens
profile or calculated from two or more overlapping photos in the [[hugin Exposure tab]].

Set the five numbers to ''0,0,0,0,0'' to use a generic response curve or change the '''Type'''
to '''Linear''' to indicate that your input photos have a ''scene-referred'' or [[HDR]]
response.

Keep '''Link''' checked to ensure '''hugin''' applies the same
response curve to all photos with the selected lens number.

__NOTOC__
[[Category:Software:Hugin]]

Panorama tools applications

2012-04-11T09:10:17Z

Zarl: Reverted edits by Beznogov (Talk) to last version by Erik Krause

There are several tools in the panorama tools package by [[Helmut Dersch]] that are intended for other use than mere panorama creation or display. And of course there are lots of possibilities to use panorama tools core functionality for non-panoramic purposes.

== Tools in the package ==
The tools for Panorama Tools consist of Java apps, plug-ins, and applications. For most of these tools there is a small readme inside the package. Apart from that there is almost no documentation found on the web. Any contribution is welcome!

===[[PTEditor]]===
Java Interactive Panorama Editor.

===[[PTPicker]]===
Java graphical interface frontend for control point selection used by [[PTStitcher]], [[PTStereo]], [[PTInterpolate]], [[PTMorpher]], and other tools. Mostly replaced by new GUIs of [[Hugin]], [[PTGui]], [[PTMac]], and [[PTAssembler]].

===[[PTCrypt]]===
Java app to encrypt panoramas to only display from one web location.

===[[PTOptimizer]]===
The tool for parameter optimization of source images. Calculates the position and lens correction parameters from a set of control points representing features in overlapping images.

===[[PTStitcher]]===
The main panorama stitching tool which remaps, adjusts and combines arbitrary images to panoramic views.

===[[PTAverage]]===
reduces noise in digital images by averaging several scans. Example on [[Helmut Dersch]]'s page: [http://www.panotools.org/dersch/average/average.html]

===[[PTInterpolate]]===
given two images of the same scene taken from different viewpoints, this tool creates any intermediate view.

===[[PTMorpher]]===
morphing tool. A nice tutorial is found on 4pi.org: [http://www.4pi.org/tutorial/ptmorpher.en.html]

===[[PTStereo]]===
creates 3-dimensional objects from pairs or many images

===[[PTStripe]]===
combines images into movie stripes for viewing in Object-viewers.

=== Plugins ===
See [[Panorama Tools Plugins]] for details.

====[[Panorama_Tools_Plugins#Adjust|PTAdjust]]====
(Former name: Adjust) Plug-in to extract and insert images from a panorama.

====[[Panorama_Tools_Plugins#Correct|PTCorrect]]====
(Former name: Correct) Plug-in to correct problems with images.

====[[Panorama_Tools_Plugins#PTRemap|PTRemap]]====
(Former name: Remap) Change an image from one projection to another projection.

====[[Panorama_Tools_Plugins#Perspective|PTPerspective]]====
(Former name: Perspective) Simulates a shift lens in software for normal or fisheye lenses.

===[[PTViewer]] Extensions===
These extensions are described in total on [[Helmut Dersch]]'s page: [http://www.panotools.org/dersch/PTVJ/helpers.html] (Descriptions taken mostly from there)

====PTCompass====
Inserts a user defined image which rotates synchronized with the pan-angle. It may be used as navigation and orientation aid. The image may be placed anywhere in the appletwindow, and it can rotate in both directions: like a real compass, or opposite.
====PTMovies====
Inserts a set of images into the panoramic image or the viewer window, depending on the warp-parameter. If warp is true (default) the images are inserted into the panorama and they have to be warped to the panoramic projection. They are displayed perspectively corrected in PTViewer and appear like natural elements of the VR-scene. Example on [[Helmut Dersch]]'s page: [http://www.panotools.org/dersch/movie/PanoMovie.html]
====PTMedia====
Many media formats are available in [[PTViewer]] if JMF is installed on the host computer. These include avi-video, linear quicktime video, flash 2, mpeg1/2/3, many soundformats etc. See [http://www.javasoft.com/ the Sun Java site] for supported media types.
====PTObject====
displays 3D-objects using a set of images similar to the Apple [[QTVR]]-viewer. The images are organized in horizontal stripes, and may cover several rows. There is an optional mask image, that can be supplied to make portions of the original image transparent. Example (with a panorama as background!) on [[Helmut Dersch]]'s page: [http://www.panotools.org/dersch/object/Object.html]
====PTZoom====
High resolution zoomable images can be inserted using this extension. These images are seamlessly integrated in the viewer window, and automatically show up when the user pans and zooms into the respective feature. PTZoom uses [[Rectilinear Projection|rectilinear]] images from any normal or telephoto lens. Example on [[Helmut Dersch]]'s page: [http://www.panotools.org/dersch/zoom/Zoom.html]

==Non-panoramic uses of panotools==
Due to its incredible flexibility panotools core functions can be used for a wide range of non-panoramic uses including (but not limited to) the following:

===Lens distortion correction===
[[Barrel distortion|Barrel]], [[Pincushion distortion|pincushion]] and even wavy lens distortion can be corrected with panotools [[lens correction model]]. A project dedicated to this purpose is [[PTLens]] by Thomas Niemann. Tutorials on how to find suitable lens correction parameters are several on the web. A small selection:
*Philo's tutorial on how to correct distortion and perspective in one go: [http://www.philohome.com/barrelpers/barrelpers.htm]
*Thomas Niemann's description of the calibration process: [http://epaperpress.com/pano/calDistort.html] (eventually follow 'Calibration' 'Lens Distortion')
*Using [[straight line control points]]: [http://www.erik-krause.de/verzeichnung/distort_en.htm]

===Perspective correction===
Panotools is able to simulate (geometrically exact) a shift lens. See [[Perspective correction]] for details.

Another nice tutorial by Philo, showing how to correct perspective and [[lens distortion]] in one go:
[http://www.philohome.com/barrelpers/barrelpers.htm]

===Chromatic aberration correction===
Since transversal [[chromatic aberration]] is essentially a different lens distortion for different colors, panotools can correct it by using different correction parameters on the different color channels. See [[Chromatic aberration]] page for details.

===Different uses with 'Correct' plugin===
The panotools [[Panorama_Tools_Plugins#Correct|Correct]] plugin can perform various tasks including:
*[[Panorama_Tools_Plugins#Radial_Shift|Radially]], [[Panorama_Tools_Plugins#Vertical_Shift_.26_Horizontal_Shift|horizontally]] or [[Panorama_Tools_Plugins#Vertical_Shift_.26_Horizontal_Shift|vertically]] shift an image or it's single color channels.
*[[Panorama_Tools_Plugins#shear|Shear]] or [[Panorama_Tools_Plugins#scale|scale]] an image using high quality [[Interpolation|interpolators]].
*Adjust [[Panorama_Tools_Plugins#radial_luminance|radial luminance]] (edge light fall off - [[vignetting]])
*[[Panorama_Tools_Plugins#cut_frame|Crop]] images to the brightest rectangle of a given size.
*Apply a [[Panorama_Tools_Plugins#Fourier_filter|Fourier filter]] for example to restore stars from star trail images.

===Photographing in Tight Spaces===
Since a fisheye allows for a very wide field of view it can be used to shoot in tight spaces or if you can't get enough distance for a wide angle shot. Panotools will remap to a more conventional view:
* A nice tutorial on tight spaces by 'Big' Ben Kreunen: [http://www.path.unimelb.edu.au/~bernardk/tutorials/360/alternatives/tight_spaces.html]
* Architectural example on [[Helmut Dersch]]'s page: [http://www.panotools.org/dersch/architect/arch.html]

===Stitching Flat Images===
such as a large paper document, scanned in pieces on a flatbed scanner. See [[How to stitch flat images]].

--[[User:Erik Krause|Erik Krause]] 12:14, 16 Jul 2005 (EDT)

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

Hugin Camera and Lens tab

2012-04-04T08:09:20Z

Zarl: /* Lens */ added lens types

{| cellspacing="0" cellpadding="0" style="clear: right; margin-bottom: .5em; float: right; padding: .5em 0 .8em 1.4em; background: none; width:auto"
| __TOC__
|}
The '''Camera and Lens''' tab looks a lot like the [[hugin Images tab]], except that the lens settings can be edited here.
As in the Images Tab, multi-selection can be used to change the parameters for multiple images.

[[Panorama Tools]] and [[hugin]] allow the usage of images shot with different lenses and settings inside the same project.
Each image is associated with a lens number.
All images that share the same lens number use the same lens type, and may be forced to share the same lens parameters.

The '''Load lens...''' and '''Save lens...''' buttons allow you to keep calibrated lens profiles. Once a set of lens parameters has been obtained through [[lens calibration]] it shouldn't vary much for future projects. The advantage of this is that if only positions are being optimised in the [[hugin Optimizer tab]], then as few as two or three [[control points]] are needed per image pair.

'''Load EXIF''' examines the selected image file and tries to determine the [[Field of View]]
of the photo by reading embedded [[EXIF]] data. The same function is performed when initially adding photos so you only need
this button to reset the '''Field of View''' if it has since changed.

By default, every photo in a project is assigned to ''lens number'' '''0'''. If you are including
pictures taken with a different camera, a different lens or at different zoom settings; then
you need to assign a ''new lens'' for these pictures by clicking the '''New Lens''' button.
Assign additional photos to this ''lens number'' with the '''Change Lens...''' button.

== Geometric ==

The Panorama Tools [[lens correction model]] has enough parameters to model most photographic images, these parameters can be set manually here in the '''hugin Camera and Lens tab''' or calculated automatically in the [[hugin Optimizer tab]].

Note that any or all of these parameters can be changed back to good defaults in the [[Hugin Reset Values window]] reached by clicking the '''Reset...''' button.

=== Lens ===

The most important parameters are the '''[[Field of View|Horizontal field of view]]''' and the '''Lens type'''. Hugin supports the following projections in input images:

* '''[[Rectilinear Projection|Normal (rectilinear)]]''' - The projection used by most cameras. It keeps straight lines straight. The maximum horizontal field of view is 180 degrees (for an image of infinite size, that is).
* '''[[Cylindrical Projection|Panoramic (cylindrical)]]''' - Often used by panoramic cameras, such as the Horizon, Roundshot and Spheron cameras. This projection is also called simply ''cylindrical'' projection.
* '''[[Fisheye Projection|Circular fisheye]]''' - Used by fisheye lenses. If the image is circular or the corners of the image are black, use this type of fisheye lens. A circular crop in the [[Hugin Crop tab]] can be used for cutting away the edge borders.
* '''Full frame fisheye''' - Exactly the same projection as '''circular fisheye''', but the crop option will crop to a rectangle instead of a circle. This should be used for full frame fisheye images.
* '''[[Equirectangular Projection|Equirectangular]]''' - A full spherical projection. These are generally created as the result of the stitching process, but it can be useful to reload a finished panorama to extract further images.
* '''Orthographic'''
* '''Stereographic'''
* '''Equisolid'''
* '''Fisheye Thoby''' is modeling the Nikkor 10.5 mm fisheye lens

After the lens type has been specified, an estimate for the horizontal [[field of view]] (HFOV) is required. The HFOV specifies the horizontal opening angle of the image in degrees. Since most photographers are more familiar with [[Focal Length]] as a measure for the HFOV, it can be entered into hugin, and hugin will compute the HFOV from it. For this calculation the actual focal length and the [[crop factor]] of the camera are required. If the 35mm film equivalent focal length is known, a crop factor of 1 should be used.

With [[JPEG]] images, hugin can usually automatically calculate the HFOV based on the [[EXIF]] information.

=== Radial Distortion, Image Center Shift and Image Shearing ===

Usually lenses do not project images exactly according to the selected projection type, but suffer from distortions.
In many cases the distortions are acceptable for single image shots, but they need to be corrected when stitching a panorama.
The '''a''', '''b''' and '''c''' parameters are used to remove that distortion.
They are applied radially from the image center, which can be moved by changing the '''d''' and '''e''' parameters.
These '''a''', '''b''', '''c''', '''d''' and '''e''' parameters are the basis of the panotools [[lens correction model]].

Scanned images might also suffer from image [[shearing]]. This can be corrected using the '''g''' and '''t''' parameters.

The distortion parameters usually vary with the focal length, and to a lesser degree with the focus.
The '''link''' checkbox indicates whether the parameter is linked or not.
A linked parameter is forced to the same value for all images with the same lens number.
This is the default for the HFOV and distortion parameters.
If a parameter is not linked each images is allowed to have individual values for the respective parameter.
This is useful if a different zoom or focus setting has been used for some images.
If scanned images are used, they are usually not perfectly centered, and each image should have individual '''d''' and '''e''' parameters.

== Photometric ==

[[hugin]] models the '''photometric''' parameters of a lens/camera combination in a similar way to the [[lens correction model]] for '''Geometric''' parameters. These parameters can be set manually here in the hugin '''Camera and Lens tab''' or calculated automatically in the [[hugin Exposure tab]].

Note that any or all of these parameters can be changed back to good defaults in the [[Hugin Reset Values window]] reached by clicking the '''Reset...''' button.

=== Exposure and Color ===

'''Exposure (EV)''', EV stands for ''Exposure Value'', setting it to ''0'' (zero) will
result in [[hugin]] applying no exposure change to the photo.

EV is a standard photographic scale, each increase or decrease by one unit will change the
exposure by the equivalent of one ''f-stop'' (ie. halving or doubling the exposure).

Very often, different photos in the same project, even those with the same ''lens number'',
will require a different '''Exposure'''. This could be because the photos were taken
with a different shutter-speed or simply because the light changed between shots, if so
uncheck '''Link''' here before optimising exposure in the [[hugin Exposure tab]].

The '''Red multiplier''' and '''Blue multiplier''' settings are used to account for changes
in '''white balance''' (also known as ''colour balance'' or ''colour temperature'') between
photos. Setting them both to ''1'' will result in no ''white balance'' change (the numbers
are relative to the green channel which stays unaltered).

As with exposure, different photos in the same project are quite likely to require different
''white balance''. Typically this will be caused by variations in lighting conditions between
shots - For example a cloudy scene will contain considerably less ''red'' light than the same scene
under direct sunlight, so uncheck '''Link''' here before optimising '''White balance'''
in the [[hugin Exposure tab]].

=== Vignetting ===

[[Vignetting]] is dependent mainly on your lens and the ''aperture''. Usually the
centre of the image is brighter with a falloff towards the edges. The three
numbers here represent a polynomial curve used by [[hugin]] to correct vignetting.

You are not expected to guess these values, they are generally loaded with a lens
profile or calculated from two or more overlapping photos in the [[hugin Exposure tab]].

Set the values to ''0,0,0'' for no vignetting correction.

Usually all photos taken with the same ''lens'' will have the same vignetting, keep
'''Link''' checked to ensure '''hugin''' applies the same vignetting correction to all
photos with the selected lens number.

=== Vignetting Center Shift ===

The centre of [[vignetting]] is rarely the exact centre of the photo. The two numbers
here indicate the position of the vignetting centre. The scale is in pixels, with
''0,0'' indicating the centre of the photo. The values are independent of the '''d'''
& '''e''' parameters which specify the origin for projection and geometric distortion.

As with other lens parameters, this '''Vignetting Center Shift''' can be optimised in
the [[hugin Exposure tab]]. Keep '''Link''' checked to ensure [[hugin]] applies the same
vignetting centre to all photos with the selected lens number.

=== Camera Response ===

The [[camera response curve]] is used both for mapping the images to a linear
colourspace when creating [[HDR]] output, and for normalising the colourspace
for internal vignetting, brightness and colour corrections when creating
'normal' '''LDR''' output.

[[hugin]] uses the [http://www1.cs.columbia.edu/CAVE/projects/rad_cal/rad_cal.php EMoR response model]
from the Computer Vision Lab at Columbia University which simplifies the full
response curve to these five empirical coefficient numbers. You are
not expected to guess these values, they are generally loaded with a lens
profile or calculated from two or more overlapping photos in the [[hugin Exposure tab]].

Set the five numbers to ''0,0,0,0,0'' to use a generic response curve or change the '''Type'''
to '''Linear''' to indicate that your input photos have a ''scene-referred'' or [[HDR]]
response.

Keep '''Link''' checked to ensure '''hugin''' applies the same
response curve to all photos with the selected lens number.

__NOTOC__
[[Category:Software:Hugin]]

Hugin Stitcher tab

2012-04-04T07:29:39Z

Zarl: /* Projection */ Some hint what the thoby projection is used for

The rest of [[hugin]] is all about setting up the project and aligning images, the '''Stitcher''' tab is where
the final output file is created.

= Projection =

Here you can set the output '''[[Projections|Projection]]''' of your project, there are lots
to choose from, each with different advantages and disadvantages:

* [[Rectilinear Projection|Rectilinear]], this is the same projection as a photo taken with a 'normal' camera and lens. Use this if you are just stitching a handful of photographs together with a narrow [[Field of View]] or [[Perspective correction|correcting perspective]] in a single shot.
* [[Cylindrical Projection|Cylindrical]], actually a simple [[Cylindrical Projection]] as used by traditional rotating panoramic cameras. A good projection for printing a 360 degree panorama, though you may prefer ''Mercator Projection''.
* [[Equirectangular Projection|Equirectangular]], the all purpose format for representing an entire spherical scene. It covers 360 degrees horizontally as well as the [[zenith]] and [[nadir]].
* [[Fisheye Projection|Fisheye]], the same projection as a photo taken with a ''fisheye lens''. Better for representing a wide [[Field of View]] than ''rectilinear'', but in many cases ''Stereographic Projection'' gives less distortion than simple ''fisheye''.
* [[Stereographic Projection|Stereographic]], a ''conformal'' fisheye image. Objects in a stereographic image keep the same shape and show less distortion than simple ''fisheye''.
* [[Projections#mercator projection|Mercator]], a ''conformal'' cylindrical image. A good projection for printing a 360 degree panorama.
* [[Projections#Transverse mercator projection|Trans Mercator]], a ''mercator'' image rotated 90 degrees, suitable for displaying tall or overhead objects.
* [[Projections#sinusoidal projection|Sinusoidal]], an ''equal area'' projection of an entire spherical scene.
* [[Lambert Equal Area Cylindrical Projection|Lambert Cylindrical Equal Area]]
* [[Lambert Equal Area Azimuthal Projection|Lambert Equal Area Azimuthal]]
* [[Albers Equal Area Conic Projection|Albers Equal Area Conic]]
* [[Miller Cylindrical Projection|Miller Cylindrical]]
* [[Panini]]
* [[Architectural]]
* [[Orthographic]]
* [[Equisolid]]
* [[Equirectangular Panini]]
* [[Biplane]]
* [[Triplane]]
* [[The General Panini Projection|Panini General]]
* [[Thoby Projection]], is modeling the 10.5 mm Nikkor fisheye lens and was introduced with [http://hugin.sourceforge.net/releases/2011.0.0/en.shtml hugin 2011.0.0]. The projection is called after Michel Thoby who was able to empirically find it.

== Field of View ==

This is the horizontal and vertical [[Field of View|angle of view]] of the output image,
clicking '''Calculate Field of View''' will shrink or enlarge the field of view of the
output to fit the arrangement of the input images - The '''Fit''' button in the
[[Hugin Preview window]] does the same thing.

Note that some [[Projections]] have a limited field of view, notably:

* Rectilinear has to be less than 180 degrees both vertically and horizontally.
* Panoramic (cylindrical) has to be less than 180 degrees vertically.
* Stereographic has to be less than 360 degrees both vertically and horizontally.
* Mercator has to be less than 180 degrees vertically.
* Transverse Mercator has to be less than 180 degrees horizontally.

== Canvas Size ==

Set the '''width''' and '''height''' of your output panorama in pixels. '''Calculate Optimal Size''' will estimate
a size that has about the same resolution as your input images.

Some examples: a ''three megapixel'' image has pixel dimensions of 2048 x 1536, an A4 print at 300 pixels per inch will
have a pixel size of 3500 x 2480, a ''full screen'' spherical [[Equirectangular Projection]] image will have pixel
dimensions of 6000 x 3000 or greater and a ''gigapixel'' image has a pixel size of 32768 x 32768.

Note that the [[interpolation]] used by [[hugin]] doesn't handle downsampling very well, so output images smaller
than about half the size of the ''Optimal Size'' will show [[aliasing]] artefacts. If you want to create high quality
small images, it is better to create an ''Optimal Size'' image in hugin and downsize it later in an image editor such as [[Gimp]].

== Crop ==

The crop settings allow just a portion of the panorama to be stitched, there are various reasons to do this:

* When [[Perspective correction|correcting perspective]] large areas of the panorama output will be empty anyway.
* Large 'gigapixel' style panoramas can be stitched in sections then blended later.

The cropped-out areas are shown darkened in the [[hugin Preview window]].

The '''Fit Crop to Images''' button will automatically determine a crop that has a maximum number of pixels and no empty space. This is the same function as the '''Autocrop''' button in the [[Hugin Fast Preview window]].

== Output ==

Hugin can output 'normal' stitched images, [[Exposure fusion|exposure fused]] images or high dynamic range ([[HDR]]) images.
The following options determine which kind of image is created, and allow keeping the intermediate images created during the process.

=== Normal ===

If '''Exposure corrected, low dynamic range''' is enabled then [[enblend]] is used for blending. In the final stitching process [[nona]] reprojects and distorts images to fit, '''enblend''' takes these images as individual [[TIFF]] files and merges them using sophisticated seam positioning and blending. Further '''enblend''' settings can be found in the [[hugin Preferences]].

Enable '''Exposure corrected, low dynamic range''' under '''Remapped Images''' if you want to keep the intermediate images that '''enblend''' uses as input - For example modifying the [[alpha channel]] of these images and then blending manually is one technique for including and excluding people or objects that move between shots.

=== Exposure fusion ===

If '''Exposure fused from stacks''' is enabled then hugin will group the input images into exposure stacks by comparing positions, any images with more than 70 % overlap are grouped like this. Each of these [[Bracketing|bracketed]] exposure stacks will be [[Exposure fusion|exposure fused]] with [[enfuse]] and the results seam blended together into a panorama with [[enblend]].

Note that for this to work, the scene has to be photographed multiple times using exposure [[bracketing]] and the EV exposure values set either manually in the [[hugin Camera and Lens tab]], automatically from [[EXIF]] data or by optimising exposure in the [[hugin Assistant tab]] or [[hugin Exposure tab]].

Note also that unlike '''Normal''' and '''HDR merging''' options where images are exposure corrected as part of the remapping process, enfuse requires that each exposure layer is supplied uncorrected - Hugin takes care of this automatically and will not apply exposure correction in this case.

If '''Exposure fused from any arrangement''' is enabled then hugin will seam blend images with similar exposure with [[enblend]] and than it will [[Exposure fusion|exposure fuse]] them using [[enfuse]]. This variant is often much more successful than '''Exposure fused from stacks''' in two situations:

* Where entire panoramas have been shot at each EV level consecutively rather than each shot [[Bracketing|bracketed]], in this case it isn't guaranteed that shots will line up into the approximate stacks expected by the '''Exposure fused from stacks''' option.

* When the panorama has been shot entirely on automatic exposure, in this situation it is useful to seam blend adjacent photos with small EV differences, but then exposure fuse larger EV differences - As effectively happens with this option.

Note that hugin uses a threshold of 0.5 EV exposure difference to determine which photos can be fused into each layer.

Enable '''Blended layers of similar exposure, without exposure correction''' from '''Layers''' to keep exposure layers from the '''Exposure fused from any arrangement''' step, these are useful for manual [[Contrast Blending]].

Enable '''No exposure correction, low dynamic range''' from '''Remapped Images''' to keep the intermediate images supplied to [[enblend]] and [[enfuse]].

Normal '''Format''' can be in one several output file types:

* '''[[TIFF]]''', various compression options. [[16bit]] and ''8bit'' depth supported. '''None''' compression is supported by most other applications, '''LZW''' compression is common in Windows/Mac applications and '''Deflate''' compression is more common with Linux tools.
* '''[[JPEG|JPG]]''', lossy compression suitable for web/email. '''Quality''' can vary from ''0'' (extremely low quality, small file size) and ''100'' (high quality, large file size). A typical quality setting for web/email would be between ''70'' and ''80''
* '''[[PNG]]''', lossless compression. [[16bit]] and ''8bit'' depth supported.

=== HDR merging ===

If '''High dynamic range''' is enabled then hugin will identify likely [[Bracketing|bracketed]] stacks of images, then create remapped [[HDR]] images which are then blended with [[enblend]].

Note that like the Exposure fusion option above, this generally only makes sense if the scene has been photographed multiple times using exposure bracketing, and the EV exposure values optimised in the [[hugin Exposure tab]].

Enable '''High dynamic range merged stacks''' from '''Combined stacks''' to keep copies of the remapped HDR images as supplied to enblend.

Enable '''High dynamic range''' from '''Remapped Images''' to keep copies of each image remapped in linear colour space before merging to HDR.

Click '''Stitch now!''' to generate output panoramas immediately. Selecting '''Save project and send to batch''' adds the current project to the [[Hugin Batch Processor]] stitching queue, note that the queue won't be processed unless this queue manager is running.

High dynamic range '''Format''' can be either:

* ''floating-point'' [[TIFF]], various compression options.
* '''[[OpenEXR|EXR]]''', this is a high dynamic range format which is more compact than a high dynamic range TIFF.

= Processing =

[[nona]] is the default '''Remapper''' (stitching engine) supplied with [[hugin]], normally there is no need to
change this or any of the options below.

Set the '''Interpolator (i)''' to change the sampling [[interpolation]]. You probably won't notice
much difference between the various options except that '''Nearest Neighbour''' is fast but with
very low quality. The default of '''Poly3 (bicubic)''' is generally good for most purposes.

[[Cropped TIFF]] files are smaller and more efficient because unused parts of the image are not stored in the file. You should
always '''save cropped images''' unless you need to open them in an image editor without [[Cropped TIFF]] support.

[[enfuse]] is the default for [[Exposure fusion]], '''Options''' are similar to [[enblend]].

The default '''HDR merger''' is [[hugin_hdrmerge]].

[[enblend]] is the default '''Blender''' for use with [[hugin]], normally there is no need to change this. Additional command-line '''Options''' can be set here or in the [[hugin Preferences]] for new projects.

__NOTOC__
[[Category:Software:Hugin]]

Hugin FAQ

2012-03-30T15:39:43Z

Zarl: /* OS X / iPhoto */ 10.7 Lion related bug added

== Common error messages ==

=== enblend: no input files specified ===

There are no input images relevant to the output 'panorama' so hugin had nothing to do, probably because all the input images are outside the panorama 'frame' or disabled. Open the [[Hugin Preview window]] or [[Hugin Fast Preview window]] to adjust the view, enable some images inside the panorama frame and/or adjust the crop.

Note also that hugin versions up to and including 2009.2.0 allow you to draw an inverted crop frame where the top is below the bottom, this is easy to see in the Preview window as the entire panorama is 'greyed'. A crop frame drawn like this will result in an empty panorama and the above error message.

=== enblend: excessive overlap detected ===

This is an error new to enblend-4.0. Photos that nearly entirely overlap won't blend very well, enblend now fails instead of attempting to blend them. There are various workarounds:

* Follow the error message and remove the suggested image from the set, you probably don't need it to complete the panorama.
* Switch back to enblend-3.2.
* Hugin will merge stacked images before blending if you select 'Exposure fusion' in the [[Hugin Stitcher tab]]. This error will go away, but Hugin will take a very different approach to variable exposure between photos.
* Mask out major parts of one image.

=== enblend: error writing to image swap file ===

[[enblend]] needs a lot of memory and uses its own swap routine to store picture data on the disk, this message indicates that you have run out of disk space. The data is stored in the system temp folder which is specified by TMP, TEMP or TMPDIR environment variables, note that this temp folder may be on a different physical disk to your photos and panorama output.

=== execvp(make ...) failed with error 2 ===

Hugin requires the 'make' utility to stitch, you need to install it and/or report the problem to whoever supplied Hugin to you.

=== false --compression NONE ===

This error is caused by a bug in the 0.7.0 release that is fixed in 0.8.0. The problem is that your preferences are messed-up, the workaround for 0.7.0 is to go to File -> Preferences -> Enblend and click Load Defaults -> Yes -> Ok

=== Enblend error: Mask is entirely black, but white image was not identified as redundant ===

This is a well known "error" for [[enblend]]. Try to use the additional enblend parameter "--fine-mask" to get rid of the error. The parameter will result in generation of masks in higher resolution that will fix the problem in most cases. Sometimes the "--fine-mask" parameter may result in memory errors (malloc: ...), which are the result of not enough memory available due to the (much) bigger masks that are used.

An alternative workaround would be to set the enblend --no-optimize parameter, this will place the seam directly along the middle of the image overlaps regardless of image content. This option is also considerably faster and uses less memory.

This error also occurs when one photo is completely covered by another, try removing redundant photos.

Note also that for the same reasons this error often appears when rendering a scene with extreme distortion such as a stereographic 'little planet'. For this and other reasons, such as overall speed, it is always preferable to render a 'normal' 360° [[Equirectangular Projection]] panorama first, then load this as a single source image into a new project and render whatever views you need.

Note (Jan 2010): This should be fixed in the latest [[enblend]] 4.0 release.

=== enblend: illegal option -- compression ===

hugin 0.7.0 and later versions require at least [[enblend]] version 3.2. This error indicates that you need to upgrade enblend.

=== enblend: Error -1073741795 ===

See [[#Enblend: The system cannot execute the specified command]], in particular if you are a Windows user try switching to the 'nosse' enblend-enfuse.

=== Makefile: target pattern contains no % ===

This is a message generated by [[w:Make_(software)]] (which [[Hugin]] uses to manage the stitching sequence). The error is caused by a ''':''' or '''#''' character in one of the file paths. The workaround is to rename to remove any 'special' shell characters and try again.

=== gnumake: *** No rule to make target ===

This is a message generated by [[w:Make_(software)]] (which [[Hugin]] uses to manage the stitching sequence). The error is caused by a ''':''' or '''#''' character in one of the file paths. The workaround is to rename to remove any 'special' shell characters and try again.

=== nona: GL error: Framebuffer incomplete, incomplete attachment in: ===

This is a message generated by nona when using the GPU for stitching (feature available starting with Hugin-2009.2.0). See section below about [[#GPU-stitching_.28nona.29|GPU-stitching]].

=== make: enfuse: command not found ===

This is a message generated by make when assembling your panorama. It most likely means that enfuse is not on your computer. Enfuse is part of the enblend package, but many Linux distributions, even recent ones, ship with an older version of enblend that does not contain enfuse. You need to install enblend-3.2 or later.

=== Enblend: The system cannot execute the specified command ===

This message could be generated by either
* the lack of Microsoft Visual C++ 2008 Redistributable Package (x86) that is necessary to run an OpenMP enabled version of Enblend. Download [http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en here].
* the lack of [http://en.wikipedia.org/wiki/SSE2 SSE2] support. Use a non-SSE build of Enblend. See also [[#Enblend-Enfuse_OpenMP_SSE_GPU:_which_one_is_the_right_one_for_me.3F | types of Enblend-Enfuse binaries]] or [[#Selecting_right_version_of_enblend-enfuse_binary_for_Windows | types of Enblend-Enfuse binaries for Windows ]]

===Windows error message "application configuration is incorrect"===

Double clicking the Hugin icon to run the program produces a message like this:
<pre>
C:\Program Files\Hugin\bin\hugin.exe
This application has failed to start because the application configuration is incorrect.
Reinstalling the application may fix this problem.
</pre>
Try installing the [http://www.microsoft.com/downloads/en/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en Microsoft Visual C++ redistributable].

=== Stitching fails on Windows (syntax error)===

If the stitching step fails on windows with a error message like

<pre>
/usr/bin/sh: -c: line 1: syntax error near unexpected token `(6'
/usr/bin/sh: -c: line 1: `echo Operating System: Windows 7 (6.1 )'
make: *** [info] Error 258
</pre>

or

<pre>
Syntax error: "(" unexpected
make: *** [info] Error 2
</pre>

then you have probably an other shell (e.g. sh.exe or bash.exe) somewhere in your path. In this case remove the path to this executable from the PATH variable.

=== Hugin Quits (Seg Faults) at Launch (Linux) ===

There may be many reasons why a program dies before it has even started.

One possibility is bad configuration or installation of the video drivers. See this [https://bugs.launchpad.net/hugin/+bug/679427 ticket]. To diagnose, try running glxgears. On Ubuntu (the package is probably available on most Linux distributions):

<pre>
sudo apt-get mesa-utils
glxgears
</pre>

If glxgears does not run on your system, Hugin will not run either. See your Linux distribution's instruction on how to fix the video drivers.

== Known Limitations ==

=== Linux: Compiz ===

Linux: Compiz interferes with the [[hugin Fast Preview window]]. This is not a hugin specific issue. Research shows all direct rendered stuff will have various problems under Compiz: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/96991

This problem is fixed with DRI2, e.g with fedora 11 and intel graphics hardware you can have a 'wobbly' Fast Preview window if you really want.

It's not an issue with NVidia's proprietry driver.

If you're affected, the workaround is to not use Compiz.

=== Windows: International Characters in Path ===

Hugin is fully internationalised and can cope with special characters in file paths. However, hugin apparently fails on some Windows systems with Polish, Japanese, Russian or Czech codepages, the workaround is to use shell-safe ascii characters in file and folder names: '''A B C D E F G H I J K L M N O P Q R S T U V W X Y Z a b c d e f g h i j k l m n o p q r s t u v w x y z 0 1 2 3 4 5 6 7 8 9 - _ .''' This includes the path for the temporary folder which is named after your username on Windows systems.

=== OSX: error when clicking on the help button ===

In a language other than English, French or Italian you get an error message when clicking on the help button. This will be fixed in Hugin-2009.4.0. In the meantime, the work around is to change language to one of the above three; or to ask for help on the mailing list.

=== Non-Unique Filenames ===

Some components of Hugin have been reported not to deal well with image files
that have the same name in different folders. The workaround is to rename
your images files so that all image files in a project are unique.

=== Temporary Files ===

Hugin has a preference setting for the temporary files folder. Currently it
is not implemented properly and files will be written in the same folder as
the project file.

A partial workaround on Linux is to start Hugin from a terminal with
<pre>
TMPDIR=/media/disk-2/tmp hugin &
</pre>

A workaround on Windows is to create a batch file which sets the temp folder before running Hugin.
eg using notepad, create a file called HuginWithNewTemp.cmd with the following in it:
<pre>
REM Create a folder on C Drive called Temp for this to work

REM Set the temp file environment variables for hugin
set temp=c:\temp
set tmp=c:\temp

REM run hugin
"C:\Program Files\Hugin\bin\hugin.exe
</pre>

These temporary files have to be deleted manually after the stitch.

=== Special Characters in Paths ===

{| style="margin: 1em auto 1em 1em;background:#FFFF99;color:#FF0000;text-align:left;border: solid #FF3300;"
|-valign="top"
! =
! ;
! :
! $
! "
! %
! #
! |
! '
! (
! )
! `
! &
! *
! +
! ^
! ~
! <
! ?
! >
! and the space character.
|}

Hugin currently does not do plausibility checks on the paths and file names that are given to it. It relies on the operating system's conventions and limitations. However Hugin uses [http://en.wikipedia.org/wiki/Make_%28software%29 make] to run the stitching process, and make has more restrictive limitations than the operating system.

Please don't use the above characters in your files and folders when you want to make sure they work with Hugin. If you absolutely need files named this way, rename them after processing. Do not file bug reports based on filenames with the above characters. The [https://sourceforge.net/tracker/?func=detail&atid=550441&aid=2883450&group_id=77506 issue] is known, analyzed, and may be fixed in the future.

=== Stitch fails when '&' is part of the Windows ''user-name'' ===

This is a variant of the above, but more difficult to work around. The ''user-name'' is part of all paths in the user's data area, including the temporary file locations defined by TMP and TEMP. Stitch fails almost immediately with a make path error.

Work-around: See the Temporary Folders section above, or Move your hugin data to a folder in the root directory such as C:\hugin. Then go to the Windows Control Panel and change ''System, Advanced, Environment, user TMP'' to a folder in the root, such as 'C:\temp' (create it if necessary).

Notes: This work-around probably needs Win 7 ''Administrator'' privileges.

A simpler solution should be to set hugin ''File, Preferences, Temporary dir'' to C:\hugin; but it doesn't fix
the problem! Seemingly, at least one temporary file still gets created in the TMP folder.

=== Hugin fails stitching some stereographics and other polar projections ===

This is a known limitation caused by photos being distorted into extreme 'C' and 'O' shapes. The workaround: stitch all of your pictures into a single equirectangular, and then load the equirectangular into Hugin to generate the stereographic or other projections you wanted to do in the first place.

=== OS X and iPhoto ===

Dragging the photos from iPhoto to Hugin works perfectly as long as there is no forward slash in the Name of the events in iPhoto (which translates to folders inside the iPhoto Database).

=== OS X 10.7 and Enblend / Enfuse ===

When using Hugin on Mac OS X 10.7 ''Lion'' with the built-in versions of enblend and enfuse (i.e. those packaged inside the hugin bundle) the stitching process will stop abruptly with an error. See [https://bugs.launchpad.net/hugin/+bug/814280 bug 814280]. The workaround is to use the enblend and enfuse versions for Mac OS X 10.4 ''Tiger'' that are inside the dmg in the ''enblend-enfuse-4.0'' folder.

=== Fast Preview ===

Why are there two preview windows, and which one should I use?

For most purposes, the newer Fast Preview window is faster. However it is still under development and sometimes shows artefacts. The old preview still does a logarithmic tone mapping of stacked
images and is the only way to preview hdr or fused output.

=== Makefile based stitching process ===

Can I restart a stitching process that was interrupted manually or by an error without starting everything from scratch?

Unfortunately the Hugin Makefile system only supports restarting if you stitch on the command-line. The GUI tools always create new temporary .pto project and Makefile files every time they stitch, so this forces make to recreate everything for every stitch.

=== Patching nadir shots using XYZ mosaic mode cuts the photos in half ===

"If an image is mapped to the [[nadir]] of a panorama and all translation parameters (X,Y,Z) are set to zero, the image is properly mapped and covers the entire nadir of the shot. However, if any of the X,Y,Z parameters are non-zero, then the image is cut in half and only occupies half of the nadir."

Basically the XYZ mosaic mode as it is implemented currently in [[Hugin]] requires that the mosaic photos must be mapped to a plane perpendicular to the view direction - In practice this means that what you are trying to do only works if the panorama is rotated such that the nadir is in the middle of the canvas and not at the bottom.

This isn't so bad, the nadir-in-the-middle image looks a bit weird, you can just reload the stitched [[equirectangular Projection]] result into a new single-photo project and straighten it there.

== Python Scripting ==

=== What is Python Scripting? ===

Python is a powerful scripting language. Starting with Hugin 2011.2, Hugin exposes the panorama object through hsi.py in Python. It must be explicitly activated at build time with the CMake boolean parameter -DBUILD_HSI:BOOL=ON. It is currently untested / unavailable on OS X.

=== How do I start Scripting? ===

<pre>
$ python
Python 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53)
[GCC 4.5.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import hsi
>>> help (hsi)
</pre>

=== What is the difference between a Plugin and a Script? ===

Strictly speaking, they are both Python scripts. A Plugin runs inside Hugin, while a Script runs in a shell or desktop.

=== Where Are the Plugins in Hugin and how do I use them? ===

If Hugin was compiled with HSI, a menu Action will list categories of system-wide plugins. Just select one to run it. Moreover, you can write your own plugins and run them with the menu Edit -> Run User Python Plugin. The default location for user plugins is set in the preferences.

=== Script Returned -10 ===

This error message indicates that the plugin tried to import something and failed. hpi.py currently has no other way of telling hugin what's wrong than to 'return -10'. Try to start Hugin from the command line and see if there is more verbose output there. Copy the output and ask for help on hugin-ptx.

=== Script Returned -11 ===

The plugin failing with an exception. Ask the plugin maintainer to produce more specific error messages. It is good practice to catch such exceptions and let the user know what dependency is missing.

=== Why do I read of users having access to a certain action and I don't see it on my system? ===

Some actions only work with specific versions of Hugin or operating systems. It is possible that they have a different system than yours and that the plugin in question does not support your system. Often times this is just a matter of lack of testing resources on a particular platform. Help test the plugin and it may become accessible on your system as well.

== Control Point creation ==

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

1. Selecting control points in 100% zoom.

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

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

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

2. Selecting control points in fit to window mode.

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

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

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

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

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

=== How do I stop Hugin pausing for a moment after every click? ===

The ''preview window'' updates continuously whenever anything changes, so disable the preview auto-update, close it or make it smaller if you don't need it.

Otherwise, picking [[control points]] with ''auto fine tune'' selected can involve a lot
of processing. You can reduce this by ''selecting File -> Preferences -> Finetune'' and
lowering the values for ''Patch width'', ''Search area width'' and ''Local search area width''.
This means you can't be so sloppy when clicking to create control points, but the results will
be the same.

=== Windows: when user is not admin, not all cp-creators are available to choose from ===

Preferences are stored in the registry on Windows. Every users has their own. To have all the cp-creator pre-sets like the admin users, hit the "Load defaults" button on the Control Points tab in the Preferences dialog.

=== cpfind: not enough control points generated ===

Cpfind is a recent addition to the Hugin suite and its parameters still require some fine tuning. Unlike older CP generators used with Hugin, it depends on information passed in the PTO file. Make sure that your input project file contains reasonable information about the used lens. If you are using a fisheye or wide angle lens, try increasing the parameters --sieve1width --sieve1height --sieve1size. A combinations that may work is "--sieve1width 50 --sieve1height 50 --sieve1size 300". Sometimes also the option "--fullscale" might help. Read the [[Cpfind]] documentation.

== Common problems when creating a panorama ==

=== I get thin horizontal black or white lines in large panoramas ===

This is a known bug in the memory handling of [[enblend]] that manifests with large panoramas.

You can workaround it by reducing the size of the panorama, or by adjusting the cache size in [[Hugin_Stitcher_tab]] -> '''Blender options'''. e.g. the default is 1024MB (1 GB), so if you have 4GB RAM you can try raising the cache to use most of your free memory, such as 3000MB, i.e: ''-m 3000''

=== The Control Points tab shows my photos rotated ===

The rotation of photos in the [[Hugin Control Points tab]] isn't necessarily
related to the orientation of the files themselves.

Hugin shows photos at the angle they best fit into the panorama, so if the
panorama fit is bad, then you will see strange angles in the Control Points
tab. Probably the problem is caused by bad alignment, you can
identify 'bad' [[Control points]] in the [[Hugin Control Points table]], delete them and re-optimise.

=== How can I reuse a project as a template? ===

If you copy a .pto project to a different folder and open it with hugin, you will be prompted for the 'missing' images. You should delete any control points from this template project since they won't be relevant to the new photos.

Alternatively you can load your images as normal, then ''Apply template''
from the ''File'' menu, this will import image settings and parameters
from a previous project.

=== How do I straighten a curved horizon? ===
If the panorama looks nice but the horizon is curved, there are various ways to improve the image and straighten the horizon.

First, try clicking the '''Straighten''' button in the [[Hugin Fast Preview window]].

If this doesn't work then you can use the Move/Drag tab of the [[Hugin Fast Preview window]] to visually straighten the panorama, drag the photos with the mouse, use the right mouse button to rotate. One useful tip is to drag the panorama so a vertical feature is in the middle, rotate it so the feature lines up with the 'cross hair', then drag the panorama up or down until all the vertical features in the scene are vertical on the screen (holding down the shift key while dragging limits the motion to just up/down or left/right).

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

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

=== Half the panorama is black, my pictures fill only the right half of the output ===

Hugin uses the first photo as the ''anchor'' image and puts it in the middle by default. This means that if you shot a sequence from left to right, the images will fill the right hand side of the panorama. There are three ways to fix this:

* Open the '''preview''' window and click the '''center''' button.
* or select the middle photo, hit '''anchor this image for position''' and '''reset''' in the '''images''' tab, then reoptimise.
* In the 'Fast Panorama Preview' window select 'Drag'. Left mouse drags the image, right mouse rotates the image.

=== I get visible bands in the sky and other flat areas, what can I do? ===

If the banding looks like [[w:Posterization|posterization]] then this is likely due to a error with estimation of the [[camera response curve]]. To get an accurate response curve, Hugin needs significant [[vignetting]] and/or [[bracketing|bracketed exposures]]. The workaround is to '''Reset...''' the '''Camera Response''' in the [[Hugin Camera and Lens tab]] and stitch again - [[Hugin]] usually produces acceptable results for a simple panorama when the camera response parameters are all zero.

If there is a wave of light and dark patches in the sky this could be due to [[vignetting]] in the source photos, you can deal with this by optimising '''Vignetting (Vb, Vc, Vd)''' in the [[Hugin Exposure tab]]. Another workaround is to increase the number of [[enblend]] blending levels, try setting '-l 29' as the enblend '''Command line options''' in the [[Hugin Stitcher tab]].

=== My photos never quite line up, what can I do? ===

It is normal to get little stitching [[parallax]] errors if
the camera moves between photos. The solution is to rotate the camera around
the [[no-parallax point]] using a [[Heads|panoramic head]] or [[philopod]].

Otherwise you can sometimes improve things by optimising the ''d & e'' parameters
separately - When you optimise '''everything''', unselect '''Inherit''' in
the '''camera and Lens''' panel for 'd & e'. Also you can open the control point window sort it by distance and check the ones large distance.

If these parallax errors are still large, you need to decide which
parts of the scene that you want to line-up and which parts don't
matter. Select [[control points]] only on objects that you do want to
line-up and which are all about the same distance from the camera.

The remaining broken lines can then be retouched in a photo editor like the [[gimp]].
The ''shear'' tool is ideal for bending the lines and
[[Mending parallax errors with the shear tool|getting them to line up]].

=== I have extracted and edited cubefaces and want to merge them together again. How do I do that ? ===

Manually enter the values for [[yaw]] and [[pitch]] for each of the photos. When you stitch set the '''enblend options''' in the [[Hugin Stitcher tab]] to -l1 --fine-mask --no-optimize

=== Can I stitch my HDR images ? ===

Yes. If you already have merged your HDR stacks, follow the '''Normal''' Output on the '''Stitcher''' tab ('''HDR merging''' is for stacks that will be merged by Hugin). In the '''Processing''' step the output will be an HDR in TIFF format.

=== Why is my panorama upside down ? ===

Hugin stitches the panorama on a sphere and can't determine what is up or what is down. Even if vertical control points are assigned, there is still no notion of up and down, so the panorama can flip upside down. The solution for that is to open the Preview window, click on the Num. Trans. button in the toolbar, enter 180 in the roll field and apply. This will flip the panorama back to the right orientation.

=== Why do multi-lens projects end up distorted/broken? ===

You have probably optimized 'Everything'. This will cause the optimizer to try to optimize lens parameters for each of the different lenses, and there may not be a big enough spread of control points for the optimization to work well.
When stitching photos from different lenses, or when you don't have a good spread of control points, optimize 'Position, view & Barrel (y,p,r,v,b).

=== Why does my output covers only 180°? ===

Did you observe that the output is cropped at the +-90° borders? (e.g. saw teeth like borders in the fast preview window)

Then you have probably used the translation parameters X/Y/Z. This behaviour is a fundamental limitation of the used approach of the translation parameters. It is (internal) working in the rectilinear space, which is limited to maximal FOV of 180°, and therefore also the output is limited to FOV<180° (for more information see [[Stitching a photo-mosaic]]).

The solution/workaround is to set all X/Y/Z values to zero or to limit the horizontal field of view (HFOV) to a value smaller than 180°.

== GPU-stitching (nona) ==

Starting with Hugin-2009.2 nona has a new, experimental feature: it can use the video card (GPU) to accelerate the stitching. How much acceleration you will get, if any, depends on the combination of video card and driver.

=== I get a nona: GL error. Does this mean that I found a bug? ===

Not necessarily. This functionality is highly experimental. It may be that you have an outdated driver, or that the functionality is not supported on your video card. Note down the version of the driver you are using and the specs of your video card (GPU and RAM). Then update to the latest driver from [http://www.nvidia.com/page/drivers.html nVidia] or [http://support.amd.com/us/gpudownload/Pages/index.aspx AMD] (ATI has been bought by AMD). Currently only these two families of GPUs support the functionality.

=== How can I know if nona-GPU works on my system? ===

At the moment we have too little information to predict this. We know that only nVidia and AMD(ATI) powered video cards work, and not all of them. The more recent the video card, the higher the likelihood that it works. Improve your chances by updating to the latest driver for your GPU. Look at experience reports from other users and report your experience [[Nona GPU stitching reports|here]].

=== What speed improvement can I expect? ===

It depends on the video card. Bandwidth is mostly the bottleneck, specifically getting the transformed data from the GPU back to the main system memory.

=== Bug Reporting ===

When reporting success or failure using the GPU for stitching, always report also the driver version, video card GPU and RAM. Tell us what you were doing, the size and number of input images (note that if you stitch from within Hugin or PTBatcher, it is only one input image at a time).

== Postprocessing ==

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

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

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

* Use the [[nona]] stitcher on the command-line, to output to a multilayer [[TIFF]] format:

nona -m TIFF_multilayer -o multi_layer.tif project.pto

This will will produce a multi_layer.tif file, that contains all remapped images, cropped to their bounding box.

* Alternatively select the '''Remapped Images''' option in the [[Hugin Stitcher tab]], this will create each ''layer'' as a separate file. Then use the '''tiffcp''' command-line tool (part of libtiff) to join them together into a multi-page TIFF:

tiffcp project0000.tif project0001.tif project0002.tif multi_layer.tif

* You can also use [[tif2xcf]], to combine the '''Remapped Images''' TIFF output into a multilayer XCF.
Unfortunately this requires a lot of memory because it stores each remapped image in a layer with the size of the final panorama.

== Installation ==

=== Where can I download hugin installers ===

Official releases are available from [http://hugin.sourceforge.net/download/ hugin.sf.net].

=== How can I compile Hugin.app on my OSX machine? ===

See [[Hugin Compiling OSX]], [[Autopano-sift-C Compiling OSX]] and [[Enblend Compiling OSX]].

=== How do I compile hugin on my linux machine? ===

See [[Hugin Compiling Fedora]], [[Hugin Compiling Gentoo]], [[Hugin Compiling OpenSuse]] and [[Hugin Compiling Ubuntu]]

=== make[2]: *** No rule to make target `/usr/lib/libGL.so', needed by `src/hugin_base/libhuginbase.so.0.0'. Stop. ===

So you're trying to build from source. Most likely you have proprietary nVidia or ATI drivers. They are a moving target and so is X. On debian based systems including Ubuntu, diagnose with `dpkg -S /usr/lib/libGL.so` and check that the linked library exist (i.e. it is not listed in red when doing `ll /usr/lib/mesa/libGL.so`). If it is listed in red, check where the library is (`ll /usr/lib/libGL*` is a good start on Ubuntu) and link it properly.

=== How do I compile hugin on my Windows machine? ===

See [[Hugin Compiling Windows]]

=== Enblend-Enfuse OpenMP SSE GPU: which one is the right one for me? ===

Enblend and Enfuse can be optimized at build time for different hardware configurations. This yields four categories of Enblend-Enfuse builds, with a few variations. If you build Enblend-Enfuse from source, check the build options in the README file. If you download a binary, you can find out how it has been built with the following command:

enblend -v -V

look for the following in the output text:

# '''Extra feature: OpenMP: yes''' this version has OpenMP.
# '''Extra feature: image cache: yes''' this version has image cache
# '''Extra feature: GPU acceleration: yes''' this version has GPU support
# SSE-support is not mentioned, you'll find out if you have an unsupported CPU and the binary will refuse to run.

These are approximate guidelines to help you choose what may work for you:

* if you have a recent, multi-core / multi-thread CPU, you probably want the OpenMP-enabled version. Note however that speed improvement does not scale well, so don't expect a 6 cores CPU to be 3x faster than a 2 cores one.
* if you have a recent, fast video card, you probably want the GPU-enabled version. This is not mutually exclusive with OpenMP and a good builder will add both features to his binaries. If speed is important to you, you want to test which of the two is faster on your system. If system responsiveness is important to you, the GPU-enabled version frees CPU resources for your other tasks. Note that even if your binary is GPU-enabled, the GPU will not be used unless you specify the option `--gpu`.
* if you have an old CPU without SSE2 support, you want a NOSSE build. This is the least performing version.
* Last but not least, if blending fails because of large images, try the image cache variation. The image cache allows for processing of large project when memory is scarce but images are large (and disk is large enough too). Image cache is incompatible with OpenMP, but a good bilder will make this version GPU-enabled too, so test it with `--gpu` if speed is important.

=== Selecting right version of enblend-enfuse binary for Windows ===

There are 3 variants of enblend-enfuse binaries officially released for Windows. Each one has a special feature set:

1. enblend.exe/enfuse.exe

These executables are the standard release. They are using one processor core and the image cache for processing very big images.

2. enblend_openmp.exe/enfuse_openmp.exe

These executables can utilize several cores of modern multi-core processors and are therefore significantly faster on modern processors. But they may fail on very big images because they are working without the image cache. In this case, please switch to the standard version.
For running the OpenMP variants you will need [http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en "Microsoft Visual C++ 2008 Redistributable Package (x86)"].

3. enblend_nosse.exe/enfuse_nosse.exe

If you have an old CPU without [http://en.wikipedia.org/wiki/SSE2 SSE2] support, you want a NOSSE build. This is the least performing version.
You will need to download a separate package to get this version from [http://sourceforge.net/projects/enblend/files/enblend-enfuse/enblend-enfuse-4.0/enblend-enfuse-4.0-win32-nosse.zip/download sourceforge.net]

All three variants can utilize a modern graphic card to accelerate the optimizing of the seam line between two images. To use this feature supply the parameter --gpu to enblend.

=== Selecting right version of enblend-enfuse binary for Debian/Ubuntu ===

At the time of writing the official Debian/Ubuntu package ships with one executable only, however in July 2010 a change has been committed to debian-unstable that delivers two binaries:

1. enblend/enfuse

These executables are the standard release. They are using one processor core and the image cache for processing very big images.

2. enblend_mp/enfuse_mp

These executables can utilize several cores of modern multi-core processors and are therefore significantly faster on modern processors. But they may fail on very big images because they are working without the image cache.

Both variants can utilize a modern graphic card to accelerate the optimizing of the seam line between two images. To use this feature supply the parameter --gpu to enblend.

== Support ==

=== Reporting Bugs ===

If you think you have found a bug in Hugin, please report it to help us make Hugin better. Before reporting a bug, try a few things to make sure it is really a bug. Then collect the following information and transmit it to the developers via the bug tracker.
# What version of Hugin are you using? Consider upgrading and try to reproduce the bug. Maybe it was fixed in a more recent version.
# read the output log. Are there any suggested actions or messages in there? If so, follow the advice and try again. Save the output log to a text file and attach it to the report if you file a bug report.
# Attach the .pto file to the bug report.
# Use a meaningful title for the bug report. The line reporting the error in the output log is a good place to start. Before filing a new bug report, check for duplicates. Launchpad does already a little bit so. If the bug is already known, add yourself and you files with a comment to the bug. This will give your report and your log more visibility than if somebody looking at your bug has to mark it as duplicate.

=== Why is my Bug Report marked Invalid? ===

We trust you that you are experiencing the issue on your end and that it bugs you, but most likely the solution lies not in the Hugin codebase. If you feel that your report has been marked Invalid by mistake, feel free to reply and to set the status back to New for a re-evaluation. Somebody may explain to you why the report was marked as Invalid and what you can do.

=== Why is my Bug Report marked Incomplete? ===

Every system is different and those trying to help fixing the bugs do not see and experience what you do. In order to help you, they are likely to need more information. Without that information the bug report is of little use. We mark as Incomplete reports that require additional information. Once you provide it, please mark the report status as New again

=== How do I Change the Status of my Report? ===

* If you reply via the web interface: hit the yellow round button next to the current status to get a selection of stati. Unless you know what you are doing, set it to New to attract developer's attention.
* If you reply by email: at the bottom of your email enter a line starting with one single space and the following words: <code> status new</code>. Read more about the [https://help.launchpad.net/Bugs/EmailInterface email interface].

=== User Support: Mailing List ===

Hugin has a lively and friendly user groups. Connect with expert users and ask questions on the Hugin-PTX mailing list. To subscribe send an empty email to hugin-ptx+subscribe@googlegroups.com and follow the instructions in the email you receive back.
To ask questions, send an email to hugin-ptx@googlegroups.com
Your first emails will be moderated, so be patient if you don't see your message right away.

[[Category:Software:Hugin]]

Hugin FAQ

2012-03-30T15:22:40Z

Zarl: /* What is Python Scripting? */ typo

== Common error messages ==

=== enblend: no input files specified ===

There are no input images relevant to the output 'panorama' so hugin had nothing to do, probably because all the input images are outside the panorama 'frame' or disabled. Open the [[Hugin Preview window]] or [[Hugin Fast Preview window]] to adjust the view, enable some images inside the panorama frame and/or adjust the crop.

Note also that hugin versions up to and including 2009.2.0 allow you to draw an inverted crop frame where the top is below the bottom, this is easy to see in the Preview window as the entire panorama is 'greyed'. A crop frame drawn like this will result in an empty panorama and the above error message.

=== enblend: excessive overlap detected ===

This is an error new to enblend-4.0. Photos that nearly entirely overlap won't blend very well, enblend now fails instead of attempting to blend them. There are various workarounds:

* Follow the error message and remove the suggested image from the set, you probably don't need it to complete the panorama.
* Switch back to enblend-3.2.
* Hugin will merge stacked images before blending if you select 'Exposure fusion' in the [[Hugin Stitcher tab]]. This error will go away, but Hugin will take a very different approach to variable exposure between photos.
* Mask out major parts of one image.

=== enblend: error writing to image swap file ===

[[enblend]] needs a lot of memory and uses its own swap routine to store picture data on the disk, this message indicates that you have run out of disk space. The data is stored in the system temp folder which is specified by TMP, TEMP or TMPDIR environment variables, note that this temp folder may be on a different physical disk to your photos and panorama output.

=== execvp(make ...) failed with error 2 ===

Hugin requires the 'make' utility to stitch, you need to install it and/or report the problem to whoever supplied Hugin to you.

=== false --compression NONE ===

This error is caused by a bug in the 0.7.0 release that is fixed in 0.8.0. The problem is that your preferences are messed-up, the workaround for 0.7.0 is to go to File -> Preferences -> Enblend and click Load Defaults -> Yes -> Ok

=== Enblend error: Mask is entirely black, but white image was not identified as redundant ===

This is a well known "error" for [[enblend]]. Try to use the additional enblend parameter "--fine-mask" to get rid of the error. The parameter will result in generation of masks in higher resolution that will fix the problem in most cases. Sometimes the "--fine-mask" parameter may result in memory errors (malloc: ...), which are the result of not enough memory available due to the (much) bigger masks that are used.

An alternative workaround would be to set the enblend --no-optimize parameter, this will place the seam directly along the middle of the image overlaps regardless of image content. This option is also considerably faster and uses less memory.

This error also occurs when one photo is completely covered by another, try removing redundant photos.

Note also that for the same reasons this error often appears when rendering a scene with extreme distortion such as a stereographic 'little planet'. For this and other reasons, such as overall speed, it is always preferable to render a 'normal' 360° [[Equirectangular Projection]] panorama first, then load this as a single source image into a new project and render whatever views you need.

Note (Jan 2010): This should be fixed in the latest [[enblend]] 4.0 release.

=== enblend: illegal option -- compression ===

hugin 0.7.0 and later versions require at least [[enblend]] version 3.2. This error indicates that you need to upgrade enblend.

=== enblend: Error -1073741795 ===

See [[#Enblend: The system cannot execute the specified command]], in particular if you are a Windows user try switching to the 'nosse' enblend-enfuse.

=== Makefile: target pattern contains no % ===

This is a message generated by [[w:Make_(software)]] (which [[Hugin]] uses to manage the stitching sequence). The error is caused by a ''':''' or '''#''' character in one of the file paths. The workaround is to rename to remove any 'special' shell characters and try again.

=== gnumake: *** No rule to make target ===

This is a message generated by [[w:Make_(software)]] (which [[Hugin]] uses to manage the stitching sequence). The error is caused by a ''':''' or '''#''' character in one of the file paths. The workaround is to rename to remove any 'special' shell characters and try again.

=== nona: GL error: Framebuffer incomplete, incomplete attachment in: ===

This is a message generated by nona when using the GPU for stitching (feature available starting with Hugin-2009.2.0). See section below about [[#GPU-stitching_.28nona.29|GPU-stitching]].

=== make: enfuse: command not found ===

This is a message generated by make when assembling your panorama. It most likely means that enfuse is not on your computer. Enfuse is part of the enblend package, but many Linux distributions, even recent ones, ship with an older version of enblend that does not contain enfuse. You need to install enblend-3.2 or later.

=== Enblend: The system cannot execute the specified command ===

This message could be generated by either
* the lack of Microsoft Visual C++ 2008 Redistributable Package (x86) that is necessary to run an OpenMP enabled version of Enblend. Download [http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en here].
* the lack of [http://en.wikipedia.org/wiki/SSE2 SSE2] support. Use a non-SSE build of Enblend. See also [[#Enblend-Enfuse_OpenMP_SSE_GPU:_which_one_is_the_right_one_for_me.3F | types of Enblend-Enfuse binaries]] or [[#Selecting_right_version_of_enblend-enfuse_binary_for_Windows | types of Enblend-Enfuse binaries for Windows ]]

===Windows error message "application configuration is incorrect"===

Double clicking the Hugin icon to run the program produces a message like this:
<pre>
C:\Program Files\Hugin\bin\hugin.exe
This application has failed to start because the application configuration is incorrect.
Reinstalling the application may fix this problem.
</pre>
Try installing the [http://www.microsoft.com/downloads/en/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en Microsoft Visual C++ redistributable].

=== Stitching fails on Windows (syntax error)===

If the stitching step fails on windows with a error message like

<pre>
/usr/bin/sh: -c: line 1: syntax error near unexpected token `(6'
/usr/bin/sh: -c: line 1: `echo Operating System: Windows 7 (6.1 )'
make: *** [info] Error 258
</pre>

or

<pre>
Syntax error: "(" unexpected
make: *** [info] Error 2
</pre>

then you have probably an other shell (e.g. sh.exe or bash.exe) somewhere in your path. In this case remove the path to this executable from the PATH variable.

=== Hugin Quits (Seg Faults) at Launch (Linux) ===

There may be many reasons why a program dies before it has even started.

One possibility is bad configuration or installation of the video drivers. See this [https://bugs.launchpad.net/hugin/+bug/679427 ticket]. To diagnose, try running glxgears. On Ubuntu (the package is probably available on most Linux distributions):

<pre>
sudo apt-get mesa-utils
glxgears
</pre>

If glxgears does not run on your system, Hugin will not run either. See your Linux distribution's instruction on how to fix the video drivers.

== Known Limitations ==

=== Linux: Compiz ===

Linux: Compiz interferes with the [[hugin Fast Preview window]]. This is not a hugin specific issue. Research shows all direct rendered stuff will have various problems under Compiz: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/96991

This problem is fixed with DRI2, e.g with fedora 11 and intel graphics hardware you can have a 'wobbly' Fast Preview window if you really want.

It's not an issue with NVidia's proprietry driver.

If you're affected, the workaround is to not use Compiz.

=== Windows: International Characters in Path ===

Hugin is fully internationalised and can cope with special characters in file paths. However, hugin apparently fails on some Windows systems with Polish, Japanese, Russian or Czech codepages, the workaround is to use shell-safe ascii characters in file and folder names: '''A B C D E F G H I J K L M N O P Q R S T U V W X Y Z a b c d e f g h i j k l m n o p q r s t u v w x y z 0 1 2 3 4 5 6 7 8 9 - _ .''' This includes the path for the temporary folder which is named after your username on Windows systems.

=== OSX: error when clicking on the help button ===

In a language other than English, French or Italian you get an error message when clicking on the help button. This will be fixed in Hugin-2009.4.0. In the meantime, the work around is to change language to one of the above three; or to ask for help on the mailing list.

=== Non-Unique Filenames ===

Some components of Hugin have been reported not to deal well with image files
that have the same name in different folders. The workaround is to rename
your images files so that all image files in a project are unique.

=== Temporary Files ===

Hugin has a preference setting for the temporary files folder. Currently it
is not implemented properly and files will be written in the same folder as
the project file.

A partial workaround on Linux is to start Hugin from a terminal with
<pre>
TMPDIR=/media/disk-2/tmp hugin &
</pre>

A workaround on Windows is to create a batch file which sets the temp folder before running Hugin.
eg using notepad, create a file called HuginWithNewTemp.cmd with the following in it:
<pre>
REM Create a folder on C Drive called Temp for this to work

REM Set the temp file environment variables for hugin
set temp=c:\temp
set tmp=c:\temp

REM run hugin
"C:\Program Files\Hugin\bin\hugin.exe
</pre>

These temporary files have to be deleted manually after the stitch.

=== Special Characters in Paths ===

{| style="margin: 1em auto 1em 1em;background:#FFFF99;color:#FF0000;text-align:left;border: solid #FF3300;"
|-valign="top"
! =
! ;
! :
! $
! "
! %
! #
! |
! '
! (
! )
! `
! &
! *
! +
! ^
! ~
! <
! ?
! >
! and the space character.
|}

Hugin currently does not do plausibility checks on the paths and file names that are given to it. It relies on the operating system's conventions and limitations. However Hugin uses [http://en.wikipedia.org/wiki/Make_%28software%29 make] to run the stitching process, and make has more restrictive limitations than the operating system.

Please don't use the above characters in your files and folders when you want to make sure they work with Hugin. If you absolutely need files named this way, rename them after processing. Do not file bug reports based on filenames with the above characters. The [https://sourceforge.net/tracker/?func=detail&atid=550441&aid=2883450&group_id=77506 issue] is known, analyzed, and may be fixed in the future.

=== Stitch fails when '&' is part of the Windows ''user-name'' ===

This is a variant of the above, but more difficult to work around. The ''user-name'' is part of all paths in the user's data area, including the temporary file locations defined by TMP and TEMP. Stitch fails almost immediately with a make path error.

Work-around: See the Temporary Folders section above, or Move your hugin data to a folder in the root directory such as C:\hugin. Then go to the Windows Control Panel and change ''System, Advanced, Environment, user TMP'' to a folder in the root, such as 'C:\temp' (create it if necessary).

Notes: This work-around probably needs Win 7 ''Administrator'' privileges.

A simpler solution should be to set hugin ''File, Preferences, Temporary dir'' to C:\hugin; but it doesn't fix
the problem! Seemingly, at least one temporary file still gets created in the TMP folder.

=== Hugin fails stitching some stereographics and other polar projections ===

This is a known limitation caused by photos being distorted into extreme 'C' and 'O' shapes. The workaround: stitch all of your pictures into a single equirectangular, and then load the equirectangular into Hugin to generate the stereographic or other projections you wanted to do in the first place.

=== OS X / iPhoto ===

Dragging the photos from iPhoto to Hugin works perfectly as long as there is no forward slash in the Name of the events in iPhoto (which translates to folders inside the iPhoto Database).

=== Fast Preview ===

Why are there two preview windows, and which one should I use?

For most purposes, the newer Fast Preview window is faster. However it is still under development and sometimes shows artefacts. The old preview still does a logarithmic tone mapping of stacked
images and is the only way to preview hdr or fused output.

=== Makefile based stitching process ===

Can I restart a stitching process that was interrupted manually or by an error without starting everything from scratch?

Unfortunately the Hugin Makefile system only supports restarting if you stitch on the command-line. The GUI tools always create new temporary .pto project and Makefile files every time they stitch, so this forces make to recreate everything for every stitch.

=== Patching nadir shots using XYZ mosaic mode cuts the photos in half ===

"If an image is mapped to the [[nadir]] of a panorama and all translation parameters (X,Y,Z) are set to zero, the image is properly mapped and covers the entire nadir of the shot. However, if any of the X,Y,Z parameters are non-zero, then the image is cut in half and only occupies half of the nadir."

Basically the XYZ mosaic mode as it is implemented currently in [[Hugin]] requires that the mosaic photos must be mapped to a plane perpendicular to the view direction - In practice this means that what you are trying to do only works if the panorama is rotated such that the nadir is in the middle of the canvas and not at the bottom.

This isn't so bad, the nadir-in-the-middle image looks a bit weird, you can just reload the stitched [[equirectangular Projection]] result into a new single-photo project and straighten it there.

== Python Scripting ==

=== What is Python Scripting? ===

Python is a powerful scripting language. Starting with Hugin 2011.2, Hugin exposes the panorama object through hsi.py in Python. It must be explicitly activated at build time with the CMake boolean parameter -DBUILD_HSI:BOOL=ON. It is currently untested / unavailable on OS X.

=== How do I start Scripting? ===

<pre>
$ python
Python 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53)
[GCC 4.5.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import hsi
>>> help (hsi)
</pre>

=== What is the difference between a Plugin and a Script? ===

Strictly speaking, they are both Python scripts. A Plugin runs inside Hugin, while a Script runs in a shell or desktop.

=== Where Are the Plugins in Hugin and how do I use them? ===

If Hugin was compiled with HSI, a menu Action will list categories of system-wide plugins. Just select one to run it. Moreover, you can write your own plugins and run them with the menu Edit -> Run User Python Plugin. The default location for user plugins is set in the preferences.

=== Script Returned -10 ===

This error message indicates that the plugin tried to import something and failed. hpi.py currently has no other way of telling hugin what's wrong than to 'return -10'. Try to start Hugin from the command line and see if there is more verbose output there. Copy the output and ask for help on hugin-ptx.

=== Script Returned -11 ===

The plugin failing with an exception. Ask the plugin maintainer to produce more specific error messages. It is good practice to catch such exceptions and let the user know what dependency is missing.

=== Why do I read of users having access to a certain action and I don't see it on my system? ===

Some actions only work with specific versions of Hugin or operating systems. It is possible that they have a different system than yours and that the plugin in question does not support your system. Often times this is just a matter of lack of testing resources on a particular platform. Help test the plugin and it may become accessible on your system as well.

== Control Point creation ==

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

1. Selecting control points in 100% zoom.

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

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

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

2. Selecting control points in fit to window mode.

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

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

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

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

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

=== How do I stop Hugin pausing for a moment after every click? ===

The ''preview window'' updates continuously whenever anything changes, so disable the preview auto-update, close it or make it smaller if you don't need it.

Otherwise, picking [[control points]] with ''auto fine tune'' selected can involve a lot
of processing. You can reduce this by ''selecting File -> Preferences -> Finetune'' and
lowering the values for ''Patch width'', ''Search area width'' and ''Local search area width''.
This means you can't be so sloppy when clicking to create control points, but the results will
be the same.

=== Windows: when user is not admin, not all cp-creators are available to choose from ===

Preferences are stored in the registry on Windows. Every users has their own. To have all the cp-creator pre-sets like the admin users, hit the "Load defaults" button on the Control Points tab in the Preferences dialog.

=== cpfind: not enough control points generated ===

Cpfind is a recent addition to the Hugin suite and its parameters still require some fine tuning. Unlike older CP generators used with Hugin, it depends on information passed in the PTO file. Make sure that your input project file contains reasonable information about the used lens. If you are using a fisheye or wide angle lens, try increasing the parameters --sieve1width --sieve1height --sieve1size. A combinations that may work is "--sieve1width 50 --sieve1height 50 --sieve1size 300". Sometimes also the option "--fullscale" might help. Read the [[Cpfind]] documentation.

== Common problems when creating a panorama ==

=== I get thin horizontal black or white lines in large panoramas ===

This is a known bug in the memory handling of [[enblend]] that manifests with large panoramas.

You can workaround it by reducing the size of the panorama, or by adjusting the cache size in [[Hugin_Stitcher_tab]] -> '''Blender options'''. e.g. the default is 1024MB (1 GB), so if you have 4GB RAM you can try raising the cache to use most of your free memory, such as 3000MB, i.e: ''-m 3000''

=== The Control Points tab shows my photos rotated ===

The rotation of photos in the [[Hugin Control Points tab]] isn't necessarily
related to the orientation of the files themselves.

Hugin shows photos at the angle they best fit into the panorama, so if the
panorama fit is bad, then you will see strange angles in the Control Points
tab. Probably the problem is caused by bad alignment, you can
identify 'bad' [[Control points]] in the [[Hugin Control Points table]], delete them and re-optimise.

=== How can I reuse a project as a template? ===

If you copy a .pto project to a different folder and open it with hugin, you will be prompted for the 'missing' images. You should delete any control points from this template project since they won't be relevant to the new photos.

Alternatively you can load your images as normal, then ''Apply template''
from the ''File'' menu, this will import image settings and parameters
from a previous project.

=== How do I straighten a curved horizon? ===
If the panorama looks nice but the horizon is curved, there are various ways to improve the image and straighten the horizon.

First, try clicking the '''Straighten''' button in the [[Hugin Fast Preview window]].

If this doesn't work then you can use the Move/Drag tab of the [[Hugin Fast Preview window]] to visually straighten the panorama, drag the photos with the mouse, use the right mouse button to rotate. One useful tip is to drag the panorama so a vertical feature is in the middle, rotate it so the feature lines up with the 'cross hair', then drag the panorama up or down until all the vertical features in the scene are vertical on the screen (holding down the shift key while dragging limits the motion to just up/down or left/right).

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

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

=== Half the panorama is black, my pictures fill only the right half of the output ===

Hugin uses the first photo as the ''anchor'' image and puts it in the middle by default. This means that if you shot a sequence from left to right, the images will fill the right hand side of the panorama. There are three ways to fix this:

* Open the '''preview''' window and click the '''center''' button.
* or select the middle photo, hit '''anchor this image for position''' and '''reset''' in the '''images''' tab, then reoptimise.
* In the 'Fast Panorama Preview' window select 'Drag'. Left mouse drags the image, right mouse rotates the image.

=== I get visible bands in the sky and other flat areas, what can I do? ===

If the banding looks like [[w:Posterization|posterization]] then this is likely due to a error with estimation of the [[camera response curve]]. To get an accurate response curve, Hugin needs significant [[vignetting]] and/or [[bracketing|bracketed exposures]]. The workaround is to '''Reset...''' the '''Camera Response''' in the [[Hugin Camera and Lens tab]] and stitch again - [[Hugin]] usually produces acceptable results for a simple panorama when the camera response parameters are all zero.

If there is a wave of light and dark patches in the sky this could be due to [[vignetting]] in the source photos, you can deal with this by optimising '''Vignetting (Vb, Vc, Vd)''' in the [[Hugin Exposure tab]]. Another workaround is to increase the number of [[enblend]] blending levels, try setting '-l 29' as the enblend '''Command line options''' in the [[Hugin Stitcher tab]].

=== My photos never quite line up, what can I do? ===

It is normal to get little stitching [[parallax]] errors if
the camera moves between photos. The solution is to rotate the camera around
the [[no-parallax point]] using a [[Heads|panoramic head]] or [[philopod]].

Otherwise you can sometimes improve things by optimising the ''d & e'' parameters
separately - When you optimise '''everything''', unselect '''Inherit''' in
the '''camera and Lens''' panel for 'd & e'. Also you can open the control point window sort it by distance and check the ones large distance.

If these parallax errors are still large, you need to decide which
parts of the scene that you want to line-up and which parts don't
matter. Select [[control points]] only on objects that you do want to
line-up and which are all about the same distance from the camera.

The remaining broken lines can then be retouched in a photo editor like the [[gimp]].
The ''shear'' tool is ideal for bending the lines and
[[Mending parallax errors with the shear tool|getting them to line up]].

=== I have extracted and edited cubefaces and want to merge them together again. How do I do that ? ===

Manually enter the values for [[yaw]] and [[pitch]] for each of the photos. When you stitch set the '''enblend options''' in the [[Hugin Stitcher tab]] to -l1 --fine-mask --no-optimize

=== Can I stitch my HDR images ? ===

Yes. If you already have merged your HDR stacks, follow the '''Normal''' Output on the '''Stitcher''' tab ('''HDR merging''' is for stacks that will be merged by Hugin). In the '''Processing''' step the output will be an HDR in TIFF format.

=== Why is my panorama upside down ? ===

Hugin stitches the panorama on a sphere and can't determine what is up or what is down. Even if vertical control points are assigned, there is still no notion of up and down, so the panorama can flip upside down. The solution for that is to open the Preview window, click on the Num. Trans. button in the toolbar, enter 180 in the roll field and apply. This will flip the panorama back to the right orientation.

=== Why do multi-lens projects end up distorted/broken? ===

You have probably optimized 'Everything'. This will cause the optimizer to try to optimize lens parameters for each of the different lenses, and there may not be a big enough spread of control points for the optimization to work well.
When stitching photos from different lenses, or when you don't have a good spread of control points, optimize 'Position, view & Barrel (y,p,r,v,b).

=== Why does my output covers only 180°? ===

Did you observe that the output is cropped at the +-90° borders? (e.g. saw teeth like borders in the fast preview window)

Then you have probably used the translation parameters X/Y/Z. This behaviour is a fundamental limitation of the used approach of the translation parameters. It is (internal) working in the rectilinear space, which is limited to maximal FOV of 180°, and therefore also the output is limited to FOV<180° (for more information see [[Stitching a photo-mosaic]]).

The solution/workaround is to set all X/Y/Z values to zero or to limit the horizontal field of view (HFOV) to a value smaller than 180°.

== GPU-stitching (nona) ==

Starting with Hugin-2009.2 nona has a new, experimental feature: it can use the video card (GPU) to accelerate the stitching. How much acceleration you will get, if any, depends on the combination of video card and driver.

=== I get a nona: GL error. Does this mean that I found a bug? ===

Not necessarily. This functionality is highly experimental. It may be that you have an outdated driver, or that the functionality is not supported on your video card. Note down the version of the driver you are using and the specs of your video card (GPU and RAM). Then update to the latest driver from [http://www.nvidia.com/page/drivers.html nVidia] or [http://support.amd.com/us/gpudownload/Pages/index.aspx AMD] (ATI has been bought by AMD). Currently only these two families of GPUs support the functionality.

=== How can I know if nona-GPU works on my system? ===

At the moment we have too little information to predict this. We know that only nVidia and AMD(ATI) powered video cards work, and not all of them. The more recent the video card, the higher the likelihood that it works. Improve your chances by updating to the latest driver for your GPU. Look at experience reports from other users and report your experience [[Nona GPU stitching reports|here]].

=== What speed improvement can I expect? ===

It depends on the video card. Bandwidth is mostly the bottleneck, specifically getting the transformed data from the GPU back to the main system memory.

=== Bug Reporting ===

When reporting success or failure using the GPU for stitching, always report also the driver version, video card GPU and RAM. Tell us what you were doing, the size and number of input images (note that if you stitch from within Hugin or PTBatcher, it is only one input image at a time).

== Postprocessing ==

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

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

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

* Use the [[nona]] stitcher on the command-line, to output to a multilayer [[TIFF]] format:

nona -m TIFF_multilayer -o multi_layer.tif project.pto

This will will produce a multi_layer.tif file, that contains all remapped images, cropped to their bounding box.

* Alternatively select the '''Remapped Images''' option in the [[Hugin Stitcher tab]], this will create each ''layer'' as a separate file. Then use the '''tiffcp''' command-line tool (part of libtiff) to join them together into a multi-page TIFF:

tiffcp project0000.tif project0001.tif project0002.tif multi_layer.tif

* You can also use [[tif2xcf]], to combine the '''Remapped Images''' TIFF output into a multilayer XCF.
Unfortunately this requires a lot of memory because it stores each remapped image in a layer with the size of the final panorama.

== Installation ==

=== Where can I download hugin installers ===

Official releases are available from [http://hugin.sourceforge.net/download/ hugin.sf.net].

=== How can I compile Hugin.app on my OSX machine? ===

See [[Hugin Compiling OSX]], [[Autopano-sift-C Compiling OSX]] and [[Enblend Compiling OSX]].

=== How do I compile hugin on my linux machine? ===

See [[Hugin Compiling Fedora]], [[Hugin Compiling Gentoo]], [[Hugin Compiling OpenSuse]] and [[Hugin Compiling Ubuntu]]

=== make[2]: *** No rule to make target `/usr/lib/libGL.so', needed by `src/hugin_base/libhuginbase.so.0.0'. Stop. ===

So you're trying to build from source. Most likely you have proprietary nVidia or ATI drivers. They are a moving target and so is X. On debian based systems including Ubuntu, diagnose with `dpkg -S /usr/lib/libGL.so` and check that the linked library exist (i.e. it is not listed in red when doing `ll /usr/lib/mesa/libGL.so`). If it is listed in red, check where the library is (`ll /usr/lib/libGL*` is a good start on Ubuntu) and link it properly.

=== How do I compile hugin on my Windows machine? ===

See [[Hugin Compiling Windows]]

=== Enblend-Enfuse OpenMP SSE GPU: which one is the right one for me? ===

Enblend and Enfuse can be optimized at build time for different hardware configurations. This yields four categories of Enblend-Enfuse builds, with a few variations. If you build Enblend-Enfuse from source, check the build options in the README file. If you download a binary, you can find out how it has been built with the following command:

enblend -v -V

look for the following in the output text:

# '''Extra feature: OpenMP: yes''' this version has OpenMP.
# '''Extra feature: image cache: yes''' this version has image cache
# '''Extra feature: GPU acceleration: yes''' this version has GPU support
# SSE-support is not mentioned, you'll find out if you have an unsupported CPU and the binary will refuse to run.

These are approximate guidelines to help you choose what may work for you:

* if you have a recent, multi-core / multi-thread CPU, you probably want the OpenMP-enabled version. Note however that speed improvement does not scale well, so don't expect a 6 cores CPU to be 3x faster than a 2 cores one.
* if you have a recent, fast video card, you probably want the GPU-enabled version. This is not mutually exclusive with OpenMP and a good builder will add both features to his binaries. If speed is important to you, you want to test which of the two is faster on your system. If system responsiveness is important to you, the GPU-enabled version frees CPU resources for your other tasks. Note that even if your binary is GPU-enabled, the GPU will not be used unless you specify the option `--gpu`.
* if you have an old CPU without SSE2 support, you want a NOSSE build. This is the least performing version.
* Last but not least, if blending fails because of large images, try the image cache variation. The image cache allows for processing of large project when memory is scarce but images are large (and disk is large enough too). Image cache is incompatible with OpenMP, but a good bilder will make this version GPU-enabled too, so test it with `--gpu` if speed is important.

=== Selecting right version of enblend-enfuse binary for Windows ===

There are 3 variants of enblend-enfuse binaries officially released for Windows. Each one has a special feature set:

1. enblend.exe/enfuse.exe

These executables are the standard release. They are using one processor core and the image cache for processing very big images.

2. enblend_openmp.exe/enfuse_openmp.exe

These executables can utilize several cores of modern multi-core processors and are therefore significantly faster on modern processors. But they may fail on very big images because they are working without the image cache. In this case, please switch to the standard version.
For running the OpenMP variants you will need [http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en "Microsoft Visual C++ 2008 Redistributable Package (x86)"].

3. enblend_nosse.exe/enfuse_nosse.exe

If you have an old CPU without [http://en.wikipedia.org/wiki/SSE2 SSE2] support, you want a NOSSE build. This is the least performing version.
You will need to download a separate package to get this version from [http://sourceforge.net/projects/enblend/files/enblend-enfuse/enblend-enfuse-4.0/enblend-enfuse-4.0-win32-nosse.zip/download sourceforge.net]

All three variants can utilize a modern graphic card to accelerate the optimizing of the seam line between two images. To use this feature supply the parameter --gpu to enblend.

=== Selecting right version of enblend-enfuse binary for Debian/Ubuntu ===

At the time of writing the official Debian/Ubuntu package ships with one executable only, however in July 2010 a change has been committed to debian-unstable that delivers two binaries:

1. enblend/enfuse

These executables are the standard release. They are using one processor core and the image cache for processing very big images.

2. enblend_mp/enfuse_mp

These executables can utilize several cores of modern multi-core processors and are therefore significantly faster on modern processors. But they may fail on very big images because they are working without the image cache.

Both variants can utilize a modern graphic card to accelerate the optimizing of the seam line between two images. To use this feature supply the parameter --gpu to enblend.

== Support ==

=== Reporting Bugs ===

If you think you have found a bug in Hugin, please report it to help us make Hugin better. Before reporting a bug, try a few things to make sure it is really a bug. Then collect the following information and transmit it to the developers via the bug tracker.
# What version of Hugin are you using? Consider upgrading and try to reproduce the bug. Maybe it was fixed in a more recent version.
# read the output log. Are there any suggested actions or messages in there? If so, follow the advice and try again. Save the output log to a text file and attach it to the report if you file a bug report.
# Attach the .pto file to the bug report.
# Use a meaningful title for the bug report. The line reporting the error in the output log is a good place to start. Before filing a new bug report, check for duplicates. Launchpad does already a little bit so. If the bug is already known, add yourself and you files with a comment to the bug. This will give your report and your log more visibility than if somebody looking at your bug has to mark it as duplicate.

=== Why is my Bug Report marked Invalid? ===

We trust you that you are experiencing the issue on your end and that it bugs you, but most likely the solution lies not in the Hugin codebase. If you feel that your report has been marked Invalid by mistake, feel free to reply and to set the status back to New for a re-evaluation. Somebody may explain to you why the report was marked as Invalid and what you can do.

=== Why is my Bug Report marked Incomplete? ===

Every system is different and those trying to help fixing the bugs do not see and experience what you do. In order to help you, they are likely to need more information. Without that information the bug report is of little use. We mark as Incomplete reports that require additional information. Once you provide it, please mark the report status as New again

=== How do I Change the Status of my Report? ===

* If you reply via the web interface: hit the yellow round button next to the current status to get a selection of stati. Unless you know what you are doing, set it to New to attract developer's attention.
* If you reply by email: at the bottom of your email enter a line starting with one single space and the following words: <code> status new</code>. Read more about the [https://help.launchpad.net/Bugs/EmailInterface email interface].

=== User Support: Mailing List ===

Hugin has a lively and friendly user groups. Connect with expert users and ask questions on the Hugin-PTX mailing list. To subscribe send an empty email to hugin-ptx+subscribe@googlegroups.com and follow the instructions in the email you receive back.
To ask questions, send an email to hugin-ptx@googlegroups.com
Your first emails will be moderated, so be patient if you don't see your message right away.

[[Category:Software:Hugin]]

Hugin FAQ

2012-03-30T15:22:18Z

Zarl: /* OSX / iPhoto */ typo in headline

== Common error messages ==

=== enblend: no input files specified ===

There are no input images relevant to the output 'panorama' so hugin had nothing to do, probably because all the input images are outside the panorama 'frame' or disabled. Open the [[Hugin Preview window]] or [[Hugin Fast Preview window]] to adjust the view, enable some images inside the panorama frame and/or adjust the crop.

Note also that hugin versions up to and including 2009.2.0 allow you to draw an inverted crop frame where the top is below the bottom, this is easy to see in the Preview window as the entire panorama is 'greyed'. A crop frame drawn like this will result in an empty panorama and the above error message.

=== enblend: excessive overlap detected ===

This is an error new to enblend-4.0. Photos that nearly entirely overlap won't blend very well, enblend now fails instead of attempting to blend them. There are various workarounds:

* Follow the error message and remove the suggested image from the set, you probably don't need it to complete the panorama.
* Switch back to enblend-3.2.
* Hugin will merge stacked images before blending if you select 'Exposure fusion' in the [[Hugin Stitcher tab]]. This error will go away, but Hugin will take a very different approach to variable exposure between photos.
* Mask out major parts of one image.

=== enblend: error writing to image swap file ===

[[enblend]] needs a lot of memory and uses its own swap routine to store picture data on the disk, this message indicates that you have run out of disk space. The data is stored in the system temp folder which is specified by TMP, TEMP or TMPDIR environment variables, note that this temp folder may be on a different physical disk to your photos and panorama output.

=== execvp(make ...) failed with error 2 ===

Hugin requires the 'make' utility to stitch, you need to install it and/or report the problem to whoever supplied Hugin to you.

=== false --compression NONE ===

This error is caused by a bug in the 0.7.0 release that is fixed in 0.8.0. The problem is that your preferences are messed-up, the workaround for 0.7.0 is to go to File -> Preferences -> Enblend and click Load Defaults -> Yes -> Ok

=== Enblend error: Mask is entirely black, but white image was not identified as redundant ===

This is a well known "error" for [[enblend]]. Try to use the additional enblend parameter "--fine-mask" to get rid of the error. The parameter will result in generation of masks in higher resolution that will fix the problem in most cases. Sometimes the "--fine-mask" parameter may result in memory errors (malloc: ...), which are the result of not enough memory available due to the (much) bigger masks that are used.

An alternative workaround would be to set the enblend --no-optimize parameter, this will place the seam directly along the middle of the image overlaps regardless of image content. This option is also considerably faster and uses less memory.

This error also occurs when one photo is completely covered by another, try removing redundant photos.

Note also that for the same reasons this error often appears when rendering a scene with extreme distortion such as a stereographic 'little planet'. For this and other reasons, such as overall speed, it is always preferable to render a 'normal' 360° [[Equirectangular Projection]] panorama first, then load this as a single source image into a new project and render whatever views you need.

Note (Jan 2010): This should be fixed in the latest [[enblend]] 4.0 release.

=== enblend: illegal option -- compression ===

hugin 0.7.0 and later versions require at least [[enblend]] version 3.2. This error indicates that you need to upgrade enblend.

=== enblend: Error -1073741795 ===

See [[#Enblend: The system cannot execute the specified command]], in particular if you are a Windows user try switching to the 'nosse' enblend-enfuse.

=== Makefile: target pattern contains no % ===

This is a message generated by [[w:Make_(software)]] (which [[Hugin]] uses to manage the stitching sequence). The error is caused by a ''':''' or '''#''' character in one of the file paths. The workaround is to rename to remove any 'special' shell characters and try again.

=== gnumake: *** No rule to make target ===

This is a message generated by [[w:Make_(software)]] (which [[Hugin]] uses to manage the stitching sequence). The error is caused by a ''':''' or '''#''' character in one of the file paths. The workaround is to rename to remove any 'special' shell characters and try again.

=== nona: GL error: Framebuffer incomplete, incomplete attachment in: ===

This is a message generated by nona when using the GPU for stitching (feature available starting with Hugin-2009.2.0). See section below about [[#GPU-stitching_.28nona.29|GPU-stitching]].

=== make: enfuse: command not found ===

This is a message generated by make when assembling your panorama. It most likely means that enfuse is not on your computer. Enfuse is part of the enblend package, but many Linux distributions, even recent ones, ship with an older version of enblend that does not contain enfuse. You need to install enblend-3.2 or later.

=== Enblend: The system cannot execute the specified command ===

This message could be generated by either
* the lack of Microsoft Visual C++ 2008 Redistributable Package (x86) that is necessary to run an OpenMP enabled version of Enblend. Download [http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en here].
* the lack of [http://en.wikipedia.org/wiki/SSE2 SSE2] support. Use a non-SSE build of Enblend. See also [[#Enblend-Enfuse_OpenMP_SSE_GPU:_which_one_is_the_right_one_for_me.3F | types of Enblend-Enfuse binaries]] or [[#Selecting_right_version_of_enblend-enfuse_binary_for_Windows | types of Enblend-Enfuse binaries for Windows ]]

===Windows error message "application configuration is incorrect"===

Double clicking the Hugin icon to run the program produces a message like this:
<pre>
C:\Program Files\Hugin\bin\hugin.exe
This application has failed to start because the application configuration is incorrect.
Reinstalling the application may fix this problem.
</pre>
Try installing the [http://www.microsoft.com/downloads/en/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en Microsoft Visual C++ redistributable].

=== Stitching fails on Windows (syntax error)===

If the stitching step fails on windows with a error message like

<pre>
/usr/bin/sh: -c: line 1: syntax error near unexpected token `(6'
/usr/bin/sh: -c: line 1: `echo Operating System: Windows 7 (6.1 )'
make: *** [info] Error 258
</pre>

or

<pre>
Syntax error: "(" unexpected
make: *** [info] Error 2
</pre>

then you have probably an other shell (e.g. sh.exe or bash.exe) somewhere in your path. In this case remove the path to this executable from the PATH variable.

=== Hugin Quits (Seg Faults) at Launch (Linux) ===

There may be many reasons why a program dies before it has even started.

One possibility is bad configuration or installation of the video drivers. See this [https://bugs.launchpad.net/hugin/+bug/679427 ticket]. To diagnose, try running glxgears. On Ubuntu (the package is probably available on most Linux distributions):

<pre>
sudo apt-get mesa-utils
glxgears
</pre>

If glxgears does not run on your system, Hugin will not run either. See your Linux distribution's instruction on how to fix the video drivers.

== Known Limitations ==

=== Linux: Compiz ===

Linux: Compiz interferes with the [[hugin Fast Preview window]]. This is not a hugin specific issue. Research shows all direct rendered stuff will have various problems under Compiz: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/96991

This problem is fixed with DRI2, e.g with fedora 11 and intel graphics hardware you can have a 'wobbly' Fast Preview window if you really want.

It's not an issue with NVidia's proprietry driver.

If you're affected, the workaround is to not use Compiz.

=== Windows: International Characters in Path ===

Hugin is fully internationalised and can cope with special characters in file paths. However, hugin apparently fails on some Windows systems with Polish, Japanese, Russian or Czech codepages, the workaround is to use shell-safe ascii characters in file and folder names: '''A B C D E F G H I J K L M N O P Q R S T U V W X Y Z a b c d e f g h i j k l m n o p q r s t u v w x y z 0 1 2 3 4 5 6 7 8 9 - _ .''' This includes the path for the temporary folder which is named after your username on Windows systems.

=== OSX: error when clicking on the help button ===

In a language other than English, French or Italian you get an error message when clicking on the help button. This will be fixed in Hugin-2009.4.0. In the meantime, the work around is to change language to one of the above three; or to ask for help on the mailing list.

=== Non-Unique Filenames ===

Some components of Hugin have been reported not to deal well with image files
that have the same name in different folders. The workaround is to rename
your images files so that all image files in a project are unique.

=== Temporary Files ===

Hugin has a preference setting for the temporary files folder. Currently it
is not implemented properly and files will be written in the same folder as
the project file.

A partial workaround on Linux is to start Hugin from a terminal with
<pre>
TMPDIR=/media/disk-2/tmp hugin &
</pre>

A workaround on Windows is to create a batch file which sets the temp folder before running Hugin.
eg using notepad, create a file called HuginWithNewTemp.cmd with the following in it:
<pre>
REM Create a folder on C Drive called Temp for this to work

REM Set the temp file environment variables for hugin
set temp=c:\temp
set tmp=c:\temp

REM run hugin
"C:\Program Files\Hugin\bin\hugin.exe
</pre>

These temporary files have to be deleted manually after the stitch.

=== Special Characters in Paths ===

{| style="margin: 1em auto 1em 1em;background:#FFFF99;color:#FF0000;text-align:left;border: solid #FF3300;"
|-valign="top"
! =
! ;
! :
! $
! "
! %
! #
! |
! '
! (
! )
! `
! &
! *
! +
! ^
! ~
! <
! ?
! >
! and the space character.
|}

Hugin currently does not do plausibility checks on the paths and file names that are given to it. It relies on the operating system's conventions and limitations. However Hugin uses [http://en.wikipedia.org/wiki/Make_%28software%29 make] to run the stitching process, and make has more restrictive limitations than the operating system.

Please don't use the above characters in your files and folders when you want to make sure they work with Hugin. If you absolutely need files named this way, rename them after processing. Do not file bug reports based on filenames with the above characters. The [https://sourceforge.net/tracker/?func=detail&atid=550441&aid=2883450&group_id=77506 issue] is known, analyzed, and may be fixed in the future.

=== Stitch fails when '&' is part of the Windows ''user-name'' ===

This is a variant of the above, but more difficult to work around. The ''user-name'' is part of all paths in the user's data area, including the temporary file locations defined by TMP and TEMP. Stitch fails almost immediately with a make path error.

Work-around: See the Temporary Folders section above, or Move your hugin data to a folder in the root directory such as C:\hugin. Then go to the Windows Control Panel and change ''System, Advanced, Environment, user TMP'' to a folder in the root, such as 'C:\temp' (create it if necessary).

Notes: This work-around probably needs Win 7 ''Administrator'' privileges.

A simpler solution should be to set hugin ''File, Preferences, Temporary dir'' to C:\hugin; but it doesn't fix
the problem! Seemingly, at least one temporary file still gets created in the TMP folder.

=== Hugin fails stitching some stereographics and other polar projections ===

This is a known limitation caused by photos being distorted into extreme 'C' and 'O' shapes. The workaround: stitch all of your pictures into a single equirectangular, and then load the equirectangular into Hugin to generate the stereographic or other projections you wanted to do in the first place.

=== OS X / iPhoto ===

Dragging the photos from iPhoto to Hugin works perfectly as long as there is no forward slash in the Name of the events in iPhoto (which translates to folders inside the iPhoto Database).

=== Fast Preview ===

Why are there two preview windows, and which one should I use?

For most purposes, the newer Fast Preview window is faster. However it is still under development and sometimes shows artefacts. The old preview still does a logarithmic tone mapping of stacked
images and is the only way to preview hdr or fused output.

=== Makefile based stitching process ===

Can I restart a stitching process that was interrupted manually or by an error without starting everything from scratch?

Unfortunately the Hugin Makefile system only supports restarting if you stitch on the command-line. The GUI tools always create new temporary .pto project and Makefile files every time they stitch, so this forces make to recreate everything for every stitch.

=== Patching nadir shots using XYZ mosaic mode cuts the photos in half ===

"If an image is mapped to the [[nadir]] of a panorama and all translation parameters (X,Y,Z) are set to zero, the image is properly mapped and covers the entire nadir of the shot. However, if any of the X,Y,Z parameters are non-zero, then the image is cut in half and only occupies half of the nadir."

Basically the XYZ mosaic mode as it is implemented currently in [[Hugin]] requires that the mosaic photos must be mapped to a plane perpendicular to the view direction - In practice this means that what you are trying to do only works if the panorama is rotated such that the nadir is in the middle of the canvas and not at the bottom.

This isn't so bad, the nadir-in-the-middle image looks a bit weird, you can just reload the stitched [[equirectangular Projection]] result into a new single-photo project and straighten it there.

== Python Scripting ==

=== What is Python Scripting? ===

Python is a powerful scripting language. Starting with Hugin 2011.2, Hugin exposes the panorama object through hsi.py in Python. It must be explicitly activated at build time with the CMake boolean parameter -DBUILD_HSI:BOOL=ON. It is currently untested / unavailable on OSX.

=== How do I start Scripting? ===

<pre>
$ python
Python 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53)
[GCC 4.5.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import hsi
>>> help (hsi)
</pre>

=== What is the difference between a Plugin and a Script? ===

Strictly speaking, they are both Python scripts. A Plugin runs inside Hugin, while a Script runs in a shell or desktop.

=== Where Are the Plugins in Hugin and how do I use them? ===

If Hugin was compiled with HSI, a menu Action will list categories of system-wide plugins. Just select one to run it. Moreover, you can write your own plugins and run them with the menu Edit -> Run User Python Plugin. The default location for user plugins is set in the preferences.

=== Script Returned -10 ===

This error message indicates that the plugin tried to import something and failed. hpi.py currently has no other way of telling hugin what's wrong than to 'return -10'. Try to start Hugin from the command line and see if there is more verbose output there. Copy the output and ask for help on hugin-ptx.

=== Script Returned -11 ===

The plugin failing with an exception. Ask the plugin maintainer to produce more specific error messages. It is good practice to catch such exceptions and let the user know what dependency is missing.

=== Why do I read of users having access to a certain action and I don't see it on my system? ===

Some actions only work with specific versions of Hugin or operating systems. It is possible that they have a different system than yours and that the plugin in question does not support your system. Often times this is just a matter of lack of testing resources on a particular platform. Help test the plugin and it may become accessible on your system as well.

== Control Point creation ==

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

1. Selecting control points in 100% zoom.

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

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

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

2. Selecting control points in fit to window mode.

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

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

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

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

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

=== How do I stop Hugin pausing for a moment after every click? ===

The ''preview window'' updates continuously whenever anything changes, so disable the preview auto-update, close it or make it smaller if you don't need it.

Otherwise, picking [[control points]] with ''auto fine tune'' selected can involve a lot
of processing. You can reduce this by ''selecting File -> Preferences -> Finetune'' and
lowering the values for ''Patch width'', ''Search area width'' and ''Local search area width''.
This means you can't be so sloppy when clicking to create control points, but the results will
be the same.

=== Windows: when user is not admin, not all cp-creators are available to choose from ===

Preferences are stored in the registry on Windows. Every users has their own. To have all the cp-creator pre-sets like the admin users, hit the "Load defaults" button on the Control Points tab in the Preferences dialog.

=== cpfind: not enough control points generated ===

Cpfind is a recent addition to the Hugin suite and its parameters still require some fine tuning. Unlike older CP generators used with Hugin, it depends on information passed in the PTO file. Make sure that your input project file contains reasonable information about the used lens. If you are using a fisheye or wide angle lens, try increasing the parameters --sieve1width --sieve1height --sieve1size. A combinations that may work is "--sieve1width 50 --sieve1height 50 --sieve1size 300". Sometimes also the option "--fullscale" might help. Read the [[Cpfind]] documentation.

== Common problems when creating a panorama ==

=== I get thin horizontal black or white lines in large panoramas ===

This is a known bug in the memory handling of [[enblend]] that manifests with large panoramas.

You can workaround it by reducing the size of the panorama, or by adjusting the cache size in [[Hugin_Stitcher_tab]] -> '''Blender options'''. e.g. the default is 1024MB (1 GB), so if you have 4GB RAM you can try raising the cache to use most of your free memory, such as 3000MB, i.e: ''-m 3000''

=== The Control Points tab shows my photos rotated ===

The rotation of photos in the [[Hugin Control Points tab]] isn't necessarily
related to the orientation of the files themselves.

Hugin shows photos at the angle they best fit into the panorama, so if the
panorama fit is bad, then you will see strange angles in the Control Points
tab. Probably the problem is caused by bad alignment, you can
identify 'bad' [[Control points]] in the [[Hugin Control Points table]], delete them and re-optimise.

=== How can I reuse a project as a template? ===

If you copy a .pto project to a different folder and open it with hugin, you will be prompted for the 'missing' images. You should delete any control points from this template project since they won't be relevant to the new photos.

Alternatively you can load your images as normal, then ''Apply template''
from the ''File'' menu, this will import image settings and parameters
from a previous project.

=== How do I straighten a curved horizon? ===
If the panorama looks nice but the horizon is curved, there are various ways to improve the image and straighten the horizon.

First, try clicking the '''Straighten''' button in the [[Hugin Fast Preview window]].

If this doesn't work then you can use the Move/Drag tab of the [[Hugin Fast Preview window]] to visually straighten the panorama, drag the photos with the mouse, use the right mouse button to rotate. One useful tip is to drag the panorama so a vertical feature is in the middle, rotate it so the feature lines up with the 'cross hair', then drag the panorama up or down until all the vertical features in the scene are vertical on the screen (holding down the shift key while dragging limits the motion to just up/down or left/right).

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

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

=== Half the panorama is black, my pictures fill only the right half of the output ===

Hugin uses the first photo as the ''anchor'' image and puts it in the middle by default. This means that if you shot a sequence from left to right, the images will fill the right hand side of the panorama. There are three ways to fix this:

* Open the '''preview''' window and click the '''center''' button.
* or select the middle photo, hit '''anchor this image for position''' and '''reset''' in the '''images''' tab, then reoptimise.
* In the 'Fast Panorama Preview' window select 'Drag'. Left mouse drags the image, right mouse rotates the image.

=== I get visible bands in the sky and other flat areas, what can I do? ===

If the banding looks like [[w:Posterization|posterization]] then this is likely due to a error with estimation of the [[camera response curve]]. To get an accurate response curve, Hugin needs significant [[vignetting]] and/or [[bracketing|bracketed exposures]]. The workaround is to '''Reset...''' the '''Camera Response''' in the [[Hugin Camera and Lens tab]] and stitch again - [[Hugin]] usually produces acceptable results for a simple panorama when the camera response parameters are all zero.

If there is a wave of light and dark patches in the sky this could be due to [[vignetting]] in the source photos, you can deal with this by optimising '''Vignetting (Vb, Vc, Vd)''' in the [[Hugin Exposure tab]]. Another workaround is to increase the number of [[enblend]] blending levels, try setting '-l 29' as the enblend '''Command line options''' in the [[Hugin Stitcher tab]].

=== My photos never quite line up, what can I do? ===

It is normal to get little stitching [[parallax]] errors if
the camera moves between photos. The solution is to rotate the camera around
the [[no-parallax point]] using a [[Heads|panoramic head]] or [[philopod]].

Otherwise you can sometimes improve things by optimising the ''d & e'' parameters
separately - When you optimise '''everything''', unselect '''Inherit''' in
the '''camera and Lens''' panel for 'd & e'. Also you can open the control point window sort it by distance and check the ones large distance.

If these parallax errors are still large, you need to decide which
parts of the scene that you want to line-up and which parts don't
matter. Select [[control points]] only on objects that you do want to
line-up and which are all about the same distance from the camera.

The remaining broken lines can then be retouched in a photo editor like the [[gimp]].
The ''shear'' tool is ideal for bending the lines and
[[Mending parallax errors with the shear tool|getting them to line up]].

=== I have extracted and edited cubefaces and want to merge them together again. How do I do that ? ===

Manually enter the values for [[yaw]] and [[pitch]] for each of the photos. When you stitch set the '''enblend options''' in the [[Hugin Stitcher tab]] to -l1 --fine-mask --no-optimize

=== Can I stitch my HDR images ? ===

Yes. If you already have merged your HDR stacks, follow the '''Normal''' Output on the '''Stitcher''' tab ('''HDR merging''' is for stacks that will be merged by Hugin). In the '''Processing''' step the output will be an HDR in TIFF format.

=== Why is my panorama upside down ? ===

Hugin stitches the panorama on a sphere and can't determine what is up or what is down. Even if vertical control points are assigned, there is still no notion of up and down, so the panorama can flip upside down. The solution for that is to open the Preview window, click on the Num. Trans. button in the toolbar, enter 180 in the roll field and apply. This will flip the panorama back to the right orientation.

=== Why do multi-lens projects end up distorted/broken? ===

You have probably optimized 'Everything'. This will cause the optimizer to try to optimize lens parameters for each of the different lenses, and there may not be a big enough spread of control points for the optimization to work well.
When stitching photos from different lenses, or when you don't have a good spread of control points, optimize 'Position, view & Barrel (y,p,r,v,b).

=== Why does my output covers only 180°? ===

Did you observe that the output is cropped at the +-90° borders? (e.g. saw teeth like borders in the fast preview window)

Then you have probably used the translation parameters X/Y/Z. This behaviour is a fundamental limitation of the used approach of the translation parameters. It is (internal) working in the rectilinear space, which is limited to maximal FOV of 180°, and therefore also the output is limited to FOV<180° (for more information see [[Stitching a photo-mosaic]]).

The solution/workaround is to set all X/Y/Z values to zero or to limit the horizontal field of view (HFOV) to a value smaller than 180°.

== GPU-stitching (nona) ==

Starting with Hugin-2009.2 nona has a new, experimental feature: it can use the video card (GPU) to accelerate the stitching. How much acceleration you will get, if any, depends on the combination of video card and driver.

=== I get a nona: GL error. Does this mean that I found a bug? ===

Not necessarily. This functionality is highly experimental. It may be that you have an outdated driver, or that the functionality is not supported on your video card. Note down the version of the driver you are using and the specs of your video card (GPU and RAM). Then update to the latest driver from [http://www.nvidia.com/page/drivers.html nVidia] or [http://support.amd.com/us/gpudownload/Pages/index.aspx AMD] (ATI has been bought by AMD). Currently only these two families of GPUs support the functionality.

=== How can I know if nona-GPU works on my system? ===

At the moment we have too little information to predict this. We know that only nVidia and AMD(ATI) powered video cards work, and not all of them. The more recent the video card, the higher the likelihood that it works. Improve your chances by updating to the latest driver for your GPU. Look at experience reports from other users and report your experience [[Nona GPU stitching reports|here]].

=== What speed improvement can I expect? ===

It depends on the video card. Bandwidth is mostly the bottleneck, specifically getting the transformed data from the GPU back to the main system memory.

=== Bug Reporting ===

When reporting success or failure using the GPU for stitching, always report also the driver version, video card GPU and RAM. Tell us what you were doing, the size and number of input images (note that if you stitch from within Hugin or PTBatcher, it is only one input image at a time).

== Postprocessing ==

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

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

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

* Use the [[nona]] stitcher on the command-line, to output to a multilayer [[TIFF]] format:

nona -m TIFF_multilayer -o multi_layer.tif project.pto

This will will produce a multi_layer.tif file, that contains all remapped images, cropped to their bounding box.

* Alternatively select the '''Remapped Images''' option in the [[Hugin Stitcher tab]], this will create each ''layer'' as a separate file. Then use the '''tiffcp''' command-line tool (part of libtiff) to join them together into a multi-page TIFF:

tiffcp project0000.tif project0001.tif project0002.tif multi_layer.tif

* You can also use [[tif2xcf]], to combine the '''Remapped Images''' TIFF output into a multilayer XCF.
Unfortunately this requires a lot of memory because it stores each remapped image in a layer with the size of the final panorama.

== Installation ==

=== Where can I download hugin installers ===

Official releases are available from [http://hugin.sourceforge.net/download/ hugin.sf.net].

=== How can I compile Hugin.app on my OSX machine? ===

See [[Hugin Compiling OSX]], [[Autopano-sift-C Compiling OSX]] and [[Enblend Compiling OSX]].

=== How do I compile hugin on my linux machine? ===

See [[Hugin Compiling Fedora]], [[Hugin Compiling Gentoo]], [[Hugin Compiling OpenSuse]] and [[Hugin Compiling Ubuntu]]

=== make[2]: *** No rule to make target `/usr/lib/libGL.so', needed by `src/hugin_base/libhuginbase.so.0.0'. Stop. ===

So you're trying to build from source. Most likely you have proprietary nVidia or ATI drivers. They are a moving target and so is X. On debian based systems including Ubuntu, diagnose with `dpkg -S /usr/lib/libGL.so` and check that the linked library exist (i.e. it is not listed in red when doing `ll /usr/lib/mesa/libGL.so`). If it is listed in red, check where the library is (`ll /usr/lib/libGL*` is a good start on Ubuntu) and link it properly.

=== How do I compile hugin on my Windows machine? ===

See [[Hugin Compiling Windows]]

=== Enblend-Enfuse OpenMP SSE GPU: which one is the right one for me? ===

Enblend and Enfuse can be optimized at build time for different hardware configurations. This yields four categories of Enblend-Enfuse builds, with a few variations. If you build Enblend-Enfuse from source, check the build options in the README file. If you download a binary, you can find out how it has been built with the following command:

enblend -v -V

look for the following in the output text:

# '''Extra feature: OpenMP: yes''' this version has OpenMP.
# '''Extra feature: image cache: yes''' this version has image cache
# '''Extra feature: GPU acceleration: yes''' this version has GPU support
# SSE-support is not mentioned, you'll find out if you have an unsupported CPU and the binary will refuse to run.

These are approximate guidelines to help you choose what may work for you:

* if you have a recent, multi-core / multi-thread CPU, you probably want the OpenMP-enabled version. Note however that speed improvement does not scale well, so don't expect a 6 cores CPU to be 3x faster than a 2 cores one.
* if you have a recent, fast video card, you probably want the GPU-enabled version. This is not mutually exclusive with OpenMP and a good builder will add both features to his binaries. If speed is important to you, you want to test which of the two is faster on your system. If system responsiveness is important to you, the GPU-enabled version frees CPU resources for your other tasks. Note that even if your binary is GPU-enabled, the GPU will not be used unless you specify the option `--gpu`.
* if you have an old CPU without SSE2 support, you want a NOSSE build. This is the least performing version.
* Last but not least, if blending fails because of large images, try the image cache variation. The image cache allows for processing of large project when memory is scarce but images are large (and disk is large enough too). Image cache is incompatible with OpenMP, but a good bilder will make this version GPU-enabled too, so test it with `--gpu` if speed is important.

=== Selecting right version of enblend-enfuse binary for Windows ===

There are 3 variants of enblend-enfuse binaries officially released for Windows. Each one has a special feature set:

1. enblend.exe/enfuse.exe

These executables are the standard release. They are using one processor core and the image cache for processing very big images.

2. enblend_openmp.exe/enfuse_openmp.exe

These executables can utilize several cores of modern multi-core processors and are therefore significantly faster on modern processors. But they may fail on very big images because they are working without the image cache. In this case, please switch to the standard version.
For running the OpenMP variants you will need [http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en "Microsoft Visual C++ 2008 Redistributable Package (x86)"].

3. enblend_nosse.exe/enfuse_nosse.exe

If you have an old CPU without [http://en.wikipedia.org/wiki/SSE2 SSE2] support, you want a NOSSE build. This is the least performing version.
You will need to download a separate package to get this version from [http://sourceforge.net/projects/enblend/files/enblend-enfuse/enblend-enfuse-4.0/enblend-enfuse-4.0-win32-nosse.zip/download sourceforge.net]

All three variants can utilize a modern graphic card to accelerate the optimizing of the seam line between two images. To use this feature supply the parameter --gpu to enblend.

=== Selecting right version of enblend-enfuse binary for Debian/Ubuntu ===

At the time of writing the official Debian/Ubuntu package ships with one executable only, however in July 2010 a change has been committed to debian-unstable that delivers two binaries:

1. enblend/enfuse

These executables are the standard release. They are using one processor core and the image cache for processing very big images.

2. enblend_mp/enfuse_mp

These executables can utilize several cores of modern multi-core processors and are therefore significantly faster on modern processors. But they may fail on very big images because they are working without the image cache.

Both variants can utilize a modern graphic card to accelerate the optimizing of the seam line between two images. To use this feature supply the parameter --gpu to enblend.

== Support ==

=== Reporting Bugs ===

If you think you have found a bug in Hugin, please report it to help us make Hugin better. Before reporting a bug, try a few things to make sure it is really a bug. Then collect the following information and transmit it to the developers via the bug tracker.
# What version of Hugin are you using? Consider upgrading and try to reproduce the bug. Maybe it was fixed in a more recent version.
# read the output log. Are there any suggested actions or messages in there? If so, follow the advice and try again. Save the output log to a text file and attach it to the report if you file a bug report.
# Attach the .pto file to the bug report.
# Use a meaningful title for the bug report. The line reporting the error in the output log is a good place to start. Before filing a new bug report, check for duplicates. Launchpad does already a little bit so. If the bug is already known, add yourself and you files with a comment to the bug. This will give your report and your log more visibility than if somebody looking at your bug has to mark it as duplicate.

=== Why is my Bug Report marked Invalid? ===

We trust you that you are experiencing the issue on your end and that it bugs you, but most likely the solution lies not in the Hugin codebase. If you feel that your report has been marked Invalid by mistake, feel free to reply and to set the status back to New for a re-evaluation. Somebody may explain to you why the report was marked as Invalid and what you can do.

=== Why is my Bug Report marked Incomplete? ===

Every system is different and those trying to help fixing the bugs do not see and experience what you do. In order to help you, they are likely to need more information. Without that information the bug report is of little use. We mark as Incomplete reports that require additional information. Once you provide it, please mark the report status as New again

=== How do I Change the Status of my Report? ===

* If you reply via the web interface: hit the yellow round button next to the current status to get a selection of stati. Unless you know what you are doing, set it to New to attract developer's attention.
* If you reply by email: at the bottom of your email enter a line starting with one single space and the following words: <code> status new</code>. Read more about the [https://help.launchpad.net/Bugs/EmailInterface email interface].

=== User Support: Mailing List ===

Hugin has a lively and friendly user groups. Connect with expert users and ask questions on the Hugin-PTX mailing list. To subscribe send an empty email to hugin-ptx+subscribe@googlegroups.com and follow the instructions in the email you receive back.
To ask questions, send an email to hugin-ptx@googlegroups.com
Your first emails will be moderated, so be patient if you don't see your message right away.

[[Category:Software:Hugin]]

Talk:Dynamic range

2012-03-26T06:56:05Z

Zarl: Deleted Spam