okey, so the enblending of my 240.000 x 8.292 pixel panorama succeed. The resulting tiff file is a little under 2GB big and sadly does contain lots of those http://kaefert.is-a-geek.org/misc/hugin /360degree233pics_enblend-failure/artifacts-enblend-4-2/ artefacts. I think this artefact problem I see might be related to this bug: https://bugs.launchpad.net/enblend/+bug/721136
Though I do not understand what @rew (r-e-wolff) said about disk swapping of images --> Is this the same as the this imagecache feature and does this still exist in the latest versions of enblend? From what you guys posted I thought it was a discontinued feature, but from what I read over at https://bugs.launchpad.net/enblend/+bug/721136 it sounds like my blackish artefacts stem from a bug in this imagecache thingy. -- 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 : [email protected] Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
