Skip to main content
Inspiring
August 25, 2024

P: "Save Metadata to File" overwrites EXIF tag SubSecTimeOriginal

  • August 25, 2024
  • 22 replies
  • 1643 views

Issue: When I save metadata from Lightroom Classic via "Save Metadata to File", I lose subsecond EXIF metadata that was originally there in the file. This is new behavior, did not happen in previous versions (though I'm not sure exactly when it started).

 

Lightroom Classic version: 13.5 [ 202408062022-6258095b ]

System version: macOS 13.6.9

 

To reproduce:

 

1) Import a photo that has a subsecond creation date—for my test, I used an iPhone photo imported via mobile sync.

 

2) Check SubSecTimeOriginal from the command line:

$ -> exiftool -G -s -SubSecTimeOriginal /Volumes/Media/Photos/Import/Mobile\ Import/IMG_6067.HEIC 

[EXIF]          SubSecTimeOriginal              : 389

 

3) In LrC, run the "Save Metdata to File" command

 

4) Check SubSecTimeOriginal from the command line:

$ -> exiftool -G -s -SubSecTimeOriginal /Volumes/Media/Photos/Import/Mobile\ Import/IMG_6067.HEIC 

Warning: [minor] Bad format (16) for MakerNotes entry 14 - /Volumes/Media/Photos/Import/Mobile Import/IMG_6067.HEIC

 

(That warning does not seem directly connected to the issue, but may be a sign of something unexpected happening...)

 

22 replies

johnrellis
Genius
August 26, 2024

Hmm, following your steps, I don't see the misbehavior -- EXIF:SubjectTimeOriginal is preserved, with Iphone HEICs, JPEGs, and .xmp sidecars of .CR3s.

 

In these cases, I've found the most reliable way of demonstrating a bug is by sharing a small test catalog including the photo(s) illustrating the problem.

 

1. Select one or more problem photos that haven't yet been polluted by Save Metadata To File.

 

2. Do the menu command File > Export As Catalog with just the option Export Negative Files checked.

 

3. Zip up the exported catalog folder and upload it to Dropbox, Google Drive, or similar, and post the sharing link here.

 

Adobe generally won't pay attention unless they can easily reproduce the problem.

Inspiring
August 25, 2024

Clarification on (3): I don't believe the command does anything until you change some metadata first. I think I flagged or unflagged the file as part of this step.