hugin-devs team mailing list archive

[rew <685885@xxxxxxxxxxxxxxxxxx>]

Let's consider the "issue 2" as "fix released" and continue this
discussion on "issue 1" as you call it.

restrictions that I know of right now, is 4Gb of pixel data for TIFF
files and 64k pixels per side for JPG.

How about if we make this a warning.

if (((height * width * estimate_for_bytes_per_pixel) > 2LL^32)) &&
     (outputformat == TIFF)) {
    .....  WARNING: possibly generating more than 4Gb of pixel data. May not fit in output TIFF file. 
}
if (((width > 65500) || 
     (height > 65500)) && 
    (outputformat == JPG)) {
   ..... WARNING: JPG format may not support the output image size. 
}

Then it isn't as critical, and doesn't have to be 100% right. We can
easily add checks for limits on other output formats as we go along.

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

Title:
  Enblend fails to recognise output tiff file too large.

Status in Enblend:
  New

Bug description:
  I'm working on a big blend. I specified the output resolution to be: 62930*17113
This results in 4.01 Gb of output pixel data. With --compression NONE, this is
guaranteed to generate more than a TIFF file can handle. 

First I would like enblend to signal this before it's done hours worth of blending. 

Secondly, it silently wrote the invalid TIFF file without any complaint. It should 
at least fail writing the final output image. I was anxious to see the partial result
when I found out the tiff wouldn't open....