Save Metadata Oddities

[Ian Farlow]

Okay, so I have Lightroom set to not automatically write changes back to XMP/DNG. As I go through my workflow (import, cull, add metadata, etc.) I end with CMD-S to save metadata back to my DNG files. Everything seems to work (progress bar moves from left to right and then goes away), but when I scroll through my thumbnails, I see that some images still show a metadata changed badge and the metadata status in the metadata browser on the right hand side of the screen shows that there is unsaved metadata.

To make things more confusing, some of these images show a down-arrow-like badge and some show a thunderbolt-like badge, and these images show either "has been changed" or "..." in the metadata status field, respectively.

Very odd, very frustrating, and I can't make it stop behaving this way. Selecting all images and hitting CMD-S doesn't make any difference. Selecting one afflicted image and hitting CMD-S might work, or I might have to hit CMD-S twice to make the status reflect no changed metadata (both the badge and the text indicators).

All changes are within Lightroom and are not as a result of edits external to Lightroom.

 

[Ian Farlow]

Update: It appears that if I use the up/down arrows to move from thumbnail to thumbnail that the status is somehow altered. In other words, if the highlighted thumbnail is at the bottom edge of the thumbnail window, and I hit the down arrow, the next thumbnail to appear below is guaranteed to have either the down-arrow-like badge or the thunderbolt-like badge appear. I hit CMD-S (usually have to hit it twice) and the status finally shows no changes in metadata.

Argh...

 

[Ian Farlow]

Okay, well I figured out what the "..." and thunderbolt-like badge mean: reading/writing metadata. But, once that is done, the badge changes to a down-arrow-like badge, and the status reads "has been changed." I have saved metadata over and over, and it doesn't seem to matter. This happens with newly imported images from yesterday and with old images imported months or years ago.

 

[Ian Farlow]

I may have fixed my issue. It seems, after spending the better part of my late evening working through this problem, that I have stumbled across a very bad anomaly within Lightroom.

I have 2'75 RAW images in my Lightroom database which results in several dozen "pages" of thumbnails based on the size of the thumbnails that I have set. I selected all of the thumbnails using CMD-A. I then set the color label of all thumbnails to purple (which I have titled "temp"). I saw on the first "page" of thumbnails that the thunderbolt-like badge appeared, and after a few seconds, it was replaced with the down-arrow-like badge. Fine. That was expected. What wasn't expected was what I found when I hit PAGE-DOWN. The next "page" of thumbnails showed the thunderbolt-like badge, and as before, after a few seconds it was replaced with the down-arrow-like badge.

Huh? So I hit the PAGE-DOWN key again. Same thing. Again. Same thing. Again. Same thing...

Lightroom will not update the status of the thumbnails unless they are visible on screen. This is a huge issue as I see it. As a result, I have had to PAGE-DOWN and PAGE-UP through my thumbnails several times to ensure that all thumbnails show the proper status that the metadata changed. Then I used CMD-S to save the data, but I once again had to use PAGE-DOWN (or PAGE-UP) to show each and every thumbnail on screen before any changes to the metadata were registered.

This is a disaster, because now I am not certain that metadata changes are registered to the thumbnails (and subsequently to the DNG files when saved) without first looking at each and every thumbnail to ensure the badges are displaying correctly. I am convinced that this bizarre behavior is what led to the random thumbnail not actually saving the changes to metadata, and may even have something to do with the metadata browser not updating properly to show recent changes to files.

Comments? Questions?

 

[Ian Farlow]

Oh, and this issue also applies to other changes, such as when changing the white balance setting. Part of my workflow is to set the white balance of newly imported images. I use CMD-A to select all thumbnails, and then apply a white balance setting. Unfortunately, I have to PAGE-DOWN to each and every thumbnail to make sure the change is actually applied.

 

[Ian Farlow]

Nope. Never mind. While this issue I described above does exist, my eye-popping and exhausting work to correct the metadata issues has been in vain. I just checked some random thumbnails, and they show that metadata has been changed, even though I inspected each and every thumbnail and saved using CMD-S several times. I even optimized the database several times.

Nothing is working to correct this issue. I'm tired, frustrated, and ready to call it quits. I feel like I can't trust that Lightroom is doing its job saving metadata and image processing steps as a result of all of this.

 

[Ian Farlow]

Now I'm beginning to wonder if I literally have to select each and every thumbnail and wait for the metadata status to update (which takes roughly five seconds). Holy cow... at that rate, I will be sitting at my computer begging Lightroom to work properly for almost three hours.

Three hours of clicking the right arrow key 2'75 times really does not appeal to me at all.

Somebody please have a solution for this nightmare. :shock:

 

[jslabovitz]

I've noticed something similar.

I don't shoot digital, but film, and so the capture time of the imported scan files are the date the negative was scanned, not when the shot was actually captured. So after scanning, I will select a bunch of images and change the capture time (Metadata > Edit Capture Time). Fairly regularly, the capture time does not get saved. Sometimes, a totally bogus time is saved instead!

I've noticed that, in general, metadata settings lag behind the displayed information.

Hope this helps, or least makes you feel more sane!

 

[Kiwigeoff]

Now I'm beginning to wonder if I literally have to select each and every thumbnail and wait for the metadata status to update (which takes roughly five seconds). Holy cow... at that rate, I will be sitting at my computer begging Lightroom to work properly for almost three hours.

Three hours of clicking the right arrow key 2'75 times really does not appeal to me at all.

Somebody please have a solution for this nightmare. :shock:

Have you thought about using the autowrite, that's what I use with no issues seed or otherwise.

 

[Victoria Bampton]

Ian, you've been talking to yourself for hours! Go put your feet up and have a beer or something!

I've come across problems with XMP writing in Leopard that I never had in Tiger, so something's definitely different. There's an easy solution though. Delete the xmp's and then write fresh ones. Works a treat.

 

[Ian Farlow]

These are DNGs, so no way to delete the metadata and re-write that I know of. There are no sidecar files to delete, either.

 

[Victoria Bampton]

Doh! Well there's another reason to stick with standard raw files and sidecars then I guess!!!

 

[Ian Farlow]

Doh! Well there's another reason to stick with standard raw files and sidecars then I guess!!!

Ouch. That hurts!

 

[Braders]

Ian

I have also been following your lonely journey, trying to relate it to some of the issues that are really similar to a few i too have experienced.

I have seen and followed almost identical posts on the adobe user to user forum, and i remember it goes back to LR1.1...now i just need to find them for ya....some more relevant than others...

http://www.adobeforums.com/webx/.3c'6'''4/'
http://www.adobeforums.com/webx/.3c'5e'52/'
http://www.adobeforums.com/webx?128@@.3c'581ca
http://www.adobeforums.com/webx?128@@.3c'562e3
http://adobeforums.com/webx/.3c'55ef'/2
http://www.adobeforums.com/webx?128@@.3c'52c4d
http://www.adobeforums.com/webx?128@@.3bc356b4

Also, from here
http://www.lightroomqueen.com/community/showthread.php?t=679

When i can find the post i made that was so similar i will remember the fix..!

 

[Ian Farlow]

Thanks. Yeah, it's been a lonely journey, that's for sure. I still look forward to 1.4 or 2.', whichever comes first. There's still so much to like about Lightroom.

 

[Ian Farlow]

Is there anyone else out there in Lightroom land that can at least confirm that what I am experiencing is also happening to them? There may not be a fix, but if there are multiple people with this issue, then maybe there will be a fix.

Just want someone to give me a hug...

 

[Victoria Bampton]

I can provide the hug Ian, but no problem here, sorry!

 

[Ian Farlow]

I'm considering starting over with Lightroom to see if anything fixes the problem. What are your steps for editing, and then saving, metadata in your images? Do you edit in batches, one at a time, or some other way?

Oh, and I'll be on a plane ASAP for that hug. Just have the Nestle Smarties and Cadbury Flake ready for me when I get there! Man... love those things.

 

[Victoria Bampton]

Ooooooh, I haven't had smarties in a long time. Far too many colourings, you'll have me bouncing off the walls!

My steps - I personally get to the end of an editing session, select all, hit cmd-s and... well... that's it!

 

[Victoria Bampton]

Ian, I've just had a brainwave. Just try something for me....

Select the files, and hit one of the quick develop buttons. Now hit cmd-s and it'll force it to rewrite the xmp. Now hit the opposite QD button and cmd-s it again.

The thing that's just brought up this brainwave... I wrote to xmp, and then accidentally deleted them (don't ask! ). Then I tried to write to xmp again, but it didn't think it needed to, so it looked like it wrote to xmp but never created new xmp files. Nothing I did changed that, until I hit QD to physically give it something to update. Syncing a movement on a slider that you don't use would do the same. Then saving that created new xmp's, reversing the QD adjustment set the images back to normal, and then save worked correctly. Just a thought!

 

[Ian Farlow]

Ooooooh, I haven't had smarties in a long time. Far too many colourings, you'll have me bouncing off the walls!

My steps - I personally get to the end of an editing session, select all, hit cmd-s and... well... that's it!

That's what I had been doing as well. Odd... Something seems to have gone all wonky somewhere.

 

[Ian Farlow]

Ian, I've just had a brainwave. Just try something for me....

Select the files, and hit one of the quick develop buttons. Now hit cmd-s and it'll force it to rewrite the xmp. Now hit the opposite QD button and cmd-s it again.

The thing that's just brought up this brainwave... I wrote to xmp, and then accidentally deleted them (don't ask! ). Then I tried to write to xmp again, but it didn't think it needed to, so it looked like it wrote to xmp but never created new xmp files. Nothing I did changed that, until I hit QD to physically give it something to update. Syncing a movement on a slider that you don't use would do the same. Then saving that created new xmp's, reversing the QD adjustment set the images back to normal, and then save worked correctly. Just a thought!

I had the same thought, but I changed the color label from one to another, saved, and then changed the label back and saved. Nothing helped.

 

[Braders]

Ian

I have experienced this and the following worked.

Change the "auto write XMP" to manual. Then, try to change some of the metadata like the location or copyright info, then change it back to want it should be and then save metadata.

also as an aside, as i don't auto write xmp changes, it would be nice to be able to filter out the files that have had metadata changes away from the remainder of the files. As it is now i just do what Victoria does, by selecting all.

Love smarties...

 

[Kiwigeoff]

Ian

I have experienced this and the following worked.

Change the "auto write XMP" to manual. Then, try to change some of the metadata like the location or copyright info, then change it back to want it should be and then save metadata.

also as an aside, as i don't auto write xmp changes, it would be nice to be able to filter out the files that have had metadata changes away from the remainder of the files. As it is now i just do what Victoria does, by selecting all.

Love smarties...

I think if select all and cmd-s is applied only those files that have changed data will get written to, so sorting wouldn't matter?

Try a Crunchie Bar!!

 

[Ian Farlow]

Ian

I have experienced this and the following worked.

Change the "auto write XMP" to manual. Then, try to change some of the metadata like the location or copyright info, then change it back to want it should be and then save metadata.

also as an aside, as i don't auto write xmp changes, it would be nice to be able to filter out the files that have had metadata changes away from the remainder of the files. As it is now i just do what Victoria does, by selecting all.

Love smarties...

Thanks. I'll try this and see what happens. I may end up starting over, but that's okay. Starting fresh helps me learn more about Lightroom anyway, even though it means long nights. Plus, starting fresh gives me an opportunity to drop some bad habits that I might have developed (no pun intended).