Lightroom: "Edit" criterion in Metadata browser shows incorrect results

  • 3
  • Problem
  • Updated 3 months ago
  • (Edited)
I'd like to sort edited picture on LR Classic CC but it seems doesn't work properly (?)

For example in a folder, there are 11 edited photos (photo modifiés in french) I want to see. 

LR indicates 11 pictures on the menu but shows me 349 pictures instead. 

And if I choose No edited pictures, LR indicates "no pictures available".

Is it something wrong with LR or I don't understand something ?


Thanks 

Lightroom Classic CC 7.3.1 Apple 


Here are pictures explanations : 





Photo of Thierry Gibrat

Thierry Gibrat

  • 4 Posts
  • 0 Reply Likes

Posted 3 months ago

  • 3
Photo of Jim Robertson

Jim Robertson

  • 24 Posts
  • 3 Reply Likes
I had a problem that sounds somewhat the same as yours. I edited a few images in a folder, but LR told they all had been edited, and there were none with no edits.

After a day or so I realised what the problem was.

When I import, I do lens correction on all the files during the import. LR counted that as an edit.

Perhaps your issue is something along the same lines?
Photo of John R. Ellis

John R. Ellis, Champion

  • 3603 Posts
  • 936 Reply Likes
I observe a similar inconsistency. The Library Filter bar says there are 9193 Edited photos, but after selecting Edited, the status bar at the bottom says there 9196 such photos photos (three more): 

The Library Filter bar says there are 19989 Unedited photos, but the status bar shows 19986 (three fewer):



The status bar shows the correct numbers, while the Library Filter bar is incorrect.
Photo of Jim Robertson

Jim Robertson

  • 24 Posts
  • 3 Reply Likes
By any chance or any of the photos stacked?  The status bar does not count stacked photos that are "behind" the top one.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3603 Posts
  • 936 Reply Likes
In my symptoms, I verified all the photos are unstacked.

But even if some were stacked, when Edited is selected, the number to the right of Edited (9193) should match the leftmost number of the status bar but doesn't (9196 of 29182 photos).  It should also match the number of thumbnails actually shown in grid view (9196) but doesn't.

(I didn't actually count the photos in grid view, but when arranged in rows of 9, with a total of 9193 photos, there should be 4 photos in the last row. But in fact there are 7 photos, which corresponds with 9196 photos being shown.)
Photo of Thierry Gibrat

Thierry Gibrat

  • 4 Posts
  • 0 Reply Likes
I try with another folder with only 6 photos.
All are sync with Lightroom CC, all are in collections and two have been developped.

All photos are unstacked.

When I select All, i see 6 photos on the grid (ok) :
When I select Edited I see 6 photos on the grid (not ok)
When I select Unedited LR shows "no photos match the filter"  (not ok)







--> same photos than above (6)

And Unedited :

Photo of Patrick Philippot

Patrick Philippot

  • 337 Posts
  • 58 Reply Likes
Thierry,
Could you please make the following test :
- Select the 6 images.- Hit Ctrl-S in order to update or create the XMP files.- Go to the Metadata menu and "Read metadata from file" (this will not change anything to the actual metadata).
- Check again the edited/unedited status.
Photo of Thierry Gibrat

Thierry Gibrat

  • 4 Posts
  • 0 Reply Likes
Patrick you solve my problem !  
What happened exactly please ?

Thanks !
Photo of Patrick Philippot

Patrick Philippot

  • 337 Posts
  • 58 Reply Likes
Thierry,

I suspect that your problem could be related (or similar) to or be a side effect of another (very old and still not fixed) bug described here :

https://feedback.photoshop.com/photoshop_family/topics/wrong-timestamp-stored-in-lightroom-catalog-c...
The first message is almost unreadable due to a problem with the forum software and I cannot edit it. I re-posted it in a correctly edited form as the 7th message.

There's something wrong in the way LR manages timestamps in the catalog and this started with the first versions. John Ellis and I have given enough information to spot the problem but Adobe don't seem to be interested. I think that this problem is the cause of other issues in Lightroom.
The test above tends to confirm this idea. But I cannot be 100% sure until I get access to the source code  :-))))) .
Photo of Patrick Philippot

Patrick Philippot

  • 337 Posts
  • 58 Reply Likes
Another test that could help spot the problem : Create a new smart collection using the Has adjustments criterion and also the Source | Folder criterion in order to limit the smart collection to the images residing in the above mentioned target folder. It would be interesting to see whether  you observe the same misbehavior.
(Edited)
Photo of John R. Ellis

John R. Ellis, Champion

  • 3603 Posts
  • 936 Reply Likes
Thierry, were your photos synced to LR 7 from LR CC?

My problematic three photos were taken by the iPhone Camera app and synced by iOS LR CC to LR 7:



Patrick's magic spell of doing Metadata > Save Metadata To File followed by Read Metadata From File eliminated the inconsistency:



I suspect this bug arose from the programmer who implemented LR 7's sync with LR CC. With capture dates, she/he didn't understand LR's crufty database schema with respect to timestamps and stored times with the wrong time zone in some of the catalog timestamp fields:
https://feedback.photoshop.com/photoshop_family/topics/lightroom-classic-sync-from-iphone-lr-sets-in...
Photo of John R. Ellis

John R. Ellis, Champion

  • 3603 Posts
  • 936 Reply Likes
"I suspect this bug" => "I suspect this particular instance of the bug"
Photo of Thierry Gibrat

Thierry Gibrat

  • 4 Posts
  • 0 Reply Likes
Thierry, were your photos synced to LR 7 from LR CC?


Let's me explain how my problem occurs : :

I used LR Classic since a while. Three weeks ago, I wanted to migrate my catalog with Lightroom CC to have access photos from my devices and easily shared them. 

The duration of migration on Lightroom CC has been rather short. 

But when I launched Lightroom Classic after, it has been sync all my photos (25K) during days and days ... (and I have a good connection).
I didn't understand why after migration Classic needs to sync all photos. I thinked than migration with CC download all photos on the cloud. 

After syncing my problems occurs... I think a lot of (all?)  photos synced with CC have this problem. 
Photo of John R. Ellis

John R. Ellis, Champion

  • 3603 Posts
  • 936 Reply Likes
So, at least one source of the problem seems to be sync with LR CC not setting some database field consistently.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1019 Posts
  • 331 Reply Likes
I'm seeing a large discrepancy between Edited/Unedited Filter count compared to count above the filmstrip with video files. Checking 'All Photographs' (35,547 files) I noticed that with raw and DNG File Type selected in the Filter there was NO count discrepancy. It only occurs with JPEG, PSD, TIFF, and video files formats.

Photo of John R. Ellis

John R. Ellis, Champion

  • 3603 Posts
  • 936 Reply Likes
Does Patrick's magic spell remove the discrepancy for, say, JPEGs?  (It won't work for video, since LR doesn't save metadata to file for video.)
Photo of Todd Shaner

Todd Shaner, Champion

  • 1019 Posts
  • 331 Reply Likes
Working with different folders it sometimes corrected the Edited/Unedited discrepancy count, made it worse, or no change. These were all JPEG files in separate folders.
Photo of Patrick Philippot

Patrick Philippot

  • 337 Posts
  • 58 Reply Likes
In order to further investigate the case, I created 8 smart collections and compared the number of images in each of them with the results shown when filtering using the metadata tab. Following are the results :

All Photographs                                   10029
=============================================
Has Adjustments                                 3950
+
No Adjustments                                   6079 = 10029 (OK)

Has Edits                                                 5328
+
No Edits                                                     4701 = 10029 (OK)

Has Adjustments OR Has Edits        5328 (meaning that all images having Edits have Adjustments)
Has Adjustments AND No Edits        0 (consistent with above results)

Has Edits AND No Adjustments        1378
+
No Edits AND No Adjustments          4701 = 6079 (consistent with above results)


=============================================
Metadata Filtering (Edit column)
All (2 Edits)                                                10029 (OK)
Edited                                                         4042 (inconsistent)
Unedited                                                   5987 (inconsistent)
=============================================
Now, if some Adobe rep could explain what Edited, Unedited, Has Adjustments and Has Edits mean, I would be grateful. Time to make the LR nomenclature consistent.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3603 Posts
  • 934 Reply Likes
"what Edited, Unedited, Has Adjustments and Has Edits mean"

Has Adjustments: Photo has had one or more changes made to its develop settings (except crop) since it was imported or reset. As a special case, upgrading a photo to the most recent process version counts as an adjustment, even if the upgrade was done as part of updating LR versions.

Has Edits: Photo Has Adjustments or has been cropped. (Introduced in 7.2)

One assumes that, as with all the other criteria, the Filter bar's Edited is intended to have the same meaning as the corresponding smart-collection criterion.

Of all the outstanding feature requests, it seems kind of random that Adobe added Has Edits in 7.2 (for which there were no feature requests published in this forum, I believe).
Photo of Patrick Philippot

Patrick Philippot

  • 337 Posts
  • 58 Reply Likes
For the moment, the only possible reason I see for which the problem may occur is that the hasDevelopAdjustmentsEx field in the Adobe_imageDevelopSettings table of the catalog and the crs:HasSettings in the XMP file are not in sync. So the problem might not be related to the timestamp bug mentioned above, as I first thought. But it can apparently be fixed by using the same "magic spell" :-)) .

If an Adobe developer is reading this, there is a way to verify this :

When the problem occurs, using the filename, look for one of the affected files in the AgLibraryFile table and get its id_local or id_global. Using this ID, look for the image in the Adobe_imageDevelopSettings table and get the value in the hasDevelopAdjustmentsEx field. Then check whether it's identical to the crs:HasSettings field in the XMP file.
This requires writing some SQL code, though. I have no time left for this for the moment.