hugin-devs team mailing list archive

[kaefert <kaefert@xxxxxxxxx>]

The enblend I'm running is compiled from the sources I've got on tuesday from
hg clone http://hg.code.sf.net/p/enblend/code enblend.hg
following those instructions:
http://wiki.panotools.org/Hugin_Compiling_Ubuntu#Building_Enblend

and @ this page:
http://hg.code.sf.net/p/enblend/code/shortlog/27edd6c31bd2
I found those changesets:
Sun, 09 Dec 2012 09:55:26 +0100	Chris	Disable image cache.
Sun, 09 Dec 2012 09:54:35 +0100	Chris	Make the "disable ImageCache" configuration the default.

so I think my enblend should not use this ImageCache feature. Also if it
did, why would it use 52 gigabytes of memory?

-- 
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