Skip navigation
hmmerk
Currently Being Moderated

LR 4 alters DNG files

Mar 7, 2012 6:38 AM

Tags: #dng #corruption #moire #lr4

I  purchased LR4 last night - mainly interested in the moire removal tool.  Tried it on two DNG files.  Seemed to remove the colour pattern but not the intensity contours.  BUT, after this test, I opened the DNG files in Photoshop CS5.  In Photoshop, there are now ugly brush patterns where the tool was applied.  And the DNG files now showed a 'last modified' date of today.  Seems like LR4 can corrupt DNG files

 
Replies
  • Currently Being Moderated
    Mar 7, 2012 8:06 AM   in reply to hmmerk

    I very much doubt that there is any corruption happening.  Perhaps you can post an example DNG file so that I can investigate.  Note that CS5 will not process Lr 4 results, unless you have the ACR 6.7 Release Candidate (RC) installed.  (Do you?)

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 12:24 PM   in reply to hmmerk

    DNGs do not have sidecar files.

    If you write metadata to a DNG, the xmp-part inside the file is updated.

     

    AFAIK LR3 and LR4 can only coexist if only one of them write metadata back to the files. Otherwise the last update will win. No idea if this could lead to corruption of a file.

    If you have a file format with sidecar-xmp I would also assume that they get overwritten, as long as both programs use the same naming convention <filename before the .ending>.xmp. At least for settings which are common to LR3&4.

    I did not test what LR3 reads from a file developed in LR4 with not-yet-existing settings.

     

    The general warning applies that 1 file should be member of exactly 1 catalog.

    So if you want to have LR3 and LR4 in parallel, make sure that LR4 is pointing to copies of the DNGs, not the identical files as LR3.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 12:26 PM   in reply to hmmerk

    ACR 6.6 and earlier (like 6.4) can't render Lr 4 settings.  You need ACR 6.7 RC.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 12:30 PM   in reply to hmmerk

    hmmerk wrote:

     

    I have not tried to upgrade to CR 6.7, but I did try 6.6 which is latest version I could find on the Adobe site.  It resulted in no change.

     

    You should use the ACR 6.7 RC1 to open images from LR4 to Photoshop CS5/5.5. That's the only way of being able to process out images using PV 2012 settings. Note, the ACR 6.7 PV 2012 UI is not there...meaning you can't make any adjustments in ACR from the PV 2012 settings, but 6.7 will render the files from LR4 to Photoshop. It's available at Labs.Adobe.com.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 1:59 PM   in reply to hmmerk

    Can you please provide an example DNG file with the (embedded) moire adjustment settings?  That way I can try to reproduce the issue internally.  You can use YouSendIt, Dropbox, etc. with madmanchan2000@yahoo.com.

     

    Thanks.

    Eric

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 3:09 PM   in reply to hmmerk

    hmmerk wrote:

     

    Thanks Jeff for directing me to CameraRaw 6.7.  I installed that, but it sees the files just the same as 6.6 (and earlier).  That is, using CameraRaw 6.7, the images show the brushstrokes and no moire correction!

     

    The only other thing to ask is are you 100% sure that the moire settings was the ONLY setting you applied? Is it at all possible you had other controls adjusted in the same brush pin or additional pins with adjustments that would transfer over?

     

    As far as I know, if you use one of the new tools in PV 2012 in LR4 and then go to PV 2010 in ACR, only those settings that can transfer will move over.

     

    Regarding using moire only on a brush stroke and then opening the DNG in ACR 6.6, no, I'm not seeing anything unusual. The moire is not gone...but it looks exactly the same as the original before the moire brush...if I open the image in ACR 6.7, I get a warning that the selected image uses PV 2012 and in order to make any modifications to the basic or local controls I have to convert to PV 2010. If I don't convert and zoom in, the PV 2012 moire removal is there...

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 6:20 PM   in reply to hmmerk

    Thanks; I'll take a look. 

     

    BTW, the reason for the 'last modified' date changing in the case of the DNG is because XMP settings are stored within the DNG itself (in the header), so saving changes or updating metadata involves changing the timestamp.  In the case of non-DNG files like the Kodak .DCS, changes to metadata or settings are stored in a sidecar XMP file, which is why the 'last modified' date of the .DCS file doesn't change.

     

    Eric

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 6:26 AM   in reply to MadManChan2000

    I studied the file (thanks Harold) and have the following to share:

     

    1.  The DNG file is not corrupted.

     

    2.  The DNG file does contain incorrect (more accurately, stale) local correction adjustment values for the brushed regions.  The stored values indicate an increase in Exposure, which is why the brush strokes appear visible in older versions of ACR (like 6.3 or 6.4) which support PV 2003/2010, but not PV 2012.

     

    3.  The reason for the incorrect/stale values being recorded for the PV 2003/2010 settings is because of a bug in Lr 4.  I will work with the team to get this fixed.

     

    4.  In the meantime, to remove the visible "brush stroke" effects, you can either clear the local corrections, or click on an individual pin (once the Adjustment Brush tool is selected) and reset Exposure to 0. 

     

    5.  You will not encounter this problem if you open the image from Lr 4 directly into ACR 6.7 RC. 

     

    6.  The reason the problem didn't go away in this case when you tried ACR 6.7 RC, is because you already saved the image settings from an earlier version of ACR 6.  That is, you did this path: Lr 4 -> ACR 6.3/6.4 -> ACR 6.7 RC.  When you saved the image settings (e.g., by clicking "Done") in ACR 6.3/6.4, this threw out your moire adjustments.  This is because older ACR versions don't understand the newer settings (e.g., moire).

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 9:40 AM   in reply to hmmerk

    Hi Harold,

     

    The reason is that Lr always stores a copy of the metadata (including your adjustments) in the catalog file itself.  The database, in other words.  The catalog's stored metadata & adjustments are what is used to process the image in Develop. 

     

    Hence, when you replace the external DNG file on disk with a backup copy, the embedded XMP settings in the DNG will be different, but that doesn't affect Lr because Lr will be using its internal catalog settings to process the image.

     

    Of course, the thing that's probably going thru your head is that catalog-internal settings and external XMP settings (e.g., sidecars, or XMP embedded in DNGs) can get out of sync.  This is true.  When this happens, it is indicated with a metadata bade warning icon in the Library module.  Syncing between catalog settings and external files can be done manually, or automatically.  To do so manually, you use the "Save Metadata to File" (cmd-S) and "Read Metadata from File" options from the Metadata menu in the Library module.  To do so automatically, visit the Catalog Settings -> Metadata section and check the "Automatically write changes into XMP" box; note that this automatically syncs changes made in Lr 4 to the embedded/sidecar XMP (i.e., catalog -> external), but not the other way around.

     

    Eric

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points