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.
I do have only 3Gb on my primary/program disk but I have lots of space on my Page File disk. In apps like Photoshop I can configure where I want temporary files to be created. It is not unusual that people have a smaller system disk and then a separate disks for data and temp.
3. Hum. So you have a random crash when opening a directory ... Never saw that. Hope the next release will fix that.
I have to test some more, maybe that's just the free disk space problem on my primary drive. Autopano just disappears while showing the progress bar while populating the icon view. After Autopano disappears, an XP popup comes up offering to send a problem report to Microsoft
I have to admit that some of those folders contain smaller JPEGs (thumbnails), some Pentax *istD RAW files (.PEF) and maybe even a couple of .PSDs. Whatever the reason, I have never had it crash in the same exact conditions so as I already said it might be the free space on disk.
4. On group options (icone with a hammer), improve there's a quality settings you can raise.
This is probably me wishing for the impossible. Seems that this is the parallax thing grouse talked about. Turning quality settings all the way up somewhat helps.
5. Remove of a picture is already planned to be added soon (The add ... hum, not yet).
The remove is really more important than add, I don't even think that this is something worth the effort. This is good news.
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.
I'm still doubtful about that. I had some pictures with large overlapping areas and the ghosts from the topmost image are visible but ghosts from underlaying pictures are not. Maybe I should send you an example? I must admit that this is not a typical use for panorama software but, seeing that Autopano is extremely capable in combining pictures you would have never thought possible, it is tempting. And this is the weirdest thing, sometimes pictures that were never intended to be panoramas stitch really well and sometimes you can try all you want and you cannot get them to stitch well.
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.
This is one feature particularly sought after by some macro photographers. I don't know how this would work in practice but the simplest way (no automation) would be to export layers with no blending whatsoever so that you can afterwards blend them manually in Photoshop.
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.
Ok, I see.
Thank you for taking time to explain this all to me, I'm now leaning more towards purchasing Autopano.