Skip to main content
chain569
Participating Frequently
February 5, 2017

P: Problem saving metadata if certain adjustment brushing is present (often with guided upright)

  • February 5, 2017
  • 35 replies
  • 1476 views

Hi,

I've been having problems saving metadata under certain conditions in 2015.8..  LR will say saving metadata, but the badge will come back on after.

So far, I've been able to narrow down that it seems to happen most often when an adjustment brush is used along with guided upright.
 
The problem comes in when I try to replicate it in photos that are ok with it.
On problem photos - copying, then deleting the problem adjustment brush will allow it to save ok.  But if I re-paste that copied brush, it wont save again.  Even more puzzling is that if that if there are more than one brush, then it seems to only have a problem with ONE of them.  And again, I haven't been able to determine a pattern as of yet..  It took me quite a while to even narrow it down to an adjustment brush issue, recently.

Also of note is that it will have problems saving even if there are snapshots with the offending brush, even if the 'current' doesn't include the problem brush.

Also important here, is that just turning off upright won't fix it - only removing the offending brush will..

Sooo, therefore it might not even be a problem collision with guided upright! ...  It's just that I notice the problem occurs most often when guided upright is involved.

The only way I've been able to work around this is to create virtual copies with the offending brush (and the other settings).  However, then I lose the belt-and-suspenders backing up of settings - which I find very important to me.

This topic has been closed for replies.

35 replies

chain569
chain569Author
Participating Frequently
February 15, 2017
Yeah, I don't think merging would be prudent either.   They're a bit too different. The timestamp issue resolves with a save-read, while the offensive-brushing problem doesn't.  Plus the [now likely] timestamp issue has existed for eons, while the offensive-brushing has only been in the recent version or two.
However, the similarities are that in both cases, it seems the metadata actually does save just fine, and they both will reshow the down-arrow badge after saving.
-----------------
And for the timestamp issue, probably not only writing out JPG's like John says - but also DNG's as well..  As I only use DNG's, and had this issue often when I was saving metadata on a higher-latency drive setup.  Though I'm guessing that there would be less of an issue with proprietary raws, as the written XMP files are small.

Either way, but especially for the offensive-brushing since it can't be resolved, it's certainly very unsettling to those of us that have come to wanting/needing the reassurance of having that belt-and-suspenders backup.  😕😕
Rikk Flohr_Photography
Community Manager
February 15, 2017
Though the other post is about a a different issue the two problems seem to be related. I have referenced both threads to the filed issue but do not feel merging them is prudent. 

Thanks John!
Rikk Flohr: Adobe Photography Org
johnrellis
Legend
February 14, 2017
This post by Patrick Philippot might be highly relevant to the problem reported here: https://feedback.photoshop.com/photoshop_family/topics/wrong-timestamp-stored-in-lightroom-catalog-c... .  Patrick examined the catalog SQL database and found that the relevant database field "touchTime" could differ quite a bit from the operating system's last-modified time and the XMP:MetadataDate field, and when it differed, invalid metadata status would be displayed.  Rather than getting a single time value and using that to set the last-modified file date, XMP:MetadataDate, and "touchTime", LR appears to be getting a separate time value for "touchTime".

This issue might happen more often with JPEGs than raws, because LR will often (always?) rewrite the entire JPEG when it writes out metadata. If LR is setting "touchTime" after it finishes writing metadata, then every now and then it could take many seconds to write out a JPEG (due to operating-system and disk variabilities), and "touchTime" would differ considerable from the last-modified date and XMP:MetadataDate.
Rikk Flohr_Photography
Community Manager
February 14, 2017
Chris, 

I still haven't been able duplicate your bug exactly but I have found an issue with the Metadata on Windows when opening your catalog that isn't there on Mac. I am filing an issue on it and we will see if it helps your condition too. 
Rikk Flohr: Adobe Photography Org
chain569
chain569Author
Participating Frequently
February 13, 2017
Windows 10, on gateway NV75S02u -- AMD A8-3500M APU w/on-board Radeon 6620--512MB graphics using shared 8GB (maxed out) memory
Rikk Flohr_Photography
Community Manager
February 13, 2017
So far, I am unable to reproduce, Chris. Either there is a missing step or you have a machine-specific issue. 

What is your OS?
Rikk Flohr: Adobe Photography Org
chain569
chain569Author
Participating Frequently
February 13, 2017
No.  I do it manually after a session.
Rikk Flohr_Photography
Community Manager
February 13, 2017
Do you have Automatically Write Changes to XMP enabled in your Catalog Settings?
Rikk Flohr: Adobe Photography Org
chain569
chain569Author
Participating Frequently
February 13, 2017
OK, here's the link:
https://drive.google.com/file/d/0B9w405O3QdgydzNnS0J4b2NPWlE/view?usp=sharing
Thanks so much for looking into this!
Rikk Flohr_Photography
Community Manager
February 13, 2017
Chris, you are correct. The file doesn't show a problem. Here's what I need. Take that file that is causing the issue with the edits/metadata flag, and select it. Export that Single file as a catalog including the Negative and any previews. The resulting folder needs to be Zipped and shared as a single file like you did before.  I will try and reproduce from your single-image catalog copy. 
Rikk Flohr: Adobe Photography Org