Can Hugin output a BigTiff file?

[David W. Jones]

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
gnome...@gmail.com
wandering the landscape of god
http://dancingtreefrog.com
My password is the last 8 digits of π.

[Paul Womack]

"Only" an 8Gb file assuming 8 bit data, 3 samples per pixels

--
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 hugin-ptx+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/hugin-ptx/d4d057f5-2975-4135-9998-51e4bf5667ac%40gmail.com.

[Paul Womack]

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 <gnome...@gmail.com> wrote:

--

[David W. Jones]

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.

[David W. Jones]

Actually, it would have been 16-bit per sample per pixel. Something ginormous! 😉

The 55122x47147 size was due to my erroneous cropping as mentioned in my other reply to this thread.

While my immediate need to make gigantic images is on hold, my longer term goal of making such remains. I like large images, with lots of details. I use a Sony A7R4A 60-mpx camera and look forward to stitching some big panoramas!

[T. Modes]

GnomeNomad schrieb am Donnerstag, 12. Juni 2025 um 02:07:23 UTC+2:

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.

Hugin can write BigTiff files since version 2018.0.

It needs to manually selected. Either on the command line or with a user defined output sequence (there is an bigtiff.executor file in an older thread from 2018).

Thomas

[David W. Jones]

Thanks. I didn't see anything in the GUI about saving output as BigTIFF, in either Hugin or the batch processor.

Where would the *.executor files be? If they're all supposed to be in /usr/local/share/hugin/data/output/, there's no bigtiff.executor file there.

[David W. Jones]

On 6/17/25 06:00, 'T. Modes' via hugin and other free panoramic software wrote:

Thanks. I didn't seen anything in the GUI about saving output as BigTIFF, in either Hugin or the batch processor.

Where would the *.executor files be? If they're all supposed to be in /usr/local/share/hugin/data/output/, there's no bigtiff.executor file there.

Ideas?

[T. Modes]

Sorry, but posting once is enough, no need to double post with some hours between.

GnomeNomad schrieb am Mittwoch, 18. Juni 2025 um 07:55:40 UTC+2:

Hugin can write BigTiff files since version 2018.0.

It needs to manually selected. Either on the command line or with a user defined output sequence (there is an bigtiff.executor file in an older thread from 2018).

Thomas

Thanks. I didn't seen anything in the GUI about saving output as BigTIFF, in either Hugin or the batch processor.

Where would the *.executor files be? If they're all supposed to be in /usr/local/share/hugin/data/output/, there's no bigtiff.executor file there.

The user executor files should go into ~/.local/share/hugin. And yes there is no bigtiff.executor. As I already wrote this file was posted in another thread on this mailing list (and is not distributed with the official release.)

[David W. Jones]

On 6/18/25 04:50, 'T. Modes' via hugin and other free panoramic software wrote:

Sorry, but posting once is enough, no need to double post with some hours between.

Sorry, I accidentally posted two messages from an address not subscribed to the list, resent one using the correct address, then forgot which one I'd already re-sent.

Ah. Why isn't it included in the official release?

I couldn't find it in Google Groups.