Checking ExifTools Failed

394 views
Skip to first unread message

Jason Chu

unread,
Aug 14, 2014, 10:28:22 AM8/14/14
to hugi...@googlegroups.com
Dear all,

Recently I started noticing none of my exif data from the source files are being saved into the final stitched panorama.  I eventually discovered that Hugin was not able to find exiftool anywhere.  I've already done a bit of research into this problem however none of them have fixed the issue.  Namely:

- I confirmed ExifTool.exe is in the Hugin/bin directory
- I tried replacing ExifTool with the latest download from the author's site
- I have no antivirus software installed so it's not being quarantined
- I've reinstalled the program v.2013 without wiping the registry settings
- I've reinstalled the program v.2013 after clearing the registry settings
- Installed the 2014 version (with new settings)

In all cases Hugin refuses to recognize ExifTool.  Lastly, I checked my *.pto.mk file and it also has the correct path as the other components (nona, etc.).  Searching on this forum yielded no results either.  Anyone have any clue???

Jason Chu

unread,
Aug 14, 2014, 6:35:09 PM8/14/14
to hugi...@googlegroups.com
Also forgot to mention I'm running everything in a Win7 x64 environment.

T. Modes

unread,
Aug 15, 2014, 12:35:06 PM8/15/14
to hugi...@googlegroups.com
 Try running exiftool from the command line: exiftool -ver

If this does not works, your exiftool installation is corrupt. Delete the folder par-USERNAME in your temp directory.

Jason Chu

unread,
Aug 16, 2014, 4:42:51 AM8/16/14
to hugi...@googlegroups.com
Thanks for the reply.  I cd'd into Hugin/bin, typed exiftool -ver and it returned 9.50.  I also tried deleting par-<username> in my AppData/Local/Temp directory anyway, just to see.

Unfortunately it still gives me exiftool failed.  Any other ideas of what may be the culprit?

Last thing is, I'm using version 2014 currently, and in the preferences "Copy metadata into final files using ExifTool" is checked, and the exiftool argfile field is empty (under the Stitching tab).

T. Modes

unread,
Aug 17, 2014, 1:54:52 AM8/17/14
to hugi...@googlegroups.com


Am Samstag, 16. August 2014 10:42:51 UTC+2 schrieb Jason Chu:
Thanks for the reply.  I cd'd into Hugin/bin, typed exiftool -ver and it returned 9.50.  I also tried deleting par-<username> in my AppData/Local/Temp directory anyway, just to see.

Unfortunately it still gives me exiftool failed.  Any other ideas of what may be the culprit?

Not really. For the test only 'exiftool -ver >NUL 2>&1 && echo OK || echo failed' is called. So, if exiftool works and the path is okay, it should work.
 

Last thing is, I'm using version 2014 currently, and in the preferences "Copy metadata into final files using ExifTool" is checked, and the exiftool argfile field is empty (under the Stitching tab).

The argfile is not used during the test.

Harry van der Wolf

unread,
Aug 17, 2014, 12:44:50 PM8/17/14
to hugi...@googlegroups.com
Do you perhaps have strange path names or file names: with quotes, double-qoutes, commas, exclamation marks, etc.?


--
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/c45e454b-a035-48b3-9c20-137ac5326cce%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Jason Chu

unread,
Aug 18, 2014, 5:09:45 AM8/18/14
to hugi...@googlegroups.com
Hi Harry,

Yes, I do use commas, [ ] and spaces in my path, but not for the actual output files.  For instance: F:\Photos\August 15, 2014 [Test]\Panorama 1\Panorama 1.tif would be a typical path.  However, I have been using paths such as the example for a long time so I know it has worked before.

One other thing that might affect things is, a month ago I reinstalled windows (same exact version) and copied all of my user directories over (C:\Users\<username>\AppData), so Hugin is using settings from those (my settings were never reset after I installed, so I'm guessing it got it from my old user files).  Is there a Hugin directory somewhere in my user directories that might cause issues?

Thanks for all the help so far!

Jason Chu

unread,
Aug 28, 2014, 10:12:13 PM8/28/14
to hugi...@googlegroups.com
I'm still having issues getting the exif data to pass onto the final output panorama.  Does anyone know why the exiftool would fail?

T. Modes

unread,
Aug 30, 2014, 3:27:09 AM8/30/14
to hugi...@googlegroups.com


Am Freitag, 29. August 2014 04:12:13 UTC+2 schrieb Jason Chu:
I'm still having issues getting the exif data to pass onto the final output panorama.  Does anyone know why the exiftool would fail?

Not really.

You could try it on the command line. Maybe there is some printing.

Try the following on the command line (make sure you have your Hugin\bin directory in the PATH environment variable)
1. Create the makefile (pto2mk will not read your settings. So the will be excluded in this test):
pto2mk -o makefile.mk -p test project.pto
2. Print the commands which will be executed:
make -f makefile.mk --dry-run test
3. Now run the tests:
make -f makefile.mk test

(Additional you can run the exiftool command which will be displayed in step 2 directly running the command line. Maybe there is some more output to find the cause.)

Thomas

T. Modes

unread,
Aug 30, 2014, 3:40:50 AM8/30/14
to hugi...@googlegroups.com


Am Samstag, 30. August 2014 09:27:09 UTC+2 schrieb T. Modes:

Additional you can run the exiftool command which will be displayed in step 2 directly running the command line. Maybe there is some more output to find the cause.


Forgot one thing: for this test you should remove ">NUL" und "2>&1" from the command line, so more information is printed on screen.


Reply all
Reply to author
Forward
0 new messages