Lightroom Classic has been arbitrarily changing an images capture date, shifting it by a few hours consistently. It only does this (from what I have gathered) to photos that are synced and accessible in the cloud (i.e. Lightroom Cloud integration via collections), and have edits made to them.
I have been struggling with this on a daily basis. I edit a photo. Suddenly the photo becomes out of order. I realize the capture date's metadata shifts forward by about 4 or 5 hours. I physically change the capture time to be accurate. From here, the new date will either stick (until I edit the photo again), or it will just immediately revert back to the inaccurate date/time, prompting me to replicate the same process until it sticks.
Furthermore, once the catalog reads these files with the corrected date/time, it does not always get read this way via the Cloud-based Lightroom. So to fix this, I then have to delete these files from the cloud and reupload them. I have done this multiple times, dealt with separate difficulties of getting these photos to upload without LrC falling into a constant state of syncing the same 149+ images. I refuse to do this again as it did nothing to solving the problem, except creating separate sync problems. These functionalities are very simple and there's no reason LrC should be changing metadata on its own. I have also ensured that both "Automatically write changes into XMP" and "Write date or time changes into proprietary RAW files" are deselected.
I have noticed this only with film photos I have scanned, where the dates/times were changed to be accurate following import. It's just weird because it is not "reverting" the image to its original date/time from when the images were scanned, but randomly shifting the hours forward by a substantial margin. If it helps, the camera listed for those film scans is "Applied Graphics Technology Digital Link".
I am running Lightroom Classic v. 14.1.1 on Windows 11, build 10.0.22635.4660. I recently updated LrC to 14.1.1 in hopes it would resolve this problem, but it has not.
1
Reply
AdChoices