![]() Out of the whole process (with the exception of one or two of my panos), I find that actually stitching the image together, colour corrections (etc.), and sharpening take much more time than dealing with errors in the panos (that said, my computer is fairly slow and I only have a 1.25 gig of ram.). Once I find them, I can simply import one or two of the warped images into the pano and in a minute or two, mask out the offending misalignment). What I end up finding difficult is finding the bloody errory/misalignments after I've used Enblend or Smartblend. Just give either of them a shot yourself (PTAssembler has become almost completely automated and for about 90% of my images, I don't have to play with any of the stitching parameters.), play around with one or two smaller panos, play around with editing the output from one or two panos where you have stitching problems (ie, reroute the seams so that you can't see them), and then you'll better be able to see how these programs fit into your needs and how well they can work with just a little additional user input (yes stitching 103 images together is time consuming, but so far, in my experience, rerouting the seams isn't that difficult. IMHO, if you'd spend one quarter to half of the time you've spent reading and posting in this thread, you would likely have already figured out/mastered how to use PTAssembler or PTGui (along with the accompanying programs like Autopano (the control point generating program, not the complete stitching software) and Enblend/Smartblend) to get better results than you've been getting and could probably have generated (and fixed (just by rerouting seams in PS), if there were any huge problems) a pano or two. The point of the story is, if I'd had to spend hours doing manual adjustments prior to rendering these images, I'd be tearing my hair out by now. However, after opening in CS2 the file size diminishes to 1.77GB. This 4th attempt has worked fine, but oddly enough the finished file size is shown as 4.73GB. Anyway, I couldn't find a way of opening the file so I had to begin the rendering again, a fourth time, selecting the PSB format and being very sure I specified 8 bit. I'm sure I clicked on the 8 bit option before rendering but for some reason the saved TIFF file was 4.11GB which appeared to be 16 bit, or maybe that's due to the alpha channel. I therefore felt safe in using the TIFF file format which has a size limit of 4Gb. I'd calculated that 103 x 24MB images should not be larger than 2.5GB at most. However, the third obstacle was the file size. There was no power cut and the stitched, rendered file seem to have been saved okay. I'm connected to a UPS and the computer shut down nicely, but I had to start the rendering a third time when the power came back on. There was a bit of thunder and lightning and the usual power cut. The second obstacle occurred about 4 hours into the rendering. I had to close the program, after renaming the path of the temporary folder, and start again. ![]() ![]() When I attempted to render the image (after it took an hour or so for the preview to be created) I got a message to the effect that my hard drive had only 24Gb of free space when 44GB was required. The first obstacle was a lack of space on the hard drive I had allocated for the temporary scratch folder. Because the process was automatic, it didn't worry me too much when things didn't go quite to plan. ![]() I recently tried stitching with Autopano 103 images taken with my 20D, 3 rows of 33-35 images. I've now put it all back on, sitting in front of the computer, processing images and chatting to people on LL.īefore getting Autopano I was fearful of the effect that even more time sitting in front of the computer would do to my overweight situation, especially with huge 100 image projects.
0 Comments
Leave a Reply. |