Skip to main content
Inspiring
February 13, 2014

P: LR5 not immediately flagging metadata changes in DNG

  • February 13, 2014
  • 18 replies
  • 452 views

I have JPG and DNG versions of images. If I edit metadata in these files externally to Lightroom, then only the JPG versions get flagged by LR5 as having had their metadata changed on disk. As far as LR5 is concerned, the DNG files remain untouched, which is incorrect. Is this a bug?

18 replies

Inspiring
March 28, 2014
Excellent. Thanks for investigating. Relieved to know that I wasn't the only person seeing this...
Participating Frequently
March 28, 2014
It's true... been busy. 🙂
areohbee
Legend
March 28, 2014
Hi Ben - long time no post.

Thanks for looking into this and reporting back.

Rob
Participating Frequently
March 28, 2014
Hi Rob and Geoff,

Thanks for your work and all the specific info, sorry for the trouble. Just wanted to let you know that I've been able to reproduce the problem that you describe, and I've reported it to the Lightroom engineers.

Thanks,
Ben
Inspiring
February 14, 2014
I will wear it with pride! 🙂
areohbee
Legend
February 14, 2014
I gave ya the gold star 😉
Inspiring
February 14, 2014
OK, after messing about with this the whole afternoon, I think I'm beginning to see what's going on.

First, the issue has nothing whatsoever to do with Photo Supreme, so whoever is responsible for changing my title of this thread to imply that it is - kindly change it back to what I originally wrote. Here's a clue: look at the URL for the thread.

The issue is that LR5 responds very quickly (in a few seconds) to external changes in metadata in JPGs. However, for DNG files, LR5 will sit there looking the other way for what seems like (and apparently is) hours at a time before it finally deigns to note that a DNG file has had its metadata changed by an external application.

And note that I say: an external application, *not* Photo Supreme. I have tested this with two external metadata editors: Photo Supreme and Geosetter (which actually uses ExifTool under the covers). The results are the same.

The results are also the same whether the DNG files in question originate from my Nokia 1020 or have been converted by LR5 from Canon CR2 RAW files.

The bottom line:

LR5 does not respond quickly to metadata changes in DNG files.

Now that I know this, I shall adjust my workflow accordingly. I shall not rely on LR5 to tell me whether the files it is tracking have changed. I know that I cannot rely on LR5 telling me the truth.
areohbee
Legend
February 14, 2014
Wasn't me.

PS - Good job trouble-shooting :-).
Inspiring
February 14, 2014
Rob,

You, or someone else, have edited the title of this thread, and altered the meaning from the original.

I had a title along the lines of LR5 not flagging metadata changed externally.

It now reads as though it is an issue with the combination of LR5 and Photo Supreme.

It is NOT. I have just used Geosetter to edit metadata in a DNG file produced by a Nokia 1020, and the same thing happens - LR5 does not notice that the metadata has been changed on disk.

Next step is to try some other DNG files...

But I think that we can rule Photo Supreme out of the issue.
Inspiring
February 14, 2014
Rob,

Thanks for looking further. I'll rustle up some Adobe-converted DNGs (and some Canon CR2 RAW files) and do some further testing.