The red X indicates that at a later time the image was not used to create the final panorama.Ī look at the PTGui derived control points between #35 and #37 shows several cloud matchesĪfter telling PTGui to not include #33 in the panorama and at a later time adding some 180 pano images to straighten out other minor regions to the right of the #33-#37 mismatch, a good horizon was obtained. Several horizon 'horizontal line' control points were added to the image overlap region. There were no control points found between #33 and #37 by PTGui PTGui has a zoomable detail viewer to focus on the mismatch area between #33 and #37) Note that the internal image sequence numbers of the mismatch can be viewed and that the highest image sequence number in the panorama is 46 Here is the PTGui of the 46 image sphere. Here is the ICE (Microsoft's Image Composite Editor) panorama of the 46 image sphere My experiences as a newcomer to PTGui (paid version). I like the program needless to say.Fixing a 360sphere from Spark with PTGui. I have no clue how the stretching/blending/magic worked but somehow it gave me a clean file without any artifacts. For whatever reason, I don't remember, I put both the close up photos and the further away photos both into AutoPano pro and voila, it stitched them together and gave me the RUSH picture. I took a photo of the waterfall closer to it, and then went to an entirely new location further away and took some more photos of it. The photo I took called "RUSH" on my website of Snoqualmie Falls in WA was all done using AutoPano Pro. One time I was utterly blown away by the program and I will tell you what I did. Not sure if this is the best thing to do but I have had good results using Autopano Pro. I then stitch the TIFF files using autopano pro and then import them back into C1 or LR depending on the situation. I usually do minor tweaking on the photos in C1 including applying any LCC. I would consider both of them, along with CC.Īll of my work was done using AutoPano Pro. But most times I get a clean one the first time. I just finished what I though would be a simple 3 part from a 15mm L C and 15mm R stitch, that I ended up having to use both tools to finally get a good solution. Autopano has a nice video guide that can help. You will find a ton of control features in both Autopano and PTgui, none in CC, Both tools I feel would benefit from a better user guide, but I have basically learned by trial and error. Solid blue skies with a lot of gradient to the sky will be the most problematic, and PTGui works very well here.Īll 3 work fine on 16 bit images (but CC can bog down on multilayer stitches in 16 bit for me) I am windows based all 64 bit. Where as both PTGui and Autopano make a lot of upgrades.Įxposure blending again I often will have to work with all three at times to find one tool that gets the best solution. CC's engine is pretty much the same as CS5, I see no changes or differences in results between all of them. They also work much better on multi-layer stitches, like 6 ot 9 shots, where CC seems to both get bogged down and lost at times. PTGUI and Autopano work better on nodal pans, as they give you a lot more solutions to pick from. With nodal pans from a tech camera, the wider the lens, the less likely CC will get a good solution even with a pretty good nodal placement. I have found that most inline stitching CC will do fine, but there are certain times where I have a lot of color shifting even with the LCC correction in C1, (mainly with the 40mm Rod and blue skies), where I can't get a good blend with CC, especially if I had a CLPL on. I seems that both companies are not looking much at the Phase One files when writing the programs. But both tools allow for an easy way to input the data when needed. But even PTgui seems to have problems seeing all the focal data, from a tech camera, since the lens info is missing and PTgui will ask for the sensor size sometimes and other times it sees it correctly. I use both autopano Pro (Kolor) and PTgui, along with CC for stitching with P1 files.Īutopano will have problems with the exif info, as for some reason, C1 does not export it the way it's needed by Autopano Pro, PTGUI seems OK.
0 Comments
Leave a Reply. |