Output image has no EXIF metadata

[Milan Knizek]

Hugin 2016.2.0.be8da0221960
Arch Linux x86_64
ExifTool 10.50

Hugin does not add any EXIF metadata (neither XMP) to the output JPEG file.

I tested with "empty" argfile name in Preferences / Stitching (2) for both intermediate and final args.

Then I also created simple argfiles for both:
1) "-ImageDescription"
2) "-ImageDescription=Test"

But to no avail - the output JPEG has neither EXIF nor XMP metadata at all (tested with "exiftool image.jpg" and "exiv2 image.jpg")

P.S. It used to work some times ago (cca one year, I guess it was older hugin version).

[tmodes (tmodes)]

It works fine here. I can't reproduce the issue here. (There is an issue when no argfile is specified in the preferences. This is fixed in the repository now.)
If you specify an empty argfile, then no tags are copied. This should be clear.
Go the preferences, delete the filename for the argfile and then press "Edit". This will ask for a new filename and create a default argfile and try with it.
(Maybe in PTBatcherGUI activate the options always save log and try again. At the end of the log it should read
Updating metadata...
    1 image files updated
The option use exiftool should be activated in settings.)
Please report what you get.

PS: XMP GPano tags are only created for equirectangluar output.

[Milan Knizek (knizek)]

Thanks for info re. "always save log" in PTBatcherGUI, it helped to see the last line of the log:

Updating metadata...
execvp(exiftool, -overwrite_original_in_place, -TagsFromFile, /srv/Photos/2017-04/p04/20170423-121217.jpg, -WhitePoint, -ColorSpace, -@, /home/user/test.arg, -@, /tmp/heCCPCAL, 20170423-121217 - 20170423-121644.jpg) failed with error 2!

I did try the same on CLI (having copied the /tmp/heCCPCAL to a another file during stitching before the tmp file disappeared) and it works as expected.

Is there a way to to get the full error output of exiftool from Hugin/PTBatcherGUI ("PTBatcherGUI --verbose" did not show anything)?

(BTW, I installed Hugin from HG and the problem disappeared.)

[tmodes (tmodes)]

That's strange.

For debugging there is "hugin_executor --stitching --dry-run .." which creates all needed temporary files (you have to delete them manually at the end) and prints all commands to console. (So you can try it on the command line.)

This command line is passed to wxWidgets wxExecute(). The error message is then raised inside this function. I have no idea how to debug this further. But when it works for you now, there is no need to dig deeper. Is this right?

[Milan Knizek (knizek)]

Running the commands from "dry run" worked just fine. Weird.

Nevermind, I stay with hugin-hg - you can close the bug now.

Thanks for help.