I ran a rough test (I don't have the tripod) and determined that my NPP was displaced by approximately 10cm - which caused about a 4px pixel error for mid-range objects. It's really neat that object distance can be estimated from pixel error.
I've noticed that enblend is 99% of the stiching process; furthermore it seems severely limited by disk-io. If enblend is swapping to disk due to a memory limit then the enblend manually describes how to increase the limit; is this a good idea? I run a 4GB system of which 3.25GB are available to user processes; enblend uses 28%, 932MB very near to the 1GB limit. If I increase the limit to 2.5GB or 2.25GB will it create a noticeable speed-up? On the other hand, if enblend is simply writing to disk, then I'd like to know how much space on-disk it uses/requires - to where is it writing? Therefore maybe I can create a 1.5GB ramdisk.. which begs the question, if the ramdisk becomes full, will enblend fall back to another partition? -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
