Hi, first thanks Phil for this great tool.
I've a bunch of .jpg I need to write data in. I've files named like:
garten_1.jpg
garten_2.jpg
garten_3.jpg
house_1.jpg
house_2.jpg
car_1.jpg
car_3.jpg
Every group of images must be written with the same data.
I've made an argfile.txt where is specified garten*.jpg, house*.jpg and so on.
The I run: exiftool.exe -@ argfile.txt and it works as expected.
The standard output of exiftool show shows something like:
3 image files updated
No file specified
2 image files updated
And sometimes it shows warnings or errors from some image.
The argfile is quite big so if a warning occurs or if a file is not processed, it's difficult to know what file is wrong.
I'm looking for an option that can log every change made to images (image successfully changed or not and what image).
I've tried with verbose options but I can't get it.
-progress option could be useful too but it only works for the first file in argfile.txt
I'm working with windows version.
It's possible to do what I'm looking for?
Thanks.
Try looking at the STDERR output from exiftool. It think this contains the information you want.
- Phil
Thank you for your quick answer.
I know that standard error shows No file specified if a file is not found, but it doesn't show what file it is, so it's difficult find the error.
How can I know which images were modified and which not?
also, how can I view progress when using -@ argfile?
Thanks.
ExifTool gives a "no file specified" message if a file is not specified in your command.
If the file is not found, it says "File not found: FILENAME".
Add the -progress option to see the progress.
Sometimes the answers are so obvious that I wonder if I understand the questions.
- Phil
You're right, if I specify a full file name in the argfile and this file doesn't exists then ediftool shows:
Error: File not found - image.jpg
But as I use * as wildcard (see example in my first post), when no file matchs the expression it shows:
No file specified
Maybe I'm doing something wrong but, as I say in the first post, -progress option doesn't work (exiftool for windows ver. 9.52) when -@ argfile is used; at least in my examples.
Thanks Phil.
Quote from: emporium on February 21, 2014, 03:28:20 PM
You're right, if I specify a full file name in the argfile and this file doesn't exists then ediftool shows:
Error: File not found - image.jpg
But as I use * as wildcard (see example in my first post), when no file matchs the expression it shows:
No file specified
I see. You're making life difficult for me. You somehow want to know if your "garten*.jpg" didn't match any files in a command with other filename arguments. You should just consider yourself lucky because the wildcards are handled by the shell in Mac/Linux, so exiftool wouldn't run if this argument was on the command line (the shell would just say "exiftool: No match."), and wildcards are not expanded from arg files in Mac/Linux because this is handled by the shell. It was my oversight in implementing the Windows filename globbing (because the Windows shell doesn't do it) that resulted in this asymmetry. If anything, maybe I should fix the Windows version to behave like the Mac/Linux version.
QuoteMaybe I'm doing something wrong but, as I say in the first post, -progress option doesn't work (exiftool for windows ver. 9.52) when -@ argfile is used; at least in my examples.
You say your argfile is quite big. Try something simple first to get it working, then figure out what options you are using that break it. Offhand I can't guess what this could be.
- Phil
Thanks Phil.
Your tool saves me a lot of time. It's logical that, if no file matches the expression, exiftool just say "No file specified", but I'm only asking if it's possible to know what argfile entry has affected no files (probably this entry was wrong and I had to modify it). I don't found solution to this in documentation nor in the forum, but I'm newbie to exiftool and I prefer asking before discard a solution.
As If is possible as if not, exiftool is a great tool, it does an excellent work. I'm looking for a workaround, maybe doing a second pass and checking if image values changed.
In relation to -progress option, I have to work with big argfiles, but first I try examples with argfiles of 3 or 4 entries. True example: I create an argfile.txt with 3 entries, each entry uses * wildcard for filename (is this the problem?) and matches two images, then I execute: exiftool.exe -progress -@ argus.txt and the output is:
======== garten.JPG [1/2]
======== garten_1.JPG [2/2]
2 image files updated
2 image files updated
2 image files updated
that is, first entry matches 2 images and -progress option shows progress of them, but next entries don't show progress. Is that normal operation or am I doing something wrong?
Quote from: emporium on February 22, 2014, 04:26:09 AM
I create an argfile.txt with 3 entries, each entry uses * wildcard for filename (is this the problem?) and matches two images, then I execute: exiftool.exe -progress -@ argus.txt
If the argfile contains any
-execute options, then the
-progress in this example will only apply to the first executed command. If you want it to apply to all commands, then you must either add
-progress to these commands or use the
-common_args feature.
- Phil
Thanks Phil, that did the trick.
I've put -progress in argfile before every -execute and now it works like a charm.
Many thanks Phil for this tool and for your work in this forum.