krisjaniz wrote:I am considering buying Autopano but am reluctant to do so. I have been checking it out for the last couple of days with mixed success. Maybe you could help me out. Here are my observations.
1. I have a dualcore system with 2Gb RAM. Is Autopano configured to swap to disk or can it be set to use all available memory? From the amount of disk writes I get when rendering I have a sneeking suspicion that this could be improved for machines with more than average memory.
2. If I point Autopano at a large collection of images it crashes sometime during operation. I have observed that before crash I still have at least 1Gb of free memory.
3. Sometimes Autopano just crashes when opening a directory of images. When I try again it works. I don't have any precise data on that but seeing that Autopano is the only software that ever crashes on my machine (I can accept it crashing in point 2 but this is something that really bugs me) is there something I can do for improved stability?
4. There are many errors in rendering - in some places the images are stitched perfectly, in some you can see the two or more features duplicated. Can I do something to force Autopano to perform better morphing of images? Or will this come with the support for "fisheye"?
5. It would be cool if I could remove individual images from a pano in preview mode or add individual images to it. Sometimes that one last image of the series screws up a panorama or there is not enough spacing between the frames and it is a pain to find and delete the correct images from the thumbnail view and then launch panorama search again.
6. Is there any way to change the Z-order of the stitched images? Sometimes the quality of one image is better or people have moved so you would want this image to be on top.
7. There are occasions when I would want to make a stack of images to increase Depth Of Field instead of Dynamic Range. Can this be done (put the image with the strongest image detail/sharpness on top)?
8. Other panorama software I have worked with previously have relied on lens data - either only the focal length or even a full distortion map. I find it that Autopano tends to distort corners of large panoramas heavily. Maybe this could be remedied with some lens information?
This is it for now, I will continue my testing and try to find some more information on crashes and other things. Thank you for reading this far
AlexandreJ wrote:1. True. In the fix version that comes out today (I hope so), you'll have the ability to adjust used memory.
2. Crash can comes from "no more memory" or "no more place in temporary drive". We fixed many of those crash in the next release.
AlexandreJ wrote:3. Hum. So you have a random crash when opening a directory ... Never saw that. Hope the next release will fix that.
AlexandreJ wrote:4. On group options (icone with a hammer), improve there's a quality settings you can raise.
AlexandreJ wrote:5. Remove of a picture is already planned to be added soon (The add ... hum, not yet).
AlexandreJ wrote:6. As pictures are blended, Z-order doesn't do anything to it. For ghost removal, we'll add alpha channel support in input picture and a new blending algorithm.
AlexandreJ wrote:7. It's planned, but not quickly. Our engine allows us to change easily for example the blending process and still keeping all others tools. So I just need to write a small piece of code to blend depth of field instead of color.
AlexandreJ wrote:8. It could help a little but not really. If you talk about PanoTools lens distortion data, I will not rely on that because the lens model is not really good. Anyway, we are working on a big revamp of the optimization stage (algorithm which finds yaw, pitch, roll, fov, and distortion), which should solve some of issues when closing panorama.
f.simond wrote:Hello krisjaniz,
Have you tried the layered psd output ?
If you're comfortable with Photoshop you will be able to help Autopano Pro to blend everything using layers
Users browsing this forum: No registered users and 2 guests