Copy link to clipboard
Copied
Hi everyone. I'm using the latest version of Lightroom Classic (10.1) on Windows 10 but I think I've seen this issue in previous versions as well.
Lightoom provides a "metadata has been changed" flag as a library filter item or when defining a smart collection. When a file has this flag set, I can usually go to Metadata --> Save Metadata to File (Ctrl+S) and it will rewrite the image file and clear the flag. But I am running into a handful of images where this doesn't work. I use Ctrl+S to save the metadata, and alhough I can see the modification time on the file change, the "metadata has been changed" flag remains set for that image.
It happens for several different file types (DNG, TIFF, and PSD). My library settings are ON for "Include Develop settings in metadate inside JPEG, TIFF, PNG, and PSD files", and OFF for "Automatically write changes into XMP".
Is there another setting somewhere I should check? Any insight into why this might be happening?
Thanks.
This bug has been acknowledged by Adobe:
Please add your details to the bug report, and be sure to click Like and Follow at the bottom of the first post. That will make it a little more likely that Adobe will prioritize a fix, and you'll be notified when the bug's status changes.
[Use the blue reply button under the first post to ensure replies sort properly.]
Copy link to clipboard
Copied
**UPDATE** - In the description above, I stated DNG files were sometimes included in the problematic image list. But the menu item Metadata --> Update DNG Previews & Metadata corrects that issue. I still see the problem with some JPG, TIF, and PSD files.
Copy link to clipboard
Copied
Please post your System Information as Lightroom Classic (LrC) reports it. In LrC click on Help, then System Info, then Copy. Paste that information into a reply. Please present all information from first line down to and including Plug-in Info. Info after Plug-in info can be cut as that is just so much dead space to us non-Techs.
Copy link to clipboard
Copied
Will do... thanks! Here's the information:
Lightroom Classic version: 10.1 [ 202012012023-e92d50bb ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Home Premium Edition
Version: 10.0.19041
Application architecture: x64
System architecture: x64
Logical processor count: 12
Processor speed: 3.6 GHz
SqLite Version: 3.30.1
Built-in memory: 32573.1 MB
Real memory available to Lightroom: 32573.1 MB
Real memory used by Lightroom: 1443.7 MB (4.4%)
Virtual memory used by Lightroom: 1622.0 MB
GDI objects count: 704
USER objects count: 2328
Process handles count: 2040
Memory cache size: 89.7MB
Internal Camera Raw version: 13.1 [ 658 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 335MB / 16286MB (2%)
Camera Raw real memory: 336MB / 32573MB (1%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 2560x1600
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No
Graphics Processor Info:
DirectX: NVIDIA GeForce GTX 1050 Ti (27.21.14.5638)
Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: C:\Users\Patrick\Dropbox\Home\Photos\Lightroom\Lightroom Primary Catalog\Library\Lightroom Primary Catalog.lrcat
Settings Folder: C:\Users\Patrick\AppData\Roaming\Adobe\Lightroom
Installed Plugins:
1) AdobeStock
2) ColorChecker CameraCalibration
3) Facebook
4) Flickr
5) HDR Efex Pro 2
6) Nikon Tether Plugin
7) Perfect Effects 8
8) SmugMug
Copy link to clipboard
Copied
This bug has been acknowledged by Adobe:
Please add your details to the bug report, and be sure to click Like and Follow at the bottom of the first post. That will make it a little more likely that Adobe will prioritize a fix, and you'll be notified when the bug's status changes.
[Use the blue reply button under the first post to ensure replies sort properly.]
Find more inspiration, events, and resources on the new Adobe Community
Explore Now