Sharing knowledge around Autopano
You are not logged in.
Hi Everybody,
I post here a sticky thread to get some images that are hard to stitch in control point editor. I mean, pictures that obviously have some part in common but even with detection quality settings set to high, APP isn't able to find a relation. I remember one pair of pictures from a rocket where the iron structure wasn't recognized, but that's quite all. So if you have some cases that meet those criterion, please get back to me :
- 2 pictures
- no relation found even with high detection quality in control point editor
Thanks.
Offline
I think these two images meet those criterion.
Offline
Alexandre, you call sounds like "I have a solution but I'm still searching for a problem it could solve" !
More seriously, I have examples similar to lc8b105's example but I'm not sure this is what you are calling for. Are you interested in fisheye images where CPs can't be added (probably because they are near the zenith or the nadir?)
Offline
Hi Alexandre!
here we are: . . . . well, the upload-slots didn´t work. Both are under the size limits.
I´ll put it on my server.

best, Klaus
Last edited by klausesser (2008-03-01 13:50:19)
Offline
I have a set of pictures that Im stying but they come out wavy. They are a series of shots of moss growing on bricks, and after stitching the bricks are curved in several places, using the verticals tool doesnt help. 16 images. Should I upload to ftp?
Offline
Yes, please.
Offline
Hi,
Here some examples. This is original images.
If you need more, I have dozen of such examples like this one. (with no control point even at maximum detection.)
http://kalain.pierre.free.fr/autopano/DSC_7157.JPG http://kalain.pierre.free.fr/autopano/DSC_7158.JPG
Good luck.
Last edited by kalain (2008-04-11 11:43:16)
Offline
kalain it would be better if you'd edit that post and put those image URLs into
[url][/url]
, that way they won't load every time someone just looks at this page and you won't have to pay for wasted bandwidth.
Last edited by DrSlony (2008-03-12 16:58:01)
Offline
AlexandreJ I uploaded it into /incoming, its a file called 20080225 belgium moss.zip
They weren't shot using a rail and a dolly, so there is some user error there, but I dont think it should be impossible to stitch and keep the bricks flat. I stacked the original photos in gimp and cropped out the center parts, the files I uploaded are those center parts. I did that to minimize parallax, since this is supposed to look like an orthogonal projection. I set focal length to 1000mm when detecting.
Offline
To hankkarl, yes, it's interesting me not really for this thread, but for another research topic.
This thread is more to improve 2 pictures CP creation : improved SIFT, new kind of CP, etc.
Offline
OK, they are on their way. The images were taken at Kennedy Space Center's Rocket Garden. The sun was bright, and I stood in the shadow of a rocket for each pano. One pano is a 360 x 180, the other is a 360 x 90, the top half of a sphere (who needs lots of pictures of the sidewalk?)
To see what I did with APP and a lot of editing go to http://www.hankkarl.com/KennedySpaceCen … enter.html and click on one of the top two links. Note that I used HDView (Sorry to all the Mac and Linux guys).
The mistake I made was to make the circle centered on my feet rather than the NPP. I went round in a circle, then changed rows. Also, I didn't pay much attention to keeping the NPP at the same height. So there is a lot of parallax.
Offline
AlexandreJ wrote:
This thread is more to improve 2 pictures CP creation : improved SIFT, new kind of CP, etc.
24 mm equivalent: http://a.img-dpreview.com/lensreviews/o … ov-001.jpg
28 mm equivalent: http://a.img-dpreview.com/lensreviews/o … ov-001.jpg
84 mm equivalent: http://a.img-dpreview.com/lensreviews/o … mm-aov.jpg
J'ai trouvé l'expérience qui consiste à assembler ces photos 2 à deux intéressante...
En plus, le test effectué sur deux exemplaires de l'objectif objectif 12-60 mm pour mesurer à 12 mm (équivalent 24 mm) le non alignement de l'axe du capteur et de l'objectif est suffisamment rare pour être intéressant :
http://www.dpreview.com/lensreviews/
Lens axis offset angle
One issue we did observe during the course of these tests (and a reason for requesting a second sample) was that the lenses did not project an image of what was precisely in front of the camera, but instead apparently pointed off at a slight angle. The practical effect of this was that we had to move the camera slightly out of line with the centre of our test charts in order to obtain a symmetric image; and by measuring this displacement could determine an apparent ‘offset angle’. The effect is largest at the widest angle setting, so this is the figure we report.
[...]
the numbers we report should therefore be taken as representative only of the sample(s) we have tested.
[...]
The measured lens axis offset angles at 12mm were approximately 1.3° and 0.9° for the two samples tested.
Offline
DrSlony wrote:
kalain it would be better if you'd edit that post and put those image URLs into
Code:
[url][/url], that way they won't load every time someone just looks at this page and you won't have to pay for wasted bandwidth.
Well, that 's what I did (with ).
I tried also without , but seems to behave in the same way. ![]()
So, I just puted in 'code'.
I'm not sure to really understand all edition possibility....![]()
Offline
Hi there!
I just finished a pano that was fun to shoot and hell to stitch. Neither Autopano Pro nor Hugin could do anything useful with it in automatic mode. In the end I had to set all the control points manually in hugin (it would be nice if I could do that in Autopano Pro) and then create the pano with Autopano Pro.
I'm not sure if it fits in this category, though. The reason? The place! I took the photos under the Eiffel Tower. Right in the middle. I guess the stitchers got really confused with four pillars all looking exactly the same...
You can see an early version (photoshopping yet to come) at http://dreiwolf.eu/fotos/Eiffeltower.mov.
I'm uploading the photos (40 of them, converted to jpg) to http://dreiwolf.eu/fotos/Eiffelturm.zip right now. Should be ready in a few minutes, if you need them.
Regards,
Christian
Offline
Tipjip wrote:
reason? The place! I took the photos under the Eiffel Tower. Right in the middle. I guess the stitchers got really confused with four pillars all looking exactly the same...
You can see an early version (photoshopping yet to come) at http://dreiwolf.eu/fotos/Eiffeltower.mov.
I'm uploading the photos (40 of them, converted to jpg) to http://dreiwolf.eu/fotos/Eiffelturm.zip right now. Should be ready in a few minutes, if you need them.
Regards,
Christian
I reckon this scene was always going to be very difficult to stitch when shot with a lens as long as this.
If you knew (from your pano head) the Yaw, Pitch and Roll data for your images manually entering that data may have been an alternative approach?
I think there are 42 images in your zipped set?
Offline
mediavets wrote:
I reckon this scene was always going to be very difficult to stitch when shot with a lens as long as this.
Still saving for that fisheye lens...
mediavets wrote:
If you knew (from your pano head) the Yaw, Pitch and Roll data for your images manually entering that data may have been an alternative approach?
I'm doing that if a few images don't align well, not sure if it would work for the whole pano.
mediavets wrote:
I think there are 42 images in your zipped set?
Correct, I didn't use two of those shot straight up. One proved to be sufficient (and I got nearly as confused as the software figuring out which side was which anyway...
Regards,
Christian
Offline
Tufused files, an obviously hard to stitch pair since the waves changed and the clouds are fuzzy. I uploaded to FTP a file called drslony_quay1_unstitchable.zip
For others interested, here are the same photos just rotated 90 degrees and saved as jpg @ quality ~83.
Last edited by DrSlony (2008-04-28 14:58:15)
Offline
Controls points are not possible ...but do you really need them?
The following attempt was manually stitched using PS and two layers:
- I aligned the horizon
- I decided of the overlap
- I placed a gradient mask over the overlap
- I adjusted the relative brightness of the source images.
If the pano includes more than 2 images, I would attempt to stitch them separately using APP and then would use the same manual stitch.
Offline
GURL thats a good solution to bypass this problem although i think the point of this topic is to help improve the SIFT algorithm in various difficult situations, so i posted one. Yes, this was a bigger pano, there were 5 shots, 2 to the left, 1 to the right, only this pair didnt stitch automatically no matter what I tried. The funny thing is that once I manually positioned the images, i selected some similar regions, got red CPs with a high RMS, then I optimized and some of those CPs turned green... so there is definitely a chance to improve APP so it could do that by itself.
ps. ignore the fact that the CPs on the screenshot despite being green are actually bad, because they were placed on waves or clouds, the point is that no CPs were found automatically but they WERE found after I moved the images around manually - which means two things: 1) there is room for improvement of the automatic CP discovery, and 2) APP is good enough to find some CPs even in this very difficult set with a minimal amount of human help!
Offline
DrSlony wrote:
GURL thats a good solution to bypass this problem although i think the point of this topic is to help improve the SIFT algorithm in various difficult situations
I'm afraid of some surfer (one who browses, as my dictionary explains) could conclude that APP present version should be able to stitch such a pano. Presently the best solution is (in my opinion) to shot one more view, preferably in landscape orientation and preferably at a wider zoom setting...
Using manual tools was interesting: it made clear for me that having the horizon well stitched is mandatory, having a not strangely adjusted stitch across the sun reflections is very important but any gradient will suffice for the clouds (Smartblend can do that.)
BTW, I find your proposal "option to prioritize the correct alignment of 'narrow & long' areas" (http://www.autopano.net/forum/t2766-cp- … -cp-editor) - the horizon is such an area in this example - more attractive than attempts to place CPs on moving clouds or on a random texture like waves on the sea. That being said, angular speed of clouds next to the horizon is always low and changes in the waves are much slower in distant regions ![]()
Offline
Hi everybody,
My first post here,
I am currently evaluating the means for so-called "2-shots" or "Double-Shot" full automatic stitching.
There are presently several and very different hardware combo solutions that allow to shoot full circular images of >>180 degrees of Angle of view. There are some software that can do automatic stitch more or reliably though. Some others can do a perfect job but from manual coontrol of the user.
From a pair of opposite such hemispherical images, the panographer can get a 360x180 panorama of more than decent quality for full-screen acceptable resolution. BTW much better than the images from a venerable CP 990 posted above by lc8b105, but with the same problem with AutopnoPro: While APP can stitch quite easily three of these circular images shot 120 deg apart (i.e. 3-shots stitch) there seems to be no way to get a decent stitch from a pair of opposite images. Furthermore APP seems to refuse to let a circular image to be of more than 180 degrees of FOV, so there is no way to manually force a good manual 2-shots stich even if APP can sometime detect correctly some CP in a crescent of the circular image.
Am I missing something?
There are some sample images on the Sunex Superfisheye web page that can be used for test. I could provide others and from different combos.
Edit (May 14,2008):
From more recent testing I have found that APP 1.4.2 can do very fine and efficient detection of CP on 2-shots images. On the same images it is also easy for APP to detect more CP by forcing it to do so when needed.
In fact it all depends on the images overlap quality and surface area. In short: the more the FOV, the best is the detection.
For example (CP P5100 + FC-E8 with an adequately modified lens adaptor) combo is providing 2-shots (190 deg FOV) with more than 95% success rate of auto detection by APP, providing that there are sufficient subject features in the images overlap region.
Same successful outcome with (EOS 5D + "shaved" Nikkor 10.5 mm) or (EOS 5D + "shaved" Tokina 10-17 mm) combos. Cropped circular- 2-shots images must then be shot in lanscape mode, of course.
Both the Sunex 5.6 mm superfisheye and the Sigma 4.5 mm (185 deg FOV on APS-C DSLR) yield almost never any CP automatic or forced-manual detection by APP at all.
Michel
Last edited by enbilaman (2008-05-14 11:58:44)
Offline
Hi,
2 shots stitching ... Let be honest. I don't like them !
I found that in such panorama a lot of pixels are coming from areas in input pictures which combines too much distortion, chromatic aberration, etc. So I never trained APP to work with such double shot panorama and will probably never do it.
In fact, if you think about the time you spend putting the pano head on a location and shot 2 pictures, shooting one more is just not an issue and it gives far better results in the post-processing ( you've get automatic stitching far more often this way ) : shoot more, think less.
Even with the sunex superfisheye which has a large fov, I found that it is just not the right way to work to get a good panorama ( even with other softwares which supports more this kind of stitching ). I'm always interested into the quality of the result over shooting complexity ratio.
Offline
2 shots stitching ... Let be honest. I don't like them !
Well, I don't like them either. And I look at them only by insatiable curiosity... until the right lens comes by:-)
Some people love them though. They have paid a high price for years to run their 2-shots system business.
The unique and often forgotten cabability of the 2-shots system is indisputable: it is the **only** way to assure **absolute no parallax** error wathever is the (stationnary) subject distance in the scene from 2 cm to infinity.
BTW I have done some for fun with incredible ease and on a snap. Of course, the quality is limited by the miserable size of the sensor: http://michel.thoby.free.fr/FC-E8_revis … som-2.html
This unique feature is why Stakhanovistic panographers make dozen of (real estate) panoramas per day. They shoot each and every rooms of the houses for sale or for rent, without gear dismounting.
The time advantage doesn't come mainly from shooting less images. Having to shoot more than two photos simply means the advantage of full "safe automatism" is lost and much more manual and intelligent action is required in the workflow.
TCA, softness and other annoyances near the seam can be fully overcome as the technology is already here. Nikon have shown the way with the Nikkor 10.5 mm then Pentax (designing the Tokina 10-17 mm) have followed. Both produce however a too large circular image for true 2-shots even on a FF DSLR.
My experiments have demonstrated that when the **useful** angle of view of the lens is >> 190 deg and when the projection radial mapping of the fisheye is OK, there is almost no observable loss of quality near the seam. Necessary corrections prior to stitching could eventually be made on board the camera in the near future.
I don't expect that a ~30 x 30 mm 16-20 MP sensor camera to be affordable in the near term but I am convinced that a sharp 8 mm f 2.8 fisheye with a truly useable FOV >190 deg. shall be available soon. And then, high quality (with today's standard) 2-shots panoramas shall also be at last possible.
Even with the sunex superfisheye which has a large fov, I found that it is just not the right way to work to get a good panorama ( even with other softwares which supports more this kind of stitching )
IMO Sunex has failed to invent the right lens. The "Superfisheye" can support 3-shots at low resolution with low end DSLR but I think there are other better means to produce 3-shots with higher quality and resolution. The FOV of the 5.6 mm lens is definitly too small for 2-shots and after a carefull study I have told them so. The same holds for the Sigma 4.5 mm.
Michel
Offline