So: yes it blends when you try it without imagecache and have enough swap space available. Enblend crashes without any reason according to your first message. Just "enblend was killed" is output by make. Probably "segmentation fault" is somewhere in there, but lost....
I personally stitch at one third or one tenth of the final resolution first to check if I have my controlpoints right. In 99% of the cases you can already see problems there. And the blends go 10 - 100x faster. -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/685105 Title: enblend fails to blend large pano Status in Enblend: Confirmed Bug description: Enblend failed with: enblend --compression=LZW -m 1200 -w -f135659x3947+0+1091 -o pano8110_l.tif .... ... enblend: info: loading next image: pano8110_l0000.tif 1/1 enblend: out of memory enblend: std::bad_alloc This is a simple 0.5Gpixel panorama I shot. And agreed, Hugin did warn me that it might take a lot of memory. The thing is: There is no other tool to stitch this with, so I'll have to make do with hugin and its toolset.... I thought there was an "imagecache" that would swap parts of images to disk... _______________________________________________ Mailing list: https://launchpad.net/~hugin-bug-hunters Post to : [email protected] Unsubscribe : https://launchpad.net/~hugin-bug-hunters More help : https://help.launchpad.net/ListHelp
