hugin-devs team mailing list archive

[tmodes <1316967@xxxxxxxxxxxxxxxxxx>]

Implemented in changeset 37e4d310b065. For BigTIFF output you need to
compile enblend/vigra with libtiff with BigTIFF support and add
`--parameter=export-bigtiff´ to command line.

** Changed in: enblend
       Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1316967

Title:
  Maximum TIFF file size 4GB

Status in Enblend:
  Fix Committed

Bug description:
  Hi there!

  After running for 2 days the enblend binary that I compiled myself
  from the enblend sources revision 1049 failed with this error:

  enblend: info: writing final output
  enblend: error: Maximum TIFF file size exceeded

  enblend: an exception occured
  enblend: 
  Postcondition violation!
  exportImage(): Unable to write TIFF data.
  (/build/buildd/libvigraimpex-1.9.0+dfsg/src/impex/tiff.cxx:811)

  enblend: info: remove invalid output image "x1.tif"
  ===================================================

  I've used these parameters:  --compression=LZW --verbose
  --output=x1.tif

  The output pixel dimensions would have been 119598 * 17362 =
  2076460476 which is still well within the 2^31 pixel count limit =
  2147483648

  In the bug report #685105 I've mentioned that I've run into this problem before, and back then Jeff Hungerford (hungerf3) told me:
  "If you are seeing that error, either the TIFF library you linked against doesn't support bigTIFF, or for some reason it decided to only use the old format."

  It would be very kind of you if you could guide my way how to compile
  enblend (and libtiff?) in a way that enblend will not fail when the
  output exceeds 4GB in file size.

  Or is there maybe a way to use another output format then tif to
  workaround this problem? (With Gimp I like to use png for images that
  are too big for 4GB tif, it has the same problem of failing to save
  >4GB tiffs for me)

To manage notifications about this bug go to:
https://bugs.launchpad.net/enblend/+bug/1316967/+subscriptions