This is an intermittent issue that was introduced sometime in the last few months.  Running on Windows 10, with the latest versions of Lightroom (13.1) and Photoshop (25.31) The metadata filters at the top of the grid should display 1) the correct count and 2) all the data variables for the images on display.  There are times when they don't, either listing variables that aren't present or failing to show entries that are.  Counts are also off.  Below are examples.   An example of not fully updating: Starting display, with 5 images in grid   Clicking to open the first stack displays the 2nd image in the stack, and updates the “label” filter to show there’s one “No Label” image.  But note that the date filter still shows only 5 images for Tuesday, Oct 3 while Label, Camera, etc show 6.   Here’s an example where one filter fails to update in the other direction.  The grid below once displayed 13 images, but no longer.  Ten blue images, yet the Label column still shows 13 total selected.   I've also experienced cases where an image is added to the grid (by expanding a stack, or returning a new tif from Photoshop), but the filters fail to show the new variables.  For example, a 4 image stack where the top image is "blue" and the underlying three are "No label".  The label filter would start by showing one "Blue" image.  Expand it, and it should update to one "Blue" and three "No Label".  Instead, the "No Label" variable doesn't show up at all. ... View more

"Date" is one of the filter options in Lightroom Classic's library module.  When I take a raw file (with all date fields) and "Edit in Adobe Photoshop 2024", the file that is returned to Lightroom shows up as "Unknown" in that date filter.  A "sync" operation between the old and new files is needed to restore the date information.   This has been an issue for a few months, and wasn't fixed in the last update.   Running LR Classis 13.1, Photoshop 25.3.1, on Windows 10 ... View more

Lightroom Classic 11.3.1 Camera Raw 14.3 Photoship 23.3.1 Windows 10 Pro v21H2 19044.1645 (up to date)   Under normal operations, a raw image in LR is opened for editing in Photoshop using Ctrl-E.  When editing is completed, Ctrl-W in Photoshop saves a tif file which is auto-imported into LR and stacked with the original.   In my workflow, I do this for groups of images:  opening 8-12, processing them all in Photoshop, then returning to LR where their would normally be 8-12 stacked pairs.   Starting roughly 5 days ago, the return from Photoshop occasionally fails and causes LR to hang.  The observed result, in the library module, is: In library, clicking on the '1 of 2' stacking icon should collapse the stack.  It does nothing.  The module is hung The library module fails to auto-import multiple tif files.  My guess is that this breaks after the module hangs.  The files are on disk, just not added to the module. Attempting to optimize and back up on exit fails.  The system looks like its going through the process, but it never completes.  A normal exit works. On restart, everything is fine, though I have to manually 'add' the tif files that failed to import.   Unfortunately, this is intermittent.  Sometimes images return normally.  Sometimes they don't.  But I've had to restart LR 3 times in 5 days as a result of the problem.     This bug has also been reported by another user on this thread:  https://community.adobe.com/t5/lightroom-classic-discussions/lightroom-locking-up-when-returning-from-editing-in-photoshop/m-p/12892140     ... View more

I've crashed this version of Photoshop several times, but this post isn't about that.  It's about AutoRecover, which seems to be missing / not functioning.   I went looking for it when restarting Photoshop after a crash failed to bring back any of my work.   In Windows 10, 'Edit' -> 'Preferences' -> 'File Handling' is checked to Automatically Save Recovery Information (every 5 minutes). But when I went to C:\Users\[my name]\AppData\Roaming\Adobe\Adobe Photoshop 2020\ there was no AutoRecover folder (there is one for previous versions of Photoshop, in their respective folders).  Just in case that was the bug, I created the folder.  Still no luck.  Nothing is being saved there, so after a crash all work is gone.   Note that I'm entering Photoshop from Lightroom ('Edit In' -> Photoshop), if that has anything to do with the failure to backup work.   Is there something different about how Photoshop 2020 is handling recovery info?  Or is this just a bug?   ... View more

This is a recent, intermittent issue (I've used LR for years, and only seen this recently).  I'm running Lightroom Classic CC release 7.5.  When merging photos to HDR, Lightroom will process the images and at the moment it creates the DNG it sometimes outputs an error "Some save metadata operations were not performed".  It then states "Photos have read only access (1)", and lists the new dng file that was just created.  This also happens occasionally when merging to Panorama. To try to debug this, I made sure that the folder containing all my raw files had no read-only files in it (I did this in the properties pop-up for the folder, clearing the "read-only" attribute box and applying that setting to all files in the folder).  This was done BEFORE any HDR merges were performed.  If there's a read-only file involved, its something LR is creating temporarily during the merge. I also checked the files in question after the error (both the raw images and the new dng):  none of them are read-only. I can also state that this doesn't happen consistently.  I had 30 sets of bracketed images that I set to processing all at once in the background (using ctrl-shift-H on each set of 3).  The error popped up for only 2 of the 30 sets. One other unfortunate side-effect of the problem is that it halts all background tasks until its acknowledged.  That's the big reason I'm logging it and not just ignoring it:  I routinely turn a large queue of background tasks loose, then leave and enjoy life elsewhere.  Coming back several hours later to find out nothing has happened is a drag. ... View more