Hello,
i'm using exiftool from about 10 years. I always used a common arg of about 10 images without any problem.
Yesterday I tried in all ways to process 80 images within the arg. Photos were exported from Lightroom.
This is the command line
exiftool.exe -@ config.args -common_args -overwrite_original
sample args:
-iptc:keywords=mykey
img001.jpg
-execute
-iptc:keywords=mykey
img002.jpg
-execute
-iptc:keywords=mykey
img003.jpg
-execute
the output is this for 15 images
1 image files updated
Warning: ICC_Profile deleted. Image colors may be affected - img001.jpg
After it exiftool change in "suspended" status on windows task manager, and also the command shell stops to show other information.
I tried to process separately the file where the script interrupts it work and it works. I tried to remove the first 15 images from the args and the problem reappears after the next 15.
I have to kill the process from task manually then to start again the command.
exiftool version: 12.2.6.0.
what could be the problem?
Thank you in advance
Please to post the actual args-file instead of just a sample, but making changes if has some personal data.
Because your sample does have an extra -execute at the end, so the sample should look like either...
If "mykey1" stays the same...
-iptc:keywords=mykey1
img001.jpg
img002.jpg
img003.jpg
If "mykey1" changes for each file...
-iptc:keywords=mykey111
img001.jpg
-execute
-iptc:keywords=mykey222
img002.jpg
-execute
-iptc:keywords=mykey333
img003.jpg
But this only conducts 3-files, so its still not like your args-file that "processes 10 images without any problem".
Hopefully, Im thinking its just the extra -execute at the bottom, so you're not having to redact personal data?
Hello Luuk2005, thank you for helping me.
I didn't paste the original arg because the problem happens with any args after the first. only the first 16 images were processed the process goes in pause...
I tried with only a keyword, in any way....
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3354_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3353_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3355_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3356_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3359_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3361_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3362_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3364_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3370_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3368_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3371_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3374_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3373_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3375_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3377_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3378_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3380_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3381_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3382_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3383_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3384_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3385_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3386_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3387_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3390_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3388_10_06_2021.jpg
-execute
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3391_10_06_2021.jpg
I can't explain this problem (unless there is some sort of anti-virus software interfering with the process), but you shouldn't be executing separate commands if you are writing the same information to all files. You can process as many files as you want in a single command.
- Phil
Thank you Phil.
I'm on windows 10 with the windows antivirus (defender).
It's very strange. Is there a way to have detailed log?
You can add the -v3 option, but I don't know if that will help. Try adding exiftool as an exception for Windows Defender to see if that helps.
- Phil
with -v3: same problem.
Replaced windows defender with Panda antivirus: the same.
Rebooted computer and installed latest updates: same
i also started the cmd as "adiministrator" without any change..
it is absurd....
Does it always stop on the same file? If so, could it be that file? Maybe try changing the order of the files.
Also, you haven't mentioned about trying to process all the files in one -execute.
- Phil
Yes, Phil, sure. I tried to save the tag separately on the jpg where exiftool stops and all were ok.
Tried to remove the first 16 photos and changed to other and is the same.
they don't care what the photo is. The problem is the exact amount of 16.
I completed all photos manually removing 16 by 16 all photos completed with success. After the missing photos the script continued for other 16 (with obviously missing photos error becouse i used the same arg file).
Quote from: Phil Harvey on June 11, 2021, 09:01:58 AM
Also, you haven't mentioned about trying to process all the files in one -execute.
How can I do it? Where have I to put this command? Inside the arg?
But is this way I cannot add different tags for each images, this is only to add the same information, right? But I can try only to see how works
This is very confusing, so I used your args-file as a template to create the same 27 /keywords/filenames.jpg
So now Im using the exact same args-file like... exiftool -@ crazy.args -common_args -overwrite_original
Im tested with both v12.11 and v12.26, but after each time, it presented the same 27 results...
-->>exiftool -q -m -r -p "$filename $IPTC:Headline" .
P01_3353_10_06_2021.jpg TEST ALL THE SAME
P01_3354_10_06_2021.jpg TEST ALL THE SAME
P01_3355_10_06_2021.jpg TEST ALL THE SAME
....3391.....................................
Can you verify that the exact command is... exiftool.exe -@ config.args -common_args -overwrite_original
So never including things like "." or other -options from the commandline, because another part thats confusing...
How does the original post get a warning: "ICC_Profile deleted" when its only writing to $keywords ????
So now Im thinking the problem is really nothing about the args-file, but having no ideas what it could be.
But I would still simplify the args-file, since its always writing the same value to the same tag, so like...
-IPTC:Headline=TEST ALL THE SAME
keywords/P01_3354_10_06_2021.jpg
keywords/P01_3353_10_06_2021.jpg
keywords/P01_3355_10_06_2021.jpg
.........P01_3391...............
But it still conducts exactly the same results, so it wont help troubleshooting this very strange problem.
Hi,
The arg file is to add different information to all photos and not the same tags. Only for test, and to simplify the debug i added the same information for all photos.
About the command yes, it's correct as you wrote.
I also tested with two previous version of exiftool and the problem is the same.
I can do a test to all directory and without args to understand if the problem is there. But actually, all seems correct from command line to arg file.
Regarding the output error of profile color, i think is not a problem becouse in that files all tags were added correctly.
If you like to post the exact args-file, I might can do some experiments with it later on.
But if the args-file you already posted, duplicates the same trouble, then not to worry about posting another one.
Because it already conducts perfectly for me, so the trouble would have to be from something else on your system.
But Im still very curious, wondering what this problem is coming from????
I think is worthwhile to attach the exact argfile you are using as Luuk2005 says (don't paste it in, use an attachment). Depending on the text editor you are using, there may be something funny going on there (page breaks maybe?).
Another idea: Exactly how are you running the command? Is the stdout getting piped anywhere? The process could possibly hang if the stdout buffer fills and isn't drained downstream.
It must be something about the way you are running it because many other people are doing the same thing and don't have this problem.
- Phil
Hello,
I added che arg file in attach. tested before to upload with the screenshot where it stops.
it's a mystery and I'm also curious to understand where the problem is.
Thank you in advance :)
The attached args-file did run perfectly for me, so updating all 44 images inside of the keywords folder.
Since you typed from J:\HTDOCS\keywords, Im guessing the files are at J:\HTDOCS\keywords\keywords\ ?
So my only guess is maybe its something about the J-drive, or the images themselves????
I can see nothing wrong with your config file or the way you are running exiftool. So I'm stumped. :(
The only other idea I have is that maybe it hits some memory limitation on your system. If this happens, it shouldn't hang, but could get very, very slow. Did you try leaving it for a long time (say 20 minutes) to see if it eventually processes the next file?
- Phil
Hi Phil,
tried as you asked. over 20 minutes but the shell shows me the same first 16 photos.
About memory, my pc has 64GB of ram and, during this task, only 8,2 GB used. Cpu is i7 6700k.
If you want to see more I can send you my teamviewer ID and you can do a test from remote.
At this point, I'm stumped. The only other thing I can suggest is to try the alternate ExifTool Windows package (https://oliverbetz.de/pages/Artikel/ExifTool-for-Windows) to see if that makes any difference.
- Phil
with the package is exactly the same. Any other idea?
Wow. This is a weird problem.
The only thing I can think of is that you said 14 files in the subject, and 16 files later on. What changed? Are the same number of files processed when you add the -v3 option. How about when all files are processed in the same -execute? Still exactly 16 processed?
- Phil
If all of the posted arg-files created this same trouble, then it sounds like someting on the J-drive not likes to read all of the args-file?
So maybe after x-characters, it stops giving the args-file to exiftool? or inserts a bad-character? or limits applications to x-amount of writes????
My first experiment would be changing all of the tag-values to "something very, very, very, long with at least 100-characters"
So then, if exiftool did write to less files before stopping, you could know its something about the x-characters guess.
Another experiment could be slowly incrementing using how many -execute is used, but really this part should not matter.
Also, this should not help either, but I would try adding -v0 on the commandline, just to see if there was any difference.