A

5 Messages

 • 

110 Points

Thu, Dec 17, 2020 10:23 PM

Lightroom Classic: Save Metadata To File doesn't change metadata status, Read Metadata From File doesn't always work

Ever since upgrading to the latest version I've had Metadata conflicts - little exclamation mark in Grid view. I even deleted my catalog of more than 200k images and started again to no avail.  I also synched all of my folders and no difference.

When I click on the exclamation mark I get the message that says that metadata has been changed by another program and Lightroom, even when I have only used Lightroom. When I click to upate the metadata the exclamtion dissapears but comes back very quickly. I made a Quick Collection of all metadata conflict shots - over 6000 - and syched them. The number dropped by a third but then came back to the original total within minutes.

I have lost all of the displayed colored flags in Grid View but can still select various colors in the Metadata panel at the top and get the appropriate shots. When clicking on an individial cell in Grid View I get a thin colored line around the shot which then dissapears when I click on another shot. I get the correct color but no flag.

I have auto save xmp on. I'm also at my wits end. anyone have any ideas? Thanks

Andrew Ptak

Responses

Champion

 • 

5.8K Messages

 • 

100.4K Points

6 m ago

[Update: LR 10.2 fixes the problem with black & white but not with crop angle. -JRE]

After changing a raw to black & white or changing its crop angle, the Save Metadata To File command writes a .xmp sidecar but the photo's Metadata Status remains Has Been Changed.  Only after doing Metadata > Read Metadata From File does the status change to Up To Date.  In addition, Read Metadata From File doesn't correctly read in a changed crop angle that exists in the sidecar.

 

To reproduce:

 

1. Make a new catalog and import one raw that currently doesn't have a .xmp sidecar.

 

2. Edit the raw in Develop and click Treatment: Black & White.

 

3. In grid view observe that Metadata Status is Has Been Changed and the badge on the thumbnail is the down-arrow.

 

4. Do Metadata > Save Metadata To File and observe that Metadata Status hasn't changed.

 

5. Open the .xmp sidecar in a text editor and observe that it records the black & white setting.

 

6. Do Metadata > Read Metadata From File and observe that the photo remains black & white but Metadata Status is now Up To Date.

 

7. Remove the photo from the catalog and delete its .xmp sidecar.

 

8. Import the photo again into the catalog.

 

9. Edit the photo and in the Crop tool type in an angle of 25.

 

10.  In grid view observe that Metadata Status is Has Been Changed and the badge on the thumbnail is the down-arrow.

 

11. Do Metadata > Save Metadata To File and observe that Metadata Status hasn't changed.

 

12. Open the .xmp sidecar in a text editor and observe that it records the crop angle of 25.

 

13. Do Metadata > Read Metadata From File and observe that the crop angle has been lost, but the Metadata Status is now Up To Date.

 

Screen recording: https://www.dropbox.com/s/fi0scv3vauqj5hu/metadata-save-read-bug.2020.10.31.mov?dl=0 

 

Someone else reported that metadata status wasn't updating after saving:

https://community.adobe.com/t5/lightroom-classic/metadata-badge-is-not-updated-after-the-metadata-is-updated/m-p/11538321?page=1 

 

Tested on LR 10.0 / Mac OS 10.15.5.

Note: This comment was created from a merged conversation originally titled Lightroom: Saving metadata not updating status; reading metadata doesn't always work

(edited)

34 Messages

 • 

332 Points

When the development of a photo consists solely of a horizontal adjustment the change can not be written to the metadata of a JPG.  The metadata status remains "has been changed". I guess that behaviour is not as it is supposed to be?

Note: This comment was created from a merged conversation originally titled Lightroom Classic - Metadata cannot be not saved after horizontal adjustment

636 Messages

 • 

11.4K Points

Seems to be working fine here in LrC 10.0/Win10.

- What version of LrC & OS are you using?

- Can you be more specific with what you mean by "consists solely of a horizontal adjustment"?  What are the exact steps you're taking?

34 Messages

 • 

332 Points

Thank you for your immediate reply.

Yes, I am using the same versions (LRC 10 and Win10). 

The steps have been: import, develop, change angle, crop, and after some tries, say done. I came upon two photos in my catalogue with this problem.

Now, I repeated the process with another picture and everything worked fine. There is a difference, though: The problematic photos show only the cropped sign in the lower right corner. The newer one also has the marker for the development adjustments. Maybe that's the reason behind this?

636 Messages

 • 

11.4K Points

What happens if you select the file(s) and press Ctrl+S (keyboard shortcut to save metadata to the file)?

34 Messages

 • 

332 Points

It seems that nothing happens, i. e. after the confirmation that the metadata really should be saved, the confirmation window closes and the down arrow showing that the meta data has changed, is remaining.

34 Messages

 • 

332 Points

Apparently the problem occurs, if the angle is provided manually. In this case there is only information about the cropping and the saving fails.

When using "Auto" instead, there are both symbols, "Photo has been cropped" and "Photo has Develop adjustments" and the saving just works  fine.

636 Messages

 • 

11.4K Points

I can't replicate exactly what you're describing, but I am beginning to think you've tripped over something here.

In my case, there's no indication of a problem, but LrC does not appear to be writing the cropping info to the file consistently when that's the only change that's been made.

With "Include Develop settings in metadata inside JPEG, TIFF, PNG, and PSD files" and "Automatically write changes to XMP" checked, my steps to reproduce were - 

  1. Import file.
  2. Press R to access the crop tool and change only the horizontal and/or vertical crop.
  3. Go back to Library and remove the image from LrC.
  4. Re-import the image to LrC.
  5. Image comes back without the cropping changes applied in step 2.

Variations -

  • It appears if I make any other change along with the crop in step 2 - change the angle, up the color temp by 1, etc. - when the image is re-imported in step 5, the cropping changes are there.
  • If I explicitly save the metadata using the menu or Ctrl+S in between step 2 and 3, when the image is re-imported in step 5, the cropping changes are there.
  • Behavior is similar with files already in LrC that have a crop applied to them.  If I reset the crop without changing anything else, remove the image from LrC, and re-import, it comes in with the original crop applied

I tested with a number of jpg & png files.

A new catalog made no difference.

Resetting preferences made no difference.

We'll have to wait and see if anybody else chimes in here, but something appears to be misbehaving.

34 Messages

 • 

332 Points

Thank you for your thorough testing and detailed reply. So, for the time being it might be best to work around it...

375 Messages

 • 

6.6K Points

@Irma_VG7 , @TomM I have been trying this and have found a problem, but before I go further with it, can you tell me what Import Build Previews setting you are using?

34 Messages

 • 

332 Points

Does this help? Or, if you need something else, where can I find the information?

375 Messages

 • 

6.6K Points

No, not the software build. When you Import into Lightroom Classic, the Import Dialog  has an option in the upper left called Build Previews with choices of Minimal, Embedded & Sidecar, Standard and 1:1.

Which option are you using for Build Previews?

Champion

 • 

5.8K Messages

 • 

100.4K Points

I encountered similar symptoms -- I'll merge the two conversations.

375 Messages

 • 

6.6K Points

@John_R_Ellis, Confirming all of this on my Windows 10 system.

In addition, upon executing step 13, I note that in Develop a Reset Settings has been added to the History, which is obviously wrong.

Employee

 • 

295 Messages

 • 

7.8K Points

Thanks for reporting this.

We have been able to reproduce this and logged a bug for the same.

Thanks,
Smit K
Lightroom Classic team

34 Messages

 • 

332 Points

@anthony_blackett Thank you. It's the Standard Build Previews.

375 Messages

 • 

6.6K Points

@Irma_VG7 Thanks, I have another problem that is related to Embedded & Sidecar previews which I will report separately.

529 Messages

 • 

12.7K Points

Here's another case in point.....

Lightroom Version 10.0

Operating System Windows 10


In some (not all) cases where I have a DNG file where LrC shows the down-arrow icon indicating that the metadata in LrC has changed and the change has not been copied to the file, when I click the icon (or use the menu to save metadata to file). The date/time shown in Windows/10 file manager is not updated and the icon in LrC does not clear. (LR.10.0)

1) Note "metadata in Lrc Has changed" icon
1606431693783.png


2) click icon circled above. Click "Save" in ensuing pop up box
1606431823478.png


3) Saving Metadata progress bar appears for a few seconds then goes away. However, the icon on the image remains and the date/time on the file in File manager does not update
1606432051670.png


The DNG metadata on some images is empty (just says unknown) , but on others with same problem it is filled in. Here is an example of one that is filled in
1606432162729.png

But, the metadata date in LrC gets updated
1606432242314.png

I've disabled all plugin's which didn't help?
Addendum:  After saving Metadata to disk as described above, If I read metadata from disk the tag gets reset (and the image is removed from my smart collection which is based on metadata status)

19 Messages

 • 

250 Points

This is an old problem that continues to plague me in Lightroom. I'm currently running Build [202008061458-dbb2971e] under Windows 10, but the same issue occurred in earlier versions and under Windows 7. There have been other threads about the issue going back at least to 2011.

Routinely, for some (but not all) images, the "Metadata file needs to be updated" icon does not disappear after writing the metadata to the XMP sidecar file by either pressing Ctrl-S or clicking on the icon. I can confirm that the XMP file was updated by checking the timestamp in Windows file explorer.

In these two screenshots you can see that image 0504952.cr2, the selected one, shows the metadata needs to be updated icon, while the file exlorer snippet shows the timestamp of the XMP file to be current today (12/9/2020).

It appears the metadata is being updated, but the icon is not. I can examine the contents of the plain-text XMP file in Notepad++ and see that the item I'd updated in Lightroom metadata has indeed been written to the file.

It doesn't seem to matter whether I select one image to write out the metadata or several hundred. Sometimes the icon gets updated (going away) and sometimes it doesn't.

Closing, then re-launching LR still shows that the metadata needs to be written to the file.

In my workflow, I'll make changes to one or many image in Lightroom and then manually use Ctrl-S to write out the metadata changes (rather than have LR do it automatically with every edit).

In case it helps someone at Adobe figure this out, here's my System Info report:

Lightroom Classic version: 9.4 [ 202008061458-dbb2971e ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.18363
Application architecture: x64
System architecture: x64
Logical processor count: 4
Processor speed: 3.3 GHz
SqLite Version: 3.30.1
Built-in memory: 24551.0 MB
Real memory available to Lightroom: 24551.0 MB
Real memory used by Lightroom: 2582.5 MB (10.5%)
Virtual memory used by Lightroom: 2561.8 MB
GDI objects count: 762
USER objects count: 2636
Process handles count: 1916
Memory cache size: 205.0MB
Internal Camera Raw version: 12.4 [ 555 ]
Maximum thread count used by Camera Raw: 3
Camera Raw SIMD optimization: SSE2,AVX
Camera Raw virtual memory: 207MB / 12275MB (1%)
Camera Raw real memory: 208MB / 24551MB (0%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1200
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No

Graphics Processor Info: 
DirectX: NVIDIA GeForce GT 630 (23.21.13.8813)

Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: I:\Turner_LR5_Catalog\Turner_LR5_Catalog-3-2.lrcat
Settings Folder: C:\Users\Mark\AppData\Roaming\Adobe\Lightroom

Installed Plugins: 
1) AdobeStock
2) Animoto
3) Any Filter
4) Aurora HDR
5) ColorChecker Passport
6) Export to Photomatix Pro
7) Facebook
8) Flickr
9) HDR Efex Pro 2
10) jb Search Replace Transfer
11) jf Collection Publisher
12) LR/Enfuse
13) LR/Instagram
14) LR/Mogrify 2
15) LR/Transporter
16) Luminar 4
17) Magic Export
18) MyKeyworder for Lr
19) Nikon Tether Plugin
20) Perfectly Clear Complete v3
21) ProSelect Album Builder

Config.lua flags: None

Adapter #1: Vendor : 10de
 Device : f00
 Subsystem : 35441458
 Revision : a1
 Video Memory : 2000
Adapter #2: Vendor : 1414
 Device : 8c
 Subsystem : 0
 Revision : 0
 Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: LR5x42
Direct2DEnabled: false
GL_ACCUM_ALPHA_BITS: 16
GL_ACCUM_BLUE_BITS: 16
GL_ACCUM_GREEN_BITS: 16
GL_ACCUM_RED_BITS: 16
GL_ALPHA_BITS: 0
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 4
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: GeForce GT 630/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.60 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.6.0 NVIDIA 388.13
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_polygon_offset_clamp GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_bit_encoding GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_spirv_extensions GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_filter_anisotropic GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_KHR_parallel_shader_compile GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_blend_equation_advanced GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_query_resource GL_NV_query_resource_tag GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_rectangle_compressed GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NV_shader_thread_group GL_KHR_blend_equation_advanced GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control 

Note: This comment was created from a merged conversation originally titled Lightroom Classic: Icon "Metadata file needs to be updated" still shown after saving metadata to files

529 Messages

 • 

12.7K Points

I have this problem as well but not limited to files with XMP side cars.  also happens to files with embedded XMP data such as JPG's

19 Messages

 • 

250 Points

Also happens with PSD files.

202 Messages

 • 

1.9K Points

This problem can appear if the file are on a NAS. in fact there is small difference between the time recorded in LR and the time on the NAS because of read/write buffers. This was existing with Synology and there was a post explaining how to solve it but I don't remember were it was. You should check not h/m but seconds in the property of the file and compare to the second recorded in LR

19 Messages

 • 

250 Points

That's not my issue. All my photo files are on internal hard drives inside my Windows box. I use a NAS for backup, but that's not what LR is looking at.

3 Messages

 • 

78 Points

I'm having the same problem! The progress bar appears, but the 'needs to be updated' icon reappears. This is with a <ctrl><s> or clicking on that icon.

This is a long shot, but I noticed this the same time as I ran across that lovely problem with the new camera raw and 3rd party LUTs when opening a LRC developed file in PS.

529 Messages

 • 

12.7K Points

Mine are on a WD external hard drive (not a NAS)

10 Messages

 • 

140 Points

I have the same problem since LR 10.0, occuring on my local harddisk. But, I mapped the folder with my images to a network drive and used this always in LR. This makes it easier for me to switch between 2 different computers. I'm doing this for a long time now, without any problems, until LR 10. Since LR 10 I had the problem with wrong update status and tried now to not use the real folder instead of the mapped network drive. And it seems to work now...

Best regards

Friedemann

10 Messages

 • 

140 Points

NO! Please excuse me, the problem still exists... As mentioned on the local harddrive, without a mapped network drive....

Champion

 • 

6.5K Messages

 • 

109.6K Points

Are you on 10.1 now @friedemann_schmidt , or still on 10.0?

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

67 Messages

 • 

1.2K Points

On 10.1 here - have same issue. Metadata status icon does not change regardless of saving it. OS 10.15.7

Professional Photographer at Tansley Photography

202 Messages

 • 

1.9K Points

4 m ago

I have see type of conflict several time with the XMP writing on because of a small difference between the time stored in the lightroom Catalog and the xmp file time. This can happen with some NAS because of writing cache processes. If you have one photo with the exclamation mark check the last modified time in Lightroom and then open the  explorer (finder) and check the time of the xmp file to see if there is a difference

5 Messages

 • 

110 Points

4 m ago

Thanks. I was pretty excited when I read your answer because I have also just migrated my work to a NAS from a DAS based unit and your answer made sense. Alas, this isn't the issue because I just created a catalog on my local hard drive with a few thousand images to test this out and I still have the same problems. Hmmmm.

It was a good thought you had but unfortunately I'm still at square one here. It is so frustrating.

Andrew Ptak

5 Messages

 • 

110 Points

@Andyptak 

Bump. Anyone else have an idea?

Andrew Ptak

202 Messages

 • 

1.9K Points

have you check the time recorded in the catalog and the time of the xmp ? 

3 Messages

 • 

90 Points

4 m ago

After editing a picture in Lightroom Classic 10.1 (on Windows 10), I clicked on the button next to "Metadata Status" to save the metadata. However, the status immediately changed back to "Has been changed" and the icon with the text and down arrow that indicates unsaved metadata continued to appear in the upper right corner of the thumbnail, even after repeated clicking on it.

This seems to happen only with pictures that are treated as black and white. I am seeing this with raw files (Nikon .NEF) and with TIFF files but not with JPG files from an iPhone. It probably started happening when I upgraded to Lightroom Classic 10.1.

When I change the treatment of the picture from "Black and white" to "Color" and save the metadata, the save is successful and the "Metadata file needs to be updated" icon disappears.

Note: This comment was created from a merged conversation originally titled Metadata status stays at "Has been changed" for black and white images in Lightroom 10.1

67 Messages

 • 

1.2K Points

4 m ago

As someone else mentioned - this appears to be an issue that only affects BW images. 

I'm on 10.1 on a Mac running OS 10.15.7  - colour images I can save the metadata with Cmd + S, but BW images, it won't save (or at least the metadata status icon will not change to show it's been saved). 


Professional Photographer at Tansley Photography

67 Messages

 • 

1.2K Points

Interestingly - I just turned on Auto Write to XMP - and the icon disappears.....

Most of us have this turned off, as it used to slow down processing in Develop Mode. I wonder if it still does?

Professional Photographer at Tansley Photography

Champion

 • 

5.8K Messages

 • 

100.4K Points

"it used to slow down processing in Develop Mode."

Since LR 3 was released, I haven't seen any reports on these forums that Automatically Write Changes Into XMP slows down LR in any noticeable way. I've always had it enabled and I've recommended to others to enable it.

Champion

 • 

5.8K Messages

 • 

100.4K Points

"this appears to be an issue that only affects BW images."

It also affects raws with non-zero crop angles. See the first reply above.

1 Message

 • 

62 Points

For me it is also only B&W images. I actually converted to color and the metadata saved without trouble. Also, the DNGs are updating according to finder, just LR doesn't recognize they have.

13 Messages

 • 

266 Points

3 m ago

I have a smart collection in Lightroom Classic v10 (Windows 10) to gather images I've made changes to but have not saved (I do not auto write changes to XMP). When I'm ready, I open this collection, select all the photos and do Ctrl-S to save metadata to file. Usually this works fine.

Sometimes the save happens but LRC still tells me the metadata has been changed in LR but not saved. So I select again and choose Metadata>Read metadata from file. Often this works and the images clear the collection.

However, sometimes I have "stubborn" files that no matter how many times I repeat the above steps the metadata remains unsaved. And this can be pictures that I have not changed in my recent session, just opened the folder where those files reside.

Even after quitting LRC and shutting down the computer overnight, the "unsaved" images remain. This has continued with various photos through multiple LR upgrades.

I appreciate any thoughts/suggestions.

Thanks!

Note: This comment was created from a merged conversation originally titled Lightroom Classic: Problems saving to XMP 10.1

Adobe Administrator

 • 

10.1K Messages

 • 

135.9K Points

Are the 'stubborn' files stored on a NAS?

Adobe Photography Products

Quality Engineering - Customer Advocacy

5 Messages

 • 

110 Points

RIKK - does NAS storage make a difference in this? I'm having similar issues with unresolved changes and have recently moved to a NAS.

Andrew Ptak

Champion

 • 

5.8K Messages

 • 

100.4K Points

Andy, when you select a photo whose metadata-status badge indicates a conflict or that the catalog data needs saving to disk and do Metadata > Save Metadata To File, does the status badge go away, or does it often come back?

5 Messages

 • 

110 Points

Hi John. It goes away but usuallycomesback again. Sometimes all it takes is to go in to Develop mode - do nothing - and come back to Library and that makes it come back. 

Today I went to close LR after it sitting idle for about 4-5 hours and got a message that said changes hadn't finished writing to .xmp yet. I had done very little work today and it had sat for hours. What did it still have to change for Pete's sake? Should have finished hours before. 

All of these metadata conflicts and issues just started very recently 

Andrew Ptak

Champion

 • 

5.8K Messages

 • 

100.4K Points

Thanks for the details.

5 Messages

 • 

90 Points

2 m ago

Since the update to Lightroom Classic Version 10 reading crop metadata from .XMP sidecar files for .NEF RAW files fails reproducably. 

My workflow is as follows: 


I ingest all my .NEF files with Photo Mechanic which writes .XMP sidecar files to the .NEF RAW files. It adds IPTC metadata information on a usual level like description, headline, keywords, event, location etc. Nothing unusual here.


After ingesting I still use Photo Mechanic for image culling where I assign the star rating (1 up to 5) and do some cropping which is faster than in Lightroom Classic. Afterwards I switch to Lightroom Classic and synchronize the folder by right clicking on the folder in the Library module. I let Lightroom search for new pictures and changes in the metadata. After that it shows metadata conflicts for the photos where I did metadata changes in Photo Mechanic.


The following step was working for many years in Lightroom Classic: I let Lightroom read all metadata for the conflicted files from the .XMP sidecar files (clicking "Read Metadata from File"). These hold star rating and crop information. This data was always updating in Lightroom perfectly well without any issues. Now since Version 10 Lightroom updates only the star rating. All crop information or color codes are not updated in Lightroom catalog at all on "Read Metadata from File". This is a bit annoying as it was working perfectly fine for years prior to V10.

What works instead ? If I remove that folder which holds the photos with changed crop metadata from Lightroom catalog and let this folder be imported again into Lightroom it imports all metadata perfectly fine again. Not only star rating but also color labels and the expected crop information shows up correctly in the lightroom catalog. All that is quite time consuming as Lightroom is creating the preview and smart preview data again.

I additionally checked Adobe Bridge here as well. It is working perfectly fine. When I access photos with .XMP sidecar files with crop information it shows that even in its previews correctly. So everything is fine with Adobe Bridge.

Just as a side note here: The behaviour of Lightroom was exactly the same for photos stored on local hard drives or NAS drives.

There were only .NEF and .XMP and no JPG files in these folders.

Versions currently used here:
Lightroom: Version 10.1.1
CameraRaw: Version 13.1
Adobe Bridge: Version 11.0.1.109

It seems that Lightroom does not respect the following crs: XML tags when the metadata is intentionally read back from the .XML files: These tags are added by Photo Mechanic. The crs: tags are common and look reasonable in the .XML as the following site suggests: https://www.adobe.io/open/standards/xmp.html#!adobe/xmp-docs/master/XMPNamespaces/crs.md

   crs:HasSettings="False"
   crs:AlreadyApplied="False"
   crs:HasCrop="True"
   crs:CropLeft="0.049250"
   crs:CropTop="0.049164"
   crs:CropRight="1.000000"
   crs:CropBottom="1.000000"
   crs:CropAngle="0.00"
   crs:CropUnit="3"
   crs:CropWidth="3.000000"
   crs:CropHeight="2.000000"
   crs:CropConstrainToWarp="0"

When a photo is not cropped by Photo Mechanic it does not have these crs: tags in it.

Thanks for some comments if someone else can reproduce this. In my case this behaviour persist since V10 and is  reproducable each time. It is definitely not related to Photo Mechanic as this was not updated for a longer while and reading the crop data works if photos are freshly imported in Lightroom. Only reading metadata from files fails for crop metadata.

I feel this is a bug in Lightroom and I do hope someone can chase it down and if approved create a bug entry for Lightroom classic V10.

I can provide some example and sidecar files for that issue if needed.

Thanks a lot,Heiko

Note: This comment was created from a merged conversation originally titled Lightroom Classic V10 does not read crop metadata in .XMP sidecar files on "Read Metadata from File"

5 Messages

 • 

90 Points

@TomM Yes somehow, however I have seen that thread previous to my post and concluded that the described issue is more on the loss of metadata when writing metadata changes out to disk when files are located on NAS drives which afterwards results in inconsistent indication whether metadata is up to date or not. Possibly both issues might be having similar/same root cause.

To me it looks that handling (reading and possibly writing) metadata from sidecar files seems to be somehow broken since V10.

What I forgot to mention: I'm running Lightroom Classic on Windows 10.

Champion

 • 

5.8K Messages

 • 

100.4K Points

The bug report TomM linked to describes the same issue -- crop information isn't properly read by the Metadata > Read Metadata From File command.  The recipe for reproducing the bug doesn't involve NAS. 

Adobe acknowledged the bug on November 1, 2020, which means that it has been filed in their internal tracking system.  But that doesn't indicate when they'll prioritize a fix. They have their hands full with the performance/crashing issues and lots of other bugs also introduced in LR 10 -- a real mess.

(edited)

3 Messages

 • 

78 Points

2 m ago

There may be a good reason for merging conversations, but in this instance it is extremely frustrating! I have been fighting with this icon/badge/whatever not being updated ever since LR 10x got updated. I am NOT using a NAS. It doesn't matter what changes I've made (or have not made). Some of the problem files are from years ago and have not been touched. I found them on one of my searches for unsaved metadata changes. Previously they had not been flagged by those searches. These files are on my INTERNAL hard drive, NOT a NAS. Sorry, but reading this topic has been a major exercise in frustration.

Champion

 • 

6.5K Messages

 • 

109.6K Points

I get that it can be frustrating to see other people reporting the same issue, but merging conversations is a good thing because it combines all of the votes and conversation so the engineers can see all of the different reports in one place, so they can hopefully catch all of the different variations. I verified it without a NAS too (not remembering this thread existed), and uploaded a sample catalog to internal bug LRD-4205847 yesterday. 

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

3 Messages

 • 

80 Points

2 m ago

Note: This is a reproduceable bug. It seems to be present in v10x of LR Classic, but not in older v9x versions

ISSUE: Crop settings aren't maintained when IPTC metadata is updated in another program.

REPRODUCABLE STEPS:

  • Open a JPG photo in LR Classic
  • Crop, rotate, and apply a LR Develop preset
  • Metadata\Save Metadata to File (this saves the settings within the JPG file itself)
  • Open the photo in Photo Mechanic
  • Enter text in an IPTC metadata field, such as a Caption or Keyword
  • Returned to LR Classic and did a Metadata\Read Metadata from File to update the IPTC metadata
  • The Caption/Keyword text updates appear

However, the crop setting is lost and reset to the 'As-shot' setting

Older LR Classic version works OK
This issue only happens in LR Classic v10. An Adobe tech support agent asked me to install an older v9.4 version of LR Classic, and the issue IS NOT present in that version. The crop settings are maintained when reading updated IPTC metadata.

Note: This comment was created from a merged conversation originally titled Lightroom Classic: Crop settings are reset when metadata is changed

Champion

 • 

1K Messages

 • 

15.8K Points

@umbighouse 

Your issue seems similar to these.

Adobe Administrator

 • 

10.1K Messages

 • 

135.9K Points

1 m ago

Updates to Lightroom Classic and the Lightroom Ecosystem products for Desktop, Mobile and Web were released today and contain a fix for this issue.

Please refresh your Creative Cloud application and install your update when it becomes available. Thank you for your patience.

Adobe Photography Products

Quality Engineering - Customer Advocacy

Champion

 • 

1K Messages

 • 

15.8K Points

1 m ago

@Rikk 

There were two issues with the Save Metadata discussed in this thread.  The issue with B&W was resolved but the similar issue with Crop and Rotate is still a problem in 10.2.  

(edited)

5 Messages

 • 

90 Points

1 m ago

Just checked out as well that the Crop and Rotate issue on the latest Lightroom Classic V10.2 still persist.

Champion

 • 

5.8K Messages

 • 

100.4K Points

1 m ago

I observe the same as Robert Somrak: LR 10.2 fixes the problem with black & white but not crop angle. The bug recipe posted above still fails with crop angle:

https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-save-metadata-to-file-doesnt-change-metadata-status-read-metadata-from-file-doesnt-always-work/5fdbda743a4b973cd0edccf0?commentId=5fe43e6e1544d52a90aa05d2 

Adobe Administrator

 • 

10.1K Messages

 • 

135.9K Points

1 m ago

Correct: The fix has been made for the BW issue but not the crop. That is filed on a different bug. Though it appears related it is a separate issue. 

Adobe Photography Products

Quality Engineering - Customer Advocacy

3 Messages

 • 

80 Points

@Rikk What's the other bug filed for the crop issue? I posted details about a reproduceable bug with crops not being honored (and 'reset') when doing a Read Metadata command in LR Classic. It looks like it was merged into this thread- see the details below. 
- - -
Note: This comment was created from a merged conversation originally titled Lightroom Classic: Crop settings are reset when metadata is changed

13 Messages

 • 

266 Points

1 m ago

I upgraded to 10.2. In my smart collection that contains images with unsaved metadata I have 5 images, 4 TIFF and 1 PSD. All have the arrow indicating changes in Lightroom Classic that have not been saved. 1 image is originally a raw file (PSD), the others are scans (TIFF). Running both Save Metadata to file and Read Metadata from file produced no change in their metadata status. None of them have a b&w treatment. Three of the TIFF files have a crop applied. Other images that appear in the smart collection (mix of raw, jpg, tiff, psd) do save appropriately. But some like these files can linger for weeks or months and then one day the save or read "works." Apparently something is still not right even though this problem is listed as a fixed bug in the announcement.