 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
I am trying out APG 3, Alpha 2, under Linux, specifically under Mint 12, which is based on Ubuntu.
For most of the panoramas I have tried up till now, the tool behaves as expected. However, for a couple of the panoramas I was working on, the result in the preview window of Autopano was "warped". It looks as if the original photos are placed in the wrong location and are wrongly shaped. I attached a few screenshot with different areas highlighted. All screenshots are from the same project.
The final, rendered, output, does look ok and does not have these warped images.
When closing and re-opening the project, the preview continues to be warped, so it is not a temporary problem.
As the final result looks ok, the biggest impact of this issue is that it is very hard to work on the panorama before rendering it - e.g., straightening the panorama and masking become a real challenge in the warped preview.
I upladed the files that create this problem for me to the ftp server.
Offline
Interesting result 
I think, you have one or two images for which the lens distortion got out of range. Could you post here the layer editor screenshot where we can see values of yaw, pitch, raw, for all images ?
Offline
I agree that the result is artistic in its own right 
Looking at the details in the layer editor, it looks as if the editor is using the wrong focal length for some reason. I attached two screenshots: one with a panorama that has the issue, the other with a panorama that does not have the issue. As you can see from the subject, both were taken very shortly after one another and therefore I did not adjust any camera settings.
Note that for both of them, the panorama renders fine without any problems. The problem only occurs in the preview window while working on the panorama.
I am using a 5D Mark III with a 8-15mm lens set at 12mm if that makes a difference.
Last edited by Photonicwand (2012-08-29 18:36:54)
Offline
So I confirm the analysis : it seems that the optimizer wasn't able to go through the first case as the focal did reach the internal limit of 220°. When you have this way in focal, then the optimizer didn't converge to the real solution.
1. check the control point and add some near the corner of images, it does help a lot.
2. provide me the images through FTP, I want to play with them : http://www.kolor.com/forum/t766-ftp-server
Offline
Interesting. Not sure why it would do that for some panoramas and not for others, considering they were taken with the same camera and lens at the same settings. Unless the raw converter I use (Darktable) has something to do with it.
I uploaded to the FTP server yesterday. The file name startes with Photonicwand_ (don't remember the entire name).
Offline
Got the sample, found the bug
Thanks for sharing it.
Offline
Great! Thanks for fixing it! :-)
Offline
Well, I had something like this today. A 2-row pano shot with a 50mm lens on a clickstop pano mount -- so nice intervals for all. But it insisted the focal length was 24mm and double overlapped. This was probably due to the presence of sky shots where there were light cloud patterns which allowed blending for most but not all shots, but the lack of blending shouldn't cause this. Would be nice if I could tell it, "really, believe the focal length in the exif, or at least don't drift more than 5% from it."
Offline