Skip to main content
R
RoyPrasad
Known Participant
September 26, 2025
Answered

Issues with LensTagger plugin for Lightroom

  • September 26, 2025
  • 2 replies
  • 940 views

Sorry for the lengthy post, but it has to do with the LensTagger plugin for Lightroom. For several years, I've been successfully using this to edit EXIF data for manual focus or legacy lenses adapted to a non-OEM camera (e.g., Leica M lenses on Hasselblad or Sony cameras). The plugin uses exiftool and is not exactly robust, but if you set up the path for exiftool correctly and use the plugin's workflow as designed, it works. After I installed LR Classic 14.5.1, LensTagger stopped working. I endlessly get Error 256 or 512 or some other codes once in a while that I don't understand. About the only thing I can think of is, this plugin uses the /tmp folder to write/read some files, and it looks like there is some issue with the LensTagger plugin logic under macOS sandbox / integration and permissions. (My macOS is Sonoma version 14.6.1.) I've given both Lightroom and exiftool Full Disk Access on my MacBook, but that has not helped. If anyone else has experience with this issue or if the Adobe LR team has any suggestions, kindly reply. Many thanks in advance!

Correct answer johnrellis

Sure, here you go. Was .log, but I had renamed a copy of it to .txt, and this is attached.


"Error: Writing of 3FR files is not yet supported - /Users/royprasad/Selling/Capture/25-0924 Laowa9mm-0051 (X2D II 100C, Unknown).3FR"

 

That error is coming from Exiftool, which doesn't support writing into .3fr files.  Reading the release notes, Exiftool's author Phil Harvey is pretty scathing about Hasselblad's firmware programmers:

https://exiftool.org/ancient_history.html 

 

"Patched FFF reader to be more tolerant of the mess made by incompetent Hasselblad programmers (wrong IFD count for some values)"

 

Lenstagger should do a better job of surfacing such errors to the user.

2 replies

R
RoyPrasadAuthor
Known Participant
September 26, 2025

Thank you for responding. Yes, I have verified that I exiftool via Terminal works. I've tested it on several raw files, one at a time. And yes, I also have the latest version of  exiftool (13.37) and LensTagger (1.9.2), as well as the latest versions of Lightroom and macOS.

R
RoyPrasadAuthor
Known Participant
October 1, 2025

Footnote to my post above: There was a new update to exiftool, 13.38. I updated my macOS to Tahoe 26.0 and installed the new exiftool version, but no luck. LensTagger still does not work, and I continue to get Error 256.

JohanElzenga
Community Expert
JohanElzengaCommunity Expert
Community Expert
October 1, 2025

Most likely you'll have to give EXIFTools 'full disk access' permissions in MacOS. Check that this is enabled.

 

-- Johan W. Elzenga
E
ExUSA
Legend
September 26, 2025

If you use EXIFTool via Terminal does everything work? Do you have the latest version? I use EXIFTool with custom scripts that integrate it with Bridge, and haven't seen any issues under Sonoma, Sequoia, or Tahoe.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices