Questions about turning on BigTiff output in Hugin

[David W. Jones]

Good afternoon!

Sorry, from what I read, I need to add a command line switch to Hugin to turn on BigTiff output.

Two questions:

What is the switch?

Where do I put it?

I can't find anything online that covers this, just repeated statements that it needs to added to Hugin, but no instructions on how to do it.

Ideas?

-- 
David W. Jones
gnome...@gmail.com
wandering the landscape of god
http://dancingtreefrog.com
My password is the last 8 digits of π.

[tbransco]

I've been following your questions on BigTIFF lately as the answer may be of use to me as well down the road.  I don't have that answer as yet; but, perhaps all you need are the BigTIFF executor file (user output sequence) attached to that 2018 message mentioned previously along with the PTBatchGUI application.  The command line switches for the latter are described in the documentation here: PTBatcherGUI.  At the very bottom of that article is some discussion about the switch "--user-defined=<str>" which seems to suggest you can start PTBatchGUI with the BigTIFF executor, or use the 'Change user-defined sequence..." button in the GUI itself to add the same switch.

Hopefully, there's something you can use here.  Do let us know how you get on.  Thanks.

Terry

[David W. Jones]

Thanks. I can't find that 2018 email anywhere in my collection or in the Google Groups, so I can't find the executor file. And can't figure out enough from the executor file documentation to tell what I would need to have in an executor file to have the project generate a BigTIFF file.

I found that one of the applications I use RawTherapee, can output BigTIFF files. I did a test using that output in Hugin, it seems to work, but I still can't tell where I need to set things to have Hugin output BigTIFF files.

[tbransco]

I've attached the BigTIFF executor file here.  You just need to open your project (pto) file in PTBatchGUI, select it with in the application's main window, and click the "Change user-defined sequence..." button in the right sidebar.  This will open a popup with 3 options and it's the "External" option you want to activate.  This then allows you to select the executor file from your storage location.  You can turn on log files in the same sidebar to confirm what works and run the batch.  Et voila!  Your BigTIFF output file.  My own quick experiment and log file shows that exiftool is incapable of adding exif data to BigTIFF files; but, I do get a BigTIFF file!  MYYV; but, good luck.

Terry

[tbransco]

For completeness, here is the source of the bigtiff.executor file I sent you:

Link to the original 2018 post

Terry

On Wednesday, June 18, 2025 at 10:10:13 PM UTC-7 GnomeNomad wrote:

[Terrence Branscombe]

Forgot to include the mailing list in my response to GnomeNomad, so I'm forwarding it here to wrap up our discussion about getting BigTIFF output from Hugin.

Terry

-------- Forwarded Message --------

Subject:	Re: [hugin-ptx] Re: Questions about turning on BigTiff output in Hugin
Date:	Thu, 19 Jun 2025 09:15:49 -0700
From:	Terrence Branscombe <thirdmo...@gmail.com>
To:	David W. Jones <gnome...@gmail.com>

The PTBatchGUI method of running the BigTIFF executor may not be ideal for everyone as it's a bit of a faff for a single pano.  To run such executors from the main Hugin GUI simply load the exectutor file using the Output menu option and select the "User defined output..." item.

Terry

On 2025-06-19 12:36 a.m., David W. Jones wrote:

Thanks, Terry. I didn't see any executor attachment, but the text of it came through in your other post.

--
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/8b5e696d-1ead-4d96-bb2e-aac21c91f428n%40googlegroups.com.

[David W. Jones]

That's exactly what I did. Worked for me. 🙂

To view this discussion visit https://groups.google.com/d/msgid/hugin-ptx/ab55c78e-44a0-4cd4-8c04-dfb64e852b84%40gmail.com.

[T. Modes]

tbransco schrieb am Freitag, 20. Juni 2025 um 05:13:49 UTC+2:

To run such executors from the main Hugin GUI simply load the exectutor file using the Output menu option and select the "User defined output..." item.

If you place the executor file in  ~/.local/share/hugin  it will directly displayed in the GUI - as already written in the other thread. I don't know why a new thread was necessary instead of continuing in the other one.

[David W. Jones]

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

tbransco schrieb am Freitag, 20. Juni 2025 um 05:13:49 UTC+2:

To run such executors from the main Hugin GUI simply load the exectutor file using the Output menu option and select the "User defined output..." item.

If you place the executor file in  ~/.local/share/hugin  it will directly displayed in the GUI -

Yes, but simply placing the file there doesn't say where it will be found in the GUI.

Only place I've found it is Output > User defined output, or the "Change user defined sequence" button in the Batch Processor. Any other places?

as already written in the other thread. I don't know why a new thread was necessary instead of continuing in the other one.

Sorry, I understand the annoyance of multiple threads. I just find that threads get annoying when one thread starts on topic A, expands and diversifies as people reply to it, and reply to replies to it, eventually leading to a tangled mess that buries the information in a mass of semi-related (or even unrelated) information. 

I prefer that communication remains focused on the topic. I suppose this is why I find "team chat" tools like MS Teams and Slack et al poor choices for a team knowledgebase.