I've been using a Lightroom plugin called Lenstagger for the last couple years. Some time ago (possibly with the launch of MacOS Catalina), it stopped working. So it has been about a year, and I figured that there would be an update from Apple in one of the newer version of MacOS that would restore compatibility. Today I tried uninstalling and reinstalling the plugin as well as ExifTool itself. Within the plugin GUI, I tried various file paths to ExifTool but cannot get it to work. Any help would be appreciated.
System: MacBookPro (2015)
OS: 10.15.6
LR Classic Version: 9.2.1
Unfortunately, I am not proficient in command line usage, but I did attempt to copy and paste the following from Lenstagger to try in a Terminal window:
exiftool -Lens="Jupiter-8M" -LensSerialNumber="7650785" -LensModel="Jupiter-8M" -LensType="Jupiter-8M" -FocalLength="50" -MaxApertureValue="2" -FNumber="2" "/Users/andy/Pictures/PM Import 2/Jupiter-8_20200908_17_221554_20C_5476.NEF" -v0 > /tmp/excmd.log
And what messages did you get from your command? To the Terminal, and to excmd.log.
- Phil
No message in Terminal.
How do I check excmd.log?
Just remove this from the command and it will go to the terminal: > /tmp/excmd.log
- Phil
======== /Users/andy/Pictures/PM Import 2/Jupiter-8_20200908_17_221554_20C_5476.NEF
1 image files updated
So the command line entry seems to have modified the file. Any idea why the Lenstagger plugin can no longer achieve this result?
I don't know where LensTagger expects to find ExifTool. You should ask the LensTagger people about this one.
- Phil
Yes, that was actually my first move. I think the developer of that plugin has lost interest in supporting it. Apparently it is no longer a good revenue stream for him (though I still continue to donate to him). In any case, it has forced me to consider using ExifTool in its purest form, but I am still having trouble. Sometimes the file is modified, sometimes it isn't. I'm trying to be careful with syntax, file path and filename accuracy, but in the end, I'm only mimicking what I see rather than really understanding the structure of the code. Can I trouble you to describe the basic framework (and the limits of what can be included) in a command line entry?
If you don't pipe the output to a file (ie. drop the "> /tmp/excmd.log"), then you will see any warnings or errors that may occur. This should help you determine which commands failed and why.
I don't know what you mean by the basic framework of a command-line entry, but this may help:
The ExifTool application documentation (https://exiftool.org/exiftool_pod.html) lists all of the available options and gives a number of examples. The only thing it doesn't do is explain the shell features, like output redirection.
- Phil
You might also take a look at hvdwolf java based GUI (https://exiftool.org/forum/index.php?topic=11355.msg62048#msg62048) to see if that might cover your needs.
Phil,
It has been more than three decades since I really thought about any kind of coding. You could say that I have become crippled in that area by GUI applications. Luckily, I have neither the need nor the desire to do anything very complex. I just want to be able to correctly tag the images captured with non-chipped lenses.
exiftool [OPTIONS] -TAG[+-<]=[VALUE]... FILE...
So, if I understand correctly, addition of -overwrite_original_in_place before FILE is needed because certain tags, such as Fnumber are already populated and/or not normally intended for modification.
Andy
Hi Andy,
Quote from: acnomad on September 09, 2020, 11:41:53 AM
So, if I understand correctly, addition of -overwrite_original_in_place before FILE is needed because certain tags, such as Fnumber are already populated and/or not normally intended for modification.
No. It is to preserve some filesystem attributes if necessary. See the documentation here (https://exiftool.org/exiftool_pod.html#overwrite_original_in_place).
- Phil