Panoramic Photography Services in the Austin, TX Area
Writing the HTML
This is a basic example of how to add HTML code to your web page that will send a .mov file to the PangeaVR plug-in for viewing:
<embed PLUGINSPAGE = "http://www.pangeasoft.net/pano/plugin/downloads.html" src="thepano.qtvr" type="graphics/pangeavr2" width="99%" height="90%">
The required parameters are:
The optional parameters are:
Below is a sample panorama with the following HTML code:
<embed pluginspage="http://www.pangeasoft.net/pano/plugin/downloads.html" height="396" src="files/thepano.qtvr" type="application/pangeavr" width="560" COMPRESSION="true" CONTROLLER="true" FOV="70" PAN="45" TILT="45" DRAGFRICTION="true" TEXT="Guest Bedroom" FONTSIZE="20" THUMBNAIL="thumb.jpg">
About using Texture Compression
Compressing textures adds significant time to the loading of the panorama (over 7 seconds for a hi-rez file on a dual 2ghz G5, 15 seconds on a 1.25ghz Powerbook G4). The benefit to using compression, however, is that your pano images will retain their resolution when viewed on video cards with low VRAM. It also frees up some VRAM for other applications running concurrently.
This is a lossy compression, so the image quality does degrade. It is very noticable in smooth areas or dark gradients such as sky or flat walls. Detailed panos don't show the degredation much, so it's best to use it only on panos with lots of detail. Panos with very low detail or lots of sky may not look good with compression, so you should probably keep it turned off in those cases. This problem is very apparent in the example pano above where the dark walls have banding artifacts. This is definitely a worst-case example, so you should experiment with your own pano's to see what results you get.
Note that starting in version 1.1 of PangeaVR, the user has the option to override your compression settings in their PangeaVR Preferences dialog, but you should still set this to your desired setting since the default behavior of the plug-in is to use the HTML's compression setting.
Limits of the QTVR .mov files
1. PangeaVR only reads Cubic QTVR movie files. It won't work with any other format such as cylindrical.
2. Images in the .mov files must be JPEG. Any other format, such as TIFF or PNG may cause the plug-in to crash.
3. The headers must NOT be compressed. PangeaVR cannot parse header data that has been compressed.
5. If your file is named with the .mov or .qt extension then the web browser will automatically use Quicktime to show the panorama if PangeaVR is not installed. You may or may not want this behavior. If you want the web browser to tell the visitor that they need the PangeaVR plug-in, then rename the file with a different extension, such as ".qtvr".
The images in your cubic QTVR files can be any size that you want. PangeaVR intelligently determines what the largest allowed image size is based on each visitor's video hardware specs. The COMPRESSION tag described above will help retain the original resolution at the cost of a longer load time. Generally speaking, however, your hi-rez QTVR .mov files should follow these rules for optimal load times:
1. Avoid tiled images. This only increases the .mov file size and increases load and decompression times. It does not add any benefit to PangeaVR.
2. Avoid fast-start tracks. These also just add to the .mov file size and are ignored by PangeaVR anyway.
3. Cube face images that are a power of 2 in size will load faster; such as: 512x512, 1024x1024, 2048x2048.
4. Since most 3D hardware only supports textures up to 2048x2048, having cube faces larger than that only causes PangeaVR to shrink them down. Additionally, anything larger than that really isn't going to make any visual difference since even a 23" Cinema Display at 1920x1200 resolution cannot show all those pixels when the FOV is set to a normal value. Higher resolutions only help when you zoom in a long way.
Limits of the Equirectangular JPEG files
1. The files must have the .jpg or .jpeg file extension (can be upper-case).
2. These must be full 360º x 180º equirectangular images. Partial panos will not work - they won't crash or anything, but they won't display properly.
3. PangeaVR chops the equirectangular images into 8 textures for OpenGL to use (4 across and 2 down). Generally, the maximum texture size that most 3D hardware can render is 2048x2048. Doing the math: 2048 * 4 = 8192 tells us that the largest practical pano resolution is 8192 x 4096. It takes a lot of VRAM to store that much pixel data, so not every computer will be able to display the pano at full resolution. Odds are the textures will get reduced just as they do when loading QuickTime movie files, however, equirectangular panos will usually render at higher resolutions that cubic QTVR panos. Not always, but usually - it depends on the amount of VRAM available and the size of the pano JPEG image.
Limits of the Thumbnail JPEG images
1. You should keep these thumbnail images as small in file size as possible so that they load very quickly. Try to keep them under 20k.
2. The files MUST be 512x512, 512x256, 256x256 or 256x128 in size. Any other size simply won't show up. It won't crash, but you won't see the thumbnail.
3. The JPEG filename is relative to the pano file's directory, so you do not need to specify a full path if the file is in the same directory as the pano. See example above.
To send feedback or get information: firstname.lastname@example.org
©2010 Pangea Software, Inc.