Exif + Intermediate files

[Chris Brown]

I'm using Hugin to align 'then & now' photos and I'm trying to figure out how to keep exif data from the original 'now' photos for the remapped intermediate files. 

I'd also like to save values for each photo from the optimiser tab (orientation & lens parameters - y,p,r etc) in the exif of the intermediate so I can keep track of how originals have been changed.

I'm wondering what values can be saved using the argfiles in hugin preferences and if there is any further documention about it?

[T. Modes]

Am Sonntag, 26. März 2017 10:39:15 UTC+2 schrieb Chris Brown:

I'm trying to figure out how to keep exif data from the original 'now' photos for the remapped intermediate files. 

Currently only the metadata of the first image can be copied to all intermediate images. This refers to the blended and fused images, not to the remapped *only* images.
The EXIF data refer to the original image. So some information is not valid anymore when applied to the remapped image (e.g. when you change the field of view the focal length/cropfactor is not valid for the remapped image).

But wait, I added an additional placeholder %sourceimage% to the user defined output sequence in changeset cc6d6ff6346a. This should allow to copy selected EXIF tags to the remapped images, when you create your own user defined output sequence.

I'd also like to save values for each photo from the optimiser tab (orientation & lens parameters - y,p,r etc) in the exif of the intermediate so I can keep track of how originals have been changed.

This is not possible with Hugin tools.
 

I'm wondering what values can be saved using the argfiles in hugin preferences and if there is any further documention about it?

In principle all tags which exiftool can write can be copied. So read the tag documentation of exiftool.
All supported placeholders are described in the dialog (no undocumented one are available).

Thomas

[J. Schneider]

Hello Thomas,
this is interesting to me, too, because I have a similar wish. Could you tell us where and how this placeholder %sourceimage% is to be used? Is it in argfiles that can be specified in preferences tab Stiching (2)?
Best regards
Joachim

--
A list ...

[T. Modes]

Hi Joachim,

Am Sonntag, 26. März 2017 18:11:19 UTC+2 schrieb J. Schneider:

 Could you tell us where and how this placeholder %sourceimage% is to be used? Is it in argfiles that can be specified in preferences tab Stiching (2)?

No. As I written before you need to create a user defined output sequence for a special use case. There you can now use the new placeholder.
(The placeholder is not used in the argfiles in the preferences.)

Thomas

[T. Modes]

Hi Joachim,

find attached an example for an user-defined output sequence for this use case. Only some EXIF tags are currently copied, but you can simply extend the arguments.

Keep in mind that this user defined output sequence needs a Hugin version from default branch (after changeset cc6d6ff6346a, it does not work in released versions).

Thomas

[J. Schneider]

Thank you for your help,
it seems I lack some fundamental knowledge about how hugin is working behind the scenes. But I located C:\Program Files\Hugin\share\hugin\data and some .executor files, I guess this is where the file would go. Anyway - as I am not able to build hugin myself I will have to wait till this comes as an end user feature. But sounds promising!

No, wait, I just have to change those files to my liking if I can't yet add any new ones.

So what I don't yet understand is the role of the executor file and the arg file.
Both contain a set of arguments to pass to exiftool. But which one is used while stiching? Executor if there is no arg file specified? My modifications don't yet yield any (different) result, but I believe I must be on the right way. I changed the last line of the executor file to
"Arguments=-overwrite_original_in_place -TagsFromFile %image0% %result%"
for a try.
And I tried changing hugin_exiftool_copy.arg to "-iptc:all -exif:all".
Both should transfer all tags now, if I understand the role of these files and the exiftool documentation. (Don't mind that transferring the focal length e.g. to the result doesn't make sense. It's a try.)
Any more hint?

Best regards
Joachim Schneider

--
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 on the web visit https://groups.google.com/d/msgid/hugin-ptx/8965f199-d276-440f-bcb9-075bbeddcee1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[T. Modes]

Hi Joachim,

Am Freitag, 31. März 2017 23:03:00 UTC+2 schrieb J. Schneider:

So what I don't yet understand is the role of the executor file and the arg file.

some more details. There are 2 ways to invoke the stitching:

1.) Normal stitching.
All settings from the stitcher tab and the preferences are read and applied during stitching. (e.g. exiftool argfiles)
Here you can select which output should create on stitcher tab. The metadata are only copied to the blended/fused images, but not to the remapped only images. So modifying the argfile does not help to copy EXIF data to the remapped only images.

2.) User defined output queue
Here the steps for the stitching are fixed coded in the .executor file (so no options in the GUI, these can be implemented by different executor files). So it's easier to add additional steps to the processing queue (using other blender, process intermediate image with additional program, ...).
In this case the settings from the stitcher tab are ignored (except projection, fov and canvas size). The same applies to the settings in the preferences, these are also ignored.
There is no fixed place for an executor file. You can select the file from any place by a file open dialog. (2017.0 shows executor files from 2 directory in the menu bar: system wide executor files from Hugins data directory and user specific executor files from the users data directory).
(PTBatcherGUI can not work with an executor file, here is always the normal stitching applied.)


Thomas

PS:

And I tried changing hugin_exiftool_copy.arg to "-iptc:all -exif:all".

In the arg file all arguments have to be on an own line, also
-iptc:all
-exif:all
But this copies the data only to the final (blended/fused) image, not to the remapped images.
 

[J. Schneider]

Thank you very much Thomas, this has shed some light into this dark matter. So modifying the argfile is my way to go because a) I care only for the final result and b) I usually stitch using PTbatcher.
And it works!

Best regards
Joachim Schneider

--
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 on the web visit https://groups.google.com/d/msgid/hugin-ptx/d4b65d73-64e9-4b79-9032-29edd91defed%40googlegroups.com.

[Dick Wieboldt]

Hi Thomas,

Just found this message thread and it does exactly what I want. I appreciate the example executor file - a big help.

Question for you, is there a build for windows containing this change on SourceForge that I can download? I can see the default branch but don't see anything obvious there (like a daily build).

Thanks for your help,

Dick

[T. Modes]

Hi Dick,

Am Mittwoch, 3. Mai 2017 18:50:10 UTC+2 schrieb Dick Wieboldt:

Question for you, is there a build for windows containing this change on SourceForge that I can download? I can see the default branch but don't see anything obvious there (like a daily build).

no, there is no binary download. You have to wait for a new release.

Thomas