Sharing knowledge around Autopano
You are not logged in.
Well APP can't seem to work with a special set of images. I suppose it is okay that APP can't do it as PT Gui can't seem to digest the images either. This includes replacing all the control points with (correct) ones.
Why I can't do this manually in either PTGui or APP is the reason why I'm posting.
One of the pics of the inside of the Texas State Capitol.
I can understand why APP would do this on the first attempt as the images are very very similar.
The larger images are here:
http://images.weaver.net/gallery/5495554_pQjKZ
All shot with a D300, Sigma 8mm, on a Nodal Ninja setup.
Suggestions?
Thanks,
David Weaver
Austin, TX
Offline
1- Added images to a new group
2- two images didnt have any exif data so I clicked on Image Properties in the main APP window and made sure all were set to 8.0mm lens type: fisheye
3- I adjusted the circle cropping
3- ran detection (high, 100, strong alg., adjust lens distortion, advanced distortion), wasnt happy with the result
4- removed all nadir/zenith shots (this sometimes allegedly helps), redid step 3, still bad result.
5- conclusion: the panorama turns out bad because of the identical architecture. Wall features found in completely opposite ends of the chamber were detected as a match with a very low RMS. Solution: do it yourself. I deleted APP's CPs and selected common features myself for each image pair (6 images, each has 2 links), optimized, great stitch.
7- added nadir and zenith to the pano
8- position nadir and zenith using move tool
9- tried adding CPs between the zenith/nadir shots and the rest, but I could not create ANY cps, probably because these two imported photos somehow didnt fit in with the rest (they probably werent being detected as fisheye), so i deleted them.
10- created a new pano with just the nadir and zenith, made sure both were detected as fisheye, detected the pano, saved as zenad.pano
11- back in the main pano, i clicked File > Merge Panorama and merged zenad.pano with the main one. Moved zenith/nadir into first layer.
12- now i could place CPs between zenith/nadir and the other shots, so I did just that, linking the "REPUBLIC" text in the nadir to the same text in image _04.
13- ran local optimise on nadir, voila, positioned wonderfully.
14- did the same for zenith - first get it into position by manually placing CPs and then local optimize.
15- ran local geometric analysis on both zenith and nadir (to link them to all other pictures), local optimise on both.
16- rendered.
Life would have probably been easier if I hadn't removed the nadir and zenith in the beginning.
The zenith and nadir shots introduced some misalignment issues, so for a better result I suggest you render two layers - 1 with the 6 main shots around, and 1 with just the nadir and zenith, and combine them manually in your image editor.
I feel pity for anyone wanting to shoot a panorama in that chamber using a non-fisheye lens and having to manually link them afterwards...
Last edited by DrSlony (2008-07-22 06:20:32)
Offline
The main problem: GIGO ![]()
Problems:
1. zenith photo does not seem to have EXIF, so you have to tell APP its an 8mm fisheye lens.
2. images are very soft
3. images are very noisy
4. 5 of the 8 images are linked to 7 other images, the remaining 3 images only link to 6 other images--too many bad links, probably due to the noise.
Looks like you shot at ISO 400, f/8, 1/15, then pushed it a stop in PS, then increased brightness and otherwise manipulated the images, then sharpened the images _and_ the noise. I'm surprised, I would have thought the D300 had less noise than that at ISO 400.
A little work in the CP editor gives a fair result, which may be able to be improved.
Offline
Hi Maciek,
I disagree with your findings above, I think the issue is noise. The architecture is not identical--the doors are different, the pictures on the wall are probably different (they're too blurry to tell), and the shadows are different. Also, the stone will have many slightly different details that APP can pick up but we can't. but there's too much noise fthat APP picks up, and the walls are too OOF for the differences to be seen.
I aproached this in a different way:
1. eliminate all links except from nadir to images (may have left the vertex links in). The floor is pretty well in focus, and is unique. Its easy to set CPs on (for example) the "T" in Texas.
2. Then optimize
3. form links between adjacent images on the "equator" of the pano.
4. optimize
5. add in any links to the vertex -- not really needed, but nice to have
6. optimize
7. remove bad links from vertex.
If this was shot with an 8mm at f/8 on a 1.5 crop, the DOF should be huge! The hyperfocal distance is 1.34 feet, and if you use a distance of 4 feet, everything from 1 foot to infinity should be in focus.
Offline
Take home messages seem to be:
1. Don't pre-process images in a manner that strips the EXIF data.
2. Get the exposure and focus right when shooting.
3. IMO this is a good example of where you'd have been better off shooting the zenith at say +60 rather than +90 to get an easier link between than main row and the zenith.
4. Alternatively tilt up about 15 degrees (?) to shoot the main row so that you don't need a zenith shot because the main row will provide enough overlap without one.
5. Use the text and badges above to set CPs manually to link the main row images and the main row tro the nadir image.
I found it very tricky to get decent links between your zenith shot and the main row.
Do you really need 6-around in the main row when shooting with a D300 and Sigma 8mm FE - I thought 4-around would provide 360 coverage?
If I was shooting the scene with my D40 and Sigma 8mm on NN5 head I'd shoot 4-around at +5 and one up at +60 (possibly two up, each located to show a distinctive doorway) - this would leave 'hole' at the nadir slightly smaller than the central rotator. If you then want to shoot a nadir you can patch it in after stitching. I'd not bother and either limit FOV on the player or place a cap at the nadir.
How did you shoot/produce the nadir image with having yourself in the shot - perhaps it is already heavily post-processed?
Anyway, you can download my best effort (so far) from here, not perfect but quite good IMO, this is straight from APP with no post-processing:
http://www.three60views.org.uk/images/t … e_pano.jpg
And here's what the links looked like prior to rendering using Spline36 interpolator and Smartblend.
Last edited by mediavets (2008-07-22 16:06:49)
Offline
hankkarl I agree with you, but I also stick with what I wrote because I have proof! hehehe. No I deleted the proof once I posted that, but I did have images linking one feature with another feature that was in fact on the opposite end of the room. Why? Well I agree here that its because of GIGO - noise and lack of sharpness. I really wonder whether, if they were noise-free and sharp, would sift would see a difference between these features? Perhaps a good place to put sift to the test!
Offline
Here's my best effort as a 360x180 Flash VR - reduced size, adjusted levels, despecekled and sharpened a little after stitching, then Flash VR produced Pano2VR.
It is not perfect but it's not too bad IMO, considering the initial image set:
http://www.three60views.org.uk/texas_ca … _6k3k.html
Offline
Wow! Great words of pano wisdom!
Fortunately I can reshoot this easily.
I'll try for sharper images. This time I'll take a cable release. I know I should have done this but I wasn't actually planning on panos that day - I was killing time. :-)
I'll shoot a set like this and another set at 15 degrees up.
I shoot 8 around to give me more flexibility in keeping people in and out of frames. I will post new new pics and results back here soon.
Offline
Great! also make sure you expose to the right and don't sharpen or otherwise post process.
Experiment with smaller apertures, like f/11 or f/13 or even f/16 -- you are balancing DOF and diffraction. While the calculator I used said "big DOF", DOF is more complex and there's no easy answer. Also, SIFT is by nature a "pixel peeper", so every pixel has to be good.
Experiment with focus distance--
1. try getting the near edge of the DOF to about as high your lens is off the ground, or even 50% further than that.
2. try setting the focus distance to about 1/3 of the distance between you and the walls.
HDR may be useful here. Meter outside for the f/stop you will use and remember the speed. Take one circle with that setting to get the doors right. Then shoot inside with AEB. Use PM or other HDR program to merge the images, but lie to it--tell it the shot metered for outside is 0EV, and one of the AEB shots is 0EV. Or use tufuse.
Last edited by hankkarl (2008-07-22 18:28:06)
Offline
DrSlony wrote:
hankkarl I agree with you, but I also stick with what I wrote because I have proof! hehehe. No I deleted the proof once I posted that, but I did have images linking one feature with another feature that was in fact on the opposite end of the room. Why? Well I agree here that its because of GIGO - noise and lack of sharpness. I really wonder whether, if they were noise-free and sharp, would sift would see a difference between these features? Perhaps a good place to put sift to the test!
It will be interesting. I've seen the "repeated feature" issue with vinyl siding (the woodgrain pattern repeats).
I'm guessing that whoever cut the stone in the OPs picture didn't get each feature exactly the same, but if the resolution is not so good, they may look the same to SIFT. This may be a case where a 360x180 done with a 50mm lens would be easier to stitch -- you can focus on the walls and use a different focal distance on the floor.
Brings up a thought--the OP may want to make one circle at 0 degrees pitch and focus on the walls, and another at -45 degrees or so and focus for the floor, then let smartblend decide which is better.
Offline
davidweaver wrote:
Wow! Great words of pano wisdom!
Fortunately I can reshoot this easily.
I'll try for sharper images. This time I'll take a cable release. I know I should have done this but I wasn't actually planning on panos that day - I was killing time. :-).
I don't think the lack of sharpness is anything to do with not using a cable release/remote control. It is much more likely that the focus was set wrong on the Sigma 8mm. Are you using autofiocus? If so, don't. Use manual focus and don't set it on the infinity mark either. You'll find lots on the Panoguide.com forum via forum search about manually focusing the Sigma 8mm FE.
And do your best to get the expsoure right when shooting so there's no need to preprocess sthe images - are you shooting RAW or JPEG?
davidweaver wrote:
I'll shoot a set like this and another set at 15 degrees up..
Not sure 15 degrees is 'the magic number' - when I mentioned +15 I was thinking you were shooting with a Canon body, which doesn't produce a full 180 VFOV with the Sigma 8mm.
+5 will give a small overlap at the zenith on a Nikon DX body so I doubt you need as much as +15.
But anyway do try shooting the 'zenith' at an angle much less that +90. At + 60 you will get very good zenith coverage and the goal is to get an easier link between the 'zenith' shot and the main row - so try and take these lower angle 'zenith shots' where some readily identifiable feature will appear in the overlap of both a 'zenith' shot and a main row shot. I'd probably choose the doorway with the clock?
To get the feel/idea of this before trainling back to the State capitol building, just pop outside and shoot 4-around at +5 and one up at +60 and stitch it with APP - you can then see how it works and visualise the ovelaps using the layer tool in the Pano Editor by selecting all the images with Cnrtl-click. See screenshots below of a quick shoot in the garden using either two or one 'zenith' at +60, and 4-around main row at +5.
davidweaver wrote:
I shoot 8 around to give me more flexibility in keeping people in and out of frames. I will post new new pics and results back here soon.
8-around if all stitched will have massive overlaps and could result in a lot of superfluous/spurious links with auto CP detection and which may reduce stitch accuracy. Or perhaps you meant 4-around twice? Smartblend usually does a pretty good job with 'ghosts' anyway.
You'll probably always have to set CPs manually with this sort of scene which has a lot of repetition of architectural features which will confuse most automatic CP detection systems.
Last edited by mediavets (2008-07-22 18:59:36)
Offline