I remember the error message came during the file compression stage.
I was watching the folder where the output file was being written. I
noticed that file size went up to 4GB, reset to zero, and proceeded to
start going back up before the log appeared reporting the error. I think
it got up to around 2GB again before the error.
I think it hit the 4GB TIFF size limit, an internal counter rolled over
(regular TIFF uses 32-bit internal counters), the LZW compression
routine tried to continue, then crashed.
Unfortunately for reproducing the error, I discovered that I'd set the
crop incorrectly. With that set correctly, file size came in at 1.7GB
with no problems.
My desktop system has a Ryzen 9950X (16 cores, 32 threads), 128GB RAM,
500+ GB space free on a 2TB SSD, running 64-bit Debian Bookworm.
On 6/11/25 21:48, Paul Womack wrote:
If you capture the actual error message, and add it to this thread, it
should be possible to find the piece of source code throwing the
error, and get more information.
On Thu, 12 Jun 2025 at 01:07, David W. Jones <[email protected]> wrote:
Good afternoon!
I'm working on a panorama that's 55122x47147 pixels. When
stitching it as a TIFF, Hugin announced that the file size had
been exceeded. I'm using Hugin on Debian Bookworm with EXT4 file
system, so I don't think it's a limitation of the file system.
I read about BigTiff but don't know how to see Hugin to use that.
Or what else I might have to do to use it.
Ideas?
--
David W. Jones
[email protected]
wandering the landscape of god
http://dancingtreefrog.com
My password is the last 8 digits of π.
--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/hugin-ptx/f706cf34-130b-4c24-a891-ba22c2e469fb%40gmail.com.
