StarGeek

C:\>exiftool -G1 -a -s -xmp:all -diff "Y:\!temp\x\y\CaptureOne\250617_G9ii_1054061 After.xmp" "Y:\!temp\x\y\CaptureOne\250617_G9ii_1054061 Before.xmp" ======== diff < Y:/!temp/x/y/CaptureOne/250617_G9ii_1054061 Before.xmp > Y:/!temp/x/y/CaptureOne/250617_G9ii_1054061 After.xmp < [XMP-x] XMPToolkit : XMP Core 4.4.0 > : XMP Core 5.5.0 < [XMP-photoshop] Caption : 1 Black-bellied Starling (Notopholia corrusca), bird, Status: confident = 91.0% < [XMP-photoshop] Urgency : Unknown (.. ) < [XMP-photoshop]...

This is Common Mistake #5c You use an equal sign when you want to set a tag to a static value, but you use a greater/less than sign when you want to copy one tag to another. In your command, you are trying to set ModifyDate to a value of ${EXIF:ModifyDate; substr($_,0,4)="2009" not trying to copy the changed ModifyDate back onto the original tag. Try: exiftool '-EXIF:ModifyDate<${EXIF:ModifyDate; substr($_,0,4)="2009"}' ./2009_080823-053923-00_OCF.jpg

Any chance you can give me a before and after xmp sidecar? Now I'm really curious.

XMP can be embedded in a JPEG. Most programs that I know of will usually do this by default Ok, I may be wrong about this. I just updated Darktable and going through the setup, it seemed to indicate that it will be using sidecars by default no matter the file type.

Apologies for the double reply Fixed although that has its own many complexities, such as namespaces which get changed randomly by other programs That shouldn't happen with modern, standards-compliant software. Any program that follows the IPTC Photo Metadata Standard shouldn't be moving data to other namespaces. I'm curious about what programs might be doing that. Also I need something which is embedded in the output JPG XMP can be embedded in a JPEG. Most programs that I know of will usually do...

tl;dr Add the -m (-ignoreMinorErrors) option If you check the IPTC tags page, the third paragralph says This specification dictates a length for ASCII (string or digits) and binary (undef) values. <snip> When writing, ExifTool issues a minor warning and truncates the value if it is longer than allowed by the IPTC specification. Minor errors may be ignored with the IgnoreMinorErrors (-m) option, allowing longer values to be written, but beware that values like this may cause problems for some other...

The metadata in that file is a mess. I'm assuming that it was edited by some program, as there is metadata in there that wouldn't be directly from a camera. Here's the output from exiftool's -validate check. Samsung cameras are really bad at writing proper EXIF data, so I don't know if the problem here originates with the original image or whatever program edited the metadata. Most programs that read EXIF data are robust enough to deal with these warnings, so this mostly goes to show the lack of...

Sourceforge stripped away all the metadata in that file. Can you upload it to something like Dropbox/OneDrive/GoogleDrive and provide a link? Note that if you use Google drive, you have to right click->Share->Share and change the Access to "Anyone with a link" because Google Drive is set to "Restricted" by default.