Lightroom: Library Metadata Status filter odd behaviour

  • 4
  • Problem
  • Updated 5 years ago
  • (Edited)
I have LR 4.3. and I'm learning my way around the program slowly. I hope someone can assist me with my understanding of some odd behaviour..

I have 10,134 images in my catalog. I am around 1/3rd through applying keywords to them. I noticed this morning when in the library module, when I applied the Metadata Status filter it said I had around 3,000 whose status had been changed and around 7,000 were up to date. I selected all of the files whose status was 'Has been changed' and hit Ctrl S to save metadata to files. When that was completed, all but 279 had their status change to 'Up to date'.

I thought that was odd so selected the 279 images, hit Ctrl S and watched the status change . 'Has been changed' went to Zero and 'Up to date' went to 10,134. Good, that made sense. Within a couple of seconds though, I sat watching the numbers reverse and the 'Has been changed' status was counting back up to 279 while the 'Up to date' status counted down to 9,855!

I thought I was seeing things so repeated the exercise and the same occurred. I thought perhaps my backup program might be interfering so shut that down and repeated the exercise. The 279 images are scattered through the catalog with files from various folders represented. Same thing again. Any thoughts or assistance with this would be appreciated.

I have looked through D65s Lightroom Digital Workflow but can't see any reference to this through Google or any of my references..

I have been selecting individual folders as well. Make changes to the keywording to bring them up to date. I'll select all, Ctrl S to save and I will watch the counters change. If I select in the metadata Filter Status 'Has been changed' I can see the thumbnails disappear from view as I would expect since they no longer meet the criteria of the filter. When the save is done, there will be no thumbnails in the library filter view as none now meet the 'Has been changed' status. I'll leave the view like that for a few seconds and then some thumbnails will come back into view. It's like a rollback of the changes. Different numbers of thumbnails so I can't say it's always 10 or 20.....

Win7, 64bit, 12gb ram.
Photo of John Murray

John Murray

  • 21 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 4
Photo of Dorin Nicolaescu-Musteață

Dorin Nicolaescu-Musteață, Champion

  • 703 Posts
  • 38 Reply Likes
John, can you check if any of these 279 images had spot removal with partial opacity applied?
Photo of Ino Nimus

Ino Nimus

  • 16 Posts
  • 0 Reply Likes
I can confirm that Lr 4.3 is changing metadata status to "has been changed" simply by browsing through photos in the library module.

Other incarnations of this bug:
http://feedback.photoshop.com/photosh...
http://feedback.photoshop.com/photosh...

It has been arout for quite some time:
http://feedback.photoshop.com/photosh...
Photo of John Murray

John Murray

  • 21 Posts
  • 0 Reply Likes
Dorin, the mystery deepens. I selected one of these images that I was fairly sure wouldn't have those adjustments in the library module (using the 'Has been changed' staus filter. I then selected the Develop module and started browsing through the develop tabs. All of a sudden, I was given the message 'No image selected' and had a grey screen where the image had been. Odd!
I dropped into the Library module again and noticed the image I had selected was no longer in the 'has been changed' set. So, I repeated the exercise with the next image and the same thing happened. Puzzled, this time I selected 10 images and dropped into the develop module. I moved the cursor over the controls in the Develop/basic tab without actually clicking or adjusting any of them. Next thing, the image disappeared to be replaced by the next in the sequence, this then repeated until all ten images had cycled through and I was left with a grey screen again.
I went back to the Library module and those images were no longer in the 'Has been changed' metadata status.
I have discovered an undocumented feature? or a bug? A bug me thinks... Any thoughts anyone?
I have now selected all of the problem images, A set I am looking at now I can confirm had NO adjustments as they were my Sekonic meter calibration images.
The entire 360 odd images are now cycling through with no input from me. I shall see at the end how many still have the 'Has been changed' value set.
Photo of John Murray

John Murray

  • 21 Posts
  • 0 Reply Likes
It stopped after only several images.
Photo of Ino Nimus

Ino Nimus

  • 16 Posts
  • 0 Reply Likes
Do you have the "Automatically write changes into XMP" (Edit>Catalog Settings>Metadata) option checked?
Photo of John Murray

John Murray

  • 21 Posts
  • 0 Reply Likes
No I do not have this option checked.
Photo of John Murray

John Murray

  • 21 Posts
  • 0 Reply Likes
I tried an experiment. I selected a directory that had 34 problem images. I right clicked one of them an did a Metadat/Read Metadata from file selection. I was given a warning it would overwrite the metadata in the file. I accepted and I noticed I had one less problem file.
I selected the rest of the problem files in the directory, did the same and the same happened. Less problem files, So with a big gulp I selected all of the problem file and did the same. The read was successful and I now have the Metadata Status reading All files up to date.

Thoughts anyone? I was pretty sure that all of the files I was reading from had the latest metadata in the xmp so was confident I wouldn't be overwriting with old data. Who knows for sure though.
Photo of Chris

Chris

  • 50 Posts
  • 4 Reply Likes
This bug is getting incredibly annoying! I know that it can happen even if the only change is some added keywords. I notice it happens if I update many pics at one time (I have that auto-xmp writing option turned off). Sometimes I'll get a requester that says it can't write metadata to some files - yet the number of files in the requester is way less than the number that will reappear. Yet this requester doesn't show up every time it happens. To make it clear - I'm talking about the images reappearing with the 'needs updating (down arrow)' badge. It's happening with both jpg AND dng (my camera's native format).

It SEEMS like it may actually be saving all the metadata and that it's only LR that THINKS it has gotten out of sync. If I perform a read-metadata afterwards, I know the keywords have actually been updated for sure.. I'm not 100% certain about other info like develop settings, but I think even that stays correct after the read-metadata.

I SOO hope this gets fixed for the next update. It's not very reassuring at all knowing that all one's edits could be going belly-up at any one of these metadata mismatches. For now I'm just going to try and make sure I save only a few at a time - as often as I can manage doing that. That and making TONS of backups.
Photo of John Murray

John Murray

  • 21 Posts
  • 0 Reply Likes
Out of interest, I use Memeo Backup Premium. You? I wonder if it's a write conflict somewhere. I also have the auto xmp writing turned of.
Photo of Ino Nimus

Ino Nimus

  • 16 Posts
  • 0 Reply Likes
I don't think it has anything to do with any external problem.
Clearly it's a Lr bug.
Some xmp are refractory to writing (one has to save to xmp several times until the changes "stick"), and if the auto xmp writing is turned on one could see this symptom: http://youtu.be/5V86vBd-hLk
Photo of John Murray

John Murray

  • 21 Posts
  • 0 Reply Likes
Ok, one thing that has occurred is that I have identified a faulty ram module on my board. (Asus P6TSE) Since I switched the ram module out yesterday I am not seeing this behaviour occurring. Coincidence?
Photo of Chris

Chris

  • 50 Posts
  • 4 Reply Likes
I'm not using anything else at this point. I'm importing straight from card to LR4.3 using the import dialog, while renaming to a custom preset (3initialsDateYYMMDD_Filename_ISO_Model).

(
And on that note:
If anyone at Adobe reads this: PLEASE have LR put the ORIGINAL camera-filename into the metadata's "Original Filename" field **BEFORE** doing the renaming upon import. Please do this soon. I beg of you. :) =)
)

As Ino says.. It's clearly a LR bug. I have been meaning to check my memory modules, but since I'm not having any other strange issues in any other programs - it's on the 'back burner'.

Also - as Ino seems to be saying... I do think I remember some pics finally 'sticking' after a few "write to metadata"s. But with others, I can do it more than 10 times and it still doesn't save... Well, more to the point - it doesn't clear the down-arrow 'mismatch' icon. At that point is when I'll do a "read metadata" which clears the icon and actually does seem to have saved all the new metadata.

It's just not reassuring that one should have to do this though. It kind of makes LR feel like a beta. :)
Photo of Ino Nimus

Ino Nimus

  • 16 Posts
  • 0 Reply Likes

It's just not reassuring that one should have to do this though. It kind of makes LR feel like a beta. :)

I must disagree!
It feels like alpha...
Photo of John Murray

John Murray

  • 21 Posts
  • 0 Reply Likes
The following bug was reported by me with no response from Adobe. I notice that this bug is still in the Lightroom 4.4 Beta.

I have LR 4.3. and I'm learning my way around the program slowly. I hope someone can assist me with my understanding of some odd behaviour..

I have 10,134 images in my catalog. I am around 1/3rd through applying keywords to them. I noticed this morning when in the library module, when I applied the Metadata Status filter it said I had around 3,000 whose status had been changed and around 7,000 were up to date. I selected all of the files whose status was 'Has been changed' and hit Ctrl S to save metadata to files. When that was completed, all but 279 had their status change to 'Up to date'.

I thought that was odd so selected the 279 images, hit Ctrl S and watched the status change . 'Has been changed' went to Zero and 'Up to date' went to 10,134. Good, that made sense. Within a couple of seconds though, I sat watching the numbers reverse and the 'Has been changed' status was counting back up to 279 while the 'Up to date' status counted down to 9,855!

I thought I was seeing things so repeated the exercise and the same occurred. I thought perhaps my backup program might be interfering so shut that down and repeated the exercise. The 279 images are scattered through the catalog with files from various folders represented. Same thing again. Any thoughts or assistance with this would be appreciated.

I have looked through D65s Lightroom Digital Workflow but can't see any reference to this through Google or any of my references..

I have been selecting individual folders as well. Make changes to the keywording to bring them up to date. I'll select all, Ctrl S to save and I will watch the counters change. If I select in the metadata Filter Status 'Has been changed' I can see the thumbnails disappear from view as I would expect since they no longer meet the criteria of the filter. When the save is done, there will be no thumbnails in the library filter view as none now meet the 'Has been changed' status. I'll leave the view like that for a few seconds and then some thumbnails will come back into view. It's like a rollback of the changes. Different numbers of thumbnails so I can't say it's always 10 or 20.....

Win7, 64bit, 12gb ram.

This reply was created from a merged topic originally titled
LR4.4 Beta still has the metadata save bug....
Photo of Mick

Mick

  • 5 Posts
  • 1 Reply Like
This bug is still alive and well in LR4.4 and also in the current latest version LR5.3 - I've just discovered this posting but have already detailled my experiences here -
http://forums.adobe.com/message/6006039