Support / FAQ

Before you look any further, make sure that you are running the latest version of PTGui. The current version is 11.18. See the version history for possible bugs that have been fixed in recent versions. Licensed users can upgrade at a reduced price, or free of charge, depending on the date of the original license purchase.

Documentation and Tutorials

The Video Tutorial on this site should help you get started using PTGui. Tutorials for advanced usage of PTGui can be found on the Tutorials page. And the Links page contains links to more tutorials, written by users of PTGui.

Detailed documentation for every feature and parameter is included with PTGui: in PTGui choose 'Help -> Help for this tab'.

Getting support

If you have a question or problem please first check the list of frequently asked questions below. The answer to your question may already be listed here.

If this does not solve the problem, post your technical support questions to the PTGui Support Forum. You will quickly get an answer from the PTGui authors or from other users.

Contact us

For non-technical questions (e.g. related to purchasing, downloading, software activation) please contact us directly at . Technical support questions should be posted to the PTGui Support Forum.

Frequently asked questions

1.1. I purchased PTGui or PTGui Pro and I still haven't heard from you after a day!
1.2. I have purchased a PTGui license a couple of years ago. Do you offer discounted upgrade pricing?
1.3. I am a licensed user of PTGui; can I upgrade to PTGui Pro?
1.4. Which version should I purchase, PTGui or PTGui Pro?
1.5. Where can I find the license conditions for PTGui / PTGui Pro?
1.6. Do you offer special student pricing?
1.7. My organization needs a pro-forma invoice before we can purchase a license. Can you arrange this?
1.8. Can I still download older PTGui versions?
1.9. Can I install PTGui on both my PC and my laptop?

2.1. I tried to enter my license key, but it doesn't work
2.2. How does activation work?
2.3. My computer is not connected to internet. Can I use PTGui?
2.4. What about hardware modifications?
2.5. My computer died / was stolen. How can I deactivate my license?
2.6. How can I transfer my license to another computer?
2.7. On how many computers is my license activated?
2.8. I lost my license key
2.9. I'm planning to switch from a PC to a Mac computer, is that a problem?
2.10. We are running PTGui on multiple computers in a network environment. How can we deploy PTGui without activating each computer manually?
2.11. PTGui says 'failed to activate your license'. How can I resolve this?

3.1. Is PTGui or the documentation available in other languages?
3.2. My lens database is empty, is that normal?
3.3. Can PTGui work with 16-bit images from start to finish (ie, no 8-bit conversion)?
3.4. Can I use PTGui to create virtual tours?
3.5. Sensor sizes: millimeters vs inches?
3.6. My images were taken with a (e.g.) 28mm lens, but after optimization, PTGui reports it as a 31.5mm lens
3.7. Can PTGui read RAW/DNG files?
3.8. Will PTGui read RAW files from camera XXX?
3.9. What does 'Apply Template' do?
3.10. Apply Template does not copy the control points from the template. Why is that?
3.11. What kind of computer hardware do you recommend for use with PTGui?
3.12. Does PTGui preserve the EXIF data of my images?
3.13. Can I stitch images from a shift lens with PTGui?
3.14. Where does PTGui store its settings?
3.15. PTGui doesn't fully use my computer's processor(s); the CPU load is less than 100% during stitching
3.16. After optimizing, PTGui shows me the average control point distance. What distance should I aim for?
3.17. Why does PTGui Pro close my project and open a new blank project after I press Save and Send to Batch Stitcher?
3.18. PTGui asks me whether I would like to re-initialize the project. What does this mean?
3.19. Can PTGui create those interactive photos where the camera is rotated around the object?
3.20. After stitching a project in the PTGui Pro Batch Stitcher, the project is modified!
3.21. I have edited my RAW / DNG files in Photoshop or another application. Does PTGui recognize my changes when I use the raw files in PTGui?
3.22. What can I do to reduce the stitching time PTGui on my system?
3.23. I have moved or rotated images in the Panorama Editor by hand using the Edit Individual Images mode. But PTGui tells me it needs to optimize the panorama and this undoes my changes. Why?
3.24. Can PTGui stitch greyscale images?
3.25. PTGui keeps changing the output size in the Create Panorama tab. Why?
3.26. How does PTGui calculate the optimum output size of a panorama?
3.27. Why does PTGui 11 use a different optimum size than PTGui 10?
3.28. What exactly does the Fisheye Factor parameter do?
3.29. Can I install different versions of PTGui side by side?

4.1. I am trying to edit the seams of a layered panorama in Photoshop, but I only see the bottom layer with the merged panorama; the other layers are transparent.
4.2. Another application crashes when opening TIFF files generated by PTGui, or it displays garbled images.
4.3. My computer crashes occasionally while PTGui is running
4.4. My images have a different brightness or color when viewed in PTGui
4.5. PTGui shows a message 'PTGui was unable to detect control points for some of the images, therefore you need to add a few control points by hand'. Help! What should I do now?
4.6. PTGui is randomly rotating my images!
4.7. I'm having trouble stitching my panorama. Can you help?
4.8. Norton / Symantec antivirus says there's a virus in the PTGui installer!
4.9. After editing a 360 degree panorama in Photoshop and importing back into PTGui, I'm seeing a vertical line in the panorama
4.10. I'm getting Out of Memory errors while running PTGui
4.11. When installing on a Mac I get the error "PTGui Pro can't be opened because the identity of the developer cannot be confirmed."
4.12. I'm unable to open a QuickTime VR .mov panorama
4.13. I'm attempting to stitch images taken with multiple cameras but I'm running into stitching errors
4.14. My panoramas stitched using a template in the Batch Builder have misalignments. This only happens in the Batch Builder; the panorama is perfect if I use the same template in the GUI.
4.15. The Batch Builder seems to ignore the settings in my template; my panoramas come out different than expected.
4.16. The panorama in the PTGui Viewer is full of black dots!
4.17. I'm using PTGui 10; the stitching process hangs and never completes.

5.1. The horizon of my panorama is curved instead of straight
5.2. I get color/brightness differences between the images in my panorama
5.3. How can I change the resolution (ppi or dpi value) of the generated panorama?
5.4. I see misalignments in the stitched panorama. What can I do to improve the result?
5.5. Some control points in my project have a relatively high control point distance. Will the alignment of my panorama improve if I delete all control points with an error above a certain threshold?
5.6. My drone panoramas are showing misalignments at the horizon. How can I get a straight horizon?

6.1. My panorama contains curved lines. How do I get straight lines to remain straight in the panorama?
6.2. How do I use the Horizontal line and Vertical line control points?
6.3. How can I calibrate my lens parameters?
6.4. Does PTgui allow stitching of photos that have the camera in different locations?
6.5. How can I stitch mosaics, like partial scans from a flatbad scanner of a large image?
6.6. My panorama was taken with the camera tilted up or down. Now there's a lot of unnecessary black space above/below the panorama, increasing the size of the output. Can it be cropped away before stitching?
6.7. How can I have better control of the overlap area (i.e. the location of the seams)?
6.8. How can I create a vertical panorama? PTGui rotates my panorama 90 degrees!
6.9. I want to cover the tripod in my (360x180 degree) spherical panorama. How do I add a nadir cap?
6.10. How can I change the default settings for new panoramas?
6.11. How can I stitch extremely large panoramas?
6.12. How can I align a set of images, all taken in the same direction (not a panorama)?
6.13. How can I use exactly the same stitching settings for different sets of images?
6.14. How can I correct a single image for lens distortion?
6.15. How can I show a panorama on my website?
6.16. How can I publish a panorama to Facebook?
6.17. Why does Facebook display my panorama as a flat image, not as an interactive panorama?
6.18. How can I use PTGui to add the metadata required by Facebook to an already stitched panorama?
6.19. How do I level/straighten a panorama using horizontal / vertical line control points?
6.20. How can I correct a single image for vignetting in PTGui Pro?
6.21. My spherical panorama still has a hole in the top and/or bottom. How do I fill the missing parts to make the panorama truly spherical?
6.22. After running Publish to Website my panorama has black holes at the top and bottom; how do I get rid of these?
6.23. PTGui leaves some blank space around my panorama. How can I crop the panorama so that it fills the canvas entirely?
6.24. How can I tell PTGui to output panoramas at a specific size?
6.25. How can I defish a fisheye image in PTGui?
6.26. How can I extract a 'flat' image from a spherical panorama?
6.27. I have taken multiple panoramas from the same viewpoint, to create a time lapse movie. How can I ensure that subsequent panoramas are aligned when played back in sequence?
6.28. My project contains one or more images without any recognizable detail and it's impossible to place control points. How can I stitch my panorama?
6.29. How can I view a finished panorama interactively on my computer?
6.30. I would like to send a panorama to a friend/client/... Is it possible to view a panorama interactively without needing to install a plugin first?
6.31. I need to align/overlay an image to an already stitched panorama. How can I do this?
6.32. How can I stitch a PTGui project from the command line?
6.33. Can I use PTGui to arrange pictures into a collage? Can I disable the warping/distorting of images?
6.34. How can I display spherical panoramas on my iPad?
6.35. How can I stitch panoramic video in PTGui?
6.36. Is there a way to stitch many panoramas using the same settings?
6.37. How can I make 'little planet' images in PTGui?
6.38. How can I stitch images from Adobe Lightroom in PTGui? Do you offer a Lightroom plugin?
6.39. Can you tell me how to make 3d (stereoscopic) panoramas in PTGui?
6.40. How can I view a stitched panorama in a Cardboard VR viewer on my phone?
6.41. How can I stitch two back-to-back circular fisheye images?
6.42. How can I retouch the nadir of a spherical panorama?
6.43. How can I stitch images taken with a 360° one shot camera in PTGui?
6.44. How can I prevent PTGui from placing control points in certain areas?

7.1. What is the best way to take images for HDR stitching in PTGui Pro?
7.2. My images don't contain EXIF exposure information. Can I still use them to stitch HDR panoramas?
7.3. PTGui Pro doesn't recognize my bracketed exposures!
7.4. The stitched HDR panorama looks like it was not blended at all. I'm seeing hard edges between overlapping images.
7.5. So I forgot to switch my camera to M mode; my bracketed images are taken in auto exposure mode. Can I still stitch them to HDR in PTGui Pro?
7.6. Why should I use manual exposure mode? Isn't it much better to use automatic exposure, so that every image is optimally exposed?
7.7. PTGui Pro displays the wrong EV values! My images were taken at -2, 0, +2. This is confirmed by the EXIF data but PTGui shows something else in the Image Parameters tab.
7.8. What's the deal with linked images?
7.9. Should I link my bracketed exposures or not?
7.10. Can I retouch an HDR panorama, e.g. to remove ghost images of moving people?
7.11. I would like to stitch my panorama in PTGui Pro, but use another application (e.g. Photomatix or Photoshop) to create the HDR.
7.12. Can I use PTGui Pro for exposure fusing / tone mapping / HDR generation of non-panoramic images?
7.13. Can I extract artificial bracketed images from my (non bracketed) RAW files and have PTGui Pro assemble those into an HDR panorama?
7.14. I have read the previous answer but I still would like to stitch my pseudo bracketed images generated from RAW files!

8.1. Which GPUs are supported by PTGui?
8.2. Which graphics card should I buy?
8.3. Does PTGui support using multiple GPUs?
8.4. PTGui reports 'no supported GPU device available' even though my (Windows) computer has an NVIDIA GPU supporting OpenCL.

We send you your registration key as soon as possible after receipt of your payment, though this may take up to 24 hours. If you still haven't heard from us after that time, be assured that we did send you your registration key but apparently our email has not reached you. This occasionally happens, often caused by spam filter problems or full mailboxes.

If your mailbox has a Junk Mail folder, look for mail from PTGui Support <support@ptgui.com>. Many junk mail filters have a white list feature (often called 'trusted senders'); please add our address to it.

Then go to this page to get your key: Request registration key Every PTGui and PTGui Pro license comes with one year of free upgrades. After that year you can upgrade your license at by paying an upgrade fee. Your upgrade purchase will include another year of free upgrades. See Buy upgrade for more information. See Version History for what's new in the latest version. Yes, you can upgrade from PTGui to PTGui Pro by paying the current price difference. See Buy upgrade for more information. See Features of PTGui and PTGui Pro for a comparison of the two versions. Separate trial versions are available for PTGui and PTGui Pro, so you can try both. If you're not sure whether you need the Pro version, consider purchasing a license for the standard version first. If needed, you will be able to upgrade to PTGui Pro later by paying the price difference between the two versions. See: End User License Agreement No, we do not offer educational or any other kind of discounts on individual license purchases. We do offer discounted company licenses to universities and schools, please contact us for details. Yes, this is possible: Go to the Buy page at this site and press the Buy Now button of the desired product. On the subsequent page choose: Payment Method: Check (or Bank/Wire Transfer if available). After filling in your personal details you will be transferred to ShareIt's website. Complete the order forms until the order is finalized. You will be sent a pro forma invoice with payment instructions. If you later on decide to pay by credit card instead, just place a new order through our website. The wire transfer order will be canceled automatically if no payment is received within a month. Yes, several older versions of PTGui and PTGui Pro are still available. To download, go to the Download page, choose 'Download full version' and enter your registration key. On the subsequent page click on the 'older versions' link to access the latest version of PTGui for which your license is valid. A personal license may be installed on up to three computers, provided it is only used by the person to whom it is licensed (i.e. the name appearing in the registration key). If multiple users use PTGui on those computers, multiple personal licenses or a company license should be purchased instead.

For the company license registration keys are issued on a per machine basis: a separate registration key must be purchased for each computer on which the software is installed.

Other restrictions apply; see the End User License Agreement for details.
The license key is quite long and it is easy to make mistakes. Therefore please copy/paste the key from the original order confirmation email. Select the code and press Ctrl+C, then paste into PTGui using Ctrl+V. On mac use Cmd+C and Cmd+V instead. If you don't have the license key anymore, we can resend it to you.

The registration key and registration name are linked to each other. Be sure to enter the correct registration name: it may be different from your own name. The registration name is shown in the order confirmation email.

The gmail.com automatic translation feature is known to corrupt the license key. If you use GMail in a language different than english, switch off automatic translation by selecting 'view this email in english' when reading the email containing the license key.

A correctly entered license key would look as follows:

When you run PTGui for the first time on your computer it will ask you for your license key. This license key together with your computer's hardware configuration is sent to our servers. Assuming the permitted total number of installations is not exceeded, we will then activate your license on this particular computer.

Subject to the conditions set forth in the End User License Agreement, a personal license may be activated on up to 3 computers, for personal use by the licensed person only. For a company license multiple license keys are issued; each key can be activated on one computer.

A computer can be deactivated via Help - License Info - Deactivate; this makes the license key available for use on another computer. To prevent abuse of the deactivation facility, PTGui must verify the activation status at least once every 30 days. This happens automatically in the background while PTGui is running. Activation happens over the internet. If the computer running PTGui is not connected to Internet, it can still be activated using another computer with internet connection. Select Activate Offline to do so. This generates a code which is to be entered on a web page. The web page returns another code which can be entered in PTGui to complete the activation. You can transfer the codes between the computers using an USB drive for example. Activation is not affected by small upgrades, like adding more memory. But larger upgrades may cause PTGui to consider the computer to be a different machine and ask for a new activation. Before performing a hardware upgrade it is therefore best to deactivate the license via Help - License Info - Deactivate. When you launch PTGui again after the upgrade, use the original license key to reactivate.

If you forgot to deactivate, you can still go to License activations to request deactivation of your old hardware. If you can no longer access the computer please go to License activations and request us to deactivate your computer. For PTGui 11 and later: On the old computer, go to Help | License Info and press Deactivate. Now the license key can be used to install PTGui on the new computer.

PTGui 10 and earlier can be deactivated by going to the About window, press Register and then press the Deactivate button. On Windows, 'About' can be found in the Help menu; on macOS it's in the 'PTGui [Pro]' menu. There are two ways to find out: in PTGui select Help - License Info. Or go to License activations and enter your license key to see the currently activated computers. No problem; we can resend your license key to you. No problem, the license is platform independent and you will be able to transfer the license to another computer. Each computer running PTGui must be activated. The activation process keeps track of the number of computers on which a PTGui license is used. Normally PTGui will ask for the license key to activate the software when it is run for the first time on a computer. This step can be bypassed by installing a provisioning file containing the license key. If such a provisioning file is present, the user does not have to enter the license key and PTGui will be activated automatically when it is run for the first time on a computer, using a license key from the provisioning file.

The provisioning file must be stored in this location on Windows computers:

C:\ProgramData\PTGui\licensekey.json

and here on macOS:

/Users/Shared/Application Support/PTGui/licensekey.json

licensekey.json should be a JSON file with the following structure:

{
	"licensekeys": [
		{
			"regname": "Registration Name",
			"regkey": "QjAfghfh444466663Ykk/RJd2vdcfSqYG9cxoP5s/+JGmAoqKWk%BacGWgCAQ=="
		},
		{
			"regname": "Registration Name",
			"regkey": "MzQyQ+rtret8778h1998y9erkk4889384898hjkjkjjycGWgCAQ=="
		}
	]
}

The regname field should contain the Registration Name and the regkey field should contain the license key. The file can contain multiple license keys (2 in the above example); PTGui will attempt to activate using the keys in this order. If a key is already activated on another computer, the next key will be used, until activation is succesful.

Note that PTGui license keys consist of two lines, but strings in JSON must be represented in a single line. PTGui ignores line endings in the license key, so the two lines of the license key can simply be concatenated into a single line. You can validate the syntax of your JSON file using (e.g.) JSONLint.

If activation fails, an error message is displayed and PTGui will show the regular activation window. The provisioning file will only be used if PTGui is not yet activated. If PTGui is already activated on a particular computer, licensekey.json will be ignored.

To install PTGui on multiple Windows computers in the network you can script your deployment system to run the PTGui installer in silent mode as follows:

PTGuiSetup.exe /S /D=C:\Program Files\PTGui

The installer can be run without uninstalling a previous version first.

On a Mac no installation is necessary, just copy the PTGui application bundle into the Applications folder.

A license can be deactivated on a computer as usual, through Help - License Info - Deactivate from within PTGui on the licensed computer. If this is not possible, remote deactivation can be requested by going to License activations. Be sure to remove licensekey.json after deactivation, otherwise PTGui will be reactivated automatically and silently when it is launched again.

For activation PTGui needs to be able to contact the activation server (see Q2.11). To activate your license on your computer PTGui needs to contact the license server. This may fail if the computer is behind a corporate firewall, or if internet security software is running to block outgoing network connections.

To resolve the issue, configure your firewall to permit outgoing network connections to activation1.ptgui.com on TCP port 443.

If this is not possible, or if your computer does not have internet access, PTGui offers an offline activation option: in the activation window press the Activate Offline button and follow the instructions.
Yes, PTGui and its documentation are available in English, Deutsch, Nederlands, Español, Français, Português, 日本語, 한국어 and 中文. The language can be selected in Options/Preferences. Yes, it is. You can use it to store your optimized lens data. Yes, PTGui performs all image processing in 16 bit if a 16 bit output format is selected on the Create Panorama tab. PTGui Pro even supports 32 bit floating point images. PTGui includes a viewer for publishing panoramas on a website. See Q6.15 for more information.

The web viewer included with PTGui is just a basic viewer for publishing individual panoramas. For a true virtual tour consisting of multiple panoramas linked by hotspots, clickable floor plans, etc, dedicated panorama publishing software exists. All panorama publishing software can load panoramas in 360 x 180 degree equirectangular projection, as created by PTGui. See Q6.15 for software recommendations. To determine the lens projection, PTGui needs to know the dimensions (in millimeters) of the camera's sensor. Some manufacturers state the sensor size in fractions of an inch (e.g. 1/2.5"). The inch-designation dates back to TV camera tubes in the 50s and it does not appear to be mathematically related to the actual sensor size. See Table of sensor formats and sizes (Wikipedia) for a conversion table. This is normal; the optimizer adjusts your project in such a way that the lowest control point distance is obtained. By default this involves modifying the focal length of the lens. Apparently it is at this focal length that PTGui achieves the best alignment of the images. Yes, PTGui uses LibRaw which allows it to read RAW files produced by many cameras.

Note that RAW files are not regular image files. The RAW file records the data straight from the camera's sensor, which needs to be demosaiced and processed further before it can be used. Therefore RAW files should rather be seen as a digital 'negative' which first needs to be developed to get the actual image.

This development is done using standard settings, although PTGui Pro does allow you to adjust exposure and white balance in the HDR/Exposure tab.

If you need more control, use a dedicated RAW converter instead and save the converted RAW files as 16 bit TIFF images. The TIFF files can then be loaded into PTGui. This preserves the image quality and full dynamic range of the source images. Be sure to convert all source images in a panorama using the same settings, otherwise color or brightness differences may remain visible in the panorama.

Also, any adjustments made to the RAW file in Photoshop RAW (or other RAW converters) are ignored by PTGui. These programs do not actually change the RAW file; instead they write the modifications to a so-called sidecar (.xmp) file. The sidecar file contains closed proprietary data and cannot be read by other software. Therefore, if you need to make changes to RAW file or need finer control over the conversion, use a dedicated raw converter and save the images to 16 bit TIFF format.

Finally, since all RAW files are different it's possible that LibRaw does not (yet) support your camera. In that case it's also necessary to convert your images to TIFF before loading them into PTGui. PTGui uses the open source LibRaw library for decoding raw files. See Supported Cameras on the LibRaw website for a list of cameras supported by LibRaw. PTGui can only read raw files supported by LibRaw. If LibRaw does not support your camera, use a dedicated raw converter to convert the images to 16 bit TIFF.

See Q3.7 for more information. This copies the settings of another project to the current project, except for the images and the control points. This function is accessible both from the 'Apply Template' item in the File menu, and from the toolbar in PTGui. A template can be any PTGui project. In Tools/Options/Folders&Files, a folder can be configured where you store your templates (on Mac go to the PTGui menu, Preferences, Folders&Files). The template selection dialog will by default open in this folder. The 'Apply Template' button on the toolbar shows a drop down list of all templates in the configured template directory, for quick access.

Templates can be useful for a quick initialization of a project (lens settings, rough alignment of images), although this is usually not necessary since the Project Assistant can figure out the alignment of the panorama by itself.

Another use for templates is when you have an exact reproducable setup (high quality panoramic head with fixed angles). In this case you could copy all settings of a previous project and there would be no need for placing control points and optimizing.

By default, applying a template copies all settings from the template to the current project except for the source images and the control points. In PTGui Pro this behavior can be modified in the Project Settings tab, section 'template behavior'. By default applying a template copies all settings from the template except for the actual source images and the control points (see Q3.9). Control points are never copied since they are specific to the source images. For example a control point could originally point to the corner of a building in the template project, but in another project the same coordinates may be in the middle of plain blue sky. In other words the control points are meaningless outside the context of the original images.

If you just need a project to be stitched exactly like the template project, control points are not needed at all. Control points are only used by the optimizer to determine the best image parameters. The stitcher only uses the optimized image parameters and ignores the control points. Therefore it's sufficient to apply the template (which copies the image parameters) and proceed straight to Create Panorama without running the optimizer. PTGui does not require any special hardware, even for stitching large panoramas. But if you're looking for high performance we recommend a PC with the following specifications:

• RAM: 16 GB or more. RAM is relatively cheap these days and data in RAM can be accessed at least 100x faster than data stored on disk.
• Disk: this should be an SSD, not a spinning hard drive. Especially when stitching large gigapixel panoramas, using an SSD for temporary storage will give a huge reduction in stitching time. If you must use external disks, connect them through USB 3 or thunderbolt; USB 2 is too slow. You can configure which drive PTGui uses for temporary storage in Options/Preferences (in the Folders & Files tab).
• GPU: PTGui features OpenCL hardware acceleration, reducing stitching time significantly. Basically any current AMD or NVIDIA graphics card of $300 or more will be fine. See Q8.2 for more information.
• Processor: PTGui is multi threaded so it will run faster on processors having more cores. But with GPU acceleration enabled, disk speed usually becomes the bottleneck so money is better spent on SSD and RAM.
• OS: if running Windows, be sure to get the 64 bit version.

Currently, the following metadata is copied to the generated panorama:

• Original date and shooting date of the first image in the panorama
• Exposure data: exposure time, aperture and ISO sensitivity (only if identical for all source images)
• ICC Color Profile (only if identical for all images)
• GPS data: the GPS altitude, latitude and longitude of the source images are averaged and copied to the panorama

For rectilinear panos, PTGui also adds the FocalLength and FocalLengthIn35mm tag.

For spherical 360 x 180 degree panoramas, PTGui adds Photo Sphere XMP metadata so other applications will recognize the image as a spherical panorama.

For HDR panoramas in PTGui Pro, the 'blend planes' output contains the exposure/iso/aperture of that particular exposure, for merging in external software.

Other EXIF data is currently not copied to the output file. The above metadata is written to JPEG and TIFF images. Metadata support for Photoshop (.psb and .psd) files is limited, only the ICC profile and Photo Sphere XMP data are written. For .hdr and .exr files no metadata is currently written. First of all, you don't need a shift lens if you have PTGui! Shift lenses are often used for architectural photographs: photographing a building from ground level, while tilting the camera upwards, normally results in converging vertical lines. Shift lenses compensate for this effect by shifting the optical axis of the lens relative to the center of the image plane. The result is a photograph where parallel lines remain parallel.

The same effect can be achieved in PTGui: open the Panorama Editor window, press Ctrl-P to switch to 'Panorama Edit' mode. Now drag the panorama upwards or downwards until parallel lines in the scene are parallel in the panorama. You may need to increase the vertical field of view (using the slider to the right of the panorama).

If you do want to stitch images taken with a shift lens in PTGui, change the following parameters:

• Switch to Advanced mode by pressing the Advanced button in the side bar
• In the Lens Settings tab, select 'Individual Shift Parameters' for all images for which the lens was shifted
• Run the optimizer by pressing F5

Regardless whether a shift lens is used, or the panorama was shifted in the Panorama Editor, you will end up with some black space below or above the panorama. This can be removed by dragging yellow crop lines from the edges of the panorama in the panorama editor. The process is shown in detail in part two of our Video Tutorial. PTGui stores its configuration data in this folder:

Windows:

%APPDATA%\PTGui\

macOS:

~/Library/Application Support/PTGui/

To open this folder, do Tools - Open Folder - PTGui Configuration Folder in PTGui. Most configuration data is stored in Configuration.xml in this folder. The default folders for Templates and Batch Lists also reside here. Stitching and blending requires a lot of disk and memory access. In particular for large panoramas, or on multi core computers, not the processor but the hard disk may be the speed limiting factor. Also, with a suitable graphics card much of the processing is offloaded to the GPU. If you are looking into increasing stitching speed, see Q3.11. The control point distance indicates how well a control point pair aligns in the panorama. When the distance is zero, the two points of a control point pair overlap exactly.

One should aim for the lowest control point distance possible, but the actual lowest distance that can be achieved depends on many factors. In general if your images were shot properly using a tripod with calibrated panorama head, a control point distance well below 5 should be achievable. Most remaining misalignments can usually be masked by the blender. An average distance higher than 5 usually indicates a problem, see Q5.4 for solutions.

It's particularly important to look at 'outliers': if a control point has a distance of 20 while the average is below 5, this control point might have been placed on a moving object, or on a similar feature close to the proper location. Use the 'Delete worst control points' function (in the Control Points menu) to remove such outlying control points. The Batch Stitcher of PTGui Pro can generate control points; it will do so if instructed by the 'Do Align Images and save the modified project' checkbox in the Project Settings. By default this is enabled if the control point generator has not yet been run for the project. This allows you to quickly generate a panorama in batch: start a new project, load your source images and press Save and Send to Batch Stitcher. The batch stitcher generates control points and stitches the panorama in one go.

After generating control points and aligning the images the batch stitcher overwrites the project file with the modified version. Since the Batch Stitcher will modify the project file, problems could occur if the project would remain opened at the same time in the main PTGui Pro window: both instances would be writing to the same project file, discarding each other's changes.

For this reason, PTGui Pro will close the project after sending it to the batch stitcher if the Batch Stitcher is configured to modify the project. This ensures that only one instance of the project is open. A warning message is shown before the project is closed but the warning is no longer shown if 'don't show this again' had been selected. To re-enable the warning message, go to Options/Preferences and click 'Reset all warning messages'.

In previous version of PTGui, a temporary copy of the project would be sent to the batch stitcher. This functionality is still available through 'Send Temporary Copy to Batch Stitcher'. This creates a copy of the current state of the project in a temporary file, which is sent to the batch stitcher for stitching. When stitching has finished the temporary project file is deleted by the batch stitcher. If PTGui fails to properly align your images, the following question may appear:

"The optimizer failed to achieve a good alignment of the images. Possibly the current misalignment of the images causes the optimizer to get stuck. Re-initialization of the project may help in such a case. Would you like to re-initialize the project and try to optimize again?"

If you click OK, PTGui will reset the yaw, roll and pitch of all images to zero and reinitialize the lens settings based on the EXIF data. Then it will attempt to figure out the image positions from scratch and subsequently reoptimize the project.

In particular in cases where the optimizer got stuck in a so-called local minimum such an initialization from scratch can be the solution.

This function can be triggered manually using the Initialize and Optimize (in the Project menu). These are commonly called 'Object Movies'; they cannot be created through stitching and therefore PTGui does not support this. A software package for creating object movies is Object2VR. The batch stitcher of PTGui Pro can not only stitch projects, but it can also set up a new panorama project by generating control points, aligning the images, etc. It will do so if instructed by the 'Do Align Images and save the modified project' checkbox in the Project Settings tab. If the project or template is already set up completely and the panorama should only be stitched, make sure that the above checkbox is unchecked. No, PTGui will load the raw files as they came straight from the camera, any modifications are ignored. In Photoshop RAW files can be edited, but the changes are written to a 'side car' file (with the .xmp extension) rather than to the original raw file. The settings in the side car file are specific to the algorithms used by Photoshop and cannot be used by other applications.

To use the modified RAW files in PTGui, export them to 16 bit TIFF files and load those in PTGui instead. Since RAW files typically only have 12 or 14 bits per channel, the full dynamic range will be preserved by the 16 bit TIFF file, so there is no loss of quality. The time required to stitch a panorama is influenced by many factors, such as the dimensions of the panorama, the computer hardware and by other applications running at the same time. Some general hints to improve the stitching performance:

• First of all, stitching time depends mostly on the output size of the panorama. The size of the source images also has a slight influence. Render the panorama at a smaller size to reduce stitching time.
• PTGui is slow in loading RAW and DNG images. For best performance convert your raw images to 16 bit TIFF format.
• Stitching to 16 bit output will generate twice as much data as when stitching to 8 bit output, and thus take longer.
• External blending plugins such as Smartblend may get slow for larger panoramas. Try the built in blender of PTGui instead.
• Memory usage of PTGui can be configured with the following setting in Tools-Options-Advanced (Windows) or PTGui-Preferences-Advanced (Mac):
  Use at most ... MB of RAM memory: PTGui will attempt to stitch the panorama in RAM as much as possible, but once the panorama is too large to fit entirely in RAM, temporary data will get written to disk. This setting determines the maximum amount of RAM that will be used. There is an optimum value: if PTGui has access to little RAM it will start to use the hard disk for temporary storage earlier, which is much slower. But if PTGui attempts to use too much RAM it will attempt to 'steal' RAM from other applications. The operating system will start swapping applications to and from disk if the total needed amount of RAM exceeds the amount available. This can bring the entire computer to a crawl. Therefore this setting should be chosen as high as possible, but such that no swapping occurs. Other memory intensive applications should be closed while PTGui is stitching.
  Finding the optimum values for these settings is a matter of trial and error.
• Adding more RAM memory, a fast hard disk or an OpenCL capable graphics card can improve stitching speed. See Q3.11 for hardware recommendations.

Don't attempt to align images manually: it's impossible to get the required precision for a seamless stitch. Even if you would manage to accurately align an image to one neighbouring image, this would throw it out of alignment with its other neighbour images.

Instead, let the PTGui optimizer do all the hard work through control points. Control points tell PTGui which points of two images should overlap. By providing 3 or 4 control point for a pair of overlapping images, PTGui will know how they overlap and the optimizer will align the images with pixel accuracy.

For more information watch our our Video Tutorial. PTGui was designed to efficiently stitch RGB color images (with or without transparency). It can read single channel greyscale TIFF files but the output will always be in RGB format. If you require single channel greyscale TIFF files as output, use third party software such as Photoshop to convert the output to the desired format. By default (the Create Panorama tab will show 'fix at 100% of optimum size'), PTGui will output your panorama at the so called Optimum Size. The optimum size is the output size at which the resolution of the panorama equals the resolution of the source images. For more information see Q3.26.

Because the optimum size depends on several parameters, including the focal length of the lens which is usually fine tuned by the optimizer, the optimum size may vary slightly after each optimization. This depends also on control point placement. If this fluctuation is unwanted, in the Create Panorama tab pick a desired size and select 'Fix at ... megapixels'. From now on PTGui will keep the number of pixels in the panorama constant. The optimum size is the output size at which the resolution of the panorama equals the resolution of the source images. In other words, no detail from the source images is lost.

Because image warping is not uniform across the panorama, there is no true optimum size: some parts of the source images may get enlarged while other parts may be reduced in size. Therefore, somewhat arbitrarily, PTGui considers the optimum size to be the size where the angular resolution of the center of the source images equals the angular resolution of the center of the panorama. If images from multiple lenses are used, this calculation will be based on the source image having the highest resolution.

Because the optimum size depends on several parameters which are adjusted by the optimizer, the optimum size may vary slightly for different projects using the same lens. See Q3.25. In PTGui 11 a new lens parameter, the 'fisheye factor' was introduced (see Q3.28). This allows it to perfectly model all practical fisheye projections. PTGui 10 didn't include this parameter and used equidistant projection for all fisheye images. The difference between the actual projection and equidistant projection was modeled using the lens distortion (a/b/c) coefficients. When calculating the optimum size, the lens distortion coefficients are not taken into account, resulting in an error in the calculated optimum size. PTGui 11 does take the fisheye factor into account when calculating the optimum size.

In other words, the optimum size is calculated more accurately in PTGui 11 than in PTGui 10. Regardless, it's still a somewhat arbitrary measure (see Q3.26) and it's possible to output at any desired size. There is no single fisheye projection, different fisheye lenses exhibit different optical projections. For example, equidistant, equisolid or orthographic fisheye lenses exist. For more information see Fisheye Projection (PanoTools wiki). Visually, these projections differ by the amount of compression or stretching of the image near the edge of the fisheye circle. PTGui up to version 10 simply modeled every fisheye lens using the equidistant projection. The deviation of the actual projection from equidistant projection was compensated for by using the a/b/c lens distortion correction polynomial. This worked, but with caveats: because the relation between focal length and field of view differs for each kind of projection, PTGui could misestimate the size of the cropping circle for circular fisheye lenses. And secondly, the control point generator would have more difficulty finding control points (especially near the edges of the image) if the wrong fisheye projection was used.

In PTGui 11 this was solved by introducing the Fisheye Factor parameter. Fisheye lenses are now modeled using the following formula:



Here, k is the fisheye factor, f is the focal length, θ is the angle of the light ray entering the lens and R is the radial distance from the image center of the projected light ray.

By varying the fisheye factor k the equation morphs into the different fisheye projections. Values of the fisheye factor for the common projections are:

Equidistant: k = 0
Stereographic: k = 0.5
Orthographic: k = -1.0
Equisolid: k = -0.5
Rectilinear (non-fisheye): k = 1.0

In normal use of PTGui the fisheye factor is initialized to the known value of the lens before running Align Images. PTGui knows the fisheye factor for many common models of fisheye lenses. If EXIF data is available PTGui can often recognize the brand and model of the fisheye lens automatically, and set the fisheye factor accordingly. If no EXIF data is available, the brand and model of the fisheye lens can be selected from a list. In practise no lens follows the above projection model exactly, therefore a/b/c lens distortion correction is used to compensate for any remaining small differences between the ideal and actual projection.

The fisheye factor of a lens can be determined by the PTGui optimizer. When optimizing the fisheye factor, care must be taken to avoid interference by the a/b/c lens distortion correction parameters: in the Lens Settings tab, press the Reset button to reset a/b/c to zero. Then in the Optimizer tab, enable optization of the fisheye factor and disable optimization of a/b/c. As always, for accurate optimization of the lens parameters, images without parallax should be used. Yes, this is possible. Any version (trial, Pro, beta) can be installed in parallel to your current version of PTGui. In Windows, the installer will ask you for an installation folder (e.g. C:\Program Files\PTGui) and a Start Menu folder. If you enter different folder names, your current version will not be overwritten. On Mac, PTGui is distributed in a disk image (.dmg file). Double click the .dmg file to mount it. Inside there's the PTGui application. Drag the application to the desktop, then rename the application. Finally move the application from the Desktop into the Applications folder.

PTGui project files will by default be opened in the last installed version. To change this under Windows: right click on a PTGui project file, at 'Opens With' click on Change, click 'More Apps', click 'Look for another app on this PC', then browse (under Program Files) to the particular version of PTGui to use.

On macOS: ctrl+click on a PTGui project file, select 'Open With', 'Other...', select the PTGui application to use, enable 'Always Open With' and click Open.

Keep in mind that the settings and license information are shared by all PTGui applications for the current user.

If you accidentally overwrote your licensed version of PTGui with a trial version, you can re-download your licensed version even if it was an older version; see Q1.8.
This is by design. The idea is to use the blended panorama as the basis for retouching, selectively revealing parts of the source images for retouching by making the masks opaque. TIFF is a container format which can contain many different types of image data; almost no application supports all possible TIFF formats. PTGui can create 16 or 32 bit TIFF files and TIFF files with an alpha channel but these features are not supported by many applications. If you need create a compatible TIFF file, press the 'Settings' button in the Create Panorama tab, and choose: 8 bits, no alpha channel and no compression. The resulting file can be opened in nearly every application that supports TIFF files. Also keep in mind that not all TIFF capable applications can read BigTIFF images, so they will fail to open TIFF files larger than 4GB. A normal application like PTGui (i.e. not a driver or a kernel process) is unable to crash an entire computer; the worst that could normally happen is the application itself crashing but not the entire computer.

If the computer crashes, shows a 'blue screen' error or spontaneously reboots this is usually indicating a problem with the hardware or a driver. It's possible that you observe the problem only when running PTGui: stitching large panoramas places a heavy load on the processor, hard disk and memory. This could trigger any existing hardware problems for example due to the increased temperature of the processor, due to increased load on the power supply, or simply because any existing problem is more likely to be seen when the system is used intensively.

If you however observe crashes in PTGui but the operating system continues to run properly then this could be a bug in PTGui. The Windows version of PTGui includes a crash reporter; we encourage you to submit the crash data to us for analysis. Mac users please send the crash report to us at ; crash reports on the Mac can be found in <User>/Library/Logs/CrashReporter/. PTGui is currently not a color managed application, so it ignores any color profile embedded in the images. This means that images are always displayed in the working color profile (usually sRGB). If the images were taken in a different color profile they will be shown with incorrect brightness or color.

However the operations performed by PTGui (stitching and blending) are color neutral; therefore the output panorama will be in the same color space and the final result is not affected.

For regular (non HDR) panoramas the output file is tagged with the source ICC profile, provided that all source images have the same color space. The output from tone mapping and exposure fusion (for HDR panoramas) is currently not tagged with an ICC profile; such files need to be tagged manually with the ICC profile of the source images. To do so, open the tone mapped or exposure fused panorama in Photoshop, choose Edit-Assign Profile and pick the profile of the source images from the list.

The same applies to panoramas converted by the Publish to Website tool. When publishing panoramas to the web it is recommended to convert the images to sRGB profile. This ensures that the panoramas are shown correctly in all browsers and plugins, whether color managed or not.

Improved color management is one of the planned features for a future version of PTGui. When you press Align Images, PTGui analyzes your source images and looks for details which can be seen in multiple images. For example, the corner of a building might be visible in the right hand side of one image and in the left hand side of another image. On these matching details PTGui places so called Control Points. To see what control points look like, go to the Control Points tab in PTGui after you have run Align Images. In the Control Poins tab select two overlapping images by clicking the thumbnails above the images and you will see numbered markers indicating the matching features. Ultimately the control points are used by PTGui to set up the panorama: it warps and moves the images in such a way that the control points match as closely as possible.

If you see the above message, this means that PTGui was not able to find control points for all images. The human eye is still better in recognizing patterns than a computer and in this case you will need to help PTGui a bit. To do so, first open the Control Point Assistant (in the Tools menu). The Control Point Assistant will tell you what the problem is, for example 'Image 4 does not have any control points'.

Besides single images lacking control points it's also possible that there are clusters of images linked by control points: for example image 1,2 and 3 are linked by control points and image 4,5 and 6 are linked by control points, but there are no control points between images in either cluster. To create a panorama all images should directly or indirectly be linked by control points, so in this example adding control points between image 3 and 4 would solve the problem.

Suppose the Control Point assistant tells you that image 4 does not have control points: go to the Control Points tab in the main window, and choose image 4 in the left pane. In the right pane find an image which partially overlaps image 4 (most likely image 3 or image 5). Find an object which is visible in both images, click on that object in the left image and click on the same object in the right hand image. As you see a colored marker has been added. Repeat this until you have added at least 3 control points. Then go back to the Control Point Assistant and see if there are any other images that need control points.

When done, go back to the Project Assistant tab in the main window: the above error message is now gone. As the last step the project needs to be optimized: click on the blue underlined link to do this. The optimizer will re-align the images such that the control points match as closely as possible. Verify the result in the Panorama Editor window: the panorama should now be set up properly.

The above workflow is shown in detail in our Video Tutorial.

Sometimes an image contains no recognizable details at all (for example if the images contains pure blue sky only). In that case see Q6.28.

For more information use the on line help available for the Control Points tab and the Control Point Assistant window: in most screens you can get context help by pressing F1 (Windows) or Fn+F1 (Mac). The orientation of the images the main window is synchronized with the orientation of the images in the stitched panorama. For example, if you rotate an image in the Panorama Editor 90 degrees clockwise, the image thumbnail in the Project Assistant will be rotated clockwise as well. And if you rotate the entire panorama 90 degrees, all images in the Project Assistant will be rotated too.

If PTGui seems to randomly rotate your images after running Align Images, most likely it was unable to properly align the panorama, resulting in misaligned and randomly rotated images in the Panorama Editor. It may seem that the misalignments are caused by the random rotation but it is in fact the other way round: due to the misalignments the images get randomly rotated in the panorama, and the orientation of the images in the Project Assistant simply reflect the orientation of the images in the panorama. First of all, if you are new to PTGui check out our Video Tutorial. It may help you understand what the problem might be. In particular make sure that all images are taken from exactly the same viewpoint and that the camera is rotated around the entrance pupil of the lens (which is usually close to the front of the lens). In general a regular tripod is not suitable for taking panoramas; you need a dedicated panoramic head to ensure that the camera is rotated around the front of the lens and not around the tripod screw.

If this does not solve the issue please post your panorama to the PTGui support forum and we'll be happy to take a look. Large files cannot be uploaded to the forum directly; instead create a zip file with your panorama and upload it to a file publishing site such as sendspace or Dropbox. Then include the URL of the uploaded file in your forum post. To allow us to help you quickly, upload at least the PTGui project file (.pts). Depending on the problem we may need the image files as well. Regularly when we release a new version, the installer is diagnosed with the WS.Reputation.1 threat and blocked by Norton Antivirus.

According to Symantec WS.Reputation.1 means that the file has a low reputation score: 'The reputation-based system uses "the wisdom of crowds" (Symantec’s tens of millions of end users) connected to cloud-based intelligence to compute a reputation score for an application, and in the process identify malicious software in an entirely new way beyond traditional signatures and behavior-based detection techniques'.

In other words: PTGui was blocked just because it has had relatively few downloads among Norton Antivirus users. Which makes sense because it is a new version...

Now Symantec does offer software vendors the option to submit their software to have it whitelisted. When we do so we get a friendly reply: 'Thank you for your request [...] For a Software White-list request, Symantec will target a response of advising you of our final determination within 3 weeks.'.

To install PTGui you may therefore need to temporarily disable Norton Antivirus while downloading and installing. For more information see How to bypass Symantec’s WS.Reputation.1 System. But we recommend to switch to a different virus scanner altogether. The next time Norton nags about your expired subscription, consider switching for example to Microsoft's own free virus scanner: Microsoft Security Essentials.

If you are still unsure whether it's safe to install PTGui, upload the installer to virustotal.com and have it scanned by over 40 different virus scanners. This is caused by the fact that Photoshop isn't aware that the left and right edge of the image wrap around. When doing local adjustments (in particular contrast enhancement) near one of the edges, pixels at the other edge should also be taken into account, otherwise a hard edge will be visible when the panorama is later wrapped around in a panorama viewer.

You can work around this limitation in Photoshop by extending the panorama: a section from the right hand side of the panorama is pasted next to the left hand side, and vice versa. Subsequent adjustments will then take properly into account the pixels 'over the edge'. When done editing, reduce the panorama to the original size.

We've created a set of Photoshop scripts to accomplish this with a single mouse click: download PhotoshopExtendCanvas.zip. Please see readme.txt inside the zip file for installation instructions. This may happen while aligning or stitching large panoramas in the 32 bit version of PTGui, due to the fact that 32 bit applications can only access a limited amount of memory.

To check if you are running the 32 bit or 64 bit version, go to Help - System Information and scroll down to the line 'Platform'. This will show 'mac64/mac' or 'win64/win64' for the 64 bit version, or 'mac32/mac' or 'win32/win32' for the 32 bit version. Every Mac produced since 2007 is 64 bit capable, and PTGui will run in 64 bit mode on those machines. On Windows the situation is different: your computer can only run 64 bit applications if it was shipped with the 64 bit version of Windows. The 32 bit version of Windows is still in common use; running the 64 bit version of PTGui would require installing a new operating system.

In 32 bit Windows by default each application has access to a 2 GB memory space. When an application attempts to access more than 2 GB of memory, it will abort with an Out of Memory error. In practise the situation is worse: while the application is running the memory space becomes fragmented due to repeated memory allocations and de-allocations: even if there are 5 separate blocks of 50 MB available, requesting a single 60 MB block will fail. The memory limit does not depend on the actual amount of RAM installed: even on a computer with 8 GB of RAM each application can only use 2 GB.

Stitching large panoramas often requires several gigabytes of memory to store the pixel data. PTGui will attempt to stay within the memory limit by using no more than a certain amount of RAM. If more memory is needed some of the data will be written to temporary files, to be loaded back into memory later when needed. But because not every byte of memory is accounted for, and because the actual memory limit is unknown due to fragmentation, out of memory conditions may still occur.

If you run into out of memory errors, go to Options / Advanced and reduce the 'use at most ... MB of RAM memory' setting until the problem goes away.

There is a '3GB' switch in the 32 bit versions of Windows: this increases the memory limit from 2 GB to 3 GB. Enabling this switch may help to get rid of out of memory errors and increase the performance of PTGui. To enable the 3 GB switch in the 32 bit versions of Windows Vista, Windows 7, or Windows 8:

• Run a command prompt window as Administrator. In Windows 8 and later you can right-click on the start menu and choose Command Prompt (Admin). In earlier Windows versions go to the Accessories program group of the Start menu, right click on Command Prompt and choose 'Run as Administrator'.
• At the command prompt, enter: bcdedit /set IncreaseUserVa 3072 (followed by the Enter key).
• The command window should show 'The operation completed successfully'.
• Restart the computer.

Please note that there may be side effects of enabling the 3GB switch. If you run into any problems the 3GB switch can be disabled again by following the same steps but replacing the command above by bcdedit /deletevalue IncreaseUserVa
For some technical background information see Demystifying /3GB

To check if the 3GB switch is enabled, do Help - System Information in PTGui and scroll down to Virtual Memory. If this is 3071, the 3 GB switch is enabled. If it says 2047, the 3 GB switch is not enabled. This happens when installing older versions of PTGui on newer versions of Mac OS X. It should not occur when installing the current PTGui version.

In OS 10.9.5 Apple have changed the way application signatures are validated, and the application signature in PTGui 10.0.6 and earlier does not conform to this requirement. The problem has been solved in PTGui 10.0.7.

If you need to install an older version of PTGui: ctrl+click on the PTGui application and select Open. In the dialog box that appears click on Open. This bypasses the signature verification. QuickTime VR (or QTVR) was a special dialect in the QuickTime .mov video format supporting interactive playback of spherical panoramas. For many years this has been the format of choice for embedding panoramas in web pages: the QuickTime plugin was installed on every Mac and on many Windows computers (it was included with iTunes for Windows). With the introduction of QuickTime X in 2009, Apple has dropped support for QTVR panoramas. These days HTML5 is the format of choice for displaying panoramas on web pages (see Q6.15).

QTVR panoramas can still be viewed by installing QuickTime 7, but be aware that this creates a security risk: exploits for QuickTime 7 exist and Apple is no longer updating the software. That said:
Installing QuickTime Player 7 on your Mac
Download QuickTime 7 for Windows.
Windows users can alternatively use the DevalVR player (Unicode) which can also play back QTVR panoramas.

Pano2VR can be used to convert an existing QTVR .mov file to another format. Seamless panoramic stitching requires that all images are taken from exactly the same viewpoint. Moving the viewpoint causes parallax which makes it impossible to stitch images perfectly. For more information about parallax see Q5.4 and watch the Video Tutorial.

This requirement is very critical: even photos taken from viewpoints spaced only a few centimeters can have significant parallax, causing clearly visible stitching errors on nearby objects. When taking panoramas with a single camera parallax should be avoided by using a panoramic tripod head: this ensures that the camera is rotated around the 'no parallax point' which is usually located near the front of the lens.

When using multiple cameras, parallax is unavoidable which means that it is simply impossible to stitch the images perfectly. This problem is particularly apparent in panoramic video because this can only be created from multiple cameras. The only real 'solution' is to lower your expectations and accept that stitching errors will be visible. That said, for the best results consider the following:

• Try to mount the cameras as closely as possible to reduce the parallax
• The effect of parallax diminishes as objects get further away from the camera. If there's an object close to the camera try to make sure it is captured entirely in one of the images, instead of having a seam run through it.
• Making a stitching template for panoramic video is generally best done using images taken in a wide open space, placing control points only on distant objects (which don't have much parallax due to the distance). This ensures that PTGui is able to correctly estimate the lens parameters. While you may be able to somewhat improve the stitching of a particular scene by adding extra control points on a nearby object, this will in fact degrade the stitching of other frames where the object or the camera has moved, so don't do this when creating a stitching template.

Essentally there are two different use cases for the batch builder:

1. To stitch many panoramas using the exact same settings, without generating control points. This can be used for example with multi camera rigs, where all panoramas are guaranteed to have the same image orientations.
2. or to automatically stitch a number of panoramas by just pointing PTGui to a folder with images. The images are taken for example by rotating the camera on a panoramic tripod head.

In the latter case the image positions in each panoramas will usually be slightly different. Even if the panoramic head has click stops, mechanical tolerances will cause small variations in the image orientations in each panorama. To compensate for this PTGui should analyze the images for each panorama and generate control points.

Whether the batch stitcher will generate control points is controlled by this setting in the project:
Project Settings -> Batch Stitcher actions -> Do 'Align Images' and save the modified project
This option should be checked in the template used in the Batch Builder, unless the image positions in each panorama will be absolutely identical. If you are using a multi camera rig and need all panoramas to be stitched absolutely identically, uncheck this setting in your template:
Project Settings -> Batch Stitcher actions -> Do 'Align Images' and save the modified project
Also see Q4.14.

If you do require PTGui to generate control points but would like to keep the panorama size and projection as set in the template, see: Q6.24. This is a known issue caused by a bug in Intel's graphics driver. It's affecting the PTGui Viewer only, the stitched panorama from PTGui should be fine. The problem seems to be limited to laptops with dual graphics processors (both a low power Intel integrated GPU and a more powerful AMD or NVIDIA discrete GPU). The problem can be solved by updating the Intel graphics driver. For laptops a driver package is usually made available on the laptop manufacturer's website. Look for the drive package including the Intel graphics driver.

Alternatively, for computers with an NVIDIA GPU the following workaround is reported to work: Right‐click the Windows desktop, then click NVIDIA Control Panel from the context menu. Under Manage 3D Settings - Global Settings, select: 'Preferred graphics processor: High-performance NVIDIA processor'. Note that this may affect battery life.

Another alternative is to use FSPViewer (which doesn't use OpenGL) instead of the PTGui Viewer. See Q6.29. This may happen on Windows machines with NVIDIA graphics hardware. Recently NVIDIA have released a driver update for Windows which appears to break GPU acceleration in PTGui 10. The problem does not seem to affect PTGui 11 and later.

If you don't wish to upgrade to PTGui 11, you may do one of the following:

• Disable GPU acceleration in PTGui (see Options - Advanced)
• Or downgrade the GPU driver to an earlier version. NVidia's driver version 397.64 is known to work. To download older nvidia drivers see: NVIDIA advanced driver search. But please understand that security problems may have been fixed in later drivers. Running older driver versions may be a security risk.

See Tutorial: straightening a panorama First of all always make sure to lock the exposure and white balance of your camera. Color differences can be corrected to a certain amount by the blending process, but you will get the best results by locking the color balance and exposure when shooting the images.

Exposure is locked by choosing the M mode if your camera. To lock white balance, choose one of the white balance presets on your camera that match the current lighting, such as 'Cloudy' or 'Sunny'.

Even with color balance and exposure locked you may still see get small differences in brightness due to vignetting. PTGui Pro can correct for this, see Vignetting correction with PTGui Pro. This can be changed in the Metadata tab. Switch to Advanced mode to reveal this tab.

Be aware though that the resolution of an image has nothing to do with image quality or print quality. The ppi/dpi value of an image file is just a number embedded in the header of the file, suggesting the number of pixels to be printed in one inch. You could set the resolution to a very large dpi value but this will not modify the image in any way, except that the image would be printed smaller (and thus have more pixels per inch).

The number of pixels is what really matters: if you need a more detailed output image, increase the width and height of the output image instead (on the Create Panorama tab). Click the '100%' button in the Create Panorama tab to achieve the highest quality. Increasing the output size beyond the optimum size is possible but will only increase the file size, not the amount of visible detail, since the latter is limited by the (angular) resolution of the source images.

Also see: The Myth of DPI. Parallax: First of all, make sure that the photographs are taken properly: for panoramas, all images should be taken from exactly the same viewpoint. More in particular: the camera should be rotated around the 'no parallax point' (sometimes referred to as the 'nodal point') of the lens. For most lenses this point is located near the front element; since it does not coincide with the tripod screw of the camera, you will need to use a so called panoramic head. If the camera is not rotated exactly around this point, parallax errors will occur, preventing a perfect stitch. Don't attempt to take a panorama from a tripod without using a panoramic head, you'll get serious stitching errors.

In about 4 out of 5 support questions we receive regarding stitching problems, parallax turns out to be the reason for the problem. Therefore for an introduction to parallax please read these articles: Finding the no-parallax point (by John Houghton) or What is parallax? (PanoGuide). Be sure to also watch our Video Tutorial: parallax is explained in the first video.

Florian Knorn made an in depth video tutorial on calibrating a panoramic head.

For experienced PTGui users, in Finding the nodal point (PDF), Frank Cullmann shows an alternative method for finding the no-parallax point by analyzing control point distances in PTGui.

The impact of parallax errors differs per scene: for a landscape panorama, with no objects close to the camera, a limited amount of parallax might not be a problem and such a panorama can easily be taken handheld. But for panoramas of room interiors even a small misplacement of the camera of just one centimeter or inch will result in clearly visible stitching faults. Creating a good interior panorama is therefore impossible without using a tripod and properly calibrated panoramic head.

In contrast to (e.g.) barrel distortion, correcting for parallax faults in software is impossible. This is not a limitation of PTGui but a physical limitation. If you must stitch images with parallax, the best you can do is to mask the faults after stitching by placing the seams appropriately (see our post processing tutorial) but this can be a lot of work and often does not lead to perfect results. Parallax problems lead to overall high control point distances: if you have many control points with an optimized distance of 20 or more (see below), this usually indicates a parallax problem.

Misplaced control points can be another reason for misalignment. Especially if there are repeating structures in the images, the control point generator may occasionally misplace one or two control points. The same can happen if there are moving objects in the panorama: slowly moving clouds in the sky are notorious in particular (also see Q6.44). Finding these misplaced control points is easy: open the Control Point table (Ctrl+B on Windows or Cmd+B on Mac) and find the control points with the largest distance. This distance indicates the alignment error of the control point in the panorama. By default, the table is sorted in descending distance, so the worst aligned control points are in the top of the list. In general, a distance below 5 is sufficient, while higher values usually indicate a problem. Double click on a control point in the table to edit it, or delete it by pressing Del.

Misalignment in an area of a panorama can occur if there are no control points in that particular area. Go to the Control Points tab and add a few points in problem areas to improve the alignment there.

A common misconception is that using a wide angle lens would cause misalignments, due to the distortion inherent to wide lenses. This is not true: PTGui can perfectly correct perspective distortion and barrel distortion in wide angle lenses. A panorama from a wide angle lens will thus look exactly the same as the same scene taken with a long lens, apart from any differences in quality and resolution. No, not necessarily. When editing control points you should not just aim for the lowest possible control point error. Instead the goal should be to keep all control points that are placed correctly, and delete only the faulty ones. Faulty control points include for example points placed on moving objects such as people, clouds and cars, and control points placed incorrectly on different objects. The latter may happen in particular with repeating structures.

Often these misplaced control points have a higher than average control point error, but the reverse is not true: not every control point with high error is a faulty one. If you have a control point pair with a large error but with both markers placed on the same spot on a non-moving part of the panorama, then this control point actually improves the alignment of that particular area in the panorama. Therefore it should be kept rather than deleted, even though this increases the average control point distance.

If you are consistenly getting control points with high errors (say, 5 or higher) then this most likely means that your images suffer from parallax. Only images without parallax can be stitched perfectly. See Q5.4 for more about parallax. Ultimately these errors are caused by parallax: if the camera has been moved between taking the first and last images, foreground objects will have shifted relatively to background objects. If control points are placed on nearby objects, PTGui will attempt to align those objects but stitching errors will result on objects far away (i.e. anything on the horizon).

In drone panoramas usually the misalignment will be most severe between the first image and the last image in the sequence, due to the drone drifting over time. Especially altitude drifting will lead to clearly visible stitching errors at the horizon, because a vertical misalignment at the horizon is extremely noticable.

One workaround for parallax is to remove all control points on nearby objects and only keep control points on objects further away from the camera. This effectively removes the parallax and results in a perfectly straight horizon. But this will come at the expense of stitching errors on foreground objects. Those stitching errors would need to be retouched manually.

Often a better alternative is to use Viewpoint Correction on all images except one. Viewpoint Correction is available in the Pro version of PTGui. Although Viewpoint Correction is intended to be used on flat surfaces only, it can work quite well on drone images even when the surface is not actually flat.

Proceed as follows:

• Load all images and run Align Images
• Make sure all images have control points; if not, add control points where necessary
• Switch to Advanced mode by pressing the Advanced button in the side bar
• Go to the Optimizer tab
• Switch the Optimizer to Advanced mode by pressing the Advanced button in the Optimizer tab
• Enable Viewpoint Correction for all images except one image. This can be done by clicking the header above the 'Viewpoint' column: all cells of the 'Viewpoint' column will be selected. Then left-click in one of the cells and select 'Optimize'; this should change all cells to 'Optimize'. Now click and hold down the mouse button for one second in a cell of the Viewpoint column, so that only that cell is selected and change this cell to 'Reset'. A good candidate is an image in which the horizon is visible and not obstructed by nearby buildings.
• Run the Optimizer. It will assign viewpoint offsets to the images.
• Do Control Points - Generate Control Points. This will generate extra control points fitting the viewpoint optimized images.
• Do Control Points - Remove Worst Control Points. If the parallax was not too severe to start with, it would now report a 'good' optimization result.
• Add a couple of 'Horizontal Line' control points on the horizon. Part #8 of the Video Tutorial series shows how to do this. Although the tutorial covers Vertical Line control points, the procedure for adding Horizontal Line control points is the same. Run the Optimizer again to level the panorama.

Usually this will result in a well aligned panorama with a straight horizon. Keep in mind though that Viewpoint Correction may result in slanted (i.e. non-upright) buildings. This is not very noticable if the parallax was caused by altitude differences, but if the drone moved sideways you may see nearby high rise buildings leaning slightly to one side.

Also, when optimizing Viewpoint, it's important to keep at least one image without Viewpoint Correction. The corrections in other images will be 'anchored' to this image. If viewpoint optimization would be enabled for all images, the optimizer is given too much freedom and may distort all images extremely in order to minimize the misalignments. Therefore one of the cells in the 'Viewpoint' column in the Optimizer tab should be set to 'Reset'.
You would need to use the rectilinear panorama projection. Rectilinear projection is the only projection that preserves all straight lines; all other projections will curve certain lines. Unfortunately rectilinear projection is limited in practise to a maximum field of view of about 120 degrees, so there is no way to preserve straight lines for wide panoramic scenes in a single image. This is not a limitation in PTGui but a physical limitation.

For more information see: Projections

But by using an interactive panorama viewer it's possible to show a wide panorama while preserving straight lines: the panorama viewer only renders a narrow rectilinear view in a certain viewing direction. The user can look around in the entire scene by changing the viewing direction. See Q6.15 and Q6.29. See part #8 of our Video Tutorial series.
Also, John Houghton wrote an excellent tutorial.
German readers see this page by Bernhard Vogl For panoramic stitching you don't need to know the lens parameters since PTGui calibrates your lens automatically for each panorama. But knowing the lens parameters can be useful if you (for example) would like to correct a single image for barrel distortion. The lens parameters can be calibrated accurately as follows:

1. Take enough images to build a 360 degree, single row panorama. Make sure the images overlap by at least 30%. Make sure that the camera is rotated around the 'no parallax point' of the lens, in order to avoid parallax errors.
2. Load the images into PTGui, and execute step 2 (Align Images) of the Project Assistant.
3. Switch to the Control Points tab and review all generated control points. Remove any misplaced control points, and any control points on moving objects (including clouds in the sky!). Also remove any control points on nearby objects, since these will suffer the most from any remaining parallax errors in your setup. Make sure that each pair of overlapping images has at least 4 control points (more is better). Ensure that there are some control points in the corners of the images as well, not just in the center.
4. Optimize the project using the Optimize button in the Project Assistant.
5. Open the Control Point table (Ctrl+B or Cmd+B). The control point distances should be small, generally less than 3. If you find control points with higher distances, correct or remove them by repeating the previous two steps.
6. Switch to Advanced mode by pressing the Advanced button in the side bar.

Now the optimized lens parameters can be found as the a, b and c parameters on the Lens Settings tab. Use the Lens Database button to save the values for later use.

Please note that different orientations (landscape vs. portrait) and different focal lengths (in case of zoom lenses) will result in different correction values, so be sure to save separate entries in the lens database for each zoom setting and for landscape and portrait orientation. Even at the same zoom setting and orientation subsequent calibrations may result in significantly different a/b/c values. This is normal, since completely different a/b/c values may represent very similar lens correction curves. In general this is not possible. PTGui was designed for stitching true panoramas, by taking overlapping photos from a single camera viewpoint. If the camera is moved between shots, parallax errors will occur. Correcting for parallax errors in software is physically impossible so in general it is impossible to stitch such images without visible misalignments.

There is one exception: if the subject to be photographed is flat, like a wall or like aerial photographs (shot from some altitude and without high rise buildings), parallax faults will not be noticable. Such images can be stitched in PTGui if the following conditions are met:

• the subject should be flat, or if the subject is not completely flat, all control points should be placed on a flat surface only. When stitching aerial photographs, remove any control points that are not on the ground surface. When stitching photos of a wall or facades of buildings in a street, remove all control points on any objects in front of the surface.
• the camera should be pointed exactly perpendicular to the subject's surface, i.e. for aerial images the camera should be pointed exactly vertically
• in all shots the camera is at exactly the same distance from the surface

Under these circumstances the photos can be stitched using the process for stitching mosaics, see the section directly below.

If the subject to be photographed is not too wide and the camera can be placed at sufficient distance, consider taking your photographs as a true panorama instead, from a single camera viewpoint. Choose a rectilinear panorama projection so that straight lines in the scene will remain straight in the panorama. The result will probably look better than when attempting to stitch images where the camera was moved between shots. PTGui was designed for stitching panoramas, from photographs taken from a single camera viewpoint. When stitching a panorama, images are warped to correct for perspective distortion so that a seamless overlap is achieved. For mosaic-style stitching on the other hand the images should only be shifted and rotated; any perspective warping is undesirable. PTGui can be tricked to do no warping by setting the field of view of the source images to a very small value, which corresponds to a tele lens with a long focal length.

To stitch mosaics, proceed as follows:

• Start a new project and load your source images
• Switch PTGui to Advanced mode using the Advanced button in the side bar
• Go to the Lens Settings tab and set the Lens type to Rectilinear. Set the Horizontal Field of View to 1 degree.
• In the Control Points menu choose 'Generate Control Points'
• Go to the Optimizer tab. Deselect the 'Optimize lens focal length' checkbox. At 'Minimize lens distortion', choose 'Heavy'.
• Press the Run Optimizer button (at the bottom)
• Now go to the Panorama Editor window by pressing Ctrl+E (Windows) or Command+E (Mac). First press the Center Panorama button, then press the Fit Panorama button.

Your mosaic is now ready to be stitched at the Create Panorama tab. Yes, this is possible. Although the field of view sliders in the panorama editor always crop the panorama in a symmetrical way (keeping the horizon of the panorama in the middle), an alternative way to crop the panorama is by using the yellow crop lines which can be dragged from the corner of the image in the panorama editor. An example of this is shown on page 4 of the Quick Tour. The crop lines can be placed anywhere so this method is not restricted to symmetrical cropping. The easiest way to achieve this is by using the Masking features in PTGui Pro. See the tutorial: Masking in PTGui Pro.

If you don't have the Pro version a similar result can be achieved with some more effort by adding an alpha channel to the source images and making unwanted parts transparent in an image editing program (such as Photoshop) before loading the images in PTGui.

Finally you can also retouch a panorama in Photoshop after stitching, by using a layered output format; see the Post processing tutorial. For single row panoramas, PTGui will always attempt to align the images in a horizontal row. This behavior cannot be changed, but you can easily rotate the panorama: in the Panorama Editor, simply use the right mouse button and drag the panorama to the right orientation. After rotating, you may need to press 'Fit Panorama' in the Panorama Editor to resize the panorama area so that it fits.

Vertical panoramas usually look best in one of the Transverse projections. You can choose a suitable projection in the Projection submenu of the Panorama Editor menu. There are several options. Peter Nyfeler has created a Photoshop action for adding a mirror ball nadir cap.

Or you could use your own logo. The logo needs to be warped into the projection of the panorama, as follows:

• Start a new PTGui project
• Add your logo image to the project
• Switch PTGui to Advanced mode
• Go to Lens Parameters and select 'Rectilinear' and (e.g.) 60 degrees field of view. The value you enter here sets the size of the warped logo.
• Panorama Settings: Equirectangular, 360x180 field of view
• Image Parameters: set the Pitch angle of the image to -90 degrees
• It's not necessary to add control points or to optimize
• Create Panorama tab:
  Width/Height: same as your original spherical panorama
  Output format: .psd or .tif
  Layers: blended panorama only
• Then press 'Create Panorama'

The result is a warped version of your logo. Overlaying the logo has to be done manually in a graphics editing program. A quick way to do this in Photoshop is by selecting the entire logo image (Ctrl-A), copying it (Ctrl-C) and then pasting it into the panoramic image (Ctrl-V). This creates a new layer in the panorama with the logo.

If you have PTGui Pro, instead of covering the missing parts consider using Viewpoint Correction to create a full panorama of the entire scene including the nadir. See the Viewpoint correction tutorial. Choose 'Make Default' in the file menu to save the current settings as a starting point for new projects. This will save all settings, except for the images and control points. It works exacly like Apply Template but it is applied to every new project.

Even if you changed the defaults, the Project Assistant will still override certain settings in order to ensure a good result: it will adjust the field of view of the panorama to fit the contents, it will choose a suitable projection depending on the field of view, and it will choose an appropriate output size. All of this can be overridden as follows (Pro version only):

• First of all do: File - Reset Default Project Settings, to remove any modified default settings
• File - New Project
• Click on Advanced
• Go to the Project Settings tab and disable these checkboxes:
  
  • Fit Panorama
  • Choose a suitable projection
  • Set output to maximum size but never more..
• Go to the Panorama Editor
• Select the desired panorama projection and field of view. For example Panorama Editor - Projection - Spherical (360 x 180 degree equirectangular)
• Go to the Create Panorama tab and select the desired output size and file format
• Now either do File - Save As Template to create a template: this template should be applied before pressing Align Images, or the template can be used in the Batch Builder.
  Or do File - Make Default if these settings should be used for all future projects.

If you have enough free disk space and a fast computer, PTGui can easily stitch hundreds or even thousands of images into a panorama. Not all file formats can be used though:

• JPEG: maximum size is 65,535 x 65,535 pixels. Keep in mind that some applications cannot open JPEG files wider or taller than 30000 pixels.
• TIFF: unlimited dimensions. Traditional TIFF is limited to files of 4GB in size. PTGui supports the BigTIFF dialect which does not have this limitation. PTGui will automatically switch to BigTIFF when the file size exceeds 4GB. Keep in mind that not every TIFF capable application is able to read BigTIFF.
• Photoshop .psd: max 30,000 x 30,000 pixels and a maximum file size of 4 GB
• Photoshop .psb: no limitations in practise. Photoshop has a limit of 300,000 x 300,000 pixels. PTGui can create panoramas larger than this but Photoshop will not be able to open them.

This can be done using PTGui; it can be used for (e.g.) accurately aligning a set of images for manual HDR creation, for making a time lapse movie, or for extending depth of field by merging images taken at different focusing distance.

It requires a special workflow though. By default, PTGui expects that a project contains overlapping source images, taken from the same viewpoint, but in different directions. The perspective changes that occur when the camera is rotated allow PTGui to accurately calculate the focal length (or field of view) of the lens. When all images are taken in the same direction, this information is missing and PTGui may end up optimizing the lens parameters to wrong values. This can result in a very small field of view, or introduce barrel distortion.

If the images are taken in one direction, they can be aligned in the following way:

1. Load the source images in PTGui.
2. Switch to Advanced mode by pressing the Advanced button in the side bar.
3. Go to the Optimizer tab, uncheck 'Optimize lens focal length' and choose 'Minimize lens distortion: No'.
4. In the menu bar, choose Control Points|Generate Control Points.
5. Press F5 to launch the optimizer. The images are now aligned properly.
6. In the Panorama Editor window, press the Fit Panorama button. Optionally adjust the field of view using the two sliders if you need to adjust the cropping of the output.

This can be achieved using templates (see Q3.9). Create the first panorama in the regular way and save the project file. For the subsequent panoramas do the following:

• Start a new project
• Load the source images
• Choose File | Apply Template | Other.. and browse to the project file saved earlier
• Go directly to Create Panorama to stitch the result. Don't add any control points and don't press Align Images

To do this, you first need to get the calibrated parameters of your lens, as described in Q6.3. Save the calibrated values to the lens database in PTGui.

To correct a single image:

• Start a new PTGui project
• Load the image to be corrected
• Switch to Advanced mode by pressing the Advanced button in the side bar
• Go to the Lens Settings tab
• Press the Lens database button and load the previously calibrated values
• Open the Panorama Editor (press Ctrl+E on Windows, or Command+E on Mac)
• Choose Rectilinear in the Projection menu in the Panorama Editor
• Choose Fit Panorama in the Edit menu in the Panorama Editor
• Optionally move the sliders to adjust the cropping area

After the above steps, the project can be saved as a template. For subsequent images, start a new project, load the image to be corrected, choose File | Apply Template, and pick the template project. PTGui comes with a web panorama viewer and authoring tool. With a few clicks you can create the files needed to show your panorama on a website.

First stitch your panorama to a flat image in JPEG or TIFF format. It's best to use Equirectangular projection (click the Equirectangular button in the Panorama Editor). Make a note of the horizontal field of view of the panorama, this is shown in the status bar of the panorama editor window. Don't use the yellow cropping lines in the Panorama Editor: you'll need an image where the horizon is in the middle, otherwise the panorama viewer will distort the panorama into a curved shape.

Then go to Tools -> Publish to Website to open the authoring tool. For more information about the different settings consult the accompanying Help page. Press the Convert button to process the panorama. This creates a HTML page and 17 other files; all files should be uploaded to a folder on your web server. Then you may add a link from an existing page to the generated .htm page which will open the panorama.

Note that in order to upload the files, your web hosting company should give you raw access to the files being served. If they only offer you access to a Content Management System this may not be the case. In general this is referred to as FTP Access, so check with your web hoster whether they support this and consult their support for the FTP upload settings.

The PTGui panorama viewer automatically choses between 3 different technologies (Flash, CSS3D and WebGL) to display the panorama. This ensures that your panorama is viewable on almost every modern device, including smartphones and tablets.

It is however intended to be just a simple and quick way to show your spherical panoramas on a website. If you need more advanced features such as hotspots, custom buttons, etc, or if you need to display gigapixel panoramas, try one of these third party web viewers:

• Pano2VR
• krpano
• Marzipano

To produce a virtual tour for iPad/iPhone/iPod you can use:

• iOSVR

If you don't have a web site, or one without FTP access, consider using one of the many dedicated panorama and virtual tour hosting services. The panorama can be uploaded to such a service and optionally embedded in your own website by means of an IFRAME.

• For an overview of several services, covering Round.Me, WalkInto, 360Cities, Spinnatic, Google, YouVisit and ViewAt, see: What does it look like by Tony Redhead.
• VPiX offer a fully featured virtual tour creation and hosting platform.
• EasyZoom is service for hosting and sharing gigapixel images.
• vr-easy: A cloud based solution for 360° photography and vr-marketing.

Most panorama viewers or panorama publishing services can handle 360 x 180 degree equirectangular images and this has become the de-facto standard for spherical images. If your panorama has sufficient coverage to be considered spherical, PTGui will automatically pick this projection. If not, select it by doing Panorama Editor -> Projection -> Spherical (360 x 180 Equirectangular).

It's also possible to publish a panorama to Facebook; see Q6.16.

If you would like to view a spherical panorama on your computer (not on a website) see Q6.29. Facebook supports spherical panoramas, which are displayed in an interactive panorama viewer. The required 'gpano' metadata is embedded by PTGui by default, so it works with panoramas straight from PTGui.

You should create a 360 x 180 degree panorama in Equirectangular projection: in PTGui select Panorama Editor -> Projection -> Spherical (360 x 180 Equirectangular) and use the tiff or jpg output file format (because PTGui currently does not embed metadata in Photoshop output). Facebook apparently expects the width and height to be even, so a size of 8000x4000 pixels will work, but 8002x4001 may not work. For Facebook to recognize the image as a panorama the image should contain the 'gpano' XMP metadata. PTGui 10 and later embed this data by default; just be sure to use the proper projection and file format (see Q6.16). If the image from PTGui has been processed in an image editing application (like Photoshop, LightRoom, GIMP), it's possible that this has stripped out the metadata.

To verify if the necessary metadata is present upload your panorama to metapicz.com (or any other metadata viewer). You should see an XMP section containing the following:

ProjectionType       equirectangular
UsePanoramaViewer    1
(...)
StitchingSoftware    PTGui Pro 10.0.15 (www.ptgui.com)

If this section is missing (or even if the section is present but there is other nonrelated XMP data as well), Facebook will treat your panorama as a regular non panoramic image. Try to use an image straight from PTGui to ensure the problem is not caused by post processing. This can be done as follows:

• Start a new PTGui project
• Add the stitched panorama as a source image to the project
• Go to the Panorama Editor window
• Select [Panorama Editor] -> Projection -> Spherical (360 x 180 degree equirectangular)
• Go to the Create Panorama tab
• Click Create Panorama

Please note that this re-processes the image, including interpolation and JPEG decompression and compression (if applicable). This will slightly degrade the image quality, although in practise this is probably hardly noticable.

The image interpolation step can be avoided by switching PTGui to Advanced mode (in the side bar), then go to the Create Panorama tab and choose 'Interpolator: Nearest Neighbour'. Note that Nearest Neighbour interpolation only gives good results if the generated panorama is completely identical to the source image (same projection, same pixel dimensions, no warping).

Do File - Save As Template to save the project as a template. This template can be applied to other equirectangular images (but only if they have the same pixel dimensions). Besides straightening a panorama manually in the Panorama Editor, it's also possible to level a panorama using 'horizontal line' and 'vertical line' control points. Such control points indicate points that should end up on a horizontal or a vertical line in the panorama. PTGui is able to modify the orientation of the panorama in such a way that the horizontal / vertical line control points are aligned on a horizontal or vertical line, respectively, in the panorama.

Vertical line control points can be placed on any vertical feature in the panorama, such as the side of a building. Horizontal line control points should only be placed on the horizon itself: in a spherical panorama, all horizontal lines are curved, except for the horizon itself. For most panoramas (in particular cityscapes) it's easiest to use only vertical line control points. One exception would be a panorama of a sea shore: here you could place horizontal line control points on the horizon.

While regular control points can only be placed between two different images, horizontal / vertical line control points can be placed within the same image. To do so, choose the same image in the left and the right pane in the Control Points tab. The 'CP type to add' listbox sets the type of control point that will be created next. Choose 'horizontal line' or 'vertical line'. Then click on two points (one in the left pane and one in the right pane) that should be aligned horizontally or vertically. Even if the two points are within the same image, place one point in the left pane and one point in the right pane.

For most panoramas it's sufficient to place two pairs of horizontal line or vertical line control points, although it will not hurt to add more. The best results are achieved if the two pairs are in different parts of the panorama, preferably in a 90 degree yaw interval (e.g. one in northern direction and one in eastern direction).

Now there are two ways to have PTGui align the panorama based on the horizontal / vertical line control points:

1. In the Panorama Editor menu bar, choose Edit | Level Panorama.
   
   PTGui will rotate and move the panorama in such a way that the horizontal / vertical line control points are aligned as much as possible. This is similar to dragging the panorama in the Panorama Editor in 'Panorama Edit' mode: since the panorama is moved as a whole, the alignment of individual images is not affected. Or:
    
2. Use the optimizer by pressing the 'Optimizer' or 'Run optimizer' buttons.
   
   If the optimizer tab is in Simple mode (this is the default setting), or if in Advanced mode with 'Level in second pass' selected: PTGui will do a two stage optimization. First the images are aligned as usual based on the normal control points. The horizontal / vertical line control points are ignored in this step. In the second pass the optimizer levels the panorama as described above, using only the horizontal / vertical line control points. In other words, horizontal / vertical line control points are only used for levelling, and only the regular control points are used for aligning the images.
   
   If the optimizer tab is set to Advanced mode and 'Include in single pass' is selected, everything is optimized in one pass. Now the horizontal / vertical line control points will be used to optimize image alignment too. This can be useful in particular for straightening a single image based on horizontal and vertical features, but is not recommended for leveling panoramas. When 'Include in single pass' is selected, it is necessary to give the optimizer sufficient freedom by allowing it to modify the pitch and roll of all images (i.e. the pitch and roll checkboxes for all images should be checked). With 'Level in second pass', or with the optimizer in Simple mode this is not needed.

Be sure to watch part #8 of our Video Tutorial series.

First you need to determine the vignetting of your lens. To do so, take a small panorama (e.g. 3 images, each overlapping about 50%). The amount of vignetting depends on the aperture of the lens so this should be done for each aperture at which you intend to do vignetting correction. In this calibration project, go to the HDR/Exposure tab and press Optimize Now. Press the Save buttons below the vignetting curve and the camera response curve to save the curves to a file.

The actual vignetting correction can be done as follows:

• Start a new PTGui Project
• Load your source image. Note the lens projection that is chosen by PTGui (e.g. Rectilinear)
• Switch to Advanced mode
• Go to the HDR/Exposure tab and load the previously saved vignetting curve and camera curve.
• Go to the Panorama Editor. Set the panorama projection identical to the lens projection (e.g. Rectilinear or Fisheye).
• Press the Fit Panorama button
• Choose the desired output format and press Create Panorama. PTGui may complain about missing control points; you can ignore this warning.

You can save the thus created project to a file and use it as a template for subsequent corrections: you will only need to start a new project, load the next source image and choose Apply Template.

It's possible to combine this process with barrel distortion correction, see Q6.14. PTGui does not require your photos to be limited to a single row. To fill the missing parts just take additional pictures with the camera pointing upwards ('zenith') and downwards ('nadir') photos. As always you should make sure to rotate the camera around the 'no parallax point' (see Q5.4). This is even more important when shooting the nadir and zenith photos.

Start a new PTGui project and load all your images, including the nadir and zenith photos, before pressing Align Images. The order of the photos is not important, PTGui should be able to figure out which image belongs where in the panorama.

Sometimes PTGui is unable to find control points, and this may happen in particular with nadir and zenith images (for example if the zenith image contains mostly blue sky). In that case you will see a warning 'PTGui was unable to find control points for one or more images' in the Project Assistant. If this happens see Q4.5. If you did not include a zenith and nadir image (with the camera pointed upwards and downwards, respectively) the top and bottom of the spherical panorama are not covered by images, resulting in black circular holes at the top and bottom. To hide these holes you can limit the vertical viewing angle by setting a minimum and maximum tilt angle in the Publish to Website window.

• Go to the Panorama Editor window by pressing Ctrl+E (Windows) or Command+E (Mac)
• Move the vertical slider at the right hand side until there is no more empty space at the top and bottom
• Look at the status bar at the bottom of the panorama editor: it should show something like: 360° x 110° Equirectangular. Remember the second value (110°); this is the vertical field of view of the panorama.
• Open to the Publish to Website dialog
• Divide the vertical field of view by 2 and set the Minimum Tilt value to minus this value, and Maximum Tilt to the positive value. In this example the values would be -55 and 55. Then press OK.

This will limit the amount in which the viewer can look up and down so that the black borders remain unvisible. Cropping can be done in two ways:

• Use the two sliders in the Panorama Editor to adjust the field of view. Moving the sliders upwards/leftwards reduces the field of view, effectively cropping the edges from the panorama. This kind of cropping is symmetrical: the same amount is cropped from both sides of the panorama.
• Alternatively, yellow crop lines can be dragged from the edges of the panorama in the Panorama Editor. See the Video Tutorial. The crop lines can be placed anywhere so this method is not restricted to symmetrical cropping.

First, in the Project Settings tab (PTGui Pro only): disable the checkboxes 'Fit panorama' and 'Choose a suitable projection'. Then go to the Panorama Editor and choose the desired panorama projection and field of view in the Projection sidebar. Finally, in the Create Panorama tab enter the desired output dimensions and select 'fix at ...% of optimum size'.

These settings can be re-used by saving this as a template using File -> Save As Template. A fisheye lens distorts images such that straight lines become curved. Removing this distortion is typically called 'defishing'. Please note that it is not necessary to defish images prior to stitching, PTGui can perfectly handle fisheye source images.

Defishing is done by converting from fisheye projection to rectilinear ('flat') projection. A single image can be defished in PTGui as follows:

• Start a new PTGui project
• Add the fisheye image using the Load Images button
• Open to the Panorama Editor window by pressing Ctrl+E (Windows) or Cmd+E (Mac)
• Switch to rectilinear panorama projection by clicking the 'rectilinear projection' button in the Panorama Editor's toolbar
• Adjust the sliders until you get the desired field of view. The image can be dragged around in the Panorama Editor to modify its perspective. Asymmetric cropping is possible by dragging yellow crop lines from the edges of the panorama in the Panorama Editor.
• In the PTGui main window go to the side bar and click on 'Advanced'. This will make the Create Panorama tab visible.
• Go to the Create Panorama tab. Choose the desired size and file format and press Create Panorama to render the image.

Please note that it's typically impossible to keep the entire image. Fisheye lenses usually have a field of view of 180 degrees while rectilinear projection is limited to around 120 degrees. Attempting to get a wider view will result in extreme stretching of the corners of the image. In fact it is the fisheye distortion which allows a fisheye lens to have its wide field of view. This is done by converting the panorama to rectilinear projection. The process is nearly identical to defishing (see previous question) and the same limitations apply.

Assuming your panorama is a 360 x 180 degree equirectangular image, proceed as follows:

• Start a new PTGui project
• Add the panorama image using the Load Images button
• Open to the Panorama Editor window by pressing Ctrl+E (Windows) or Cmd+E (Mac)
• Switch to rectilinear panorama projection by clicking the 'rectilinear projection' button in the Panorama Editor's toolbar
• Adjust the sliders until you get the desired field of view. The image can be dragged around in the Panorama Editor to modify its perspective. Asymmetric cropping is possible by dragging yellow crop lines from the edges of the panorama in the Panorama Editor.
• In the PTGui main window go to the side bar and click on 'Advanced'. This will make the Create Panorama tab visible.
• Go to the Create Panorama tab. Choose the desired size and file format and press Create Panorama to render the image.

Again, flat projections are limited to about 120 degrees field of view; it's impossible to display an entire 360 degree panorama in rectilinear projection. By default, for spherical panoramas PTGui will pick a random point on the horizon as the center point. If the first image of all your panoramas was taken in exactly the same direction, you can use the following method:

• Set up and align the first panorama in PTGui. In the side bar click on Advanced
• Go to the Image Parameters tab and write down the Yaw, Pitch and Roll values of the first image.
  For every subsequent panorama:
• Click on Advanced and go to the Image Parameters tab
• Enter the above Yaw, Pitch and Roll values for the first image
• Go to the Optimizer tab and set 'Anchor Image: Image 1'
• Press the Run Optimizer button

Now the panorama is aligned around the same point in the first image.

Or, if all panoramas were taken from the same viewpoint but not exactly in the same direction: First stitch the first panorama in the normal way. Create a medium sized copy of the panorama in jpeg or tiff format, we will use this to align the subsequent panoramas against. For each subsequent panorama:

• Load all images of the panorama and press Align Images to set it up
• Add the already stitched panorama as an additional source image
• In the side bar click on Advanced
• Go to the Lens Settings tab. At 'Use Individual Parameters For' enable the Lens, Shift, Shear and Crop checkboxes for the last image (i.e. the already stitched panorama)
• Go to the Image Paramaters tab. For the last image set Yaw=0. Pitch=0, Roll=0. Set the Lens Type and FoV to the appropriate values for the panorama; for a spherical panorama for example these should be set to Equirectangular and 360 degrees. Set the a,b,c, shift and shear values to 0.
• Go to the Crop tab, select the last image and press No Crop
• Now the first panorama is overlayed over the current project. You can toggle its visibility in the panorama editor by clicking the bottom 'Include images' checkbox in the Create Panorama tab.
• To align the current panorama to the original panorama we need to add a few control points. Go to the Control Points tab. In the left pane choose the last image (which is the original panorama). In the right pane choose an image of the current panorama. Add 2 control points.
• Repeat the above step for one more image so you end up with 4 control points spread across the entire panorama
• Go to the Optimizer tab and make sure it is set to Simple mode (this is the default).
• Set 'Anchor Image' to the last image (the original panorama). Enable 'Optimizer lens Field of View' and set 'Minimize Lens Distortion: Heavy'.
• Click on the Advanced button in the Optimizer tab
• Disable the FoV, a, b, c, shift and shear checkboxes for the last image
• Press the Run Optimizer button
• Now the current panorama should be aligned to the original panorama. Verify this in the panorama editor by toggling the last 'Include Images' checkbox in the Create Panorama tab.
• Go to the Source Images tab and remove the last image. The panorama is now ready to be stitched.

Sometimes one or more images in a panorama don't show any suitable objects to place control points on, for example when an image contains only blue sky or a plain white wall. Since the exact alignment of a plain colored image is usually not critical, you can align it by hand:

First make sure that the rest of the panorama is set up properly (usually just pressing Align Images is enough). Then go to the Panorama Editor window by pressing Ctrl+E (Windows) or Command+E (Mac). Switch the panorama editor to 'Edit Individual Images' mode using the toolbar, the menu or by pressing Ctrl+Shift+I (Windows) or Command+Shift+I (Mac). In this mode you can move individual images around. Use the left mouse button to move an image, or use the right mouse button to rotate it. Single button Mac users can use Ctrl+Mouse button to rotate. For more information see the Help page for the panorama editor pressing F1 (Windows) or Fn+F1 (Mac).

When done, go back to the main window, click on Optimize and proceed to Create Panorama. You can ignore warnings about missing control points. To view a spherical panorama interactively (i.e. with the ability to 'look around' by clicking and dragging the mouse) you need a panorama viewer. Since version 10 a spherical panorama viewer is included with PTGui.

For interactive viewing the panorama should be stitched as a 360x180 degree equirectangular image. To choose this format select Projection - Spherical in the Panorama Editor menu bar in PTGui.

To view your stitched panorama interactively, press the 'View...' button in the Create Panorama tab and select 'Open in PTGui Viewer'. The PTGui Viewer can also be opened directly via Tools - PTGui Viewer. The PTGui Viewer supports panoramas in equirectangular projection, in TIFF or JPEG format.

Other panorama viewers are available as well:

• FSPViewer (Windows only)
• DevalVR player (Windows only, download 'DevalVR player Unicode')
• Panini (Windows/ Mac / Linux)

For more viewers see Panorama Viewers (PanoTools.org Wiki).

For many years Apple's QuickTime Player has been able to display interactive spherical panoramas through a special type of .mov file called QuickTime VR (QTVR). Unfortunately Apple decided to remove QTVR support in 2009, so QTVR should be considered a legacy format. See Q4.12 if you need to play a QTVR .mov file .

PTGui can be configured to launch one of these viewers when the Preview button (in the Preview tab) or the View button (Create Panorama tab) is clicked. To configure this go to Tools-Options (Windows) or PTGui-Preferences (Mac). In the Viewers tab enter the path to the viewer application. Up to 3 applications can be configured: not only panorama viewers but also image editing applications such as Photoshop.

If you would like to embed a spherical panorama on your website see Q6.15. No, unfortunately no such format exists, you need to install a panorama viewer to be able to interactively view a panorama. See Q6.29.

Alternatively publish the panorama to your website, on most computers it will be possible to view the panorama without needing to install anything. See Q6.15. This can be done as follows:

• load the image and the panorama as source images in a new PTGui project.
• After loading the images, click Advanced and go to the Lens Settings tab. If your images have EXIF data, PTGui should have added two lens profiles, one for each image. If not, add a lens profile by clicking the + button. In the 'use individual parameters' list, verify the each image is assigned its own lens profile. Verify that both images (i.e. both lens profiles) have the proper lens parameters assigned. If the panorama is a spherical panorama, it should have equirectangular 360 degree lens settings.
• Go to the panorama editor window. Set the projection identical to the projection of the original panorama (e.g. equirectangular). Then click on the Fit Panorama button. The view in the panorama editor should now be identical to the original panorama.
• If the image to be matched is a circular fisheye image, go to the Crop tab and set the crop circle accordingly. For other lens types this step is not necessary.
• Again go to the Panorama Editor. Click on the 'Edit individual images' button. The image is now shown on top of the panorama. Drag the image approximately into the right position. Exact alignment is not important at this time. Press the Help button in the panorama editor if you need to learn how to do this.
• Now for exact alignment we need to set control points. Go to the Control Points tab and place a few control points between the two images. About 6 control point pairs should be enough, but do make sure that they are spread over the entire image area.
• Go to the Optimizer tab. Click on the Advanced button at the top. At 'optimize globally' disable all optimizations for the lens profile of the panorama. For the overlay image's lens profile enable Field of View, a, b, c, LShift and SShift. Disable the Shear checkboxes. At 'optimizer per image' only enable the Yaw, Pitch and Roll checkboxes of the overlay image. All checkboxes for the panoramic image should be cleared, so you have only 3 checkboxes selected here.
• Press the Run Optimizer button at the bottom. Hopefully the optimizer reports a good result.
• Go back to the panorama editor and check the alignment of the images, by hovering the mouse over the panorama. If the image is not aligned perfectly yet you may need to add a few more control points and run the optimizer again. If you cannot get the image to align perfectly this may be due to parallax (see below).
• Once you're happy with the alignment, go to the Create Panorama tab.
• Choose 'Output: Individual layers' only. This disables blending, which usually would not give the desired result. If you do want PTGui to blend the two images you may need to use the Mask tab (Pro version only) to indicate which parts of which images should be used, otherwise the blender may choose to use only a small fraction of the overlay image.
• Choose File format: TIFF or Photoshop. For TIFF output, two separate output files will be generated. For Photoshop a single file will be generated with two layers. Using JPEG output is not recommended since it does not support transparency.
• Finally press the Create Panorama button to render the output.

Keep in mind that as with any panorama, parallax errors will prevent proper stitching. Therefore the image to be overlaid should be taken from exactly the same location as the original photos for the panorama.

If you need to do the same for multiple panoramas or overlay images, you can save some time by using templates. Use File - Save As Template to save the settings of the project to a template, and use File - Apply Template to apply the settings to a future project. Control points still need to be placed by hand though since they are specific to the images used. PTGui supports two methods for command line stitching: the '-batch' flag adds project files to the batch stitcher queue for background stitching; the '-stitchnogui' flag stitches a project in a command line window without showing any windows.

Use the -batch flag as follows:

On Windows:

"C:\Program Files\PTGui\ptgui.exe" -batch "C:\Path\To\Projectfile.pts"

On macOS use the open command as follows:

open "/Applications/PTGui Pro.app" --args -batch "/Path/To/Projectfile.pts"

The above command returns immediately. The '-x' parameter can be added (after -batch), this causes the batch stitcher window to close when stitching has finished.

The second method stitches the project on the command line, without using the batch stitcher, and blocks until rendering has finished.

On macOS launch as follows:

"/Applications/PTGui Pro.app/Contents/MacOS/PTGui Pro" -stitchnogui project1.pts project2.pts batchlist.ptgbatch

On Windows:

START "" /WAIT "C:\Program Files\PTGui\PTGui.exe" -stitchnogui project1.pts project2.pts batchlist.ptgbatch

If configured the batch stitcher can also align the images and generate control points (Pro version only). To do so enable 'Align images and save the modified project' at 'Batch Stitcher actions' in the Project Settings tab. This allows for fully automated batch stitching of images without user interaction. Yes this is possible. The trick is to simulate using a long (narrow angle) lens, in this case hardly any warping will be done. Also, PTGui needs to be told not to optimize the lens field of view or lens distortion. To get an unblended collage you need to choose layered Photoshop output and flatten the panorama in Photoshop.

In short:

• Load your images
• Press Align Images. PTGui will analyze your images, generate control points and attempt to set up your panorama. If your images were actually taken as a panorama (i.e. overlapping, taken from the same viewpoint) this may result in a nice panorama, otherwise you may get garbage. Just ignore any warnings about missing control points.
• Switch PTGui to Advanced mode by pressing the Advanced button in the side bar
• Go to the Lens Settings tab and enter the following values:
  • Lens type: rectilinear
  • Focal length: 400mm
  • Press the 'Reset' button to reset the lens correction, shift and shear values to 0
• Go to the Optimizer tab, and disable 'Optimize lens focal length'. Select 'Minimize lens distortion: No'.
• Press the Run Optimizer button at the bottom. Most likely the optimizer will report a 'not so good' or 'bad' result.
• Go to the Panorama Editor by pressing Ctrl+E (Windows) or Command+E (Mac)
• In the Panorama Editor press the Center Panorama button and then the Fit Panorama button. To preview the actual collage without blending press the Overlay Mode button.
• You can move and rotate the panorama in the editor. Or you can move and rotate individual images by selecting 'Edit Individual Images' mode. See the on line help for more information. If you move individiual images, don't optimize the project anymore (even if PTGui prompts you to do so) otherwise your changes may be undone.
• To render the collage, go to the Create Panorama tab. Choose 'File Format: Photoshop (.psd)' and 'Layers: Individual layers only'.
• Press the Create Panorama button. Open the resulting layered file in Photoshop and flatten it in Photoshop through Layer - Flatten Image

If you have your own web server you can use the Publish to Website tool in PTGui (see Q6.15) and upload the results to your website. The panorama will be viewable on Apple iOS devices.

If you don't have a web server or if you would like to be able to view your panoramas without an internet connection, we are aware of two apps that support offline viewing of spherical panoramas: iPano and PangeaVR HD. Both can be purchased in Apple's App Store. Please note that these are third party applications for which we cannot provide support. PTGui currently does not directly support stitching of video footage. But the Batch Builder can be used as a rudimentary tool for stitching video. To do so, the videos first need to be converted into individual JPEG or TIFF frames using a suitable third party video editing application. Stitch the first frame as a regular panorama in PTGui and save the project file. This project file can be used as a template in the batch builder so that all subsequent frames are stitched exactly like the first. The resulting panoramas need to be assembled into a video in a video editing application.

To learn more about the batch builder, choose Tools - Batch Builder in PTGui Pro and press the Help button there.

For a dedicated panoramic video stitcher see SGO Mistika VR, this supports stitching based on a PTGui template. Yes, PTGui Pro includes the Batch Builder for this purpose. The Batch Builder scans a chosen folder for images and creates project files automatically. The project files can be based on a custom template. Once the project files have been generated they can be stitched overnight using the Batch Stitcher. If needed, control points can be generated as part of this process. Or, if the camera positions are known, control point generation can be skipped and all panoramas stitched with exactly the same settings.

For more information, launch PTGui Pro, go to Tools - Batch Builder and click on the Help button. A little planet is a panorama projected such that the floor of the scene is in the center. By using a stereographic projection, the horizon of the scene will become circular, thus giving the impression that the photo was taken from above a small planet.

A the little planet image actually is a fully spherical panorama since it covers both the floor (nadir) and the sky (zenith). Just like a regular spherical panoramas it is most easily taken with a fisheye lens.

To create a little planet panorama load your source images in PTGui and press Align Images. Then go to the Panorama Editor side bar and choose Projection -> Presets -> Little Planet.

Also see: Projections. Currently we do not offer a plugin for Adobe Lightroom, but PTGui can be integrated in Lightroom as an external editor as follows:

• In Lightroom, go to Edit - Preferences - External Editing
• Select Preset: Custom
• Click the Choose button next to Application and browse to the PTGui application. On Windows select C:\Program Files\PTGui\PTGui.exe, on Mac choose /Applications/PTGui.
• Select:
  File Format: TIFF
  Color Space: <your preferred color space, or sRGB if in doubt>
  Bit Depth: 16 bit
  Resolution: 300 (in fact any value is fine)
  Compression: None
• Select Preset: Save Current Settings as New Preset
• Enter Preset Name: PTGui and click Create.

Now you can open your photos from Lightroom into PTGui as follows: in Lightroom's library view select the photos to be stitched, right-click (Ctrl+click on Mac) on the selection and choose Edit In - PTGui. Then if you want to stitch the original photos choose Edit Original (note that PTGui will only read and never modify your source images). Or to stitch the photos with any Lightroom adjustments choose Edit a Copy with Lightroom Adjustments.

After the panorama has been stitched in PTGui, go to the folder in Lightroom's library where PTGui has created the panorama, right click on the folder name and choose Synchronize Folder. This imports the stitched panorama back into Lightroom. It might look easy at first sight (just stitch two panoramas, one for the left eye and one for the right eye), but stitching stereoscopic 360 degree panoramic images is actually far from trivial. Image alignment will not be perfect and it's impossible to get a true 3d view at the nadir and zenith using only a single panorama per eye.

The reason is parallax: to stitch seamless panoramas one needs to get rid of any parallax (see Q5.4). On the other hand parallax is a requirement for stereoscopic images: it's the parallax caused by the distance between our eyes that allows the brain to sense depth. Therefore any attempt to create a stereoscopic panorama will be a compromise between perfect image alignment and getting 3D depth.

That said, several people have developed techniques for stereo panoramic stitching. All methods come down to taking many images at small yaw increments (say 10 degrees). The camera is deliberately placed away from the no-parallax point. Due to the small yaw increments only a narrow slice of each image is used and this prevents the parallax error to accumulate over a wider area. In other words there will be many stitching errors but they are small and perhaps even unnoticeable.

Getting a stereoscopic view of the nadir and zenith remains impossible though. Imagine looking at the nadir and zenith while rotating the view: the panoramas for the left and right eye would gradually need to swap when the viewer rotates from 0 to 180 degrees, and intermediate views would be needed for the viewing angles inbetween. This is impossible to do with just a left eye and right eye panorama. But if the zenith is just plain blue sky and the nadir a flat surface one may get away without stereoscopic depth in these areas.

Wim Koornneef has developed an easy workflow for creating stereo panoramas with PTGui: Revised version of the tutorial "How to make a spherical 3D panorama with a single camera and a fisheye lens".

Also see this thread at the PTGui support forum: Managing stitching for stereo and Jim Watters' video tutorial: Stereo Stitching with PTGui.

If you would like to discuss 3D panoramic stitching please join the PTGui support forum! By placing your phone in a Cardboard VR viewer it's possible to experience a spherical panorama in virtual reality. The panorama should be stitched in 2:1 equirectangular format. This can be done in PTGui by going to the Panorama Editor menu and choosing Projection -> Spherical (360 x 180 degree equirectangular). In the Create Panorama tab select JPEG (.jpg) as the file format. Transfer the panorama to your phone's camera roll (for example by emailing or by using Airdrop on iOS).

To view the panorama on your phone in the cardboard viewer you can use these apps:

• Android: PSViewer for Google Cardboard
• Apple iOS: LookSee - VR
• Or by publishing to a website and using the phone's web browser: Pano2VR using the cardboard template

This is just a selection; any application capable of handling 2:1 equirectangular images is suitable. First of all, if possible (i.e. when using a single camera on a rotating panoramic tripod head), it would be better to use 3 images (spaced 120 degrees apart) instead of 2 images back-to-back. With 3 images there is much more overlap, PTGui will be able to align the panorama fully automatically and and the larger overlap area allows the blender to make smoother transitions between the. But if you must use two images, read on:

The difficulty when using two circular fisheye images back-to-back is the small overlap area: the images overlap only in a small ring at the outer edge of the images. This ring usually too small for PTGui to be able to find control points, so you will need to place control points manually. Also due to the small overlap area PTGui is not able to determine the lens distortion accurately. Therefore proceed as follows and create a template for your setup:

• Start a new project and load the two images
• Click on the Advanced button in the side bar
• Go to the Crop Tab and verify that the cropping circle matches the circular image; adjust if needed
• Go to the Image Parameters Tab and enter 180 degrees as the Yaw angle of the second image (originally it was 0)
• Go to the Control Points tab and place a couple of control points between both images. Try to spread the control points along the entire edge. If there's parallax (in particular if the images were taken with two cameras back to back), try to place control points only on distant objects. Nearby objects will suffer from parallax errors the most.
• Go to the Optimizer tab and set:
  Optimize Lens focal length: yes
  Minimize Lens Distortion: Medium
• Run the Optimizer
• Go to the Panorama Editor menu and choose Projection -> Spherical (360 x 180 equirectangular)

Assuming the result looks good, save it as a template using File -> Save As Template. For the next panorama most of the above steps can be skipped. Instead use the template by starting a new project, loading the two images and choosing File -> Apply Template -> and browse to the saved template. If the panorama needs better alignment, add control points and run the optimizer. If it looks good already, just skip the control points and go straight to Create Panorama.

If the photos were taken with two cameras back-to-back (as opposed to a single camera on a rotating tripod head), keep in mind that there will be parallax and the panorama will have stitching errors. See Q4.13. Often it's necessary to retouch the nadir (the floor) of a spherical panorama, in order to get rid of the tripod or to remove small stitching errors. Retouching the nadir can be done in several ways; it's easiest to do the edits in cube faces images.

• Go to Tools - Convert to Cube Faces.
• Add the panorama to the Source Files list. The panorama should be in 360° x 180° equirectangular projection (a 2:1 image)
• Select: Convert to cube faces, 6 separate tiles, TIFF
• Select: Save to source image folder
• Cube face size: automatic
• Press Convert
• In the same folder as the panorama, 6 cube face images have been generated (.front.tif, .right.tif, etc). Open the file named .bottom.tif in your image editing application and retouch as needed.
• To convert the cube faces back to equirectangular: start a new PTGui project and add the 6 cube face images to it. Go straight to the Create Panorama tab and create the panorama. You'll now have the retouched panorama in a file named '...Reconstructed.tif'.

Several single shot 360° panoramic cameras exist, producing a single image containing two circular fisheye images side by side. PTGui supports several of these cameras, including the Samsung Gear 360, Xiaomi Mijia Mi Sphere, Yi 360 VR and Ricoh Theta Z1. If an image from such a camera is loaded into PTGui, PTGui will actually add the same image to the project twice, with different cropping circles and masks, positioned at -90 and +90 degrees yaw.

While this already results in a roughly stitched image, the images still need to be aligned for perfect stitching. This is due to small differences between individual cameras of the same type, resulting in different small offsets of the image circles. You only need to perform manual alignment once for each camera, the result can be stored in a template and re-used. To create the template:

• Start a new PTGui project
• Load a picture from the 360° camera. It's best to use a photo taken outside, with no objects close to the camera, to prevent parallax. PTGui will automatically load the same image twice.
• Go to the Control Points tab and add a few control points. Image 1 is the leftmost or topmost circular image; Image 2 is the right hand or bottom one. Just click once on a point in image 1, then once on the same point in image 2. It can be helpful to use the Generate Control Points Here function: Shift+drag to create a rectangle, right-click in the rectangle and choose Generate Control Points here. Often this will find control points automatically. Avoid placing control points on objects close to the camera since these will suffer from parallax.
• Optimize the project (menu Project -> Optimize). The result should be 'good' (otherwise you've probably misplaced a control point somewhere)
• Open the panorama editor (Control+E on Windows, Command+E on mac) and check the result.
• Do File | Save As Template and choose a suitable name.

For subsequent images the template can be used instead: Load a picture from the 360° camera, then do File | Apply Template and select the template created above. The images are aligned already and the panorama can be stitched by going straight to Create Panorama.

The template can also be used for batch conversion using the Batch Builder (PTGui Pro only):
 

• Tools | Batch Builder
• Click 'Detect panoramas...'
• Method: Multiple panoramas per folder with a fixed number of images
• Source folder: (select the folder containing the unstitched images)
• Image file extension: leave empty, or enter 'JPG', 'DNG' (if applicable)
• Images per panorama: 1
• Press Detect Panoramas
• Use template: (select the template you created above)
• Select 'the batch stitcher will not run Align Images'
• Press Generate Projects
• Finally, PTGui asks whether the projects should be sent to the Batch Stitcher. Press Yes and all your images will be converted.

Keep in mind that all cameras with multiple lenses will produce images with parallax. Some stitching errors will be unavoidable, especially in small rooms or with objects close to the camera. Also see: Q4.13 Sometimes it can be useful to exclude certain areas of images from having control points added to. For example clouds in the sky: these may have moved significantly between shots. Or the panoramic tripod head might be visible in the images (and it has been rotated). Any control points placed on moving objects will cause misalignments in the stitched panorama.

The control point generator in PTGui Pro ignores any red masked areas, so the solution is to go to the Mask tab (Pro version only) and paint the areas to be exluded with a red mask. Then run Align Images to generate control points. Red masked areas will also be excluded from the stitched panorama; if this is unwanted, the masks must be deleted again. To delete all masks go to the Source Images tab; press Ctrl+A (Windows) or Command+A (Mac) to select all images. Right click (or Ctrl+Click on mac) to open the context menu and select Clear Mask.

If the same masks can be re-used for future panoramas, save the project with masks to a template using File | Save Template.
Disable all automatic features of your camera, except for automatic bracketing. In particular:

• Set the camera to the 'M' mode (not the A, T or P mode)
• Lock the white balance
• Disable auto ISO adjustment (if your camera has this feature)
• Enable auto bracketing. Make sure that the camera brackets the exposure time, not the aperture or iso.
• Take a complete bracketed set of images in every direction

The 'M' mode is present on every (digital) SLR camera, but most compact cameras lack this mode, which makes them unsuitable for HDR stitching with PTGui Pro. Yes, just enter the exposure data in the Image Parameters tab. At least the exposure time should be filled in for each image; the aperture and iso fields can be left blank. Switch PTGui Pro to Advanced mode to make the Image Parameters tab visible. Most likely your camera was in automatic exposure mode when taking the images.

Please take a look at the actual exposure data (aperture, exposure time, iso) in the Image Parameters tab. Switch PTGui Pro to Advanced mode to make the Image Parameters tab visible.

For HDR, only the exposure time should be varied. The aperture and iso value of all images should be the same. Further, the exposure times of the images should follow a repeating sequence. For example: 1/25, 1/100, 1/400, 1/25, 1/100, 1/400, and so on.

If the exposure times do not follow such a repeating sequence, even though auto bracketing mode was enabled, this can only be caused by the camera being set to an automatic exposure mode. In automatic exposure mode, the camera adjusts the exposure between each set of bracketed images and as a result, the exposure times will be different in each set of bracketed images.

On SLRs, automatic exposure is enabled in the P, Av and Tv modes. Only in the M mode automatic exposure is disabled, hence the M mode is the only mode suitable for photographing HDR panoramas. Most digital compact cameras are not suitable for HDR panoramas due to the lack of a manual exposure mode. Most likely your camera was in automatic exposure mode; see Q7.3.

In general, the this problem is caused by the fact that the images do not cover the full panorama for every exposure time used. For example, if you took images at (e.g.) 1/25, 1/100 and 1/400s, then a full panorama should be taken at each of these three exposure times.

PTGui Pro groups the images by exposure time, and stitches and blends a complete panorama from each group. These blended panoramas are called 'blend planes'. Finally, the blend planes are merged to HDR and optionally tone mapped.

If an image is missing, e.g. you forgot to take one of the 1/100 images, then the resulting blend plane contains a gap. PTGui will attempt to merge the three blend planes into HDR, but the gap causes a hard edge in the result. HDR merging should not be compared with regular panoramic blending: it does not attempt to create a soft transition between overlapping images. Instead it picks the 'best' pixel data from each blend plane.

To verify that at each exposure time a full panorama is covered, enable the 'blend planes' output setting in the Create Panorama tab. Take a look at the resulting files to make sure that each blend planes covers the full panorama. You can trick PTGui into recognizing your images as bracketed exposures by modifying the exposure data in the Image Parameters tab. If you took sets of 3 bracketed exposures, copy the exposure times of the first three images into the remaining images. The result should be a repeating sequence, e.g. 1/25, 1/100, 1/400, 1/25, 1/100, 1/400, and so on. Switch PTGui Pro to Advanced mode to make the Image Parameters tab visible.

However, the result will not be perfect. The automatic exposure has caused brightness differences between neighbouring images. The blender is able to make gradual adjustments, but it does not actually correct the exposure differences. Therefore we recommend to go back and take the bracketed images in manual exposure mode.

As an alternative workaround you could take the images from only one bracket (e.g. only the 0EV images) and stitch those into a non-HDR panorama. For non-bracketed source images PTGui Pro can compensate for automatic exposure: in the HDR/Exposure tab enable the Exposure Compensation checkbox. Additionally PTGui Pro can apply tone mapping even to non-bracketed source images: enable the 'Tone map stitched panorama' checkbox in the HDR/Exposure tab. The nice thing about HDR is that you don't need to worry anymore about proper exposure! By taking bracketed exposures, everything will be exposed properly in at least one of the images (provided the bracketing range is sufficiently wide). During HDR merging, the best part of every image is used in the final merged result. Over and underexposed pixels are discarded automatically. The Exposure Value (EV) recorded in the EXIF data (in the Exif 'exposure bias' field) indicates the difference between the actual exposure and the optimum exposure as measured by the camera's light sensor. In other words, it's the exposure offset the camera was instructed to use. It is not an absolute value and does not tell the actual amount of light captured.

On the other hand, the EV shown in PTGui Pro (Image Parameters tab) is calculated from the actual exposure data (exposure time, aperture and iso). This is the data that is used when generating HDR. The EV is a relative value, which can have an arbitrary offset. PTGui Pro offsets the EV such that the lowest EV equals zero minus the highest EV (i.e.: low = -high).

A difference between the displayed EV and the recorded EV can have two reasons: If you used auto bracketing in auto exposure mode, the camera has likely adjusted the base exposure time between each set of bracketed shots. In that case the bracketed sets themselves have an exposure offset within the panorama. A second reason is the limited choices of exposure times. For a +1 EV offset from 1/15s, most cameras will use 1/8s instead of 1/7.5s. The actual offset in this case is +0.9 EV. PTGui Pro can link images. Linked images have the same yaw, pitch, roll and other parameters. When a parameter of one such image is changed, the same changes are applied to the linked images. The optimizer treats the linked images as a single image and combines all control points of the linked images.

Images can be linked and unlinked using the right-click context menu in the Source Images tab. PTGui treats a set of linked images as if they are a single image. Use the little triangle button in the Source Images tab to switch between displaying linked images as a group, or as individual images.

PTGui Pro can detect bracketed sets of images, and automatically link the images in each bracketed set. This is done by choosing 'Link HDR Bracketed Exposures' in the Images menu. For this to work, the exposure times of the images must follow a strictly repeating sequence, e.g. 1/25, 1/100, 1/400, 1/25, 1/100, 1/400, and so on. In this case, PTGui would recognize the sequence of 3 bracketed exposures each, and link each group of 3 images. If PTGui Pro doesn't recognize your bracketed exposures, the exposure times do not follow such a sequence; see Q7.3 above. If your images were taken from a sturdy tripod, with absolutely no camera movement within each bracketed set, it's best to link the exposures. This way, the bracketed images are guaranteed to be aligned with pixel accuracy. Furthermore it would not be a problem if a certain image is lacking control points, as long as the other images in the bracketed sets are linked by control points.

However, it's not necessary at all to link bracketed images. Linking only locks the image positions, PTGui Pro doesn't need linked images to create HDR. For that it only needs to know the exposure data of each image.

If the images were taken handheld, or if the camera may have moved between shots, the images should not be linked. In this case, PTGui Pro will attempt to align the images using control points. This is possible by creating a layered HDR panorama in PTGui Pro:

• In your HDR panorama project go to the Create Panorama tab
• Choose 'HDR file format: Photoshop'. Click on Settings and select Bit Depth: 32 bit, Layers: Layered
• At 'Output' enable the 'HDR panorama' component and the 'HDR blend planes' component

PTGui will create a layered document with the blended panorama in the bottom layer. On top of that are the individual blend planes. Each blend plane corresponds to the stitched panorama at one exposure level. The blend plane layers have a blend mask which is initally black. By painting with a white brush in the layer mask you can selectively reveal parts of the blend planes.

For details see the Post Processing tutorial. It's not necessary to use external applications since PTGui Pro can create HDR files. But if you prefer to use an external tool for merging to HDR, there are two ways to do this:

• First merge your bracketed source images to HDR files (.hdr or .exr format) in your external HDR application. Then load the HDR source images in PTGui. Please note that the control point generator currently is less sensitive when HDR source images are used, therefore you may need to add some control points manually.
• Or load all bracketed source images in PTGui. On the Create Panorama tab, enable only the 'Blend planes' output component (not to be confused with the 'HDR blend planes', see the online help). The blend planes can be loaded in an external application and merged to HDR

Yes, this is possible. But keep in mind that PTGui was originally designed for creating panoramas and you need to adjust some settings to make this work.

If your images were taken from a tripod and are already aligned perfectly:

1. Start a new project in PTGui Pro
2. Click on the Advanced button in the side bar to switch to Advanced mode
3. Click Load Images and open your set of bracketed images
4. Go to the Exposure / HDR tab and select 'Group bracketed images into separate blend planes'
5. Go to the Panorama Editor by pressing Ctrl+E (or Command+E on Mac)
6. Choose Edit -> Fit Panorama. On Mac choose Panorama Editor -> Edit -> Fit Panorama. Now the images should fill the entire output area.
7. Go back to the Exposure / HDR tab. Choose whether you want to use Exposure Fusion or True HDR and adjust the settings. See the online help for more information.
8. If necessary adjust the output settings in the Create Panorama tab
9. Finally press Create Panorama to render the output files

If your images were taken handheld they need to be aligned first. Proceed as follows:

1. Start a new project in PTGui Pro
2. Click on the Advanced button in the side bar to switch to Advanced mode
3. Click Load Images and open your set of bracketed images
4. Choose Control Points -> Generate Control Points
5. Go to the Optimizer tab. Disable 'Optimize lens focal length' and select 'Minimize lens distortion: No'
6. Press the Run Optimizer button at the bottom. This aligns your images.
7. Proceed with step 4. in the above paragraph

You can save the project as a template using File -> Save as Template. The template can be used again (by choosing File -> Apply Template) for subsequent projects with the same setup (i.e. the same number of brackets, same camera and same lens). If the images are taken handheld, control points need to be generated for each project: repeat the steps 4-7 after the template has been applied. Yes this is possible, but there is no benefit in doing so. The purpose of generating HDR images is to overcome the limited dynamic range of a camera's imaging sensor. Suppose you are photographing a scene with both very dark objects and very bright objects: the dark objects will be close to the sensor's noise level: if you attempt to reveal dark objects by brightening the image in (e.g.) Photoshop, the noise will be amplified too so the dark objects will drown in image noise. Similarly, bright objects may be brighter than the maximum brightness that can be recorded by the sensor and thus completely white (this is called 'clipping'); darkening the photo will not reveal bright clipped objects anymore. To overcome this you take multiple photos of the same scene at different exposure levels. The HDR software (PTGui Pro) will take the 'best' pixels from all photos, i.e. those pixels that are not noisy and not clipped.

It's possible to do 'pseudo HDR' by extracting multiple exposures from a single RAW image, but all exposures will still suffer from the same limited dynamic range of the original RAW image. Hence the brighter exposure will be noisy and the darker exposure will not reveal any detail that was clipped. If you assemble these exposures again into an HDR image you will just end up with an image identical to the original RAW file, only in a different format.

Typically a RAW image has a dynamic range of 12 or 14 bits. No detail will be lost if you convert the RAW image to a 16 bit TIFF file as long as you make sure that no highlights are clipped. I.e. make the TIFF file dark enough until you see as much detail in bright objects as is available in the RAW file. Then stitch those TIFF files in PTGui.

Don't confuse HDR and tone mapping: what is typically referred to as the 'HDR look' is actually the result of tone mapping. You don't need bracketed images in order to do tone mapping; in PTGui Pro go to the Exposure/HDR tab and enable the 'Tone Map Stitched Panorama' checkbox. When generating HDR images PTGui will look at the exposure settings in the EXIF data of the images to determine which images belong to a bracketed set. Normally the camera sets the proper exposure data in the EXIF header, but when extracting multiple images at different brightness from a single RAW file, all images will still carry the original EXIF data despite the difference in exposure.

To overcome this you need to override the the EXIF exposure data in the Image Parameters tab in PTGui Pro. For example if your original image was taken at a shutter speed of 1/200s but the exposure was boosted by +1EV this effecticely simulates an exposure of 1/100s. EV is a logarithmic scale: +1EV corresponds to a doubling of exposure time; +2EV is a quadrupling of the exposure time, +3EV multiplies the exposure time by 8, and so on.

Once you have entered the artificial exposure times for all images in the Exposure column in the Image Parameters tab, PTGui Pro should recognize your bracketed images if you do Images -> Link HDR Bracketed Exposures.
To use GPU accelerated stitching a graphics card supporting OpenCL 1.1 is required. Do not confuse OpenGL and OpenCL, they are different technologies. PTGui requires 512 MB of graphics RAM but at least 2GB is recommended and will result in faster stitching.

GPU stitching is optional, a supported GPU is not required for running PTGui. If no suitable GPU is found PTGui will be fully functional, it just means that the CPU will be used for stitching.

Windows

• NVIDIA cards: no known issues. Install the latest driver.
  Download NVIDIA drivers here.
• AMD cards: no known issues. Install the latest driver.
  Download AMD drivers here.
• Intel integrated graphics: Not supported

Apple Mac
A mac with a dedicated AMD or NVIDIA GPU is required. Many models only have Intel integrated graphics (Intel Iris or HD Graphics); this is not supported for GPU acceleraton by PTGui. OpenCL 1.1 is required, Mac models released before 2010 only have OpenCL 1.0.

There's a known problem causing occasional random image corruption under macOS 10.14 (Mojave). This appears to be caused by a bug in Apple's OpenCL implementation but we haven't been able to narrow down the problem. If this happens, disable GPU acceleration in PTGui and render the panorama again. GPU acceleration worked without problems under macOS 10.13 (High Sierra).

Unfortunately Apple have decided to deprecate OpenCL. While it is still supported in current macOS versions, Apple may decide to remove OpenCL from future macOS versions. This means that PTGui's GPU acceleration may no longer be available under some future macOS version. Apple is suggesting that developers rewrite their software to support Apple's proprietary Metal framework but this involves a huge amount of work. We can't say if or when PTGui will support Metal-based GPU acceleration.

Again, GPU acceleration is completely optional, it only serves to speed up the rendering of panoramas. When looking for a GPU to upgrade your Windows desktop computer the following factors are relevant:

• Brand: PTGui supports cards with chipsets from AMD and NVIDIA, from any manufacturer.
• Video memory: get a card with at least 2GB of memory (but also see (NOTFOUND))
• Memory speed: Currently cards are offered with DDR3 or GDDR5 memory. The latter is faster. Another factor is memory bus width: a 256 bits memory bus can transfer double the amount of data compared to bus a 128 bits wide.
• Number of processors: on AMD cards this metric is called 'Stream Processors', NVIDIA calls this 'CUDA Cores'. More is better.
• 'gaming' GPU vs 'workstation' GPU: besides their regular graphics cards both chipset manufactures offer a range of Workstation GPUs: NVIDIA offers Quadro and Tesla cards and AMD have their FirePro cards. The workstation cards are said to be more stable and suitable for 24/7 usage. They also have higher 'double floating point' performance but this is not used by PTGui. From our experience a regular consumer/gaming GPU will work just as well and the price/performance ratio is much better.

A detailed overview of GPU chipsets can be found on Wikipedia:
List of Nvidia graphics processing units
List of AMD graphics processing units

A basic guideline would be to get a recent NVIDIA or AMD card with 4 GB of GDDR5 memory and as many CUDA Cores or Stream Processors as your budget allows.

Note that other components of the computer are just as important: in particular be sure to have enough RAM installed (16 GB or 32 GB for larger panoramas), and use SSD drives instead of spinning hard disks for temporary storage, input and output images. No, PTGui will only use one OpenCL device for GPU accelerated stitching. Also, linking multiple graphics cards via NVIDIA's SLI or AMD CrossFireX will not work: the cards will still appear as two separate OpenCL devices to the system. Under some circumstances the NVIDIA GPU driver may become installed with OpenCL support missing. We haven't figured out why or how this happens, but it can be resolved by performing a clean installation of the latest NVIDIA GPU driver. This can be done as follows:

• Go to NVIDIA driver downloads and select your GPU model and Windows version.
• Run the downloaded installer
• After the System Check has completed, select 'NVIDIA Graphics Driver'. Geforce Experience is optional but not required.
• Installation options: choose Custom (Advanced) and press Next
• Under Custom installation options 'Graphics Driver' must be selected. Also 'Perform a clean installation' must be selected. The other options can be selected but they are not needed by PTGui.
• Press Next to install the driver.

After restarting PTGui, your GPU should be visible under Advanced - GPU Acceleration.