exiftool VS exiv2

If you're doing a pipelined bulk processing pass to add metadata tags after extracting them via Speech to text, or have delimited notes in a text file, or ... etc.

You might find ExifTool useful.

It's pure commandline (with a few third party GUI's IIRC) multiplatform and purpose built to display, edit, add media tags to all sorts of AV files.

https://exiftool.org/

> Any method that I've found to clean them up (exporting the originals, deleting them from the library, and then re-importing the JPEGs only seems easiest) will lose all of the years of metadata that I've built up in the library.

The open source tool osxphotos (https://github.com/RhetTbull/osxphotos) can help with this. You can export the JPEG images while preserving metadata using the thrid-party exiftool utility:

`osxphotos export /path/to/export --has-raw --skip-raw --exiftool`

This exports all images that have a raw pair but skips the raw component then uses exiftool (https://exiftool.org/) to write the metadata (keywords, etc.) to the exported JPEG files. You can then re-import these into photos either by dragging them or by running `osxphotos import /path/to/export/*`

Both the export and import commands have many other options for controlling export directory, etc. `osxphotos help export` or `osxphotos docs` to open docs in browser. (Disclaimer: I'm the author of osxphotos)

Check out exiftool.org

Locationator also comes with an optional CLI that can be used to perform reverse geocoding on images from the command line or perform the reverse geocoding and then write the location data to the file's XMP metadata using exiftool. It also comes with two services for doing the same from the Finder or other apps using the Services menu.

Edit: Nevermind, I got it. I used PyExifTool and installed exiftool from exiftool.org.

May not work as not all camera store the serial number in the EXIF, but if you've got exiftool installed you can try running:

I think TIFF has some unique features that makes it more prone to certain security issues[1] compared to other formats, such as storing absolute file offsets instead of relative offsets. So I am not sure TIFF is a good container format, but many camera raws are TIFF-based for some reason.[2]

[1] https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libtiff

[2] https://exiftool.org/#supported (search for "TIFF-based")

I have struggled with this in the past, and I found the utility called exiftool quite useful.

A change causing a crash has been identified in this version, depending on how applications using exiv2 pass data to it: https://github.com/Exiv2/exiv2/issues/2649.

Complete release notes

In addition, this commit isn't available in 0.27.6 yet, so newer JXLs which use Brotli to compress metadata (e.g. files encoded with libjxl 0.7.0) will also show no metadata unless you build exiv2 from the main branch with BMFF (and rebuild dependents of exiv2).

Thanks for the reply. I went a little bit deeper to get more out of images metadata using Exiv2/exiv2. It's getting everything from "exif" to "xmp" tags. And it's fairly maintained ! Only drawback, it's not written in GO. So I'm gonna call it using the cmdline ^^.

some of these appear to not actually have curated tasks. it lists exiv2 for example which links to an issues tag on github, but it's empty https://github.com/Exiv2/exiv2/issues?q=label%3A%22good+firs...

"WebP has been supported since 2016. You're right. I should add JXL. We only need to add a few lines of code to support JXL/bmff. JXL/codestream is still being negotiated by the standards committee and will add ICC support. Exiv2 doesn't provide ICC support for every image format." https://github.com/Exiv2/exiv2/issues/1466

exiv2 is a similar, but different program than exiftool.

Does jhead, exiftool, exiv2, etc., allow me to use a command or a series of commands to accomplish this goal?

Great! Reading through issue 1503 though, this support is for EXIF and XMP data in the "container" version of the format. Support for an ICC profile in the "codestream" format (both bare files and inside a container format file) is in issue 1506 and left for future work. So the support is not complete, but a good step forward for the format.