Log In now to add this Gigapan to a group gallery.
Log In now to add this Gigapan to a gallery.
About This GigapanToggle
- Taken by
- Wim Koornneef
- Explore score
- 1.62 Gigapixels
- Date added
- Sep 26, 2011
- Date taken
- Aug 06, 2008
The 396 JPEG images for this image where shot in 2008 by Traugott Emrich (*) with his GigaPanBot, Olympus E-520 camera, a 80-300mm lens with 2x extender (effectively 600 mm !) when we attended the PanoTools Meeting in 2008 in Prague. (*) Traugott shot the images on my request and used one of my memory cards in his camera.
Some image specs:
Exposure Time: 1/640 sec
Exposure Program: Manual
ISO Speed Rating: 200
Image Width: 3648
Image Height: 2736
Back in 2008 I only stitched and published a small Zoomifyed version without the top row images because I didn't want to manualy position the 69 images with only sky and I reduced the size because I didn't want to wait for days until the images where stitched on my old iMac G5.
In september 2011 I decided to make a full size gigapan to test a faster and better PTGui 9.1b3 with its new "align to grid" option for aligning the sky images and this time I stitched the images with PTStitcherNG 0.7b using the "content aware" option.
The speed of PTStitcherNG is amazingly fast, running on a iMac from 2009 the stitch was finished within 25 minutes !
The test was a success and for me the combo of PTGui 9.1 and PTStitcherNG (*) for stitching gigapans really rocks.
(*) I had to limit the output size to 2 gpx, on my system (iMac intel, 4 GB RAM, OSX10.6.8) I got blending and filesize issues with PTStitcherNG 0.7b with any output size over 2gpx.
Cropping the 6.1 GB BigTiff file in Photoshop CS4 and saving the image in the .PSB big image format took a lot more time then stitching the 396 images, it is defenitely no fun to work with gigapans in Photoshop on consumer computers :-(
Processing the .PSB file and uploading the tiles with the Gigapan uploader (version 1.2.0086) was a bit troublesome, after 2+ hours, with only 12 minutes to go, the app crashed for no reason, luckily a second processing+upload was more succesfull...