https://wiki.panotools.org/api.php?action=feedcontributions&user=Thomas+Rauscher&feedformat=atomPanoTools.org Wiki - User contributions [en]2024-03-19T06:30:17ZUser contributionsMediaWiki 1.35.3https://wiki.panotools.org/index.php?title=File:Banging_rocks_128.png&diff=16071File:Banging rocks 128.png2019-01-03T20:30:58Z<p>Thomas Rauscher: </p>
<hr />
<div></div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=User_talk:Thomas_Rauscher&diff=16070User talk:Thomas Rauscher2019-01-03T19:09:07Z<p>Thomas Rauscher: </p>
<hr />
<div><math>asdfffdasf</math></div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=User_talk:Thomas_Rauscher&diff=16069User talk:Thomas Rauscher2019-01-03T17:52:27Z<p>Thomas Rauscher: Created page with "<math>asdfdasf</math>"</p>
<hr />
<div><math>asdfdasf</math></div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Pano2QTVR&diff=15815Pano2QTVR2016-04-26T11:10:47Z<p>Thomas Rauscher: Added notes about EOL and a link to Pano2VR & Object2VR</p>
<hr />
<div>{{Glossary|a program to make [[Quicktime|QuickTime]] VR and [[Flash]] interactive panoramas}}<br />
'''Active development for Pano2QTVR has stopped in 2007.''' Please have a look at [[Pano2VR]] and [https://ggnome.com/object2vr Object2VR] instead.<br />
<br />
A real promising Windows project by [[User:Thomas Rauscher|Thomas Rauscher]] to convert [[Equirectangular Projection|equirectangular]] and [[Cylindrical Projection|cylindrical]] panos to [[Quicktime|QuickTime]] [[Cubic Projection|cubic]] movies and link them together to virtual tours. <br />
Since version 0.9.8 it is also possible to create single and multi row Quicktime VR [[Object Movie|Object Movie]]s<br />
<br />
Features for the free version (for non-commercial usage):<br />
* graphical userinterface<br />
* converting equirectangular and cylindiric images to [[QTVR]] (.mov files).<br />
* converting equirectangular to single cube face files (either [[JPEG]] or [[TIFF]])<br />
* assembling single cube face files into a [[QTVR]] (.mov file) to allow retouching of the cubefaces<br />
* setting of [[PTStitcher]] interpolator and interpolator [[gamma]] for cube face creation<br />
* usage of the internal or the [[Pano12|PanoTools]] remapper<br />
* supported image formats: everything that [[ImageMagick]] can handle f.e JPEG, JPEG-2000, TIFF (8- an 16bit), PSD, BMP, PNG, GIF,... <br />
* creating [[hotspots]] in an internal hotspot editor using various forms (round, elliptic, rectangle, rounded rectangle, polygon)<br />
* setting of most (if not all?) QTVR parameters like f.e. pan, tilt and Field of View defaults and limits, title, description, author, date and time, copyright, source, comment...<br />
* subtiles of cube faces for progressive download<br />
* optimizer to rearrange the tiles depending on the viewing direction. [http://www.panoramas.dk/quicktime/qtvr/tiling.html more]<br />
* spot the initial viewing parameters and grab this position<br />
* high quality is enabled by default. [http://www.virtualdenmark.dk/qtvr/16bit/qtvr16bit.html more]<br />
* droplets for batch processing<br />
* individual JPEG quality for each cubeface <br />
* option for compressed headers and protection to disallow further editing with Quicktime.<br />
<br />
<br />
Additional Features for the pro version:<br />
* [[Object Movie]]s (single- and multi row)<br />
* import up to 10 [[sprites|sprite]]-tracks, soundfiles, images, [[Flash]] movies,... <br />
* background sound for panoramas <br />
* import [[autorotate]] sprite for panoramas <br />
* create thumbnails from the source image (GIF, TIFF and PNG with correct [[alpha channel]]) <br />
* create HTML files for [[Quicktime]], [[DevalVR]] and [[PTViewer]] <br />
* create vertical Image strips for [[SPi-V]] and [[Immervision]] PurePlayer <br />
* use the output files for commercial purposes<br />
<br />
Features specially for Object Movies:<br />
<br />
* Specify animation and autoplay speed with rotation or ping-pong <br />
* Unlimited viewstates and animations <br />
* Different contollers like grabber, joystick and absolute position <br />
<br />
<br />
Pano2QTVR download page: http://ggnome.com/pano2qtvr<br />
<br />
The interface is no-frills and easy to grasp in a single sitting. I was able to put together a 7 image tour with multiple links in under 30 minutes, and that was the first time using the program. See it here: http://www.add360.com/archangels/virtual_tours/tour-quicktime/image2.mov<br />
<br />
The software offers links to internal images, external webpages and tooltips.<br />
<br />
[[Category:Software:Platform:Windows]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Pano2VR&diff=15814Pano2VR2016-04-26T11:02:27Z<p>Thomas Rauscher: First short entry</p>
<hr />
<div>'''Pano2VR''' by Garden Gnome Software is commercial software for Windows, Mac OS X and Linux. It is the successor of [[Pano2QTVR]].<br />
<br />
It allows to publish panoramic images and virtual tours with HTML5, Flash and QTVR. It can handle gigapixel images as well as 8bit, 16bit and [[HDR]] formats.<br />
<br />
== External links ==<br />
[https://ggnome.com/pano2vr Pano2VR - Virtual Tour Software]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Extract_and_insert_rectilinear_views&diff=15813Extract and insert rectilinear views2016-04-26T10:48:58Z<p>Thomas Rauscher: /* Other possibilities */ Added a link to the Pano2VR documentation</p>
<hr />
<div>== Intro ==<br />
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. <br />
<br />
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 extract a partial view - best in [[Rectilinear Projection]].<br />
<br />
== Warning ==<br />
<b>Important!</b> For all transformations that use non-overlapping images like assembling cube faces to an [[equirectangular]] image the 'Fast transform' option should be disabled. As a default 'Fast transform' is disabled for the [[Panorama Tools Plugins]] and for [[PTEditor]]. However, it is enabled by default for some of the GUIs ([[PTGui]] f.e.)<br />
<br />
Fast Transform can cause the loss of some pixels in the corners of an [[Rectilinear Projection|rectilinear]] image which will be visible as small triangular black holes in the result image. More on 'Fast Transform' on [http://www.fsoft.it/panorama/pano12.htm Fulvio Senore's page].<br />
<br />
PTGui 5 has a new internal stitcher which causes a similar effect even if Fast Transform is switched off. <b>Don't use PTGui 5 internal stitcher to assemble cubefaces!</b> Choose "Panotools Stitcher" (PTStitcher) instead.<br />
<br />
== Possibilities with panotools ==<br />
There are basically three possibilities to extract partial [[Rectilinear Projection|rectilinear]] views with panorama tools:<br />
* [[PTEditor]]<br />
* [[Panorama Tools Plugins]]<br />
* [[PTStitcher]] or [[nona]] used directly or indirectly by script or batch file, GUI or [[PanoCube]] Plus <br />
<br />
=== PTEditor ===<br />
[[PTEditor]] is a [[Java]] application provided with the standard [[Panorama Tools]] distribution. It should run on any OS where Java and the panotools runtime (the [[pano12]] library) are installed. There is a nice tutorial on [[How to use PTEditor]]. This is the most convenient way to extract and insert any arbitrary [[Rectilinear Projection|rectilinear]] view. The disadvantage is that it doesn't save 16 bit images.<br />
<br />
=== Panotools plugins ===<br />
The [[Photoshop]] and [[Gimp]] compatible [[Panorama Tools Plugins]] are part of the standard Panotools distribution as well. The most recent version that corrects some bugs and works for 16 bit is available as part of the panotools download from [http://sourceforge.net/projects/panotools/ panotools sourceforge page].<br />
<br />
The plugins contain the [[Panorama Tools Plugins#Adjust|Adjust]] filter, which is capable of extracting and inserting any view in almost any projection. Any data (pan/tilt angle, size of view etc.) has to be inserted manually. Yaw, roll and pitch value have to be calculated or estimated which makes the usage a bit inconvenient. <br />
<br />
However, extracting and inserting [[Zenith]] or [[Nadir]] is straightforward and relatively easy. [[Helmut Dersch]] has outlined the basic workflow in [http://www.panotools.org/dersch/panorectilinear/panorectilinear.html Extracting Rectilinear Images from Panoramas]. You need to do the following:<br />
<br />
==== Extracting ====<br />
* Load the [[Equirectangular]] image in [[Photoshop]] (or any plugins compatible image editor).<br />
* Choose 'Adjust' or 'PTAdjust' from the Filter menu.<br />
* Press the small 'Prefs' button in the upper right corner.<br />
* In the following dialog uncheck option (a) and check options (b) and (c) (see [[Panorama Tools Plugins#Preferences|plugins description for details]]) <br />
* confirm with 'Ok'<br />
* check 'Extract', check 'Use Options' and press 'Set'<br />
* In the following dialog there is an upper part called 'Image:' and a lower one called 'Panorama'<br />
* In the 'Image' section:<br />
** Set HFOV 90 for a cube face (or any other Field of View to your need).<br />
** Choose 'Width' and 'Height' appr. 1/3 of the source image width in order to not degrade image because of too low resolution.<br />
** Choose 'Format: Rectilinear'<br />
** Set 'Yaw' and 'Roll' to 0.0<br />
** Set 'Pitch' to -90 for [[Nadir]] or 90 for [[Zenith]]<br />
* In the 'Panorama' section:<br />
** Set HFOV to 360 for a full sphere.<br />
** Leave 'Width' and 'Height' empty (will be read from the image)<br />
** Check 'Save to Buffer' if you want to merge the result into your pano later.<br />
** Choose Format: PSphere (which means [[Equirectangular]])<br />
** Uncheck 'Load Buffer' to avoid loading of previously saved images.<br />
* Press 'Ok' twice to perform the transformation<br />
<br />
The result image will be loaded into a new window where you can edit it as any other image.<br />
<br />
==== Inserting ====<br />
Once you are done with editing the image you can either insert it back to your orignal pano or load it as a masked layer.<br />
<br />
===== Merging =====<br />
You need to have checked 'Save to Buffer' in order to be able to merge the result into your pano. <br />
* With the edited rectilinear image as foremost (active) document open Adjust or PTAdjust dialog from the filter menu.<br />
* Choose 'Insert' and 'Use Options' and press 'Set'<br />
* in the following dialog leave anything as is or set it to the values described in the Extracting part if you changed them meanwhile with these exceptions:<br />
* In the 'Panorama' section:<br />
** Uncheck 'Save to Buffer' <br />
** Check 'Load Buffer' <br />
** check 'or paste'<br />
** Choose 'Color Correction: none'<br />
** Set 'Feather:' to a small value or 0 <br />
* Press 'Ok' twice to perform the transformation ans merging.<br />
<br />
===== Loading as layer =====<br />
Sometimes it might be usefull to load only the transformed Nadir or Zenith image in order to insert it as a new layer into a panorama. <br />
* With the edited rectilinear image as foremost (active) document open Adjust or PTAdjust dialog from the filter menu.<br />
* If you changed any settings since extracting the image set them as described under Extracting. <br />
* Press 'Ok' to perform the transformation<br />
<br />
The image is loaded as a document containing an [[alpha channel]] with the mask. In photoshop you can move this into a masked layer:<br />
* In the layers palette double click the layer thumbnail in order to create a layer from background.<br />
* Choose 'Load Selection' from the 'Select' menu. <br />
* Choose 'Channel: Alpha 1' as new selection and press 'Ok'<br />
* Click the 'Add vector mask' button in the bottom line of the layers palette.<br />
* Shift-Drag (pres and hold the shift key after started dragging) the layer from the layers palette to your original panorama.<br />
<br />
=== PTStitcher ===<br />
[[PTStitcher]] supports 16 bit images and can be used to extract and insert partial views in different ways. <br />
* By directly scripting it.<br />
* With [[PanoCube]] Plus<br />
* By one of it's GUIs ([[PTGui]], [[PTAssembler]], [[Hugin]], [[PTMac]]...) <br />
<br />
[[nona]] is a free alternative to [[PTStitcher]] that can be used as a drop-in replacement if [[PTStitcher]] is not available.<br />
<br />
==== Scripts ====<br />
There are several scripts or batch files available that extract 6 cube faces from an [[Equirectangular Projection]] image. One of the most convenient windows batch file is written by Eric Gerds and part of his [http://www.pinlady.net/vr/#anchor3 DOS Utilities for Panoramas]. A less convenient batch file is found on [http://www.erik-krause.de/ttt Erik Krause's ] page. [[PTStitcher]] scripts are found on [http://www.path.unimelb.edu.au/~bernardk/tutorials/360/readme/scripts.html Ben Kreunen's ] page<br />
<br />
==== PanoCube Plus ====<br />
[[PanoCube]] Plus can extract six cube faces (single, batch modes) for editing and then convert it directly into [[QTVR]] cubic movie(s). Both 8/16 bits per channel are supported - depending on the [[pano12]] library used the cube faces are the same bit depth as the source images. <br />
<br />
To activate "equirectangular to 6 cube faces" mode copy the file <code>Script.txt</code> to the folder where your source image is and set "1" as first character in this line using a text editor (notepad!):<br />
<br />
<pre>1 # create tiles for editing ( 0 = NO, 1 = YES). Default NO.</pre><br />
<br />
in the file <code>Script.txt</code> and put it into pano's folder. Next drag and drop your single pano or folder with panos onto the program icon. The source file name and path should contain no spaces. The source image must be exactly in 2:1 format (f.e. 2000x1000 or 6000x3000 pixels). [[PanoCube]] calls [[PTStitcher]] 6 times and creates 6 files in the order front, right, back, left, top, bottom and replaces the last two characters of the name with 11, 22, 33, 44, 55, 66. All files ended with 55 are represent zenith view, ended with 66 - nadir view.<br />
<br />
After editing drag again any one (not all!) tile or folder with tiles to get [[QTVR]] cubic movie(s). In batch mode important to have first six letters differ in filenames, otherwice PanoCube can skips "similar" files.<br />
<br />
This technique is good if the final product is a [[QTVR]] movie. If you need an equirectangular for PTViewer you can of course drag the .mov file on panocube plus to get it converted, but image quality suffers because of intermediate [[JPEG]] compression and decompression and another [[interpolation]] step.<br />
<br />
==== Inserting cubefaces again ====<br />
You can assemble the cube faces again using the [[PTGui]] template from http://www.erik-krause.de/ttt or the batch file from Eric Gerds: [http://www.pinlady.net/vr/#anchor3 Dos for Panoramas]. <br />
<br />
You can even remap only one cube face to equirectangular and insert it as an additional layer into your layered photoshop document. This has several benefits: <br />
* no additional [[interpolation]] for the rest of the panorama. <br />
* possibility to patch nadir in a relative early stage of editing thus leaving open any possibility of correcting over all colors etc.<br />
* preserving as much as possible of the original image data<br />
<br />
To re-insert the patched cubeface into the original document implies that you have worked on a cube face with enough resolution, preferable the pixel width of the original pano divided by 3.<br />
<br />
You can use the batch file or [[PTGui]] template mentioned above. You simply have to set output size equal to your original panorama size and create single image [[TIFF]]s as output. Any of those [[TIFF]] files can be added to the original panorama as a masked layer using the "Tiff to masked layers" action from http://www.erik-krause.de/ttt<br />
<br />
To use any of the other GUIs you need to <br />
* Add the cube face as input image<br />
* specify [[Rectilinear Projection|rectilinear]] and FoV 90° for input images<br />
* set all lens correction parameters to 0.0<br />
* specify the correct yaw and pitch values for the particular image:<br />
<pre><br />
tile front right back left top bottom<br />
Yaw 0 90 180 -90 0 0<br />
Pitch 0 0 0 0 90 -90<br />
</pre><br />
* specify the correct output size.<br />
* specify [[TIFF]] without mask or feather (TIFF_m) as output format.<br />
* don't set control points and don't optimize<br />
* create the panorama<br />
<br />
==== GUI ====<br />
All of the [[GUI front-ends]] should be capable of extracting an arbitrary [[Rectilinear Projection|rectilinear]] view from a spherical pano. Use the equirect image as input (don't forget to set the correct FoV) and specify a rectilinear image with 90° as output "panorama". Set all lens correction parameters to 0.0. Then change yaw and pitch of the input image until you get the desired view. Note that the values work the other way round than when inserting an image.<br />
<br />
==== PTGui ====<br />
[[PTGui]] offers an additional advantage: The panorama editor and numerical transform. To use it load your image as described above, open panorama editor and choose 'Numerical Transform' from the edit menu. <br />
<br />
On the 'Panorama Settings' tab don't forget to uncheck 'Use fast transform' (for details see [[#Warning|Warning]] at top of page).<br />
<br />
To pan along the horizon f.e. in 20° steps insert 20 into the 'Yaw' field and press 'Apply' repeatedly until you get the desired view. Positive values pan right, negatives left. <br />
<br />
Do the corresponding for 'Pitch' and 'Roll' if needed. This way you can extract any partial view. Once your are done create the "Panorama" (which is the desired partial view) using output format [[TIFF]]. Note down or save the exact values for Yaw, Roll and Pitch as shown on 'Image Parameters" tab page.<br />
<br />
Now edit the partial view to your need. Then add it to the project with your original panorama and on 'Panorama settings' tab change to equirectangular and 360°x180°. Choose individual lens parameters for the new image on 'Lens settings' tab and set 'Rectilinear' and 90° on 'Image parameters' tab. The image should fit now perfectly in the original panorama.<br />
<br />
In order to move the panorama back to it's original position go to panorama editor again and choose 'Numerical transform'. Now Enter the exact values for Yaw, Roll and Pitch you previously saved or noted down. The panorama should move back to it's original position now. <br />
<br />
You can create either the complete panorama or the partial view only. Choose the size of the original panorama for output.<br />
<br />
There are two templates available for conveniently extract and insert the floor cube face using this technique from [http://erik-krause.de/ttt#Bodenbild_extrahieren http://erik-krause.de/ttt]<br />
<br />
== Other possibilities ==<br />
* The free [http://www.superrune.com/technical/software_supercubic.php Super Cubic plugin] for photoshop extracts and inserts both [[zenith]] and [[nadir]]. <br />
* A video tutorial using Photoshop actions and PTGui templates can be found here: [http://www.youtube.com/watch?v=owq7kaXMTTk Nadir patching in Photoshop with actions and PTGui templates]<br />
* A two parts [http://panospace.wordpress.com/2008/03/18/edit-the-nadir/ tutorial] with [[Hugin]]<br />
* Patching a Panorama with [[Pano2VR]]: [https://ggnome.com/doc/pano2vr/5/patches-extract/ Patches documentation], [https://vimeo.com/161170513 video tutorial]<br />
[[Category:Tutorial:Basic need]]<br />
<br />
{{Incomplete|Talk}}</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Panorama_Viewers&diff=15812Panorama Viewers2016-04-26T10:42:12Z<p>Thomas Rauscher: /* Commercial */ updated Pano2VR</p>
<hr />
<div>There are basically three types of viewers for spherical panoramas:<br />
* [[Java]] based Viewers run on any platform that supports [[Java]].<br />
* Plugin based viewers require a plugin ([[Quicktime]], [[Shockwave]]) to run and might be platform specific.<br />
* Stand alone viewers that are executables for a specific platform. Unlike Java and plugin-based viewers these are not meant for use within web pages.<br />
<br />
== Java based Viewers ==<br />
=== Free ===<br />
* [[PTViewer]] was the first Java viewer. It was developed originally by [[Helmut Dersch]] and is now [[PTViewer 2.7L2|maintained and enhanced]] by [[Fulvio Senore]]<br />
<br />
* [http://www.panorado.com/ Panorado Applet] is a Java viewer applet. It only shows a "flat" view but it is fast, so it is suited for larger images where the normal immersive-style warping isn't needed.<br />
<br />
* [http://www.immervision.com/en/multimedia/multimedia_products/multimedia_products_2_2.php PURE Player for Java] (by ImmerVision) is a Java viewer applet that supports cylindrical, spherical and cubic panoramic images.<br />
<br />
* [http://www.immervision.com/en/multimedia/multimedia_products/multimedia_products_2_3.php PURE Player for PRO Java] (by ImmerVision) is a free Java viewer applet that supports cylindrical, spherical and cubic panoramic images. It also supports user interfaces.<br />
<br />
=== Commercial ===<br />
There are some commercial [[Java]] based viewers. Most of them are either a [[PTViewer]] clone or less functional.<br />
<br />
== Plugin based Viewers ==<br />
<br />
=== Free ===<br />
<br />
* [[Quicktime]] is available for Apple Macintosh and Windows. Requires panorama in [[QTVR]] movie format. ([[PanoCube]] or [[Pano2QTVR]] convert from equirectangular to .mov on Windows)<br />
<br />
* [[freepv]] is an open source cross-platform viewer for [[QTVR]] and other panorama formats.<br />
<br />
* [[DevalVR]] is a Windows browser plugin that displays both cubic QuickTime-VR panoramas in [[QTVR]] movie format panoramas. See http://www.devalvr.com/ for details.<br />
<br />
* [[PangeaVR]] is a Mac OS X browser plugin that displays both cubic QuickTime-VR panoramas in [[QTVR]] movie format and equirectangular (spherical) [[JPEG]] panoramas. See http://www.pangeasoft.net/pano/plugin/pangeavr.html for details.<br />
<br />
=== Commercial ===<br />
<br />
* There are no known commercial plugins for standard web delivery of panoramas<br />
<br />
== Flash or Shockwave based Viewers ==<br />
<br />
=== Free ===<br />
* [[CuTy]] is a tiny, dedicated viewer for (single node, JPEG encoded, cubic) QTVR .mov files based for Flash Player 10 and newer. Its functionality is deliberately kept minimal.<br />
<br />
* [[pan0]] is an open source, Flash 9 based player for panoramas in equirectangular format. The application was formely known as "fspp". See http://pan0.net/page.php?page=pan0 for details.<br />
<br />
* [[PanoSalado]] is an '''open source''' Flash 10 and Flex based viewer for cubic, equirectangular (spherical), cylindrical and QTVR panoramas. It handles multi-resolution tiled panoramas, and '''playback of panoramic video''' in common projections. It supports 2D & 3D hotspots, audio, video, and being extended via XML or directly via Actionscript (AS3) and/or MXML. See PanoSalado's [http://sourceforge.net/apps/wordpress/panosalado/ blog], download source and examples from the [http://os.ivrpa.org/panosalado/downloads IVRPA] repository and access the [http://os.ivrpa.org/panosalado/downloads API].<br />
<br />
* [http://panozona.com/wiki/SaladoPlayer:Quick_start Salado Player] is a fork from PanoSalado created in 2010. SaladoPlayer features configuration via xml files and additional modules, along with a module api.<br />
<br />
* [http://www.immervision.com/en/multimedia/multimedia_products/multimedia_products_2_4.php PURE Player for Flash] is a free Flash 9 based player that supports cylindrical, spherical and cubic panoramas.<br />
<br />
* [[SPi-V]] is a very sophisticated and smooth viewer based on Macromedia [[Shockwave]] that handles panoramas completely in graphics card memory (free version with logo).<br />
<br />
* [[Syborg Rooms]] can connect multiple panoramas and enrich the expierence with videos, images and text. Rooms are build with Syborg Architect - an easy graphical interface. It supports iPhone and iPad as well.<br />
<br />
=== Commercial ===<br />
<br />
* The [http://flashpanoramas.com/player/ Flash Panorama Player] is a cross-platform viewer that displays [[QTVR]] movies as well as equirectangular (spherical) and cylindrical panoramas. Cube faces and stripes can also be handled. It supports SWF-plugins to extend its functionality (for example to integrate distorted FLV-movies as hotspots).<br />
<br />
* [http://ggnome.com/pano2vr Pano2VR] (formerly [[Pano2QTVR]]) creates HTML5 virtual tours, and Flash 10-compatible SWF files with included spherical viewer. It also creates QuickTime VR content and can output images in a number of different projections including equirect and cubefaces.<br />
<br />
* [http://krpano.com/ KRPano] is a Flash 9 & 10 & HTML5 based panorama viewer with a wide range of configuration options. These include different projections such as stereographic ('little planet'), fisheye, Vedutismo, and 'architectural'. It can handle cubefaces, equirects and QTVR .mov files, and it can embed other media including audio and FLV videos into panoramas.<br />
<br />
== Online Services ==<br />
<br />
* [[Virtual Tour Architect]] allows users to create virtual tours with panorama images. The tours are displayed as flash (PC) and html5 (iPhone, iPad). The tours are created very fast through a very easy-to-use interface. It is based on [[Syborg Rooms]].<br />
<br />
<br />
<br />
== HTML5 based Viewers ==<br />
<br />
=== Free ===<br />
<br />
* [[Syborg Rooms]] exports virtual tours in flash and html5. Based on the users device the export shows the supported format.<br />
* [http://www.vrhabitat.com/#vr5 VR5 Pano Viewer]. You need to prepare the images to him (cube faces in 2 resolutions. Can redirect to your standard player in case the browser is not on an iPad/iPhone.<br />
* [http://pannellum.org/ Pannellum] Very lightweight HTML 5 open source viewer featuring embedding support, configuration using URL parameters, title and author information, multiresolution support, and full screen support among other things.<br />
* [http://leandigo.github.io/leanorama/ Leanorama]. A free and open source viewer for Webkit browsers (Chrome, Safari, iPad, iPhone, Android 3+). Allows simple definition of virtual tours in JavaScript. Documentation and download on [https://github.com/leandigo/leanorama GitHub]<br />
<br />
=== Commercial ===<br />
<br />
* [[Syborg Rooms]] Pro Version<br />
* [http://krpano.com/ KRPano] is a Flash 9 & 10 & HTML5 based panorama viewer with a wide range of configuration options. These include different projections such as stereographic ('little planet'), fisheye, Vedutismo, and 'architectural'. It can handle cubefaces, equirects and QTVR .mov files, and it can embed other media including audio and FLV videos into panoramas.<br />
<br />
== Stand alone Viewers ==<br />
<br />
* [[FSPViewer]] is a free hardware accelerated stand alone viewer by [[Fulvio Senore]] that supports ICC color profiles (Windows, Linux and OS X).<br />
<br />
* [[panoglview]] is an Open Source hardware accelerated stand alone viewer for [[Equirectangular Projection]] images (Windows, Linux and OS X).<br />
<br />
* <strike>panoviewer</strike> is an Open Source stand-alone viewer now superceded by [[panoglview]] (Windows, Linux).<br />
<br />
* [[PTViewer]], the original standalone viewer created by [[Helmut Dersch]] in C for X-Windows available from one of the [[mirrors]] (Linux) or the 3.2 version in compiled Java from [http://webuser.fh-furtwangen.de/~dersch/ his page] (Windows).<br />
<br />
* [[Quicktime]] also works as a standalone viewer (Windows, Mac).<br />
<br />
* [[DevalVR]] has a stand alone version, too (Windows).<br />
<br />
* [[freepv]] is a standalone hardware accelerated [[QTVR]] viewer as well as a plugin.<br />
<br />
* [http://groups.google.com/group/panini-support/web/panini-0-71-tips-and-tricks Panini] is an open source panoramic image viewer and perspective tool for all Qt platforms, including Linux, Windows, OSX. It can display files in many panoramic formats. Your video driver must support OpenGL version 1.5, 2.0 for full functionality. Get Panini at [http://sourceforge.net/projects/pvqt/ sf.net/projects/pvqt], [[Build Panini on MacOSX|build on OS X]] or [[Build Panini on Other Unixes|build on other unixes]].<br />
<br />
* [http://www.panorado.com Panorado] is a full-featured image viewer/browser supporting panoramas (JPEG & QTVR). Shareware. (Windows)<br />
<br />
* [http://www.immervision.com/en/multimedia/multimedia_products/multimedia_products_2_6.php PURE Player for Windows] is a free standalone version of PURE Player viewer for Windows OS that supports cylindrical, spherical and cubic panoramas.<br />
<br />
* [http://www.cubeworld.org/ CubeWorld] for iPhone and iPod Touch is a free app that plays cubeface-based panoramas (max 1024px cubefaces) using OpenGL. It can store panoramas locally for offline viewing.<br />
<br />
* [http://www.itunes.com/apps/ipano iPano] for iPhone and iPad, awesome pano viewing app. Lets you keep a high res portfolio (8192 x 4096).<br />
<br />
* [http://www.pangeasoft.net/pano/pangeavr/index.html PangeaVR] for iPad, iPhone and iPod Touch is an app that plays panoramas (max. 2048x1024px equirects on iPhone/iPod, 4096x2048 on iPad) using OpenGL. The standard version of PangeaVR is free, the Pro version (which can store panoramas locally for offline viewing) costs $5.99.<br />
<br />
* [http://panobender.atspace.com/ PanoBender] for Windows CE is a free standalone viewer for JPEG images of equirectangular and cylindrical panoramas.<br />
<br />
* [[SPi-V]] is also [http://fieldofview.com/spv-dev/downloads available as stand alone viewer] (requires [[Shockwave]] plugin) (Windows, OS X).<br />
<br />
* [https://play.google.com/store/apps/details?id=com.adec.apps.release.panpro PPV360HD] (aka Professional Panoramic Viewer 360 HD) is a commercial full-featured Android (from 2.0) App by Andridea (author is Andrea de Carolis) to view Panorama up to 2.27GigaPixel (max 65000x32000) on tablets/smartphones with Kinetic Rotation, full pinch and zoom, tagging. Take a jpeg (equirectangular/cylindrical, full or semi panoramic) and processes it with its own multi-tiles generator, and view them offline with its hardware accelerated 3d viewer. User can change FOV, vert/horiz degree and many options ([https://sites.google.com/site/andrewdc09/Software/ppv360hd developer site]). There'is also a [https://play.google.com/store/apps/details?id=com.adec.apps.release.pandemo free demo] available, with some limitations. Developers offer the possibility to build Virtual Tour App.<br />
<br />
[[Category:Software:Platform:Linux]]<br />
[[Category:Software:Platform:Mac OS X]]<br />
[[Category:Software:Platform:Windows]]<br />
[[Category:Software:Platform:Mobile/PDA]]<br />
<br />
== External Links ==<br />
<br />
* http://www.panoramaphotographer.com/comparisons/ shows working examples of a large number of different web-based panorama players.</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=User:Thomas_Rauscher&diff=14091User:Thomas Rauscher2012-07-27T08:41:43Z<p>Thomas Rauscher: </p>
<hr />
<div>== Short facts ==<br />
<br />
* I am a student of computer science at the university of Vienna<br />
* I have written the software [[Pano2QTVR]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Template:Extension_DPL&diff=13779Template:Extension DPL2011-11-30T09:23:37Z<p>Thomas Rauscher: Template:Extension DPL</p>
<hr />
<div><noinclude>This page was automatically created. It serves as an anchor page for all '''[[Special:WhatLinksHere/Template:Extension_DPL|invocations]]''' of [http://mediawiki.org/wiki/Extension:DynamicPageList Extension:DynamicPageList (DPL)].</noinclude></div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Diffraction&diff=12940Diffraction2010-12-27T14:44:34Z<p>Thomas Rauscher: Fixed math bug. Original formular by Erik</p>
<hr />
<div>{{Glossary|The physical property of light which causes image blur depending from the aperture used.}}<br />
<br />
==What it is==<br />
Diffraction in general is the bending of waves around an obstacle. In photography the light waves are bent around the edges of the aperture, causing f.e. the well known star like pattern around the sun if shot stopped down. Since diffraction affects any point of the image (not only very bright sources) it reduces general sharpness and limits effective resolution. Diffraction blurs any point to a pattern called "[[w:Airy disk]]".<br />
<br />
==Sharpness==<br />
Diffraction is one of three factors limiting the image sharpness. Second is aberration (f.e. [[chromatic aberration]]) which is determined by lens build quality. Third is de-focus or [[Depth of Field]]. <br />
<br />
Diffraction depends only on the physical aperture size. Hence it's effect is generally larger the smaller the used sensor is due to the larger magnification of the image. That's the reason why compact cameras can't (or shouldn't) be stopped down further than f/5.6. As a rule of thumb the limit for APS-C sized sensors is f/8 to f/11 and for full frame ones f/16 to f/22.<br />
<br />
You can balance [[Depth of Field]] against diffraction. An approach is the sharpest aperture. [[Diffraction#External_links|See link at the bottom]].<br />
<br />
==Resolution==<br />
The maximum obtainable resolution is limited by diffraction according to the [[w:angular resolution|Rayleigh criterion]]. Since this criterion defines the angular resolution it can be directly used for zoomable panoramas neglecting sensor sizes etc. By simply dividing the panorama [[Field of View]] (FoV) by the angular resolution we get the maximum possible pixel resolution. For an average value we take the wavelength of light ''λ'' = 550nm = 5.5*10<sup>-4</sup>mm. The resulting formula is:<br />
<math> pixel resolution = \frac{FoV}{asin\left(\frac{1}{1490*D}\right)}</math><br />
<br />
''D'' is the diameter of the lens' aperture, which is the focal length in mm divided by the f-number. The following table shows the maximum angular resolution in '''pixels/degree''' which is obtainable by a given focal length (vertical) and f-number (horizontal) without regard to currently available sensors:<br />
'''2.8 4 5.6 8 11 16 22 32 44'''<br />
'''50''' 464 325 232 163 118 81 59 41 30<br />
'''100''' 929 650 464 325 236 163 118 81 59<br />
'''200''' 1,858 1,300 929 650 473 325 236 163 118<br />
'''400''' 3,715 2,601 1,858 1,300 946 650 473 325 236<br />
'''800''' 7,430 5,201 3,715 2,601 1,891 1,300 946 650 473<br />
'''1200''' 11,145 7,802 5,573 3,901 2,837 1,950 1,418 975 709<br />
Some usage examples<br />
*You want to shoot a gigapixel panorama of 175° width with a 800mm lens at f/11. You get 175*1,891 = 330,925 pixel maximum horizontal resolution.<br />
*You will use an APS-C format sensor in portrait orientation for this panorama. A 800mm lens has a FoV of 1.1° in that case, which at f/11 gives 2080 pixels or app. 6 megapixels. Applying the 70% rule to compensate for bayer interpolation blur indicates that 12 megapixels per image are enough.<br />
<br />
==External links==<br />
*wikipedia on [[w:Diffraction|Diffraction]]<br />
*wikipedia on [[w:Angular resolution|Angular resolution]]<br />
*[http://www.kenrockwell.com/tech/focus.htm Ken Rockwell's page] on Selecting the Sharpest Aperture</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Help:ChangeLog&diff=12634Help:ChangeLog2010-09-17T21:15:29Z<p>Thomas Rauscher: /* 2010 */ typo</p>
<hr />
<div>== Log for changes in this Wiki installation ==<br />
<br />
=== 2006 ===<br />
* ''math'' tag enabled see [[meta:Help:Math]]<br />
<br />
* upload for ''atn'', ''zip'' and ''mov'' files enabled<br />
<br />
* self written ''pano'' tag extension enabled [[Help:Pano-Tag]]<br />
<br />
* special usergroup + namespace 'WP' for the Working Party of the PanoToolsNG admins<br />
<br />
* changed mysql config to allow searches for words with >=2 letters<br />
<br />
* InterWiki for w:, wikipedia:, m:, meta: enabled [[meta:Help:Interwiki linking]]<br />
<br />
* added Google Analytics to the page template<br />
<small>--[[User:WikiSysop|WikiSysop]] 15:24, 22 July 2006 (CEST)</small><br />
<br />
* added Extension [[meta:ParserFunctions]]<br />
<br />
<small>--[[User:WikiSysop|WikiSysop]] 17:41, 22 July 2006 (CEST)</small><br />
<br />
* added templates for rating star system <br />
** [[Template:RateStar]] (rating stars) use <nowiki>{{RateStar|1}}</nowiki> for one star, <nowiki>{{RateStar|2}}</nowiki> for two stars and so on<br />
** [[Template:RateText]] (rating text) use <nowiki>{{RateText|1}}</nowiki> for "Basic need" and so on<br />
** [[Template:RatingStarSystem]] (rating system description) use <nowiki>{{RatingStarSystem}}</nowiki> for a short description of the different rating stars<br />
<br />
<small>--[[User:Erik Krause|Erik Krause]] 18:03, 22 July 2006 (CEST)</small><br />
<br />
* changed the signature button to <nowiki><small>--~~~~<small></nowiki><br />
<br />
<small>--[[User:WikiSysop|WikiSysop]] 22:20, 22 July 2006 (CEST)</small><br />
<br />
* changed name to "PanoTools" because we got the panotools.org from Ian... waiting now for the nameservers to catch up!<br />
<small>--[[User:WikiSysop|WikiSysop]] 15:22, 25 July 2006 (CEST)</small><br />
<br />
* changed the URLs to wiki.panotools.org with redirects from wiki.panotools.net and wiki.panoramatools.org<br />
<small>--[[User:WikiSysop|WikiSysop]] 14:08, 29 July 2006 (CEST)</small><br />
<br />
* because of the recent misusage of the ''Recent changes'' changes in the WP namespace are only visible to members of the WP user group<br />
<small>--[[User:WikiSysop|WikiSysop]] 15:07, 29 July 2006 (CEST)</small><br />
<br />
* added DPL Extension http://meta.wikimedia.org/wiki/DPL<br />
* added Flash Extension http://meta.wikimedia.org/wiki/Flash<br />
<small>--[[User:WikiSysop|WikiSysop]] 13:27, 6 August 2006 (CEST)</small><br />
<br />
* changed default template: Added FireFox 2/IE 7 OpenSearch reference.<br />
* added [[meta:DynamicFunctions|DynamicFunctions]] extention<br />
<small>--[[User:WikiSysop|WikiSysop]] 14:00, 29 October 2006 (CET)</small><br />
<br />
=== 2007 ===<br />
<br />
* added interwiki to MediaWiki site<br />
* updated to [[mw:Extension:DynamicPageList2|DynamicPageList2]] Version 0.7.8<br />
<small>--[[User:WikiSysop|WikiSysop]] 14:43, 18 March 2007 (CET)</small><br />
<br />
* update to MediaWiki 1.11 + update of most extentions<br />
* installed LockDown instead of NamespacePermission<br />
* added ToggleDisplay extention<br />
* added reCaptcha Extention<br />
<small>--[[User:WikiSysop|WikiSysop]] 15:54, 4 November 2007 (CET)</small><br />
<br />
* Installed asHighlight Extention<br />
<small>--[[User:WikiSysop|WikiSysop]] 17:02, 4 November 2007 (CET)</small><br />
<br />
* Added additional buttons in the toolbar (hacked into EditPage.php)<br />
<small>--[[User:WikiSysop|WikiSysop]] 20:19, 4 November 2007 (CET)</small><br />
[[Category:Info]]<br />
<br />
=== 2010 ===<br />
* New Server! packages needed for the wiki: apt-get install highlight texlive ocaml gs imagemagick<br />
--[[User:Thomas Rauscher|thomas]] 20:30, 17 September 2010 (UTC)</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Help:ChangeLog&diff=12633Help:ChangeLog2010-09-17T20:30:24Z<p>Thomas Rauscher: new server</p>
<hr />
<div>== Log for changes in this Wiki installation ==<br />
<br />
=== 2006 ===<br />
* ''math'' tag enabled see [[meta:Help:Math]]<br />
<br />
* upload for ''atn'', ''zip'' and ''mov'' files enabled<br />
<br />
* self written ''pano'' tag extension enabled [[Help:Pano-Tag]]<br />
<br />
* special usergroup + namespace 'WP' for the Working Party of the PanoToolsNG admins<br />
<br />
* changed mysql config to allow searches for words with >=2 letters<br />
<br />
* InterWiki for w:, wikipedia:, m:, meta: enabled [[meta:Help:Interwiki linking]]<br />
<br />
* added Google Analytics to the page template<br />
<small>--[[User:WikiSysop|WikiSysop]] 15:24, 22 July 2006 (CEST)</small><br />
<br />
* added Extension [[meta:ParserFunctions]]<br />
<br />
<small>--[[User:WikiSysop|WikiSysop]] 17:41, 22 July 2006 (CEST)</small><br />
<br />
* added templates for rating star system <br />
** [[Template:RateStar]] (rating stars) use <nowiki>{{RateStar|1}}</nowiki> for one star, <nowiki>{{RateStar|2}}</nowiki> for two stars and so on<br />
** [[Template:RateText]] (rating text) use <nowiki>{{RateText|1}}</nowiki> for "Basic need" and so on<br />
** [[Template:RatingStarSystem]] (rating system description) use <nowiki>{{RatingStarSystem}}</nowiki> for a short description of the different rating stars<br />
<br />
<small>--[[User:Erik Krause|Erik Krause]] 18:03, 22 July 2006 (CEST)</small><br />
<br />
* changed the signature button to <nowiki><small>--~~~~<small></nowiki><br />
<br />
<small>--[[User:WikiSysop|WikiSysop]] 22:20, 22 July 2006 (CEST)</small><br />
<br />
* changed name to "PanoTools" because we got the panotools.org from Ian... waiting now for the nameservers to catch up!<br />
<small>--[[User:WikiSysop|WikiSysop]] 15:22, 25 July 2006 (CEST)</small><br />
<br />
* changed the URLs to wiki.panotools.org with redirects from wiki.panotools.net and wiki.panoramatools.org<br />
<small>--[[User:WikiSysop|WikiSysop]] 14:08, 29 July 2006 (CEST)</small><br />
<br />
* because of the recent misusage of the ''Recent changes'' changes in the WP namespace are only visible to members of the WP user group<br />
<small>--[[User:WikiSysop|WikiSysop]] 15:07, 29 July 2006 (CEST)</small><br />
<br />
* added DPL Extension http://meta.wikimedia.org/wiki/DPL<br />
* added Flash Extension http://meta.wikimedia.org/wiki/Flash<br />
<small>--[[User:WikiSysop|WikiSysop]] 13:27, 6 August 2006 (CEST)</small><br />
<br />
* changed default template: Added FireFox 2/IE 7 OpenSearch reference.<br />
* added [[meta:DynamicFunctions|DynamicFunctions]] extention<br />
<small>--[[User:WikiSysop|WikiSysop]] 14:00, 29 October 2006 (CET)</small><br />
<br />
=== 2007 ===<br />
<br />
* added interwiki to MediaWiki site<br />
* updated to [[mw:Extension:DynamicPageList2|DynamicPageList2]] Version 0.7.8<br />
<small>--[[User:WikiSysop|WikiSysop]] 14:43, 18 March 2007 (CET)</small><br />
<br />
* update to MediaWiki 1.11 + update of most extentions<br />
* installed LockDown instead of NamespacePermission<br />
* added ToggleDisplay extention<br />
* added reCaptcha Extention<br />
<small>--[[User:WikiSysop|WikiSysop]] 15:54, 4 November 2007 (CET)</small><br />
<br />
* Installed asHighlight Extention<br />
<small>--[[User:WikiSysop|WikiSysop]] 17:02, 4 November 2007 (CET)</small><br />
<br />
* Added additional buttons in the toolbar (hacked into EditPage.php)<br />
<small>--[[User:WikiSysop|WikiSysop]] 20:19, 4 November 2007 (CET)</small><br />
[[Category:Info]]<br />
<br />
=== 2010 ===<br />
* New Server! packaged needed for the wiki: apt-get install highlight texlive ocaml gs imagemagick<br />
--[[User:Thomas Rauscher|thomas]] 20:30, 17 September 2010 (UTC)</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Panotools_Meeting&diff=11945Panotools Meeting2009-10-31T13:41:23Z<p>Thomas Rauscher: added link to 2008 videos</p>
<hr />
<div>There is an annual meeting of the panotools community. These meetings are an opportunity for like-minded photographers to get together and discuss life, the universe and everything. Oh, and panoramas as well. There is a bias towards PanoTools-based software, but everyone is welcome.<br />
<br />
Past meetings:<br />
* 2003 Berlin, Germany<br />
* 2004 Stuttgart, Germany<br />
* 2005 Venice, Italy<br />
* 2006 Bath, UK<br />
* 2007 Lucerne, Switzerland ([http://www.panotools.org/talks07 videos of the talks])<br />
* 2008 Prague, Czech republic ([http://panotools.blip.tv/posts?view=archive videos of the talks])<br />
* 2009 Timisoara, Romania<br />
<br />
Future meetings:<br />
* 2010 Plymouth, UK<br />
<br />
Find more information on the meeting website: http://www.panotools-meeting.com/<br />
<br />
Meeting details, preparation etc. are discussed on the panotools meeting mailing list: http://groups.yahoo.com/group/panotools-meeting<br />
<br />
[[Category:Community]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Panorama_Viewers&diff=10672Panorama Viewers2008-07-18T12:53:59Z<p>Thomas Rauscher: /* Commercial */ added link for Pano2VR</p>
<hr />
<div>There are basically three types of viewers for spherical panoramas:<br />
* [[Java]] based Viewers run on any platform that supports [[Java]].<br />
* Plugin based viewers require a plugin ([[Quicktime]], [[Shockwave]]) to run and might be platform specific.<br />
* Stand alone viewers that are executables for a specific platform.<br />
<br />
== Java based Viewers ==<br />
=== Free ===<br />
* First and until now most versatile is [[PTViewer]] developed originally by [[Helmut Dersch]] and now [[PTViewer 2.7L2|maintained and enhanced]] by [[Fulvio Senore]]<br />
<br />
* [http://www.panorado.com/ Panorado Applet] - a free java viewer applet - "flat" view, but very fast, thus suited for larger images.<br />
<br />
=== Commercial ===<br />
There are some commercial [[Java]] based viewers. Most of them are either a [[PTViewer]] clone or less functional. <br />
* [[Immervision]] Pure Player.<br />
<br />
== Plugin based Viewers ==<br />
<br />
=== Free ===<br />
<br />
* [[Quicktime]] is available for Apple Macintosh and Windows. Requires panorama in [[QTVR]] movie format. ([[PanoCube]] or [[Pano2QTVR]] convert from equirectangular to .mov on Windows)<br />
<br />
* [[freepv]] is an open source cross-platform viewer for [[QTVR]] and other panorama formats.<br />
<br />
* [[DevalVR]] is a windows plugin for viewing panoramic content.<br />
<br />
=== Commercial ===<br />
<br />
* [[PangeaVR]] is a viewer for Mac OSX only that displays both cubic QuickTime-VR panoramas in [[QTVR]] movie format and equirectangular (spherical) [[JPEG]] panoramas by Brian Greenstone. See http://www.pangeasoft.net/pano/plugin/pangeavr.html for details.<br />
<br />
== Flash or Shockwave based Viewers ==<br />
<br />
=== Free ===<br />
<br />
* [[SPi-V]] is a very sophisticated and smooth viewer based on Macromedia [[Shockwave]] that handles panoramas completely in graphics card memory (free version with logo).<br />
<br />
* [[fspp]] is an open source, Flash 9 based player for panoramas in equirectangular format.<br />
<br />
* [[PanoSalado]] is an open source Flash based player for cubic panoramas, see http://www.flashpanos.com/content/welcome-forum-discussion-regarding-panosalado-and-papervision-3d-flash-panorama-delivery<br />
<br />
=== Commercial ===<br />
<br />
* The [http://flashpanoramas.com/player/ Flash Panorama Player] is a cross-platform viewer that displays [[QTVR]] movies as well as equirectangular (spherical) and cylindrical panoramas. Cube faces and stripes can also be handled. It supports SWF-plugins to extend its functionality (for example to integrate distorted FLV-movies as hotspots).<br />
<br />
* [http://gardengnomesoftware.com/pano2vr Pano2VR] (former [[Pano2QTVR]]) creates Flash 8 or Flash 9 SWF files with included spherical viewer.<br />
<br />
* [[krpano]] is a flash 9 based panorama viewer, see http://krpano.com/<br />
<br />
== Stand alone Viewers ==<br />
<br />
* [[FSPViewer]] is a free hardware accelerated stand alone viewer by [[Fulvio Senore]] (Windows only).<br />
<br />
* [[panoglview]] is an Open Source hardware accelerated stand alone viewer for [[Equirectangular Projection]] images (Windows, Linux and OS X).<br />
<br />
* <strike>panoviewer</strike> is an Open Source stand-alone viewer now superceded by [[panoglview]] (Windows, Linux).<br />
<br />
* [[PTViewer]], the original standalone viewer created by [[Helmut Dersch]] in C for X-Windows available from one of the [[mirrors]] (Linux) or the 3.2 version in compiled Java from [http://webuser.fh-furtwangen.de/~dersch/ his page] (Windows).<br />
<br />
* [[Quicktime]] also works as a standalone viewer (Windows, Mac).<br />
<br />
* [[DevalVR]] has a stand alone version, too (Windows).<br />
<br />
* [[freepv]] is a standalone hardware accelerated [[QTVR]] viewer as well as a plugin.<br />
<br />
*[http://www.panorado.com Panorado] is a full-featured image viewer/browser supporting panoramas (JPEG & QTVR). Shareware. (Windows)<br />
<br />
[[Category:Software:Platform:Linux]]<br />
[[Category:Software:Platform:Mac OS X]]<br />
[[Category:Software:Platform:Windows]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Talk:World_Wide_Panorama&diff=10562Talk:World Wide Panorama2008-06-17T23:14:51Z<p>Thomas Rauscher: activated webcal</p>
<hr />
<div>== calendar file URL ==<br />
I just tried to add an iCal address, but the wiki doesn't seem to understand the webcal:// protocol. the complete URL would be webcal://icalx.com/public/Landis/WWP.ics <small>--[[User:Zarl|Carl]] 13:14, 17 June 2008 (CEST)</small><br />
:Could be possible [[User:Thomas Rauscher|Thomas]] can implement this. Best to ask him directly. See [[mw:Manual:%24wgUrlProtocols]] <small>--[[User:Erik Krause|Erik Krause]] 23:14, 17 June 2008 (CEST)</small><br />
::Ok, it is now activated. Thx Erik, for researching the option :).<small>--[[User:Thomas Rauscher|thomas]] 01:14, 18 June 2008 (CEST)</small></div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Field_of_View&diff=10510Field of View2008-05-28T20:57:43Z<p>Thomas Rauscher: Converted formulas to <math></p>
<hr />
<div>{{Glossary|The angle in degrees that a projection covers.}}<br />
The '''angle of view''' of a photograph or camera is a measure of the proportion of a scene included in the image. Simply said: How many degrees of view are included in an image. A typical fixed lens camera might have an angle of view of 50°, a [[Fisheye Projection|fisheye]] lens can have an angle of view greater than 180° and a full [[equirectangular]] or [[cylindrical panorama]] would have an angle of view of 360°.<br />
<br />
Most people speak of '''field of view''' when in fact they mean '''angle of view'''. Field of view is the distance covered by a projection at a certain distance. So if an image exactly shows a 2 meter wide object at 1 meter distance, then the field of view is 2 meter (and the angle of view is 90°).<br />
Angle of view is also known as '''angle of coverage'''. From here on and on the rest of the wiki we will only speak of field of view (although we should speak of angle of view).<br />
<br />
Field of view is often abbreviated as '''FoV'''.<br />
Usually '''field of view''' refers to the '''horizontal field of view''' (hFoV) of an image. Some applications make use of the '''vertical field of view''' (vFoV) which can be calculated from the [[Aspect Ratio]] of the image:<br />
<br />
For rectilinear images:<br />
<br />
<math>Aspect Ratio = \frac{tan(\frac{hFoV}{2})}{tan (\frac{vFoV}{2})}</math><br />
<br />
For fisheye images (approximation):<br />
<br />
<math>Aspect Ratio = \frac{hFoV}{vFoV}</math><br />
<br />
== Conversion from focal length ==<br />
<br />
The other standard measure of the ''width'' or ''narrowness'' of a lens is [[Focal Length]].<br />
<br />
Assuming a 35mm negative width and a [[Rectilinear Projection|rectilinear]] lens, the field of view can be calculated like so:<br />
<br />
<math>FoV = 2 * atan \frac{35}{2 * Focal Length} </math><br />
<br />
See [[Fisheye Projection]] for formulas for [[Fisheyes]].<br />
<br />
== Conversion from horizontal to vertical and vice versa ==<br />
<br />
For fisheye (approximation) and equirectangular images:<br />
<br />
<math>vFoV = hFoV * \frac{height}{width}\ </math><br />
<br />
<math>hFoV = vFoV * \frac{width}{height}\ </math><br />
<br />
For rectilinear images:<br />
<br />
<math>vFoV = 2 * atan( tan(\frac{hFoV}{2}) * \frac{height}{width})</math><br />
<br />
<math>hFoV = 2 * atan( tan(\frac{vFoV}{2}) * \frac{width}{height})</math><br />
<br />
[[Category:Glossary]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Historical:SoC_2008_application&diff=10105Historical:SoC 2008 application2008-03-12T13:48:29Z<p>Thomas Rauscher: /* Steering Committee */ and text fro myself</p>
<hr />
<div>=== Describe your organization ===<br />
<br />
Our organization is a composite of several open source/free software projects: hugin, panotools and enblend/enfuse. We are used to collaborate across timezones and cultures.<br />
<br />
=== Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating? ===<br />
<br />
http://www.flickr.com/search/groups/?q=hugin<br />
<br />
http://www.flickr.com/photos/sbprzd/2126554118/<br />
<br />
http://www.flickr.com/photos/sbprzd/2125768589/<br />
<br />
=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===<br />
<br />
hugin/panotools participated in GSoC 2007. We consider this participation successful for both organization and students. Our projects were:<br />
<br />
* New extensible modular GUI framework for Panorama Photography. Ippei Ukai has refactored the hugin code, cleaning the interface and adding Qt support while keeping wxWidgets compatibility. The upcoming hugin 0.7.4 release will still feature wxWidgets directly bound from the C++ code, mainly because the development of specific Qt widgets is very time consuming. Future plans are to provide hooks for rapid GUI development with higher level languages such as Python (wxPython or PyQt).<br />
* Anti-ghosting HDR panorama blending and merging algorithm. During GSoC Jing presented her results at the IVRPA conference in Berkeley. She successfully finished the project and the code is now merged into hugin source code tree which we expect to release as 0.7.4 soon.<br />
* Interactive Panoramic Viewer. This is a work on FreePV panoramic viewer. Since GSoC the work is still happening in the [http://freepv.svn.sourceforge.net/viewvc/freepv/freepv/branches/branch_leonox/ SoC branch of SVN]. There is no release featuring changes done by the student yet. It is quite possible to see FreePV coce being integrated into VLC which is a popular crossplatform media viewer.<br />
* Feature matching for panoramic images. Zoran Mesec successfully created Matchpoint - a new automatic control points generator that isn't affected by patents. Zoran also volunteered to be mentor for further Matchpoint development this year in GSoC2008 which shows his constant involvement into the project.<br />
* VIPS integration. This project was supposed to bring very large images support to hugin, but failed.<br />
<br />
=== Who will your organization administrator be? Please include Google Account information. ===<br />
<br />
Alexandre Prokoudine will be primary administrator. He currently resides in Moscow, Russia. He is involved into open source projects since early 2002 as technical writer, GUI translator (hugin, Inkscape, Scribus, Audacity, Rosegarden etc.) and functional specifications author.<br />
<br />
Being interested in design and photography since 2005 he quickly started enjoying his role of communicator between developers of various open source projects. In 2006 Jon Philips, a Creative Commons advocate, and he co-founded a CREATE project where developers of creative applications (mostly graphics related ones as of now) can meet and work out standards, unified approaches to solving real life user issues etc.<br />
<br />
In 2007 Alexandre served as backup administrator of hugin/panotools and Scribus organizations for Google Summer of Code.<br />
<br />
His Google account is alexandre.prokoudine@gmail.com<br />
<br />
=== What license(s) does your project use? ===<br />
<br />
Both hugin, enblend/enfuse, panotools and matchpoint use GPL v2 or above. <br />
<br />
=== What is the URL for your ideas page? ===<br />
<br />
http://wiki.panotools.org/SoC_2008_ideas<br />
<br />
=== What is the main development mailing list or forum for your organization? ===<br />
<br />
http://lists.sourceforge.net/lists/listinfo/panotools-devel<br />
<br />
=== What is the main IRC channel for your organization? ===<br />
<br />
We do not use IRC for communication. During GSoC 2007 we used Skype, but this is unlikely to happen again.<br />
<br />
=== Does your organization have an application template you would like to see students use? If so, please provide it now. ===<br />
<br />
* name / university / current enrollment<br />
* short bio / overview of your educational background<br />
* did you ever code in C or C++, yes/no? please provide examples of code.<br />
* do you photograph panoramas? please provide examples.<br />
* do you make other use of hugin/panotools than for stitching panoramas? please describe and show examples.<br />
* were you involved in hugin/panotools development in the past? what was your contribution?<br />
* were you involved in other OpenSource development projects in the past? which, when and in what role?<br />
* why have you chosen your development idea and what do you expect from your implementation?<br />
* how much time you plan to invest in the project? (we expected full time 40h/week but better make this explicit)<br />
* please provide a schedule of how this time will be spent on subtasks of the project. While this is only preliminary, be aware that at the beginning of the project you will be required to provide a detailed plan, and during the project you will issue weekly progress reports against that plan.<br />
<br />
=== Who will be your backup organization administrator? Please include Google Account information. ===<br />
Yuval Levy is chosen to be backup administrator. He did a perfect job as primary administrator during GSoC 2007. His Google associated email address is google at levy.ch.<br />
<br />
=== Who will your mentors be? Please include Google Account information. ===<br />
<br />
'''Pablo d'Angelo'''<br />
<br />
Pablo d'Angelo is the initiator and main developer of the hugin project. He has studied computer engineering at the University of applied sciences Ulm, and is currently working at the DaimlerChrysler Research Center in Ulm, where he does research on advanced 3D reconstruction techniques for industrial quality inspection. He also has a PhD in the field of computer vision from the University of Bielefeld, which was granted in Summer 2007.<br />
<br />
His Google associated account is pablo.dangelo at web.de.<br />
<br />
''' Andrew Mihal '''<br />
<br />
Andrew Mihal is the project lead and main developer of the Enblend/Enfuse project. He received his Ph.D. in Electrical Engineering and Computer Science from the University of California, Berkeley. His specialization is in software for electronic design automation. He is also an amateur photographer, and enjoys turning academic research papers into useful open source projects as a hobby.<br />
<br />
His Google associated account is andrewcmihal at gmail.com<br />
<br />
''' Jim Watters '''<br />
<br />
Jim Watters is a Software Engineer at JFL Peripheral Solution, in Ottawa, Ontario, Canada, where he designs software for scanners. An avid user of PanoTools since 2000. A growing contributer to the source code of PanoTools since Aug 2003 and a current maintainer of PanoTools (http://panotools.sourceforge.net). Before receiving his degree in Computer Software in 1999, he received a diploma of Fine Art in Photography in 1990. <br />
<br />
Most recently his attention has been directed to creating Immersive Panoramic Video. <br />
<br />
His google associated account is jwatters at photocreations.ca.<br />
<br />
''' Daniel M German '''<br />
<br />
He is assistant professor at the Department of Computer Science at the University of Victoria, in British Columbia, in Canada. He received his PhD in Computer Science from the University of Waterloo in Canada.<br />
<br />
One of his areas of research is open source software development. He is interested in understanding how globally distributed individuals are able to work together to create commercial strength software. He has also explored the use of historical artefacts (such as version control logs, emails, defect tracking) to understand how a system has evolved and how this information can be used to continue its development.<br />
<br />
More recently he has been interested in the field of computational photography. More specifically on how to project extreme wide-angle images and spherical panoramas into acceptable flat representations.<br />
<br />
During the last year he has been the maintainer of Panotools (http://panotools.sourceforge.net).<br />
<br />
As a university professor one of his jobs is the supervision of students. He has graduated 6 Master's students, and currently supervising 3 Master's, and 1 Ph.D. Student. He has supervised more than a dozen honours projects of undergraduate students in computer science.<br />
<br />
He is an avid photographer. His works have been exhibited in several galleries. <br />
<br />
His Google associated account is dmg at uvic.ca.<br />
<br />
''' Alexandre Jenny '''<br />
<br />
Alexandre Jenny is graduate from Ecole des mines de Nancy, in physics and computer sciences. He spent 5 years in the computer game industry before starting to interest in panoramic.<br />
<br />
He's casual photographer and he started interest in panorama when he moved near Alps mountains. After having climbed during 5 hours and reached the top, it's really frustrating not beeing able to capture the whole panorama. So he started studying this field at this time. It was during the very early stage of Panotools. The main problem was not being able to create automatically controls points, so he wrote the first SIFT control point generator which is always used a lot today as a Panotools plugin : autopano v1.03. <br />
<br />
After this first release and because he felt that some business could be build upon panoramic, he founded Kolor, a well know business which is the creator of [http://www.autopano.net Autopano Pro], a fully automatic stitcher. Autopano Pro uses an industrial strong implementation of the SIFT algorithm, but has also many other features in a single easy to use package.<br />
<br />
His Google associated account is alexandrejenny at kolor.com.<br />
<br />
'''Zoran Mesec'''<br />
<br />
He is a student in the final year of undergraduate study of Computer and Information Science at University of Ljubljana. He has been a part of hugin's participation at GSoC 07 as a student where he successfully completed the project [[SoC2007_projects#Automatic_feature_detection_for_panoramic_images]] under the mentorship of dr. Bay. He continued to develop his work during the year and created MatchPoint, automatic control point suite. This year he is taking GSoC at a higher level, based on his past experience and knowledge in computer science and photography.<br />
<br />
His Google associated account is zoran.mesec@gmail.com.<br />
<br />
=== What criteria did you use to select these individuals as mentors? Please be as specific as possible. ===<br />
<br />
* academic experience - most of them are or will very soon become PhD and have mentoring experience<br />
* hands on experience with our code<br />
* knowledge of the wider universe of code applied to produce stitched panoramas<br />
* most of them have practical experience of applying the code to panorama production<br />
<br />
=== Steering Committee ===<br />
<br />
This year we also have a steering committee - a group of professionals in panorama making that will help us support our students.<br />
<br />
'''G. Donald Bain'''<br />
<br />
G. Donald Bain manages the Geography Computing Facility at the University of California Berkeley, where he also teaches cartography and field studies. The rest of the time he devotes to VR.<br />
<br />
Hi is a board member of IVRPA.<br />
<br />
He travels and take panoramas for his web site: [http://virtualguidebooks.com/ Don Bain's Virtual Guidebooks]. This project (his wife refers to it as his obsession) has taken him from Tahiti to the Arctic, from the prehistoric ruins of the Southwest to the glaciers of the Canadian Rockies. As a compulsive educator it has been a real treat, documenting and sharing his landscapes with the world. He has taken over 4000 panoramas, with about 3500 currently on the site.<br />
<br />
He co-founded the World Wide Panorama, the largest international collaborative effort showcasing over 3000 panoramas from VR-artists all over the world taken over 11 editions.<br />
<br />
'''Yuval Levy'''<br />
<br />
Last year's GSoC admin for this team. [http://www.photopla.net/] [http://panospace.wordpress.com/]<br />
<br />
'''Bruno Postle'''<br />
<br />
Bruno Postle trained as an architect and now works designing and engineering lightweight/portable/temporary buildings, monumental sculptures and anything else that comes along. Bruno has been a long-time contributor to the [[hugin]] project, and maintains a number of CPAN modules including [http://search.cpan.org/dist/Panotools-Script/ Panotools::Script], a module for manipulating hugin project files. He also [http://www.flickr.com/photos/36383814@N00/ takes panoramic photographs].<br />
<br />
'''Thomas Rauscher'''<br />
<br />
Thomas Rauscher is graduate student at Vienna University of Technology in computer graphics, contributed to several parts of the PanoTools like [[PanoTools Anti Aliasing Filters]], started the [[Freepv]] sourceforge project, and he is a moderator and web admin for PanoTools mailing list. He is also working 3 years in this field with his company [http://gardengnomesoftware.com/ Garden Gnome Software]. In GSoc2007 he help mentoring the [[Interactive Panoramic Viewer]] project.<br />
<br />
'''Ken Turkowski'''<br />
<br />
He is project leader, director, technical contributor, and/or consultant in the areas of 3D graphics, 2D graphics, digital video, image processing, computer vision, image compression, signal processing, dynamics and numerical analysis. Years ago he led research group of QuickTimeVR - the first panoramic images viewer.<br />
<br />
=== What is your plan for dealing with disappearing students? ===<br />
<br />
The very first thing we'll do is making sure we pick the right students. Our estimations are going to be based on the following criteria:<br />
<br />
* students should be avid photographers;<br />
* students should be able to prove that their programmings skill match our request;<br />
* students should be able to prove that they have experience working with a mentor.<br />
<br />
We are going to do our best to have them understand that GSoC is a both (close to) full time job and fun, so that they treat it with responsibility, but do not consider it a total boredom.<br />
<br />
Next step is motivation. <br />
<br />
The point of participating at GSoC for us is getting new contributors who bring innovation and stick to affiliated projects.<br />
<br />
Last year we organized delivery to student of brand new panoramic heads sponsored by their manufacturer - Agno's Tech Engineering. We are investigating such possibility for this year's project again.<br />
<br />
Depending on the context it might also be possible to structure the work as academic credits to further incentivation.<br />
<br />
In case a student cannot deliver good enough results we are not going to drop all the work he managed to do and keep development at highest possible pace to make sure the community around affiliated project will not suffer in any way and any amount of money invested to the project by Google isn't completely lost.<br />
<br />
=== What is your plan for dealing with disappearing mentors? ===<br />
<br />
The selected mentors are well known and connected in the community. We estimate the risk of a disappearing mentor to be very low. To minimize the impact of such an unlikely event we strive to have several backup mentors who can replace others. In the event that one of the two mentors disappears, recruiting efforts for a backup mentor will start immediately. Our steering committee is well connected and will support the organizer in the efforts to recruit replacement mentors. Our community has already experienced the disappearing of key figures on important projects and survived the test when Helmut Dersch, founding father of the panotools library that is at the core of our community, disappeared.<br />
<br />
=== What steps will you take to encourage students to interact with your project's community before, during and after the program? ===<br />
<br />
First of all, we hope to recruit a student from the community. This is a growing and vibrant community. We will make sure that the student has the appropriate gear to shoot panoramas and we will do all we can to share with them our passion for panoramas. We have already organized a fund raiser to donate a fish-eye lens to one of the project maintainers [http://www.nabble.com/Fundraising-complete!-t2725697.html] in 2006, a pano head for each student in 2007, and we can do this again and again.<br />
<br />
=== What will you do to ensure that your accepted students stick with the project after GSoC concludes? ===<br />
<br />
We will make sure he or she enjoys the practical aspects of panorama photography. Part of the assignement will be of practical nature: *use* the software to learn it, not just *code*. We intend to ask them to participate in the [http://www.worldwidepanorama.com/ World Wide Panorama].<br />
<br />
[[Category:Community:Project]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Enfuse&diff=9902Enfuse2008-01-22T17:35:27Z<p>Thomas Rauscher: /* Known bugs */ LZW/DEFLATE links to wikipedia</p>
<hr />
<div>[[Image:2125768589_b.jpg|thumb|[[:Image:2125768589_b.jpg|Four exposure panorama blended with enfuse]]]]<br />
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.<br />
<br />
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] The implementation was done by Andrew Mihal (developer of [[Enblend]]) and the [[hugin]] team around [[User:Pablo|Pablo d'Angelo]]<br />
<br />
== State of development ==<br />
Enfuse is currently in beta and available with the development version of [[Enblend]] (windows): [http://hugin.panotools.org/testing/enblend/enblend-3.1_win32_pre3.zip] or build it yourself<br />
[[Hugin_Compiling_OSX#Building_Enblend_.28using_Fink.29|for OS X]]<br />
<br />
=== Known bugs ===<br />
* '''Windows version only''': if used on too many and/or too large files enfuse terminates with an error message: <code>an exception occured [...] unable to create image swap file</code><br />
:: - will be fixed in final version<br />
<br />
* If used on images with unaligned alpha mask (result of aligning handheld shots) there might be colored or dark spots.<br />
: Workaround: crop the aligned images.<br />
:: - will probably be fixed in final version<br />
<br />
* If contrasty structures are near [[zenith]] or [[nadir]] in an [[equirectangular]] image, there might be an artifact (vortex) in the resulting pano.<br />
: Workaround: use on zenith and nadir images separately and stitch them in the resulting pano afterwards.<br />
:: - unknown, whether could be fixed easily<br />
<br />
* actually not a bug: Default compression for [[JPEG]] output is relatively low.<br />
: Workaround: Specify <code>--compression=100</code> on the command line if you need JPEG output.<br />
:: - default will be a reasonably high value in the final version<br />
<br />
* [[wikipedia:LZW|LZW]] compression for [[TIFF]] files is currently not supported.<br />
: Workaround: use [[wikipedia:DEFLATE|DEFLATE]] (ZIP) compression instead.<br />
<br />
== Description ==<br />
Enfuse merges overlapping images using the Mertens-Kautz-Van Reeth exposure fusion algorithm. This is a quick way to produce 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.<br />
<br />
Enfuse can also be used to build extended [[Depth_of_Field|DOF]] images, by blending a focus stack.<br />
<br />
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. A Burt & Adelson multiresolution spline blender is used to combine the images according to the weights. The multiresolution blending ensures that transitions between regions where different images contribute more heavily are difficult to see.<br />
<br />
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 focussed images.<br />
<br />
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).<br />
<br />
Enfuse expects 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 contribute to the final output. Any alpha value other than zero is interpreted as "this pixel should contribute to the final image".<br />
<br />
== Usage ==<br />
The usage below refers to the CVS version of the 21 Dec 2007. Use enfuse as follows:<br />
enfuse <options> <input files>.<br />
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.<br />
<br />
=== Common options ===<br />
<br />
-h<br />
Print information on the available options. <br />
-l num<br />
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. If you specify a high number Enfuse may still use a smaller number of levels if the geometry of the images demands it. <br />
-o output-file<br />
Required. Specify the name of the output file. <br />
-v<br />
Verbose output. <br />
-w<br />
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. <br />
--compression=COMP<br />
Write a compressed output file. Valid values are [[LZW]] and [[DEFLATE]] for TIFF files, and numbers from 0-100 for JPEG files.<br />
<br />
=== Extended options ===<br />
<br />
-b kilobytes<br />
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. <br />
-c<br />
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. <br />
-g<br />
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. <br />
-f WIDTHxHEIGHT+x0+y0<br />
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. <br />
-m megabytes<br />
Set the size of Enfuse's image cache. This is the amount of memory Enfuse will use for storing image data before swapping to disk. The default is 1 GiB.<br />
<br />
=== Fusion options ===<br />
<code>W</code> is a number between 0 (no weight) and 1 (full weight)<br />
--wExposure=W<br />
Sets the relative weight of the well-exposedness criteria. Increasing this weight relative to the others will make well-exposed pixels contribute more to the final output. <br />
--wSaturation=W<br />
Sets the relative weight of high-saturation pixels. Increasing this weight makes pixels with high saturation contribute more to the final output. <br />
--wContrast=W<br />
Sets the relative weight of high-contrast pixels.<br />
<br />
=== Expert options ===<br />
<br />
--ContrastWindowSize<br />
Window size for local contrast analysis. Values larger than 5 might result in a blurry composite and increased computation times. Values in the range of 3 to 5 have given good results on focus stacks.<br />
<br />
--HardMask<br />
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.<br />
<br />
--debug<br />
Output intermediate images for debugging.<br />
<br />
== See also ==<br />
* [http://www.nabble.com/A-christmas-present-td14438390.html Announcement on Panotools-NG]<br />
<br />
[[Category:Software:Platform:Mac OS X]]<br />
[[Category:Software:Platform:Linux]]<br />
[[Category:Software:Platform:Windows]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Enfuse&diff=9901Enfuse2008-01-22T17:32:23Z<p>Thomas Rauscher: link to Pablos user page</p>
<hr />
<div>[[Image:2125768589_b.jpg|thumb|[[:Image:2125768589_b.jpg|Four exposure panorama blended with enfuse]]]]<br />
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.<br />
<br />
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] The implementation was done by Andrew Mihal (developer of [[Enblend]]) and the [[hugin]] team around [[User:Pablo|Pablo d'Angelo]]<br />
<br />
== State of development ==<br />
Enfuse is currently in beta and available with the development version of [[Enblend]] (windows): [http://hugin.panotools.org/testing/enblend/enblend-3.1_win32_pre3.zip] or build it yourself<br />
[[Hugin_Compiling_OSX#Building_Enblend_.28using_Fink.29|for OS X]]<br />
<br />
=== Known bugs ===<br />
* '''Windows version only''': if used on too many and/or too large files enfuse terminates with an error message: <code>an exception occured [...] unable to create image swap file</code><br />
:: - will be fixed in final version<br />
<br />
* If used on images with unaligned alpha mask (result of aligning handheld shots) there might be colored or dark spots.<br />
: Workaround: crop the aligned images.<br />
:: - will probably be fixed in final version<br />
<br />
* If contrasty structures are near [[zenith]] or [[nadir]] in an [[equirectangular]] image, there might be an artifact (vortex) in the resulting pano.<br />
: Workaround: use on zenith and nadir images separately and stitch them in the resulting pano afterwards.<br />
:: - unknown, whether could be fixed easily<br />
<br />
* actually not a bug: Default compression for [[JPEG]] output is relatively low.<br />
: Workaround: Specify <code>--compression=100</code> on the command line if you need JPEG output.<br />
:: - default will be a reasonably high value in the final version<br />
<br />
* [[LZW]] compression for [[TIFF]] files is currently not supported.<br />
: Workaround: use [[DEFLATE]] (ZIP) compression instead.<br />
<br />
== Description ==<br />
Enfuse merges overlapping images using the Mertens-Kautz-Van Reeth exposure fusion algorithm. This is a quick way to produce 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.<br />
<br />
Enfuse can also be used to build extended [[Depth_of_Field|DOF]] images, by blending a focus stack.<br />
<br />
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. A Burt & Adelson multiresolution spline blender is used to combine the images according to the weights. The multiresolution blending ensures that transitions between regions where different images contribute more heavily are difficult to see.<br />
<br />
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 focussed images.<br />
<br />
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).<br />
<br />
Enfuse expects 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 contribute to the final output. Any alpha value other than zero is interpreted as "this pixel should contribute to the final image".<br />
<br />
== Usage ==<br />
The usage below refers to the CVS version of the 21 Dec 2007. Use enfuse as follows:<br />
enfuse <options> <input files>.<br />
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.<br />
<br />
=== Common options ===<br />
<br />
-h<br />
Print information on the available options. <br />
-l num<br />
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. If you specify a high number Enfuse may still use a smaller number of levels if the geometry of the images demands it. <br />
-o output-file<br />
Required. Specify the name of the output file. <br />
-v<br />
Verbose output. <br />
-w<br />
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. <br />
--compression=COMP<br />
Write a compressed output file. Valid values are [[LZW]] and [[DEFLATE]] for TIFF files, and numbers from 0-100 for JPEG files.<br />
<br />
=== Extended options ===<br />
<br />
-b kilobytes<br />
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. <br />
-c<br />
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. <br />
-g<br />
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. <br />
-f WIDTHxHEIGHT+x0+y0<br />
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. <br />
-m megabytes<br />
Set the size of Enfuse's image cache. This is the amount of memory Enfuse will use for storing image data before swapping to disk. The default is 1 GiB.<br />
<br />
=== Fusion options ===<br />
<code>W</code> is a number between 0 (no weight) and 1 (full weight)<br />
--wExposure=W<br />
Sets the relative weight of the well-exposedness criteria. Increasing this weight relative to the others will make well-exposed pixels contribute more to the final output. <br />
--wSaturation=W<br />
Sets the relative weight of high-saturation pixels. Increasing this weight makes pixels with high saturation contribute more to the final output. <br />
--wContrast=W<br />
Sets the relative weight of high-contrast pixels.<br />
<br />
=== Expert options ===<br />
<br />
--ContrastWindowSize<br />
Window size for local contrast analysis. Values larger than 5 might result in a blurry composite and increased computation times. Values in the range of 3 to 5 have given good results on focus stacks.<br />
<br />
--HardMask<br />
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.<br />
<br />
--debug<br />
Output intermediate images for debugging.<br />
<br />
== See also ==<br />
* [http://www.nabble.com/A-christmas-present-td14438390.html Announcement on Panotools-NG]<br />
<br />
[[Category:Software:Platform:Mac OS X]]<br />
[[Category:Software:Platform:Linux]]<br />
[[Category:Software:Platform:Windows]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=PTViewer&diff=9657PTViewer2007-12-14T16:42:40Z<p>Thomas Rauscher: added Glossary</p>
<hr />
<div>== History and Versions ==<br />
PTViewer {{Glossary|is the [[Equirectangular Projection|equirectangular]] and [[Cylindrical Projection|cylindrical]] panorama viewer originally distributed with the [[Panorama tools]] package|1}}. It currently is available in some different flavours: <br />
* The last version of PTViewer from [[Helmut Dersch]] before he closed his page is 2.5 and can be found on some [[Mirrors]] of this page.<br />
* At that time [[Helmut Dersch]] was working at version 2.6 that has only been available as a beta version. Its main feature was support for partial panoramic images (less than 360°).<br />
* PTViewer development moved to [http://sourceforge.net/projects/ptviewer/ Sourceforge] in 2003 but didn't yield reasonable results til now (?)<br />
* [[Fulvio Senore]] presented the first beta of his PTViewer version on 18 Jan 2004 which used a far better [[interpolation|interpolator]] (Lanczos2, hence the version line was called 'L2') which is constantly developed since then now having reached Version 2.8 final on 7 Sept. 2006: See http://www.fsoft.it/panorama/ptviewer.htm for details.<br>This line currently is the most sophisticated version of PTViewer for non-HDR panoramas, featuring very good image quality, dynamic slice loading, large viewer windows (up to fullscreen) and many other enhancements.<br />
* Around christmas 2003 [[Helmut Dersch]] introduced PTViewer 3 which as major new feature had HDR (high [[dynamic range]]) capabilites with a floating point extension to the [[JPEG]] format (called [[FJPG]]) and adaptive dynamic range in the viewer. This version has grown to 3.1.2 until now. See http://webuser.fh-furtwangen.de/~dersch/ for details.<br />
* 20 May 2004 he came out with [[PTViewerME]], a version for PDAs and Mobile Devices running on J2ME, Sun's microedition runtime for the [[Java]] language. Details again on http://webuser.fh-furtwangen.de/~dersch/<br />
<br />
== Features ==<br />
Since there are so many versions it's difficult to maintain a comprehensive list of features of PTViewer. I start with the slightly edited feature list found in the PTViewer 2.4 documentation (please correct and add):<br />
* [[Equirectangular Projection|Equirectangular]] and [[Cylindrical Projection|Cylindrical]] Panorama Playback: Horizontal field of view: 360°, Vertical field of view 0-180°.<br />
* Playback of [[Quicktime]] [[QTVR]] panoramas (Cylinders and Cubes) and Object movies (eventually using PTMViewer extension).<br />
* Display of rectilinear Images using optional PTZoom extension (not all versions)<br />
* Panning, tilting and zooming. Full navigation using either mouse or keyboard.<br />
* High Quality bilinear rendering as found in better plug-in viewers, even better Lanczos2 [[interpolation]] in the [http://www.fsoft.it/panorama/ptviewer.htm L2 version line].<br />
* Antialiasing for display of high resolution images.<br />
* Image and window size only limited by [[Java]] system memory.<br />
* Link any document to any point in the image using hotspots.<br />
* Configurable Controls in Appletwindow.<br />
* Complete VR-Tours in Browsers and Appletviewer.<br />
* Scriptable via html/javascript and internal scripting system<br />
* Tiny file size (25-70kByte) for fast download.<br />
* Package all files into one self-displaying tour using the [[JAR]] utility, see [[create a custom ptviewer jar file]].<br />
* Display 3D-objects, Panorama Movies and animations using auxiliary helper applets included in the distribution.<br />
* Supports fast downloading low resolution preview panoramas and high resolution zoomable features (ROI).<br />
* Optional protection of panoramas and images by encryption.<br />
<br />
== Usage ==<br />
On the panotools [[Mirrors]] or on [http://webuser.fh-furtwangen.de/~dersch/ Helmut Dersch's] site you find a basic PTViewer documentation.<br />
<br />
There are lots of PTViewer tutorials on the web. As a good starting point see the [http://www.path.unimelb.edu.au/~bernardk/tutorials/360/ptviewer/index.html PTViewer section] of [http://www.path.unimelb.edu.au/~bernardk/tutorials/360/index.html Big Ben's Panorama Tutorials]<br />
<br />
The most comprehensive site on PTViewer (version 2.7L2 from Fulvio Senore) parameters, scripting and features is http://users2.ev1.net/~wufdog/PT/ <br />
<br />
=== Internal ===<br />
There are some tutorials on the Wiki as well:<br />
* [[Partial Panoramas using ROI in PTViewer]]<br />
* [[create a custom ptviewer jar file]]<br />
* [[have a single ptviewer jar file per website]]<br />
<br />
<small>created by [[User:Erik Krause|Erik Krause]] 16:39, 14 Apr 2005 (EDT)</small><br />
<br />
[[Category:Software:Platform:Windows]]<br />
[[Category:Software:Platform:Mac OS X]]<br />
[[Category:Software:Platform:Linux]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=File:SVG-Logo.svg&diff=9631File:SVG-Logo.svg2007-12-04T02:55:06Z<p>Thomas Rauscher: Test for SVG upload</p>
<hr />
<div>Test for SVG upload</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Partial_Panorama&diff=9602Partial Panorama2007-12-01T02:01:53Z<p>Thomas Rauscher: Redirect to the panorama page</p>
<hr />
<div>#REDIRECT [[Panorama#Partial_panoramas]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=PanoTools&diff=9601PanoTools2007-12-01T01:45:32Z<p>Thomas Rauscher: added to glossary</p>
<hr />
<div>#REDIRECT [[Panorama tools]]<br />
[[Category:Glossary]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Panorama_tools&diff=9600Panorama tools2007-12-01T01:43:43Z<p>Thomas Rauscher: ...looks better now in the Glossary page</p>
<hr />
<div>== What are the panorama tools ==<br />
{{Glossary|A free suite of programs and libraries originally written by professor [[Helmut Dersch]]}}<br />
The Panorama Tools, also known as ''The PanoTools'' are a free suite of programs and libraries originally written by the german physics and mathematics professor [[Helmut Dersch]]. PanoTools provides a powerful framework for re-projecting and blending multiple source images into immersive panoramics of many types. An updated version of the PanoTools library serves as the underlying core engine for many software panorama [[GUI front-ends]].<br />
<br />
Helmut started development on PanoTools in 1998, producing some of the most professional and versatile software available for building panoramas and more, but had to stop development in 2001 due to legal harrassment and claims of patent infringement by a company called [[Ipix|IPIX]]. In 2003 he released some modifications to the java-based online panorama viewer [[PTViewer]]. One involved a standalone .exe version and another version could display HDR (high [[dynamic range]]) panoramas. The most recent release from Helmut is PTViewerME, a panorama viewer for PDAs and mobile devices. The homepage of Helmut can be found [http://webuser.fh-furtwangen.de/~dersch/ here]. It has no links to his older work on PanoTools, but some list members managed to make a copy of his old homepage before it shut down. See [[Mirrors]] for some links to these pages and additional information.<br />
<br />
After Helmut stopped developing Panorama Tools, the members of his mailing-list took over development, and began enhancing the software suite on their own. They started a [http://panotools.sourceforge.net/ sourceforge page] and have fixed some bugs and developed additional functionality since.<br />
<br />
== What software is included in the panorama tools ==<br />
Quoted from Helmuts original homepage:<br />
<br />
'''PanoTools is a collection of free tools for Panorama and 3D Object creation . It consists of: '''<br />
<br />
{|<br />
| ''[[PTEditor]]'' || Java interactive Panorama Editor.<br />
|-<br />
| ''[[PTPicker]]'' || Java front end to panorama stitcher and other tools. It provides a graphical interface for feature point selection and position optimization.<br />
|-<br />
| ''[[PTCrypt]]'' || Java tool for scrambling pictures intended to be viewed online with ptviewer.<br />
|-<br />
| ''[[PTStitcher]]'' || Panorama stitching tool which remaps, adjusts and combines arbitrary images to panoramic views.<br />
|-<br />
| ''[[PTOptimizer]]'' || Optimizes positions and sizes of images using control-point data.<br />
|-<br />
| ''[[PTStereo]]'' || Creates 3-dimensional objects from 2 stereoscopic or more images.<br />
|-<br />
| ''[[PTInterpolate]]'' || Physically valid true view interpolator. Given two images of the same scene taken from different positions, this tool creates views from any intermediate position.<br />
|-<br />
| ''[[PTMorpher]]'' || Morphing tool.<br />
|-<br />
| ''[[PTAverage]]'' || Averages images to reduce noise and enhance density.<br />
|-<br />
| ''[[PTStripe]]'' || Combines images into movie-stripes for viewing in object-viewers (PTMovie extension to PTViewer).<br />
|-<br />
| ''[[Panorama Tools Plugins]]'' || [[Photoshop]], GraphicConverter and [[Gimp]] plug-ins for image correction and remapping. Also compatible to many other programs that can use [[Photoshop]] plugins.<br />
|-<br />
| ''[[pano12]]'' library || The underlying panorama library, currently used by several different panorama front-ends and command line programs. This may be called pano12.dll, libpano12.so, libpano12.dylib or pano12.lib depending on the operating system.<br />
|}<br />
<br />
To make working with the panorama tools easier and to add functionality, many excellent software helpers and [[GUI front-ends]] to PanoTools, some free and some commercial, have been written, which in many cases make interacting directly with the programs in the original PanoTools toolset unnecessary. See the [[Software|software]] page to learn more.<br />
<br />
[[Category:Software:Platform:Linux]]<br />
[[Category:Software:Platform:Windows]]<br />
[[Category:Software:Platform:Mac OS X]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Panorama_tools&diff=9599Panorama tools2007-12-01T01:41:40Z<p>Thomas Rauscher: added to glossary</p>
<hr />
<div>== What are the panorama tools ==<br />
{{Glossary|are a free suite of programs and libraries originally written by professor [[Helmut Dersch]]}}<br />
The Panorama Tools, also known as ''The PanoTools'' are a free suite of programs and libraries originally written by the german physics and mathematics professor [[Helmut Dersch]]. PanoTools provides a powerful framework for re-projecting and blending multiple source images into immersive panoramics of many types. An updated version of the PanoTools library serves as the underlying core engine for many software panorama [[GUI front-ends]].<br />
<br />
Helmut started development on PanoTools in 1998, producing some of the most professional and versatile software available for building panoramas and more, but had to stop development in 2001 due to legal harrassment and claims of patent infringement by a company called [[Ipix|IPIX]]. In 2003 he released some modifications to the java-based online panorama viewer [[PTViewer]]. One involved a standalone .exe version and another version could display HDR (high [[dynamic range]]) panoramas. The most recent release from Helmut is PTViewerME, a panorama viewer for PDAs and mobile devices. The homepage of Helmut can be found [http://webuser.fh-furtwangen.de/~dersch/ here]. It has no links to his older work on PanoTools, but some list members managed to make a copy of his old homepage before it shut down. See [[Mirrors]] for some links to these pages and additional information.<br />
<br />
After Helmut stopped developing Panorama Tools, the members of his mailing-list took over development, and began enhancing the software suite on their own. They started a [http://panotools.sourceforge.net/ sourceforge page] and have fixed some bugs and developed additional functionality since.<br />
<br />
== What software is included in the panorama tools ==<br />
Quoted from Helmuts original homepage:<br />
<br />
'''PanoTools is a collection of free tools for Panorama and 3D Object creation . It consists of: '''<br />
<br />
{|<br />
| ''[[PTEditor]]'' || Java interactive Panorama Editor.<br />
|-<br />
| ''[[PTPicker]]'' || Java front end to panorama stitcher and other tools. It provides a graphical interface for feature point selection and position optimization.<br />
|-<br />
| ''[[PTCrypt]]'' || Java tool for scrambling pictures intended to be viewed online with ptviewer.<br />
|-<br />
| ''[[PTStitcher]]'' || Panorama stitching tool which remaps, adjusts and combines arbitrary images to panoramic views.<br />
|-<br />
| ''[[PTOptimizer]]'' || Optimizes positions and sizes of images using control-point data.<br />
|-<br />
| ''[[PTStereo]]'' || Creates 3-dimensional objects from 2 stereoscopic or more images.<br />
|-<br />
| ''[[PTInterpolate]]'' || Physically valid true view interpolator. Given two images of the same scene taken from different positions, this tool creates views from any intermediate position.<br />
|-<br />
| ''[[PTMorpher]]'' || Morphing tool.<br />
|-<br />
| ''[[PTAverage]]'' || Averages images to reduce noise and enhance density.<br />
|-<br />
| ''[[PTStripe]]'' || Combines images into movie-stripes for viewing in object-viewers (PTMovie extension to PTViewer).<br />
|-<br />
| ''[[Panorama Tools Plugins]]'' || [[Photoshop]], GraphicConverter and [[Gimp]] plug-ins for image correction and remapping. Also compatible to many other programs that can use [[Photoshop]] plugins.<br />
|-<br />
| ''[[pano12]]'' library || The underlying panorama library, currently used by several different panorama front-ends and command line programs. This may be called pano12.dll, libpano12.so, libpano12.dylib or pano12.lib depending on the operating system.<br />
|}<br />
<br />
To make working with the panorama tools easier and to add functionality, many excellent software helpers and [[GUI front-ends]] to PanoTools, some free and some commercial, have been written, which in many cases make interacting directly with the programs in the original PanoTools toolset unnecessary. See the [[Software|software]] page to learn more.<br />
<br />
[[Category:Software:Platform:Linux]]<br />
[[Category:Software:Platform:Windows]]<br />
[[Category:Software:Platform:Mac OS X]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Hugin&diff=9598Hugin2007-12-01T01:37:53Z<p>Thomas Rauscher: added to glossary</p>
<hr />
<div>'''Hugin''' {{Glossary|is an opensource graphical user interface (GUI) for [[Panorama tools]]|1}}.<br />
<br />
Like other [[GUI front-ends]], '''hugin''' provides an easy-to-use unified point-and-click interface to a whole range of other command-line tools including:<br />
<br />
* [[autopano-sift]], [[autopano-sift-C]] or [[autopano]] for automatic creation of [[control points]].<br />
* [[nona]] or [[PTmender]] for remapping input images and rendering output images.<br />
* [[enblend]] for seamless blending of output images.<br />
<br />
The Hugin project's mission is not only to provide a powerful GUI, but also to provide opensource replacements for the small number of closed source components of [[Panorama tools]], especially [[PTStitcher]].<br />
A [[PTStitcher]] replacement, called [[nona]] has been developed, supporting its most important features.<br />
<br />
Among the many flexible Hugin workflow options, it is possible to use increased tonal range data in a [[16bit workflow with hugin]] or work entirely with high [[dynamic range]] images such as floating-point [[TIFF]] from start to finish in a [[HDR workflow with hugin]].<br />
<br />
== Hugin components ==<br />
<br />
The following tools are part of the hugin suite:<br />
<br />
* [[hugin]] the gui front end.<br />
* [[nona]] a command-line replacement for [[PTStitcher]].<br />
* [[fulla]] correction of [[barrel distortion]], [[chromatic aberration]] and [[vignetting]].<br />
* [[nona_gui]] a version of [[nona]] with simple gui progress dialogs, similar to the windows version of [[PTStitcher]].<br />
* [[autooptimiser]] an experimental tool with the same interface as [[PTOptimizer]] except using pairwize optimization which doesn't require any manual pre-placement.<br />
* [[align_image_stack]] a tool to automate the process to [[align a stack of photos]].<br />
* [[vig_optimize]] command line tool to estimate photometric parameters.<br />
* [[panoglview]] OpenGL panorama viewer stored in sourceforge CVS alongside [[hugin]] which must be built separately.<br />
* [[hugin_hdrmerge]] merges multiple exposures to [[HDR]] using Khan anti-ghosting algorithm<br />
* [[hugin_stitch_project]] batch stitches a hugin project, performing any [[HDR]] merging or blending as necessary.<br />
<br />
More information, documentation and tutorials are available on the project website.<br />
<br />
== User interface ==<br />
<br />
* [[Hugin Main window]]<br />
* [[Hugin Assistant tab]]<br />
* [[Hugin Images tab]]<br />
* [[Hugin Camera and Lens tab]]<br />
* [[Hugin Crop tab]]<br />
* [[Hugin Control Points tab]]<br />
* [[Hugin Optimizer tab]]<br />
* [[Hugin Exposure tab]]<br />
* [[Hugin Stitcher tab]]<br />
* [[Hugin Preferences]]<br />
* [[Hugin Preview window]]<br />
* [[Hugin Control Points table]]<br />
* [[Hugin Keyboard shortcuts]]<br />
<br />
== Development ==<br />
<br />
Hugin is Open Source, and as such very much dependent on voluntary contributions of resources. If you have coding skills, you are welcome to look at the source code and contribute to it. Even if you don't have coding skills, you most likely have some skills that the project could use and you are more than welcome to contribute your time. The tasks requiring attention change frequently and so do the required skillset and resources. Join the hugin-ptx mailing list to find out what is going on at the moment and how you can help.<br />
<br />
At the time of writing (29-October-2007) there is a major effort going on to document and automate the building process of hugin so that the project can release binaries more frequently. See Test Builds below.<br />
<br />
== Test Builds ==<br />
<br />
=== Goal ===<br />
<br />
an infrastructure for on-demand build and distribution of usable test-binaries for the most popular platforms. These builds are meant to enable users to test the newest features and report bugs. Ideally, on Pablo's demand all those who have a build chain will run it against the newest source code to produce the builds.<br />
<br />
=== Process ===<br />
<br />
# Experienced users will build the most current hugin and helpers (libpano, enblend, autopano, etc.) for the target platform of their choice, with support from coders.<br />
# The build process will be documented for each of the supported platform.<br />
# Users willing to spend some time learning how to build will reproduce the documented process.<br />
# Power users will script and automate the building process.<br />
# Users with packaging skills will package the builds for distribution (installers).<br />
# The produced binaries/installers will be made available on the web.<br />
<br />
=== Specific revisions ===<br />
<br />
When building from the repository, some revisions have bugs. This process is meant to build the latest revision so that if the latest revision has bugs these can be identified and corrected. However sometimes these bugs can be more critical than other times. If you need a more or less working version of hugin, try applying the process to one of the following revisions.<br />
<br />
<br />
{| style="margin: 1em auto 1em auto;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Revision<br />
! width="500" |<br />
Comments<br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
2539<br />
| style="border-top: thin dotted #333333;" |<br />
[http://groups.google.com/group/hugin-ptx/browse_thread/thread/e67e1d5a6215b951]<br />
|-valign="top"<br />
|}<br />
<br />
<br />
<br />
<br />
=== Supported Platforms ===<br />
<br />
* If you don't find your preferred platform listed below '''and''' you are willing to contribute your time and skills to build hugin on it, feel free to add it to the table. We will accommodate any well supported platform in the regular release process.<br />
* The '''Build-Chain Responsibles''' listed below have access to a build chain on the selected platform and have agreed to run the build chain within 2 days of a request from Pablo. They will forward the resulting binary package to the Release Manager who will in turn put them up for download by the general public.<br />
* '''Redundancy is good'''. If you have access to one of the listed platforms, please try to run the documented process below and report success to hugin-ptx. If you think you could do this on a more regular basis, enter yourself in the Backup Build-Chain field.<br />
<br />
<br />
{| style="margin: 1em auto 1em auto;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"<br />
|-valign="top"<br />
! width="100" |<br />
Platform<br />
! width="100" |<br />
Status<br />
! width="100" |<br />
Process<br />
! width="200" |<br />
Build-Chain Responsible<br />
! width="200" |<br />
Credits <br />
! width="200" |<br />
Backup Build-Chains <br />
|-valign="top" <br />
! style="border-top: thin dotted #333333;" |<br />
ubuntu 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Ubuntu | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Sébastien Perez-Duarte<br />
* Yuval Levy<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
ubuntu 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Ubuntu | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Fedora 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Fedora | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Bruno Postle<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Fedora 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Fedora | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OSX IntelMac <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OSX | draft]]<br />
| style="border-top: thin dotted #333333;" |<br />
Peter A. Crowley<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Ippei Ukai<br />
* JD Smith <br />
* Daniel M. German<br />
* Peter A. Crowley<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OSX PPC <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OSX | draft]]<br />
| style="border-top: thin dotted #333333;" |<br />
Peter A. Crowley<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
Windows 32bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling Windows | draft]]<br />
| style="border-top: thin dotted #333333;" |<br />
Tom Sharpless<br />
| style="border-top: thin dotted #333333;" |<br />
* Tom Sharpless<br />
* John Navas<br />
* Jean-Marc Paratte<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OpenSuse 32bit<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OpenSuse | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" rowspan="2" |<br />
* Kornel Benko (10.3)<br />
* Peter Suetterlin (10.2)<br />
* Stephan Hegel (10.3 x86_64)<br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
OpenSuse 64bit <br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
| style="border-top: thin dotted #333333;" |<br />
[[Hugin Compiling OpenSuse | tbd]]<br />
| style="border-top: thin dotted #333333;" |<br />
tbd<br />
<!-- spanned style="border-top: thin dotted #333333;" | --><br />
| style="border-top: thin dotted #333333;" |<br />
|-valign="top"<br />
! style="border-top: thin dotted #333333;" |<br />
all platforms<br />
! style="border-top: thin dotted #333333;" colspan="5" |<br />
a big thank you to '''Pablo d'Angelo''' for supporting all of those building efforts.<br />
|-valign="top"<br />
|}<br />
<br />
=== Stati ===<br />
<br />
'''Build Chain'''<br />
* tbd: looking for responsible<br />
* OK: mostly automated build process ready on request<br />
* unavailable: temporarily unavailable (e.g. responsible on holiday)<br />
* HW-broken: the hardware is temporarily unavailable<br />
* SW-broken: temporarily dysfunctional, working on a fix<br />
* broken: nobody is working on a fix<br />
* unsupported: has been dropped for lack of support<br />
<br />
'''Process'''<br />
* tbd: status unknown<br />
* auto: work as documented and has been automated to a reasonable extent<br />
* OK: works as documented, could use automation / scripting<br />
* draft: documented, needs validation / testing / cleaning<br />
* incomplete: parts are missing (e.g. enblend, libpano)<br />
* outdated: worked in the past but needs an update<br />
* obsolete: nobody has the time to update<br />
<br />
=== Publication ===<br />
* Release Manager: tbd<br />
* Download / Webspace: thank you Thomas Rauscher / panotools.org, links will be published soon<br />
<br />
== See also ==<br />
* [[hugin FAQ]] Frequently asked questions about hugin<br />
<br />
== External links ==<br />
* [http://hugin.sourceforge.net hugin homepage] for Screenshots, Tutorials, Documentation and Links.<br />
* [http://sourceforge.net/projects/hugin hugin sourceforge project] for Downloads, Bug database and Feature requests.<br />
* [http://hugin.svn.sourceforge.net/viewvc/hugin/ sourceforge SVN] to browse the hugin sourcecode.<br />
* [http://groups.google.com/group/hugin-ptx hugin-ptx GoogleGroup] to contribute to development and peer support.<br />
<br />
== Supported operating systems ==<br />
* [[windows software|Windows]]<br />
* [[Unix software|Linux and Unix]]<br />
* [[Mac software|Mac OS X]]<br />
<br />
[[Category:Software:Platform:Windows]]<br />
[[Category:Software:Platform:Linux]]<br />
[[Category:Software:Platform:Mac OS X]]<br />
[[Category:Software:Hugin]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Nona&diff=9597Nona2007-12-01T01:36:10Z<p>Thomas Rauscher: added to glossary</p>
<hr />
<div>'''nona''' {{Glossary|is a drop-in replacement for [[PTStitcher]] and is part of [[Hugin]]|1}}. There is a [[nona_gui]] version that provides the same dialog boxes as the Windows/Mac versions of [[PTStitcher]].<br />
<br />
== Advantages ==<br />
<br />
* Unlike [[PTStitcher]], '''nona''' has full source-code availability, this means that it can be used on many more platforms such as OS X, Linux x86_64, linux powerpc, Solaris and IRIX.<br />
* When set to use [[cropped TIFF]] output, '''nona''' doesn't perform expensive transformation calculations for unused areas of output images. For panoramas consisting of many source photos this can speed things up greatly.<br />
* '''nona''' implements [[vignetting]], white-balance, brightness and [[camera response curve]] correction at the stitching stage.<br />
* nona supports [[HDR]] images for input and output.<br />
* nona can merge 8bit low dynamic range [[bracketing|bracketed]] shots into '''HDR''' output.<br />
<br />
== Disadvantages ==<br />
<br />
(Note: this is the situation as of May 2007, please correct this page if you know this has changed)<br />
<br />
* [[Morph to fit]] control points are not supported.<br />
* It doesn't yet support the ''fast transformation'' option added to [[pano12]] by [[Fulvio Senore]].<br />
* It doesn't support the adaptive filtersize anti-[[aliasing]] filters added to pano12-2.7.0.11<br />
<br />
[[Category:Software:Platform:Windows]]<br />
[[Category:Software:Platform:Mac OS X]]<br />
[[Category:Software:Platform:Linux]]<br />
[[Category:Software:Hugin]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Historical:Using_Autopano-SIFT_With_PTGui&diff=9594Historical:Using Autopano-SIFT With PTGui2007-11-30T16:00:02Z<p>Thomas Rauscher: /* Outline */ used wiki formating</p>
<hr />
<div>== Purpose and Background ==<br />
<br />
Here is a procedure for using [[autopano-sift]] with [[PTGui]], by text editing of the .pts and .pto files.<br />
<br />
To automatically define [[control points]], [http://www.ptgui.com/ PTGui] provides plug-in support for Alexandre Jenny's [[Autopano]]<br />
<br />
In some cases, however, better [[control points]] may be found by Sebastian Nowozin's [http://user.cs.tu-berlin.de/~nowozin/autopano-sift/ Autopano-SIFT]. [[PTGui]] does not provide plug-in support for [[autopano-sift]]. So, you must use a procedure like described here.<br />
<br />
== Outline ==<br />
<br />
The general procedure is simple:<br />
<br />
# Create a uniform gray dummy image.<br />
# Launch Autopano-SIFT and load the dummy image and all desired real images into it.<br />
# Have Autopano-SIFT find control points and write a .pto output file.<br />
# Create a PTGui .pts project file containing the real images in the same order as Autopano-SIFT.<br />
# Using a text editor, merge the Autopano-SIFT control points from the .pto file, into the PTGui .pts file.<br />
# Load the new .pts file into PTGui.<br />
<br />
All done!<br />
<br />
== Example ==<br />
<br />
Autopano-SIFT screen showing images and options.<br />
<br />
Note that the dummy file needs to have a filename that is alphabetical before your other image files, otherwise the dummy file will be after your image files.<br />
<br />
[[Image:APSiftPTGuiAPSscreen1a.jpg]] <br />
<br />
<p><br />
Resulting .pto file:<br />
<br />
<pre><br />
# Hugin project file<br />
# automatically generated by autopano-sift, available at<br />
# http://cs.tu-berlin.de/~nowozin/autopano-sift/<br />
<br />
p f2 w3000 h1500 v360 n"JPEG q90"<br />
m g1 i0<br />
<br />
i w200 h200 f0 a0 b-0.01 c0 d0 e0 p0 r0 v180 y0 u10 n"E:\APSiftPTGui\dummy.jpg"<br />
i w2048 h3072 f0 a0 b-0.01 c0 d0 e0 p0 r0 v180 y0 u10 n"E:\APSiftPTGui\IMG_1558.JPG"<br />
i w2048 h3072 f0 a=1 b=1 c=1 d0 e0 p0 r0 v=1 y0 u10 n"E:\APSiftPTGui\IMG_1559.JPG"<br />
i w2048 h3072 f0 a=1 b=1 c=1 d0 e0 p0 r0 v=1 y0 u10 n"E:\APSiftPTGui\IMG_1560.JPG"<br />
i w2048 h3072 f0 a=1 b=1 c=1 d0 e0 p0 r0 v=1 y0 u10 n"E:\APSiftPTGui\IMG_1561.JPG"<br />
i w2048 h3072 f0 a=1 b=1 c=1 d0 e0 p0 r0 v=1 y0 u10 n"E:\APSiftPTGui\IMG_1562.JPG"<br />
i w2048 h3072 f0 a=1 b=1 c=1 d0 e0 p0 r0 v=1 y0 u10 n"E:\APSiftPTGui\IMG_1563.JPG"<br />
<br />
v p1 r1 y1<br />
<br />
# match list automatically generated<br />
c n1 N2 x174.513458 y810.332017 X1553.193699 Y1045.629094 t0<br />
c n1 N2 x483.523575 y701.519402 X1859.457450 Y933.601250 t0<br />
c n1 N2 x499.394895 y701.872004 X1875.586670 Y933.439960 t0<br />
...many more control points not shown here...<br />
c n5 N6 x477.779291 y2808.093329 X1761.086190 Y2894.792441 t0<br />
c n5 N6 x479.476119 y2780.860167 X1764.997492 Y2866.882044 t0<br />
c n5 N6 x581.980939 y1271.543946 X1961.858230 Y1321.353301 t0<br />
<br />
# :-)<br />
</pre><br />
<br />
The PTGui screen:<br />
<br />
[[Image:APSiftPTGuiPTGscreen1.jpg]]<br />
<br />
The PTGui project file before control points added:<br />
<br />
<pre><br />
# ptGui project file<br />
<br />
#-fileversion 8<br />
#-jpegquality 90<br />
#-previewwidth 250<br />
#-previewheight 250<br />
#-vfov 100<br />
#-fixaspect 1<br />
#-outputfile <br />
#-ccdcrop 1.6<br />
#-hasbeenoptimized 0<br />
#-morphmode 2<br />
#-simpleoptimizer<br />
#-imgrotate000000<br />
# Panorama settings:<br />
p w1000 h1000 f0 v100 u20 n"JPEG g0 q90"<br />
m g1 i0 f0<br />
<br />
# input images:<br />
#-dummyimage<br />
# The following line contains a 'dummy image' containing some global parameters for the project<br />
o w1 h1 y0 r0 p0 v45.2397298960809 a0.001 b0.001 c0.001 f0 d0 e0 g0 t0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1558.JPG"<br />
o f0 y0 r0 p0 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1559.JPG"<br />
o f0 y0 r0 p0 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1560.JPG"<br />
o f0 y0 r0 p0 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1561.JPG"<br />
o f0 y0 r0 p0 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1562.JPG"<br />
o f0 y0 r0 p0 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1563.JPG"<br />
o f0 y0 r0 p0 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
<br />
# Control points:<br />
#-cpinactive<br />
#-imginactive<br />
#-previewinactive<br />
#-morphcp<br />
#-nooptcp<br />
<br />
# optimizer:<br />
v v b y2 r2 p2 y3 r3 p3 y4 r4 p4 y5 r5 p5 y6 r6 p6<br />
</pre><br />
<br />
The edited PTGui project file, after merging control points from Autopano-SIFT:<br />
<br />
<pre><br />
# ptGui project file<br />
<br />
#-fileversion 8<br />
#-jpegquality 90<br />
#-previewwidth 250<br />
#-previewheight 250<br />
#-vfov 100<br />
#-fixaspect 1<br />
#-outputfile <br />
#-ccdcrop 1.6<br />
#-hasbeenoptimized 0<br />
#-morphmode 2<br />
#-simpleoptimizer<br />
#-imgrotate000000<br />
# Panorama settings:<br />
p w1000 h1000 f0 v100 u20 n"JPEG g0 q90"<br />
m g1 i0 f0<br />
<br />
# input images:<br />
#-dummyimage<br />
# The following line contains a 'dummy image' containing some global parameters for the project<br />
o w1 h1 y0 r0 p0 v45.2397298960809 a0.001 b0.001 c0.001 f0 d0 e0 g0 t0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1558.JPG"<br />
o f0 y0 r0 p0 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1559.JPG"<br />
o f0 y0 r0 p0 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1560.JPG"<br />
o f0 y0 r0 p0 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1561.JPG"<br />
o f0 y0 r0 p0 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1562.JPG"<br />
o f0 y0 r0 p0 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1563.JPG"<br />
o f0 y0 r0 p0 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
<br />
# Control points:<br />
c n1 N2 x174.513458 y810.332017 X1553.193699 Y1045.629094 t0<br />
c n1 N2 x483.523575 y701.519402 X1859.457450 Y933.601250 t0<br />
c n1 N2 x499.394895 y701.872004 X1875.586670 Y933.439960 t0<br />
...many more control points not shown here...<br />
c n5 N6 x477.779291 y2808.093329 X1761.086190 Y2894.792441 t0<br />
c n5 N6 x479.476119 y2780.860167 X1764.997492 Y2866.882044 t0<br />
c n5 N6 x581.980939 y1271.543946 X1961.858230 Y1321.353301 t0<br />
#-cpinactive<br />
#-imginactive<br />
#-previewinactive<br />
#-morphcp<br />
#-nooptcp<br />
<br />
# optimizer:<br />
v v b y2 r2 p2 y3 r3 p3 y4 r4 p4 y5 r5 p5 y6 r6 p6<br />
</pre><br />
<br />
PTGui then shows control points like this:<br />
<br />
[[Image:APSiftPTGuiPTGscreen2b.jpg]]<br />
<br />
Optimize, adjust pano fov, center, and level the horizon to get this panorama:<br />
<br />
[[Image:APSiftPTGuiPTGscreen4b.jpg]] <br />
<br />
The final PTGui project file looks like this. The optimizer has computed control point errors and interspersed them with the control point definitions. The control point coordinates have been converted to integers by PTGui.<br />
<br />
<pre><br />
# ptGui project file<br />
<br />
#-fileversion 8<br />
#-jpegquality 90<br />
#-previewwidth 341<br />
#-previewheight 184<br />
#-vfov 89<br />
#-fixaspect 1<br />
#-outputfile <br />
#-ccdcrop 1.6<br />
#-hasbeenoptimized 1<br />
#-morphmode 2<br />
#-imgrotate000000<br />
# Panorama settings:<br />
p w9023 h4862 f1 v209 u20 n"JPEG g0 q90"<br />
m g1 i0 f0<br />
<br />
# input images:<br />
#-dummyimage<br />
# The following line contains a 'dummy image' containing some global parameters for the project<br />
o w1 h1 y0 r0 p0 v44.9777 a0.001 b-0.010922 c0.001 f0 d0 e0 g0 t0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1558.JPG"<br />
o f0 y75.6273 r-2.47403 p-14.1391 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1559.JPG"<br />
o f0 y45.0133 r-0.642895 p-9.85206 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1560.JPG"<br />
o f0 y12.9165 r1.01822 p-9.98844 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1561.JPG"<br />
o f0 y-13.0355 r-3.16182 p-8.09519 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1562.JPG"<br />
o f0 y-38.0791 r-2.58898 p-8.51665 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
#-imgfile 2048 3072 "E:\APSiftPTGui\IMG_1563.JPG"<br />
o f0 y-69.0947 r-0.619798 p-8.26177 v=0 a=0 b=0 c=0 d=0 e=0 g=0 t=0<br />
<br />
# Control points:<br />
c n1 N2 x175 y810 X1553 Y1046 t0<br />
# Control Point No 0: 1.62083<br />
c n1 N2 x484 y702 X1859 Y934 t0<br />
# Control Point No 1: 3.91225<br />
c n1 N2 x499 y702 X1876 Y933 t0<br />
# Control Point No 2: 2.81099<br />
...many more control points not shown here...<br />
c n5 N6 x478 y2808 X1761 Y2895 t0<br />
# Control Point No 67: 1.54454<br />
c n5 N6 x479 y2781 X1765 Y2867 t0<br />
# Control Point No 68: 1.07268<br />
c n5 N6 x582 y1272 X1962 Y1321 t0<br />
# Control Point No 69: 3.5892<br />
#-cpinactive<br />
#-imginactive<br />
#-previewinactive<br />
#-morphcp<br />
#-nooptcp<br />
<br />
# optimizer:<br />
v v b y1 r1 p1 y2 r2 p2 y3 r3 p3 y5 r5 p5 y6 r6 p6<br />
</pre><br />
<br />
[[Category:Tutorial:Nice to know]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=EXR&diff=9563EXR2007-11-20T18:58:36Z<p>Thomas Rauscher: still not working....</p>
<hr />
<div>#REDIRECT [[OpenEXR]]<br />
{{Glossary|(EXtended Range?) is a [[HDR|high dynamic range]] [[image format]] created by Industrial Light and Magic}}</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=RGBE&diff=9530RGBE2007-11-20T01:16:19Z<p>Thomas Rauscher: created a stub</p>
<hr />
<div>Radiance RGBE {{Glossary|is a [[HDR]] [[Image format|image format]] invented by Greg Ward Larson for his Radiance rendering software|1}}. The file extension is usually ''.hdr''. It stores pixels as one byte RGB (red, green, and blue) values with a one byte shared exponent. Thus it store four bytes per pixel and the dynamic range covers 80 decades.</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Category:Glossary&diff=9529Category:Glossary2007-11-20T00:56:21Z<p>Thomas Rauscher: added hint to the Glossary page</p>
<hr />
<div>This page contains links to all pages about technical words and concepts. If a page is not listed here, feel free to add<br />
<br />
<nowiki>{{Glossary|Short descriptive text}}</nowiki><br />
<br />
at the top of the page. Please replace 'Short descriptive text' with a short (one sentence) definition of the respective word.<br />
All pages marked this way are automatically listed on the [[Glossary]] page. <br />
If you want the short descriptive text displayed on the page as well, you can use: <br />
<br />
<nowiki>{{Glossary|Short descriptive text|1}}</nowiki><br />
<br />
Both are calls to [[Template:Glossary]] and both add <br />
<nowiki>[[Category:Glossary]]</nowiki> <br />
automatically, there is no need to specify it on the page explicitly.</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=EXR&diff=9528EXR2007-11-19T15:18:18Z<p>Thomas Rauscher: moved redirect up again....</p>
<hr />
<div>#REDIRECT [[OpenEXR]]<br />
{{Glossary|see [[OpenEXR]]}}</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Luminance_HDR&diff=9527Luminance HDR2007-11-19T15:04:15Z<p>Thomas Rauscher: fixed EXR</p>
<hr />
<div>__NOTOC__<br />
Qtpfsgui is an open source graphical user interface for [[Pfstools]] that aims to provide a workflow for [[HDR]] imaging.<br />
<br />
Supported HDR formats:<br />
<br />
* [[OpenEXR]] (extension: exr)<br />
* [[RGBE|Radiance RGBE]] (extension: hdr)<br />
* [[TIFF]] formats: 16bit, 32bit (float) and LogLuv (extension: tiff)<br />
* [[RAW]] image formats (extension: various)<br />
* [[PFS]] native format (extension: pfs)<br />
<br />
Supported [[LDR]] formats:<br />
<br />
* [[JPEG]], [[PNG]], [[PPM]], [[PBM]], TIFF(8 bit)<br />
<br />
Supported features:<br />
<br />
* Create an HDR file from a set of images (formats: JPEG, TIFF 8bit and 16bit, RAW) of the same scene taken at different exposure setting.<br />
* Save and load HDR images.<br />
* Rotate and resize HDR images.<br />
* [[Tonemapping|Tonemap]] HDR images.<br />
* Copy [[EXIF|exif]] data between sets of images.<br />
<br />
== Compiling from sources ==<br />
=== ubuntu Linux ===<br />
<br />
Dependencies:<br />
# sudo apt-get install libqt4-dev libexiv2-dev fftw3-dev openexr pkg-config build-essential libtiff-dev libopenexr-dev subversion<br />
<br />
Get the source, either the last release<br />
# wget http://kent.dl.sourceforge.net/sourceforge/qtpfsgui/qtpfsgui-1.8.12.tar.gz<br />
# tar zxvf qtpfsgui-1.8.12.tar.gz<br />
# cd qtpfsgui-1.8.12/<br />
<br />
or the bleeding edge from the subversion repository (tested at revision 181)<br />
# svn co https://qtpfsgui.svn.sourceforge.net/svnroot/qtpfsgui qtpfsgui<br />
# cd qtpfsgui/trunk/qtpfsgui<br />
<br />
build<br />
# qmake-qt4<br />
# make<br />
# sudo checkinstall<br />
<br />
===openSUSE===<br />
<br />
build<br />
# /usr/bin/qmake<br />
# make<br />
# make install<br />
<br />
== External links ==<br />
<br />
Official website: http://qtpfsgui.sourceforge.net/<br />
<br />
[[Category:Software:Platform:Linux]]<br />
[[Category:Software:Platform:Windows]]<br />
[[Category:Software:Platform:Mac OS X]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=EXR&diff=9526EXR2007-11-19T15:01:10Z<p>Thomas Rauscher: test with no space...</p>
<hr />
<div>{{Glossary|see [[OpenEXR]]}}#REDIRECT [[OpenEXR]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=EXR&diff=9525EXR2007-11-19T14:59:43Z<p>Thomas Rauscher: changed order</p>
<hr />
<div>{{Glossary|see [[OpenEXR]]}}<br />
#REDIRECT [[OpenEXR]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=EXR&diff=9524EXR2007-11-19T14:58:31Z<p>Thomas Rauscher: added Glossary</p>
<hr />
<div>#REDIRECT [[OpenEXR]]<br />
{{Glossary|see [[OpenEXR]]}}</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=EXR&diff=9523EXR2007-11-19T14:57:29Z<p>Thomas Rauscher: EXR moved to OpenEXR: better name for the page</p>
<hr />
<div>#REDIRECT [[OpenEXR]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=OpenEXR&diff=9522OpenEXR2007-11-19T14:57:29Z<p>Thomas Rauscher: EXR moved to OpenEXR: better name for the page</p>
<hr />
<div>{{Glossary|is a [[HDR|high dynamic range]] [[image format]] created by Industrial Light and Magic}}OpenEXR is a [[HDR|high dynamic range]] [[image format]], released as an open standard along with a set of software tools created by Industrial Light and Magic, released under a Free software license similar to the BSD license.<br />
<br />
== External links ==<br />
* [http://www.openexr.com/ OpenEXR.com]<br />
* [[wikipedia:OpenEXR|OpenEXR at Wikipedia]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=OpenEXR&diff=9521OpenEXR2007-11-19T14:54:48Z<p>Thomas Rauscher: removed space</p>
<hr />
<div>{{Glossary|is a [[HDR|high dynamic range]] [[image format]] created by Industrial Light and Magic}}OpenEXR is a [[HDR|high dynamic range]] [[image format]], released as an open standard along with a set of software tools created by Industrial Light and Magic, released under a Free software license similar to the BSD license.<br />
<br />
== External links ==<br />
* [http://www.openexr.com/ OpenEXR.com]<br />
* [[wikipedia:OpenEXR|OpenEXR at Wikipedia]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=OpenEXR&diff=9520OpenEXR2007-11-19T14:53:55Z<p>Thomas Rauscher: added stub</p>
<hr />
<div>{{Glossary|is a [[HDR|high dynamic range]] [[image format]] created by Industrial Light and Magic}} OpenEXR is a [[HDR|high dynamic range]] [[image format]], released as an open standard along with a set of software tools created by Industrial Light and Magic, released under a Free software license similar to the BSD license.<br />
<br />
== External links ==<br />
* [http://www.openexr.com/ OpenEXR.com]<br />
* [[wikipedia:OpenEXR|OpenEXR at Wikipedia]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Luminance_HDR&diff=9519Luminance HDR2007-11-19T14:44:47Z<p>Thomas Rauscher: Added description from the sf-page, categorized</p>
<hr />
<div>__NOTOC__<br />
Qtpfsgui is an open source graphical user interface for [[Pfstools]] that aims to provide a workflow for [[HDR]] imaging.<br />
<br />
Supported HDR formats:<br />
<br />
* [[EXR|OpenEXR]] (extension: exr)<br />
* [[RGBE|Radiance RGBE]] (extension: hdr)<br />
* [[TIFF]] formats: 16bit, 32bit (float) and LogLuv (extension: tiff)<br />
* [[RAW]] image formats (extension: various)<br />
* [[PFS]] native format (extension: pfs)<br />
<br />
Supported [[LDR]] formats:<br />
<br />
* [[JPEG]], [[PNG]], [[PPM]], [[PBM]], TIFF(8 bit)<br />
<br />
Supported features:<br />
<br />
* Create an HDR file from a set of images (formats: JPEG, TIFF 8bit and 16bit, RAW) of the same scene taken at different exposure setting.<br />
* Save and load HDR images.<br />
* Rotate and resize HDR images.<br />
* [[Tonemapping|Tonemap]] HDR images.<br />
* Copy [[EXIF|exif]] data between sets of images.<br />
<br />
== Compiling from sources ==<br />
=== ubuntu Linux ===<br />
<br />
Dependencies:<br />
# sudo apt-get install libqt4-dev libexiv2-dev fftw3-dev openexr pkg-config build-essential libtiff-dev libopenexr-dev subversion<br />
<br />
Get the source, either the last release<br />
# wget http://kent.dl.sourceforge.net/sourceforge/qtpfsgui/qtpfsgui-1.8.12.tar.gz<br />
# tar zxvf qtpfsgui-1.8.12.tar.gz<br />
# cd qtpfsgui-1.8.12/<br />
<br />
or the bleeding edge from the subversion repository (tested at revision 181)<br />
# svn co https://qtpfsgui.svn.sourceforge.net/svnroot/qtpfsgui qtpfsgui<br />
# cd qtpfsgui/trunk/qtpfsgui<br />
<br />
build<br />
# qmake-qt4<br />
# make<br />
# sudo checkinstall<br />
<br />
===openSUSE===<br />
<br />
build<br />
# /usr/bin/qmake<br />
# make<br />
# make install<br />
<br />
== External links ==<br />
<br />
Official website: http://qtpfsgui.sourceforge.net/<br />
<br />
[[Category:Software:Platform:Linux]]<br />
[[Category:Software:Platform:Windows]]<br />
[[Category:Software:Platform:Mac OS X]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Talk:Panotools_internals&diff=9336Talk:Panotools internals2007-11-16T16:26:44Z<p>Thomas Rauscher: fixed pano12 capabilities</p>
<hr />
<div>== Image formats ==<br />
Should this section also list which program transfers ICC profiles, exif tags or other meta data from input to output image files? I'm not sure if all of this (now listed) information would also fit into one table with "r/w" (or yes/no/n.a.) cells? Something like<br />
{| class="wikitable"<br />
|-<br />
! application<br />
! [[JPEG|JPG]]<br />
! [[TIFF]] (8 bit)<br />
! TIFF (16 bit)<br />
! TIFF (32 bit)<br />
! [[PNG]] (8 bit)<br />
! PNG (16 bit)<br />
|-<br />
| [[PTStitcher]] || r/w || r/w || r/w || / || r/w || /<br />
|-<br />
| [[PTMender]] || r/w || r/w || r/w || / || r/w || /<br />
|-<br />
| [[nona]] || r/w || r/w || r/w || r/w || r/w || /<br />
|-<br />
| [[PTGui]] internal stitcher || r/w || r/w || r/w || r/w || r/w || r/w<br />
|}<br />
'''r''': read | '''w''': write<br /><small>--[[User:Zarl|Carl]] 08:05, 13 November 2007 (CET)</small><br />
<br />
Very good, but with all of the images formats ( current + PSD, PSB, EXR, HDR) a bit too large. At least I didn't have an idea how to structure it... <small>--[[User:Erik Krause|Erik Krause]] 22:03, 15 November 2007 (CET)</small><br />
<br />
Oh sure, that's true. I could change x and y axis, so we need only four columns. <small>--[[User:Zarl|Carl]] 23:30, 15 November 2007 (CET)</small><br />
<br />
{| class="prettytable"<br />
|-<br />
! file format || [[PTStitcher]]<br />&nbsp; || [[PTMender]]<br />&nbsp; || [[nona]]<br />&nbsp; || [[PTGui]]<br />(internal stitcher) || [[pano12]]<br />
|-<br />
| [[JPEG|JPG]] || read / write || read / write || read / write || read / write || read / write<br />
|-<br />
| [[TIFF]] (8 bit) || read / write || read / write || read / write || read / write || read / write<br />
|-<br />
| TIFF (16 bit) || read / write || read / write || read / write || read / write || read / write<br />
|-<br />
| TIFF (32 bit) ||''n.a.''||''n.a.''|| read / write || read / write || read / write<br />
|-<br />
| [[PNG]] (8 bit) || read / write || read / write || read / write || read / write || read / write<br />
|-<br />
| PNG (16 bit) ||''n.a.''||''n.a.''||''n.a.''|| read / write || ''?''<br />
|-<br />
| [[EXR]] ||''n.a.''||''n.a.''|| read / write || read / write ||''n.a.''<br />
|-<br />
| [[HDR]] || ''n.a.'' || ''n.a.'' || read / write || read / write || read / write<br />
|-<br />
| [[PSD]] (8 bit)<br /> single or multi layer || write only ||''n.a.''||''n.a.''|| write only || ''?''<br />
|-<br />
| PSD (16 bit)<br /> single layer || write only ||''n.a.''||''n.a.''|| write only || ''?''<br />
|-<br />
| PSD (16 bit)<br /> multi layer ||''n.a.''||''n.a.''||''n.a.''|| write only || ''?''<br />
|-<br />
| [[PSB]] (8, 16 or 32 bit)<br /> single or multi layer ||''n.a.''||''n.a.''||''n.a.''|| write only || ''n.a.''<br />
|-<br />
| [[QTVR]] (cylindrical) || write only ||''n.a.''||''n.a.''|| ''n.a.'' || ''n.a.''<br />
|-<br />
| QTVR (cubic) ||''n.a.''||''n.a.''||''n.a.''|| write only || ''n.a.''<br />
|}<br />
'''n.a.''': not available<br /> How about this? Is it better to have ''read / write'' instead of ''r / w''? ''n.a.'' is now in italics... <small>--[[User:Zarl|Carl]] 10:14, 16 November 2007 (CET)</small><br />
<br />
I find it better now as the previous version. I also added the pano12 library because it is able to read/write HDR and TIFF 32 but PTStitcher can not handle it. <small>--[[User:Thomas Rauscher|thomas]] 16:07, 16 November 2007 (CET)</small><br />
<br />
I'm pretty sure hugin/nona support some other formats: BMP (8bit), GIF (!), PNG (8 & 16bit), PNM (8, 16 & 32bit), SUN (8bit) and VIFF (8, 16, 32bit and single/double float).<br />
<br />
Though only PNG and VIFF support alpha channels, the table should indicate alpha channel support.<br />
<br />
The table also shows confusion between integer (LDR) and floating-point (HDR) data, TIFF 32bit can be either 32bit integer or single precision floating-point.<br />
<br />
[[User:Bruno|Bruno]] 17:05, 16 November 2007 (GMT)<br />
<br />
Hi Bruno and Thomas, thanks for the input! Here is a new version:<br />
{| class="prettytable"<br />
|-<br />
! file format || [[PTStitcher]]<br />&nbsp; || [[PTMender]]<br />&nbsp; || [[nona]]<br />&nbsp; || [[PTGui]]<br />(internal stitcher) || [[pano12]]<br />&nbsp;<br />
|-<br />
| [[JPEG|JPG]] || read / write || read / write || read / write || read / write || read / write<br />
|-<br />
| [[TIFF]] (8 bit) || read / write || read / write || read / write || read / write || read / write<br />
|-<br />
| TIFF (16 bit) || read / write || read / write || read / write || read / write || read / write<br />
|-<br />
| TIFF (32 bit LDR)<br /> (integer) ||''n.a.''||''n.a.''|| read / write || read / write || ''n.a.''<br />
|-<br />
| TIFF (32 bit [[HDR]])<br /> (single precision floating-point) ||''n.a.''||''n.a.''|| read / write || read / write || read / write<br />
|-<br />
| [[PNG]] (8 bit) || read / write || read / write || read / write || read / write || read / write<br />
|-<br />
| PNG (16 bit) ||''n.a.''||''n.a.''||''n.a.''|| read / write || ''?''<br />
|-<br />
| [[PSD]] (8 bit)<br /> single or multi layer || write only ||''n.a.''||''read / write''|| write only || ''?''<br />
|-<br />
| PSD (16 bit)<br /> single layer || write only ||''n.a.''||''read / write''|| write only || ''?''<br />
|-<br />
| PSD (16 bit)<br /> multi layer ||''n.a.''||''n.a.''||''n.a.''|| write only || ''?''<br />
|-<br />
| [[PSB]] (8, 16 or 32 bit)<br /> single or multi layer ||''n.a.''||''n.a.''||''n.a.''|| write only || ''n.a.''<br />
|-<br />
| [[EXR]] ||''n.a.''||''n.a.''|| read / write || read / write ||''n.a.''<br />
|-<br />
| [[HDR]] || ''n.a.'' || ''n.a.'' || read / write || read / write || read / write<br />
|-<br />
| [[QTVR]] (cylindrical) || write only ||''n.a.''||''n.a.''|| ''n.a.'' || ''n.a.''<br />
|-<br />
| QTVR (cubic) ||''n.a.''||''n.a.''||''n.a.''|| write only || ''n.a.''<br />
|-<br />
| BMP (8 bit) || ''?'' || ''?'' || read / write || ''?'' || read / write<br />
|-<br />
| GIF || ''?'' || ''?'' || read / write || ''?'' || ''?''<br />
|-<br />
| PNM (8, 16, 32bit) || ''?'' || ''?'' || read / write || ''?'' || ''?''<br />
|-<br />
| SUN (8bit) || ''?'' || ''?'' || read<sup>(AC)</sup> / write || ''?'' || ''?''<br />
|-<br />
| VIFF (8, 16, 32bit, single/double float) || ''?'' || ''?'' || read / write || ''?'' || ''?''<br />
|}<br />
<sup>(AC)</sup>: alpha channel support<br />How about that indicator? I may have introduced several mistakes by now while simply duplicating several rows. Sorry for that. <small>--[[User:Zarl|Carl]] 17:17, 16 November 2007 (CET)</small></div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Talk:Panotools_internals&diff=9323Talk:Panotools internals2007-11-16T15:07:49Z<p>Thomas Rauscher: added pano12</p>
<hr />
<div>== Image formats ==<br />
Should this section also list which program transfers ICC profiles, exif tags or other meta data from input to output image files? I'm not sure if all of this (now listed) information would also fit into one table with "r/w" (or yes/no/n.a.) cells? Something like<br />
{| class="wikitable"<br />
|-<br />
! application<br />
! [[JPEG|JPG]]<br />
! [[TIFF]] (8 bit)<br />
! TIFF (16 bit)<br />
! TIFF (32 bit)<br />
! [[PNG]] (8 bit)<br />
! PNG (16 bit)<br />
|-<br />
| [[PTStitcher]] || r/w || r/w || r/w || / || r/w || /<br />
|-<br />
| [[PTMender]] || r/w || r/w || r/w || / || r/w || /<br />
|-<br />
| [[nona]] || r/w || r/w || r/w || r/w || r/w || /<br />
|-<br />
| [[PTGui]] internal stitcher || r/w || r/w || r/w || r/w || r/w || r/w<br />
|}<br />
'''r''': read | '''w''': write<br /><small>--[[User:Zarl|Carl]] 08:05, 13 November 2007 (CET)</small><br />
<br />
Very good, but with all of the images formats ( current + PSD, PSB, EXR, HDR) a bit too large. At least I didn't have an idea how to structure it... <small>--[[User:Erik Krause|Erik Krause]] 22:03, 15 November 2007 (CET)</small><br />
<br />
Oh sure, that's true. I could change x and y axis, so we need only four columns. <small>--[[User:Zarl|Carl]] 23:30, 15 November 2007 (CET)</small><br />
<br />
{| class="prettytable"<br />
|-<br />
! file format || [[PTStitcher]]<br />&nbsp; || [[PTMender]]<br />&nbsp; || [[nona]]<br />&nbsp; || [[PTGui]]<br />(internal stitcher) || [[pano12]]<br />
|-<br />
| [[JPEG|JPG]] || read / write || read / write || read / write || read / write || read / write<br />
|-<br />
| [[TIFF]] (8 bit) || read / write || read / write || read / write || read / write || read / write<br />
|-<br />
| TIFF (16 bit) || read / write || read / write || read / write || read / write || read / write<br />
|-<br />
| TIFF (32 bit) ||''n.a.''||''n.a.''|| read / write || read / write || read / write<br />
|-<br />
| [[PNG]] (8 bit) || read / write || read / write || read / write || read / write || read / write<br />
|-<br />
| PNG (16 bit) ||''n.a.''||''n.a.''||''n.a.''|| read / write || ''?''<br />
|-<br />
| [[EXR]] ||''n.a.''||''n.a.''|| read / write || read / write ||''n.a.''<br />
|-<br />
| [[HDR]] || ''n.a.'' || ''n.a.'' || read / write || read / write || read / write<br />
|-<br />
| [[PSD]] (8 bit)<br /> single or multi layer || write only ||''n.a.''||''n.a.''|| write only || ''?''<br />
|-<br />
| PSD (16 bit)<br /> single layer || write only ||''n.a.''||''n.a.''|| write only || ''?''<br />
|-<br />
| PSD (16 bit)<br /> multi layer ||''n.a.''||''n.a.''||''n.a.''|| write only || ''?''<br />
|-<br />
| [[PSB]] (8, 16 or 32 bit)<br /> single or multi layer ||''n.a.''||''n.a.''||''n.a.''|| write only || ''n.a.''<br />
|-<br />
| [[QTVR]] (cylindrical) || write only ||''n.a.''||''n.a.''|| ''n.a.'' || ''n.a.''<br />
|-<br />
| QTVR (cubic) ||''n.a.''||''n.a.''||''n.a.''|| write only || ''n.a.''<br />
|}<br />
'''n.a.''': not available<br /> How about this? Is it better to have ''read / write'' instead of ''r / w''? ''n.a.'' is now in italics... <small>--[[User:Zarl|Carl]] 10:14, 16 November 2007 (CET)</small><br />
<br />
I find it better now as the previous version. I also added the pano12 library because it is able to read/write HDR and TIFF 32 but PTStitcher can not handle it. <small>--[[User:Thomas Rauscher|thomas]] 16:07, 16 November 2007 (CET)</small></div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=PanoTools_Anti_Aliasing_Filters&diff=9311PanoTools Anti Aliasing Filters2007-11-12T13:40:51Z<p>Thomas Rauscher: added comment</p>
<hr />
<div>Since version 2.7.10 the [[PanoTools]] library contains several [[interpolation]] filter that avoid [[aliasing]]. Those filters use a dynamic kernel size where the size of the filter kernel is calculated for each pixel.<br />
<br />
There are two theoretical types of kernels that have an equal right for existence. Kernels based on the [[wikipedia:Normal distribution|Gaussian distribution]] and kernels based on the [[wikipedia:Sinc function|Sinc function]]. Both kernels have an infinite width so a windowing function is used to limit the kernel size for practical reasons. Gaussian based kernels do not contain negative values, sinc based do.<br />
<br />
The values in the plot describe the contribution of a pixel depending on the distance from the center. A wider kernel in the center means a more blurry image but if it is to narrow it tends to produce aliasing. If the kernel contains negative values the images also gets sharpened. Some examples: If you look at the plots you can see that a ''Hamming Filter'' produces blurrier image then the ''Blackmann Filter''. The ''Lanczos2 Filter'' introduces more sharpening then the ''Mitchell Filter'' because of the larger negative areas.<br />
<br />
{| class="wikitable"<br />
|-<br />
! short<br />
! ID<br />
! Name<br />
! f(x)<br />
! Kernel size<br>(radius)<br />
! Comment<br />
|-<br />
| aabox || 8 || Box Filter || [[Image:plot_s_filter_8.png]] || 0.5 || sometimes called ''nearest neighbor'' <br />
|-<br />
| aatriangle || 9 || Bartlett/Triangle Filter || [[Image:plot_s_filter_9.png]] || 1.0 || sometimes called ''bilinear''<br />
|-<br />
| aahermite || 10 || Hermite Filter || [[Image:plot_s_filter_10.png]] || 1.0 <br />
|-<br />
| aahanning || 11 || Hanning Filter || [[Image:plot_s_filter_11.png]] || 1.0 <br />
|-<br />
| aahamming || 12 || Hamming Filter || [[Image:plot_s_filter_12.png]] || 1.0 <br />
|-<br />
| aablackman || 13 || Blackmann Filter || [[Image:plot_s_filter_13.png]] || 1.0 <br />
|-<br />
| aagaussian || 14 || Gaussian 1/sqrt(2) Filter (blury) || [[Image:plot_s_filter_14.png]] || 1.25 <br />
|-<br />
| aagaussian2 || 15 || Gaussian 1/2 Filter (sharper) || [[Image:plot_s_filter_15.png]] || 1.0 <br />
|-<br />
| aaquadratic || 16 || Quadardic Filter || [[Image:plot_s_filter_16.png]] || 1.5 <br />
|-<br />
| aacubic || 17 || Cubic Filter || [[Image:plot_s_filter_17.png]] || 2.0 || default filter in [[Photoshop]]<br />
|-<br />
| aacatrom || 18 || Catmull-Rom Filter || [[Image:plot_s_filter_18.png]] || 2.0 <br />
|-<br />
| aamitchell || 19 || Mitchell Filter || [[Image:plot_s_filter_19.png]] || 2.0 <br />
|-<br />
| aalanczos2 || 20 || Lanczos2 Filter || [[Image:plot_s_filter_20.png]] || 2.0 <br />
|-<br />
| aalanczos3 || 21 || Lanczos3 Filter || [[Image:plot_s_filter_21.png]] || 3.0 <br />
|-<br />
| aablackmanbessel || 22 || Blackman/Bessel Filter || [[Image:plot_s_filter_22.png]] || 3.2383 <br />
|-<br />
| aablackmansinc || 23 || Blackman/sinc Filter || [[Image:plot_s_filter_23.png]] || 4.0 <br />
|}<br />
<br />
Some [[PanoTools Anti Aliasing Filter Examples|examples]].<br />
<br />
[[Category:Glossary]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=PanoTools_Anti_Aliasing_Filter_Examples&diff=9309PanoTools Anti Aliasing Filter Examples2007-11-11T15:30:08Z<p>Thomas Rauscher: initial version</p>
<hr />
<div>Examples for [[PanoTools Anti Aliasing Filters]].<br />
<br />
Panorama without aliasing filter:<br />
<br />
<pano file="Noaafilter.mov" width="500" height="350" scale="tofit" controller="true" cache="true" /><br />
<br />
Panorama with Gaussian filter:<br />
<br />
<pano file="Aafilter_gauss.mov" width="500" height="350" scale="tofit" controller="true" cache="true" /><br />
<br />
Panorama with Michell filter:<br />
<br />
<pano file="Aafilter_mitchell.mov" width="500" height="350" scale="tofit" controller="true" cache="true" /></div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=PanoTools_Anti_Aliasing_Filters&diff=9308PanoTools Anti Aliasing Filters2007-11-11T15:26:04Z<p>Thomas Rauscher: added examples page</p>
<hr />
<div>Since version 2.7.10 the [[PanoTools]] library contains several [[interpolation]] filter that avoid [[aliasing]]. Those filters use a dynamic kernel size where the size of the filter kernel is calculated for each pixel.<br />
<br />
There are two theoretical types of kernels that have an equal right for existence. Kernels based on the [[wikipedia:Normal distribution|Gaussian distribution]] and kernels based on the [[wikipedia:Sinc function|Sinc function]]. Both kernels have an infinite width so a windowing function is used to limit the kernel size for practical reasons. Gaussian based kernels do not contain negative values, sinc based do.<br />
<br />
The values in the plot describe the contribution of a pixel depending on the distance from the center. A wider kernel in the center means a more blurry image but if it is to narrow it tends to produce aliasing. If the kernel contains negative values the images also gets sharpened. Some examples: If you look at the plots you can see that a ''Hamming Filter'' produces blurrier image then the ''Blackmann Filter''. The ''Lanczos2 Filter'' introduces more sharpening then the ''Mitchell Filter'' because of the larger negative areas.<br />
<br />
{| class="wikitable"<br />
|-<br />
! short<br />
! ID<br />
! Name<br />
! f(x)<br />
! Kernel size<br />
|-<br />
| aabox || 8 || Box Filter || [[Image:plot_s_filter_8.png]] || 0.5 <br />
|-<br />
| aatriangle || 9 || Bartlett/Triangle Filter || [[Image:plot_s_filter_9.png]] || 1.0 <br />
|-<br />
| aahermite || 10 || Hermite Filter || [[Image:plot_s_filter_10.png]] || 1.0 <br />
|-<br />
| aahanning || 11 || Hanning Filter || [[Image:plot_s_filter_11.png]] || 1.0 <br />
|-<br />
| aahamming || 12 || Hamming Filter || [[Image:plot_s_filter_12.png]] || 1.0 <br />
|-<br />
| aablackman || 13 || Blackmann Filter || [[Image:plot_s_filter_13.png]] || 1.0 <br />
|-<br />
| aagaussian || 14 || Gaussian 1/sqrt(2) Filter (blury) || [[Image:plot_s_filter_14.png]] || 1.25 <br />
|-<br />
| aagaussian2 || 15 || Gaussian 1/2 Filter (sharper) || [[Image:plot_s_filter_15.png]] || 1.0 <br />
|-<br />
| aaquadratic || 16 || Quadardic Filter || [[Image:plot_s_filter_16.png]] || 1.5 <br />
|-<br />
| aacubic || 17 || Cubic Filter || [[Image:plot_s_filter_17.png]] || 2.0 <br />
|-<br />
| aacatrom || 18 || Catmull-Rom Filter || [[Image:plot_s_filter_18.png]] || 2.0 <br />
|-<br />
| aamitchell || 19 || Mitchell Filter || [[Image:plot_s_filter_19.png]] || 2.0 <br />
|-<br />
| aalanczos2 || 20 || Lanczos2 Filter || [[Image:plot_s_filter_20.png]] || 2.0 <br />
|-<br />
| aalanczos3 || 21 || Lanczos3 Filter || [[Image:plot_s_filter_21.png]] || 3.0 <br />
|-<br />
| aablackmanbessel || 22 || Blackman/Bessel Filter || [[Image:plot_s_filter_22.png]] || 3.2383 <br />
|-<br />
| aablackmansinc || 23 || Blackman/sinc Filter || [[Image:plot_s_filter_23.png]] || 4.0 <br />
|}<br />
<br />
Some [[PanoTools Anti Aliasing Filter Examples|examples]].<br />
<br />
[[Category:Glossary]]</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=File:Noaafilter.mov&diff=9307File:Noaafilter.mov2007-11-11T15:23:33Z<p>Thomas Rauscher: Sample panorama without anti aliasing filter</p>
<hr />
<div>Sample panorama without anti aliasing filter</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=File:Aafilter_mitchell.mov&diff=9306File:Aafilter mitchell.mov2007-11-11T15:22:56Z<p>Thomas Rauscher: Sample panorama with Mitchell anti aliasing filter</p>
<hr />
<div>Sample panorama with Mitchell anti aliasing filter</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=File:Aafilter_gauss.mov&diff=9305File:Aafilter gauss.mov2007-11-11T15:22:10Z<p>Thomas Rauscher: Sample panorama with Gaussian anti aliasing filter</p>
<hr />
<div>Sample panorama with Gaussian anti aliasing filter</div>Thomas Rauscherhttps://wiki.panotools.org/index.php?title=Pano12_Anti_Aliasing_Filters&diff=9304Pano12 Anti Aliasing Filters2007-11-11T15:14:28Z<p>Thomas Rauscher: Pano12 Anti Aliasing Filters moved to PanoTools Anti Aliasing Filters: its not only pano12...</p>
<hr />
<div>#REDIRECT [[PanoTools Anti Aliasing Filters]]</div>Thomas Rauscher