P: LR5 not immediately flagging metadata changes in DNG

Geoff,

I attempted to reproduce - I was unable to edit the metadata in ACDSee (due to an error) and develop edits in Photoshop (ACR) are NOT flagged by Lightroom as changed metadata, despite being read properly when forced.

So, problem confirmed, and my guess: DNGs are a little off, but I dunno how so...

If DNGs from other cameras (or Adobe-converted DNGs) don't have the same problem, consider reporting problem to camera manufacturer.

If only DNGs edited in PhotoSupreme have the problem - probably bug in that software..

Rob

I thought the whole point of DNGs was that you could embed metadata into them? Certainly PS does - it does not create sidecars for DNG files (although it can for other RAW formats).

I have exiftooled the DNGs, and I can't see anything untoward. LR5 certainly seems to (or rather, it doesn't see anything changing), which is why I raised the issue in the first place.

|> "imports go OK".

For me, the import did NOT go OK (I had to restart Lightroom after importing that DNG - never had to do that before), thus my theory that there is something a little off about those DNGs, but I can't be sure.

When you edited via PhotoSupreme did it create a sidecar, or embed. If it's got the option to do the other, it would be worth exercising to see if any difference. Lr supports reading metadata from DNG sidecars, it just won't write them.

I think most people don't have the problem (e.g. after editing externally in Photoshop), so it's not a common bug in Lightroom, AFAIK.

I don't have time to scrutinize which is why I passed the baton. You might consider exiftooling the DNGs to see if you can glean anything...

Good luck,
Rob

If you want to reproduce it, use the DNG test file, and edit the metadata outside of LR5 and see if LR5 will pick up the fact that the file's metadata has been changed.

The DNG file, by the way, was created by a Nokia Lumia 1020. If this issue is not being seen by others using DNG files created by different cameras, then it may be down to something about the Nokia implementation of DNG. Hopefully, further testing will start to narrow this down.

Yes, imports go OK. So I've imported my entire collection into LR5, and all the metadata that existed in the files got picked up by LR5 as expected.

The issue is about subsequently changing metadata external to LR5. These test files, which had been imported into LR5, had their metadata edited outside of LR5. The issue is that LR5 correctly flagged that the JPG file had had its metadata changed, but failed to notice that the metadata (and the file modification timestamp) had changed for the DNG file.

I imported both in Lr. Here is a complete dump of the differences metadata:
(courtesy of ChangeManager plugin).

Raw Metadata Changes:
aspectRatio | 1.7777777777778 | 1.7757352941176
dateTime | 412997494 | 412997493
dateTimeDigitized | 412997494 | 412997493
dateTimeDigitizedISO8601 | 2014-02-01T17:31:34+01:00 | 2014-02-01T17:31:33+01:00
dateTimeISO8601 | 2014-02-01T17:31:34+01:00 | 2014-02-01T17:31:33+01:00
dateTimeOriginal | 412997494 | 412997493
dateTimeOriginalISO8601 | 2014-02-01T17:31:34+01:00 | 2014-02-01T17:31:33+01:00
dimensions | 3072,1728 | 7728,4352
fileFormat | JPG | DNG
gps | 51.9561725,6.499135 |
gpsAltitude | 13 |
height | 1728 | 4352
masterPhoto | 5191854 | 5191895
path:
-----
X:\MyPictures\Special Purpose Photos\LrForumSupport\DNG_Metadata_Change_Detect\WP_20140201_17_31_36_Raw.jpg
--------------------------------------------------------------------------------------------------
X:\MyPictures\Special Purpose Photos\LrForumSupport\DNG_Metadata_Change_Detect\WP_20140201_17_31_36_Raw__highres.dng
--------------------------------------------------------------------------------------------------
root_uuid | 924B4DA2-7640-4E46-97DF-61143151DFE3 | C89448D6-8E5E-46C7-9CC6-E6F47E05873B
uuid | A745595D-CF04-4BAF-B937-01B33753A884 | B2FA511B-D166-4BA6-9C36-7E75C29418B7
width | 3072 | 7728

Formatted Metadata Changes:
caption | WP_20140201_17_31_36_Raw |
croppedDimensions | 3072 x 1728 | 7728 x 4352
dateTime | 2/1/2014 5:31:34 PM | 2/1/2014 5:31:33 PM
dateTimeDigitized | 2/1/2014 5:31:34 PM | 2/1/2014 5:31:33 PM
dateTimeOriginal | 2/1/2014 5:31:34 PM | 2/1/2014 5:31:33 PM
dimensions | 3072 x 1728 | 7728 x 4352
fileName | WP_20140201_17_31_36_Raw.jpg | WP_20140201_17_31_36_Raw__highres.dng
fileType | JPEG | Digital Negative (DNG)
gps | 51°57'22" N 6°29'57" E |
gpsAltitude | 42.7 ft |
title | WP_20140201_17_31_36_Raw | WP_20140201_17_31_36_Raw__highres

First item is jpg, 2nd is dng.

Unfortunately, I'm not sure what to conclude from this - since I never had either in catalog there wouldn't be any metadata status change issues...

Funny thing - after importing the DNG, there was NO METADATA WHATSOEVER VISIBLE in Lightroom - for *any* photos - never ever seen that before, but after restart of Lr, all was well. So, dunno if red herring or there is something about that DNG that gave Lr a bad first impression, so to speak. Maybe somebody else can also have a look.

Rob

I use Photo Supreme (http://www.idimager.com/WP/?page_id=20) since I find its metadata/keyword editing capabilities superior to LR5.

Here's a link (http://sdrv.ms/1cz4Ury) to a pair of test files (JPG and DNG versions of the same image) that were edited to have the same metadata in both files using Photo Supreme.

Following that operation, LR5 detected that the JPG file was changed on disk, and flagged that in the metadata panel, whereas it did not do the same for the DNG file - even though it had been changed.

As presented, it certainly sounds like a bug.

Would you mind elaborating how you edit the metadata in those DNGs?