@Christoph you're welcome. Yes, if you define panoramas with more than 2^31 pixels as out of scope of what you are trying to achieve with hugin, I think you can change the status of this bug to "fixed" in enblend 4.2
I don't think invalid would be the proper state, since with enblend 4.0 (at least the one included in ubuntu) you truly can't enbend bigger panoramas also far below 2^31 pixels, so this bug truly existed in enblend 4.0 My biggest issue at the moment that I have not found any workaround yet is https://bugs.launchpad.net/enblend/+bug/1193872 It would be great if someone could take a look at that. -- You received this bug notification because you are a member of Hugin Developers, 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... To manage notifications about this bug go to: https://bugs.launchpad.net/enblend/+bug/685105/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
