hugin-devs team mailing list archive

[the_mechanical <685105@xxxxxxxxxxxxxxxxxx>]

Thanks for your reply.
Finally  i did it (enblend did it ;-)  ).

BEFORE:
* Due to 16GB Memory and SSD-disk i used a RAM-disk for /tmp.
* Due to SSD (limited space - the big ones are too expensive for me), only little swap-space on a "normal hard-drive".

AFTER (means solution which worked for me):
* No RAM-disk
* Made space free on "normal hard-drive" and took it as SWAP (now ~30GB SWAP).
* mounted a folder temp (on Project-partition) to \tmp, means /tmp is as big as the free part of the project partition
* compiled enblend without imagecache (as at the beginning).

So i got the result. Not correct, but that's another story *gg* (fine-tuning of control points necessary).
Output - png is about 900MB.

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