Xmp to DNG?

I belive when you choose (Libarary>Catalog Settings>Metadata>Automatically Write Changes Into XMP) the changes to the metadata is also written into a DNG file.
I change my photos to DNG upon import so I was looking for the setting to auto write changes to file.  Checking the box above did what I wanted, at least in LR3, but I think this should be made clear in the settings dialogue.
I know when i have made suggestions before I discovered what I wanted was already there but I just didn't find it.  I'm assuming that the DNG files contains something called XMP but it wasn't clear to me that the setting above would write to the dng file or create a sidecar file.  My suggestion is that the Catalog settings dialogue makes this clear so one wouldn't wonder what to check.  Unless I'm sending xmp files back and forth to an editor whom already has the camera raw file, which I don't, it shouldn't be expected that I even know what an XMP file is.
Thanks.
Eric

jim01403 wrote:
I believe the metadata written to the DNG would be the same as written to a sidecar, BUT neither of them would be the complete set of metadata that is stored in the catalog. Specifically: Flags, VCs, collection membership, develop history, stacks plus some panel switches, are not written to the file by "Auto Write XMP", or the manual Ctrl-S operation.
Moving from LR to ACR, I do see develop settings updating in the DNG with Auto XMP on, that is good. But no a Snapshot. Using Command (control) S does update the snapshot. Interesting! There is no Develop History in ACR so I assume you are correct since Snapshots don’t appear to update with the auto XMP setting.
I suspect that the Save Metadata command for DNG might update everything expect the preview for the JPEG. It is pretty fast to operate while using the Update Metadata and Preview command takes more time for obvious reasons.
If I have this correct, with your help, I’d suggest we have three options:
1. Auto update XMP. Provides the same update for DNG as raws with sidecar files but as you point out, doesn’t update everything. Some data is within the catalog.
2. Save Metadata to File* (Command/Control S). Updates all (?) the other items expect the embedded preview (a size one sets in preferences). Here is where I’m not totally clear what does or doesn’t update the DNG that lives in the catalog. I’m not sure everything is necessary to update anyway (there are no VC’s in ACR or for that matter other converters so I see no need in specifying this data).
3. Update DNG Metadata and Preview*: Saves all of the above into the DNG.
*Only accessible from Library which is kind of a limitation. It would be really nice if one could ask for option 2 and/or option 3 along with the Auto update XMP preferences for DNG users. Then as you edit your DNG, when the system is presumably idle, all that data could be updated into the DNG. Option 3 will invoke a speed hit, option 2 seems to be as quick as option 1.

Similar Messages

  • Xmp and dng

    So I have a question.
    There is this outsourced company, that I use for editing, and I export from my raw files to dng so I can send it to them, They edit in lightroom, and they return xmp sidecar files with the edits that I simply apply back to my raw files.
    Now I want to train another person on remote location to do the editing instead of using the company i used to use, and I'm trying to replicate this process.
    The problem is, from all I read, you can't create xmp from dng files, so how did they do it? Is there another program that can save the xmp data out of dng? or did they conver the dng that I gave them to another format so that they can write xmp files out?
    Can anyone give me a way of doing this?
    thanks

    If DNG is read-only, Bridge will create sidecars for xmp. However there is no way to do the same in Lightroom, without some stunts...
    Lightroom will read DNG sidecars (if they're recent enough), but won't ever write them.
    papjohns wrote:
    Is there another program that can save the xmp data out of dng?
    Can anyone give me a way of doing this?
    Easiest way is via xEmP plugin, but you can also use exiftool directly if you prefer.
    Rob

  • Export XMP Files + DNG?

    If I currently have all of the RAW images within my Lightroom database in the DNG format, do I have to worry about exporting the XMP data to the files (using the 'Export .XMP Metadata to File' menu option)? What about the Preference setting to 'Automatically write changes into XMP'? Anyone know whether or not this preference setting is relevant to someone with a library full of DNG RAW images?
    If this is something that has to be done in order for other Apps to be able to see the various adjustments and settings I've applied to my images in Lightroom, and assuming I would like to have Lightroom do this for me automatically (using the preference setting), does having changes written to the XMP sidecar files automatically in any noticeable way have a negative affect on Lightroom's performance (i.e. slow it down in any way)?
    Please advise...Thanks!

    >If this is something that has to be done in order for other Apps to be able to see the various adjustments and settings I've applied to my images in Lightroom
    Correct, but Lr is fully functional without the requirement to export xmp data. Therefore, only export the xmp data only if it is required to do so.
    I never let Lr automatically write xmp data -- why pay the performance penalty, however small it might be, for no good reason? Instead, I use the Metadata>XMP menu to export xmp data only on those images I might want to view in Bridge or ACR.
    Other people have suggested that the xmp export can be used as a backup of Lr's metadata and parametric data. That is a valid argument but since not all Lr information is exported (e.g. collections, stacking, history, etc.) it's only a partial backup. Instead, I religiously backup the Lr database and copy it to external drives and burn to optical media.

  • XMP and DNG support?

    I'm using Aperture 2 on Mac 10.4.11...
    After importing DNG files I have some problems and what to ask if other users experience the same or perhaps I'm doing something wrong?
    I have a Lightroom Workflow where I convert all my 40d Raw files to DNG. I apply a lot of Metadata and some basic adjustments in the Lightroom Develop module. I update my DNG files with metadata and preview images to include everything in the files. After importing these files into Aperture 2 I have following problems.
    Metadata is not imported properly.
    Example 1:
    Creator in Lightroom: Susi & Paul
    Artist in Aperture after import: Paul
    "Susi &" is missing. Artist is not the only field with this problem. I have the same in behaviour in "Writer/Editor", "Credit", "Source", "Byline"....., simply i n all fields...
    Example 2:
    Caption in Lightroom: Köln, Cologne
    Caption in Aperture after import: öln, Cologne
    The "K" form "Köln" is missing.
    Example 3:
    All adjustments I have done in the Lightroom Develop Module are saved in the XMP Metadata and all previews are updated in the DNG files after adjustment to reflect the changes. I expected that Aperture is reading this metadata and use it for rendering. This is not the case.
    I was trying with Aperture 2 in German and English Language without any difference.
    Now again my question... Do you experience the same behaviour with Aperture 2 or is it my mistake?
    Thanks for any answer and... sorry for my bad english.

    Thank you very much Adsy for reply!
    After a few experiments I believe the wrong metadata import is a bug too. But this bug effects only my dng files, if I import jpeg's with the same metadata everything is fine. I'm not sure is it the DNG format or the included XMP (my jpegs also have XMP metadata).
    In my jpegs I have EXIF, IPTC and XMP (IPTC for XMP). Do you know in which order Aperture is reading this information and which information has precedence and is used?
    "IPTC" before "IPTC for XMP"?
    And who is the winner if metadata in "IPTC" and "IPTC for XMP" has the same values?

  • Ok to convert raw xmp to dng?

    I am converting a bunch of raws to DNG that have xmp files and I am noticing that the xmp files are being dumped in the trash as well. Should I be concerned?  Is this something I should do if I want to conserve space but keep my changes to my old raw files?
    Thank you

    The XMP information is stored inside the DNG, so it's not a cause for concern. (from your description, you're deleting the Raw files).

  • XMP and DNGs

    I convert RAWs in DNGs.
    When I want to go open a DNG foto in PS-CS2 via Bridge I first "export XMP metadata to file" Is this necessary when working with DNG files?

    OK, so I'm in the process of splitting up my single big library to a couple of smaller ones. I've done the "export XMP metadata to file" thing. When I read the files back into LR under a new library, it will read all the changes I've done before from the .xmp files. Am I understanding this correctly? Also, once I've re-imported all the files back in, do I still need to keep the .xmp files? Are all the changes read in from these files re-written into the new library? Thanks.

  • DNG + RAW + XMP?

    I seem to have, in some of my photo folders, a dng and raw version of my the same picture plus a xmp sidecar. My computer is a bit bloated and I want to toss out these. Is it okay to just delete the Raw and xmp files and leave the dmg ? Also the DNG seems to be twice the size of the original Raw file - should I delete it instead?
    Mac OSX 10.5.8
    LR 2.7
    Cheers,Simon

    Duck Shots wrote:
    I do not understand the xmp. I have raw files stored on my hard drive. They carry xmp extensions. I have a backup. The backup has the file and the xmp. I want to change to DNG.
    Adobe treats proprietary raws as read only. All the necessary instructions about the rendering is stored in the sidecar XMP. IF you convert the raws to DNG, you’ll be able to trash both the original proprietary raws (if you want to with or without a backup) and all the associated XMP. DNG contains the XMP instructions as Adobe does treat DNG as read and write capable. IOW, one of the advantages of DNG is you do not have to deal with these XMP sidecar files any longer.
    See:
    http://www.ppmag.com/reviews/200709_adobedng.pdf

  • DNG XMP samples.

    Does anybody have any working samples about how to extract XMP from DNG change any field (i.e. Desk) and push it back and save DNG?
    Really I'll be very glad to see such sample.
    I just need to add support of DNG to my tool and I get creazy during reading DNG SDK documentation.
    Thanks!

    The most complete approach is to use the DNG SDK. Since DNG files are well behaved TIFF though, you can also use the TIFF support in the new XMP Files component of the XMP SDK. This is available now in Adobe Labs and will be on Adobe.com in the coming months. The most visible difference is probably that XMP Files does not interpret the MakerNote tag.
    Don't use XMP Files for raw images though. Even though many raw formats look like TIFF, they can be ill behaved from a pure TIFF view. Use the Adobe Camera Raw SDK for raw.

  • How do I force lightroom to (re)load an XMP sidecar file?

    Good morning from Boston!
    I am new to Lightroom and just finished importing my Aperture library into Lightroom 5 on a Mac. For that, I followed the instructions on Adobe's landing page and Lightroom solutions. For those not familiar with the instructions, you essentially export all your originals with an XMP sidecar file and then export all the adjusted/edited files as 16-bit TIFFs. Then you add them all back into Lightroom and get everything back into Catalogs, Labels, Ratings, and such by using keywords that were added while in Aperture. It took forever, but worked pretty well overall. I had about <1% fewer images in LR5 than in Aperture, which were likely suspected duplicates. So far, so good.
    Here's is my problem. My keywords didn't always transfer over (the Keywording panel is empty). I did search forums and plug-ins, but seem to only find issues related to EXIF and GPS data. I also used "Metadata:Read Metadata from File" and "Metadata:Update DNG Preview & Metadata," which didn't do anything. I am suspecting that "Read from File" means "read from the image file itself but not from the sidecar file." Take file IMG_5888 as an example. This particular one was taken as RAW (.CR2) + JPEG on a Canon Rebel XS, but I am having the same issue with RAW only on my Canon EOS 6D. Same goes for JPG + XMP. Puzzling thing is that other files loaded just fine.
    In the directory/folder where the file is, it looks like this:
    IMG_5887.CR2
    IMG_5887.JPG
    IMG_5887.XMP
    IMG_5887.dng
    IMG_5888-2.JPG
    IMG_5888.CR2
    IMG_5888.JPG
    IMG_5888.XMP
    IMG_5888.dng
    IMG_5889-2.JPG
    IMG_5889.CR2
    IMG_5889.JPG
    IMG_5889.XMP
    IMG_5889.dng
    The .dng were generated by Llightroom. Now, the sidecar files typically have something like so in them (I cut out some keywords for clarity—you get the idea):
    <rdf:Description rdf:about='' xmlns:photoshop='http://ns.adobe.com/photoshop/1.0/'>
    </rdf:Description>
    <rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1/'>
      <dc:subject><rdf:Bag>
      <rdf:li>Black Head Trail</rdf:li>
      <rdf:li>Cliffs</rdf:li>
      <rdf:li>Maine</rdf:li>
      <rdf:li>Monhegan</rdf:li>
      <rdf:li>RAW</rdf:li>
      <rdf:li>Sunrises</rdf:li>
      <rdf:li>United States</rdf:li>
      <rdf:li>Waves</rdf:li>
      </rdf:Bag></dc:subject>
    </rdf:Description>
    So, the keywords were exported from Aperture, but for some reason, Lightroom isn't always loading them from the XMP file.
    On a related note, the keyword hierarchy that was exported as text file from Aperture and imported into LR5 worked well. Everything appears to be there and in its place.
    Any ideas for a Lightroom rookie as to how I can get LR5 to read those XMPs? Over 20,000 didn't tag, so I would rather not do this by hand!
    Many thanks in advance,
    Paul

    John, what a pleasure. Well, here is the update. First, copying over 300GB of pictures to a drive and then backing up said drive takes a bloody long time. But here is what happened, for others who might run into the same issue.
    I first tried a small set of files to narrow down whether the issue was the Aperture export or the Lightroom import.
    Conclusion: the "issue" is mostly on the Lightroom side.
    What I found: Although Aperture will export an XMP sidecar for a JPEG, Lightroom will not read it, ignoring all keywords. I exported a set of JPEGs only and then opened the XMPs with an editor (well, the UNIX cat command, to be exact). The information was there, keywords and all. However, LR appeared to ignore XMP for JPEG. That said, if you have a RAW+JPEG in Aperture, the RAW XMP sidecar will overwrite the JPEG one, effectively leaving you with only the keywords for the RAW version. That shouldn't be an issue for most, but just in case you have different keywords for your RAW and JPEG images, be aware of this.
    What I did:
    Back up all the images and catalogs/libraries from Aperture and LR.
    Make sure #1 worked out.
    Make sure #1 worked out (not a typo; you really need a backup, as you will find out below).
    Delete the old JPEG files that were uploaded into LR. I had them in a From Aperture folder, as instructed by John's article and Adobe's landing page (referenced in John's article), so I deleted all JPEGs in that folder. My Aperture database was not affected and in fact resides on a different drive.
    Run find . -iname "*.JPEG" -delete   [if you do not know how 'find' works, ask someone, as this can potentially delete every single file accessible to your computer!]
    Run find . -iname "*.JPG" -delete    [ditto! Don't tell me I didn't warn you!]This is why you need to backup everything. I was deleting copies/exports of the originals in Aperture (again, read John's article for the difference) and still had the originals in Aperture, on a different drive.
    [I didn't worry about the unmatched/orphaned XMP files for the JPEGs only; they are tiny and don't hurt.]
    In LR, select 'Library:Find All Missing Photos.' If asked, remove them from the Catalog only.
    Create a Smart Album in Aperture and include only 'Filetype is JPG.'
    Select all images in that album.
    Export those original images per Adobe's landing instructions, but for this set of images, select 'Include IPTC' instead of creating a sidecar file.
    When Aperture is done, open LR and Add the whole 'From Aperture' folder back to LR (make sure 'Ignore suspected duplicates' is selected.
    John, as you rightfully pointed out, this is tricky. If my experience is any indicator, I would suggest migrating in 3 steps:
    Export all RAW originals with IPTC in XMP sidecar files.
    Export all non-RAW originals (which I would guess are mostly JPEGs) with IPTC included. (not a sidecar)
    Export all versions as 16-bit TIFF.
    If #2 is added, then the process is actually most straightforward. Steps 1–5 in the first block above were to clean up the mess that I had created and should not happen otherwise (famous last word...)
    If the above is unclear, please let me know and I will expand on it. If I had the issue, I suspect others will as well.
    Thank you for your help and suggestions. I am officially migrated to LR and up and running!
    Cheers from Boston,
    Paul

  • Bridge CS5 not recognizing xmp files created on CS6?

    An employee of mine edited several shoots, using her own computer.  She has CC and used Camera RAW.  I still use CS5 and am trying to process the files she edited (I have the RAW and the xmp files).  Typically, I process these through Bridge.  However, Bridge doesn't seem to recognize her xmp files.  Any ideas on 1. why this is happening, and 2. how I can apply her xmp files when converting the RAW to jpeg?  We are talking about 1500 images.  Thanks!

    What camera model is she using?  What camera raw version are you using on your CS5?  Is her camera model supported by your cs5 acr?
    Perhaps she could process her raw files+xmp into dng files to pass on to you.

  • When writing changes to XMP . . . ?

    I'm using LR 3.2 -
    When I select "automatically write changes into XMP" in the catalog settings my understanding is the LR either creates a XMP file for a modified image or if the image is a DNG then LR keeps the changes inside the DNG file.
    My question is - are the changes also recorded in the LR catalog or are they only kept in the XMP or DNG file?
    Thanks -
    Adrian

    Hi everyone;
    Thank you for the multiple responses to my question.
    My trail of events leading up to this was that one day LR crashed on me
    and I lost my star ratings for 400 pictures.  This was the first time LR
    had ever lost data in my experience and I wanted to make sure it was the
    last.
    Thus I started using the XMP as a file option hoping that would save me
    if/when LR crashed and corrupted my catalogue.
    Some specific responses:
    Louie -
    My library is almost entirely DNG.  Your points on that are well taken.
      So when I modify a DNG file the whole file has to be rewritten you are
    saying?  The data is not somehow appended?
    I can live with backups being slower.  Annoying sure, but not a deal
    breaker for me.
    DdeGannes -
    You are correct about working within comfort zones.  If I lost a days
    worth of edits I'd be highly irate.    I back up my catalogue
    regularly as well, on multiple hard drives, especially after a big edit.
    I don't - at least so far - have any use for the XMP data/files in any
    other software either.  I'm looking at this only as a form of security
    blanket.
    Everyone -
    Thanks again for all the information.  Much appreciated.
    Adrian

  • Build DNG SDK on Mac with XCode 6.2

    Hello everyone,
    I am trying to build the DNG_SDK Version 1.4 with XCode 6.2. I have downloaded all the third party libraries for xmp and dng sdk. After linking errors with the current xmp sdk 201412, I tried to compile DNG_SDK with XMP SDK Version CS6. The XMP Subproject is found in my DNG_SDK and is build successfully.
    For the DNG SDK I still get linker errors and I have no clue why (regardless which architecture I select i386 or x64):
    Ld /Users/sboegel/Downloads/dng_sdk_1_4/dng_sdk/targets/mac/release/dng_validate normal i386
        cd /Users/sboegel/Downloads/dng_sdk_1_4/dng_sdk/projects/mac
        export MACOSX_DEPLOYMENT_TARGET=10.9
        /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cl ang++ -arch i386 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOS X10.9.sdk -L/Users/sboegel/Downloads/dng_sdk_1_4/dng_sdk/targets/mac/release -F/Users/sboegel/Downloads/dng_sdk_1_4/dng_sdk/targets/mac/release -filelist /Users/sboegel/Library/Developer/Xcode/DerivedData/dng_validate-fjjibtptniqsozaqnhhmkybxy udz/Build/Intermediates/dng_validate.build/Default/dng_validate\ release.build/Objects-normal/i386/dng_validate.LinkFileList -mmacosx-version-min=10.9 /Users/sboegel/Library/Developer/Xcode/DerivedData/dng_validate-fjjibtptniqsozaqnhhmkybxy udz/Build/Products/libXMPFilesStatic.a /Users/sboegel/Library/Developer/Xcode/DerivedData/dng_validate-fjjibtptniqsozaqnhhmkybxy udz/Build/Products/libXMPCoreStatic.a -framework Carbon -Xlinker -dependency_info -Xlinker /Users/sboegel/Library/Developer/Xcode/DerivedData/dng_validate-fjjibtptniqsozaqnhhmkybxy udz/Build/Intermediates/dng_validate.build/Default/dng_validate\ release.build/Objects-normal/i386/dng_validate_dependency_info.dat -o /Users/sboegel/Downloads/dng_sdk_1_4/dng_sdk/targets/mac/release/dng_validate
    Undefined symbols for architecture i386:
      "TXMPMeta<std::string>::Initialize()", referenced from:
          XMPFiles::Initialize(unsigned int, char const*, char const*) in libXMPFilesStatic.a(XMPFiles.o)
      "TXMPMeta<std::string>::SetProperty(char const*, char const*, std::string const&, unsigned int)", referenced from:
          P2_MetaHandler::SetAudioInfoFromLegacyXML(bool) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::SetVideoFrameInfoFromLegacyXML(XML_Node*, bool) in libXMPFilesStatic.a(P2_Handler.o)
          MP3_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(MP3_Handler.o)
          ReadIDXFile(std::string const&, std::string const&, TXMPMeta<std::string>*, bool&, MD5_CTX*, bool) in libXMPFilesStatic.a(SonyHDV_Handler.o)
          XDCAMEX_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(XDCAMEX_Handler.o)
          XDCAM_Support::GetLegacyMetadata(TXMPMeta<std::string>*, XML_Node*, char const*, bool, std::string&) in libXMPFilesStatic.a(XDCAM_Support.o)
          RIFF::importProperties(RIFF_MetaHandler*) in libXMPFilesStatic.a(RIFF_Support.o)
      "TXMPMeta<std::string>::SetProperty(char const*, char const*, char const*, unsigned int)", referenced from:
          ID3_Support::ID3v1Tag::read(XMP_IO*, TXMPMeta<std::string>*) in libXMPFilesStatic.a(ID3_Support.o)
          P2_MetaHandler::SetXMPPropertyFromLegacyXML(bool, XML_Node*, char const*, char const*, char const*, bool) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::SetGPSPropertyFromLegacyXML(XML_Node*, bool, char const*, char const*) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::SetAltitudeFromLegacyXML(XML_Node*, bool) in libXMPFilesStatic.a(P2_Handler.o)
          MP3_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(MP3_Handler.o)
          MPEG4_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(MPEG4_Handler.o)
          ReadIDXFile(std::string const&, std::string const&, TXMPMeta<std::string>*, bool&, MD5_CTX*, bool) in libXMPFilesStatic.a(SonyHDV_Handler.o)
      "TXMPMeta<std::string>::DeleteProperty(char const*, char const*)", referenced from:
          P2_MetaHandler::SetRelationsFromLegacyXML(bool) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::SetDurationFromLegacyXML(bool) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::SetGPSPropertyFromLegacyXML(XML_Node*, bool, char const*, char const*) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::SetAltitudeFromLegacyXML(XML_Node*, bool) in libXMPFilesStatic.a(P2_Handler.o)
          P2_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(P2_Handler.o)
          JPEG_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(JPEG_Handler.o)
          MPEG4_MetaHandler::ProcessXMP() in libXMPFilesStatic.a(MPEG4_Handler.o)
    Any hint is appreciated. Thanks
    I found a hint here (Xcode Compile Error Undefined symbols for architecture x86_64:   "TXMPMeta<std::string>::Initialize() that a include statement would be missing, but that is defined in the dng sdk (dng_xmp_sdk.cpp):
    #if qMacOS
    #ifndef MAC_ENV
    #define MAC_ENV 1
    #endif
    #endif
    #if qWinOS
    #ifndef WIN_ENV
    #define WIN_ENV 1
    #endif
    #endif
    #include <new>
    #include <string>
    #define TXMP_STRING_TYPE std::string
    #define XMP_INCLUDE_XMPFILES qDNGXMPFiles
    #define XMP_StaticBuild 1
    #include "XMP.incl_cpp"
    This cannot be the reason..

    Thank you so much! That has worked!
    I have downloaded XCode 5.1.1 and the build ran without errors. But still I is unclear to me what has changed. The Xcode-project file included in the dng sdk was configured compiling on Mac OS SDK 1.6. Anyway, I can go on with that. Thanks again

  • How can I create a new catalog of all my photos with no develop adjustments?

    I use Lightroom 4.3.  I tried this by deleting the old catalog, and creating a new one, thinking that the develop adjustments would no longer exist after first deleting the old catalog.  The develop adjustments were still there.  (I deleted the catalog out of the lightroom sub-folder of My Pictures.) 
    The reason that I want to do this is that I have one folder (of about 800 important photos) where something went very wrong in Lightroom, and every time I try to pull up one of the photos my whole computer stalls.  Everything works beautifully in my other folders.  I even re-installed Lightroom.  I want to re-add those dng photos without the develop adjustments.  It doesn't bother me if none of my files have develop adjustments.  I save all of my files after they are adjusted.  I save the DNGs also. 
    Thanks,
    Jennifer

    One easy way: reset after importing (which can be done from library module - e.g. main menu, context menu, quick-develop...). If you can't even get that far, consider using exiftool to strip the xmp from DNGs and/or jpegs, or just delete xmp sidecar file in case of proprietary raw.

  • I'm losing LIghtroom processing changes when opening photo in Photoshop.  Why?

    I have been using Lightroom only for a couple of weeks.  For several years I used Bridge and Camera Raw for RAW file processing.  After noticing that every .DNG file I process in LIghtroom 5.4 and subsequently open in Photoshop-CS4 loses the Lightroom processing in Photoshop, I conducted the following experiment:
    A  .dng file that had not previously been in LR catalog was placed in folder as Original  DNG.dng.
    File was copied and named Lightroom Processed.dng
    Both files were imported into LR
    The Lightroom Processed.dng file was loaded into Develop module and Exposure set to +5.00.  (Note that original is underexposed by about 1 stop and at +5 the photo is almost completely washed out.)
    Lightroom Processed.dng was opened in Photoshop-CS4. (There was no prompt for "Edit a copy with  Lightroom adjustments".  I'm assuming it was because it was a .dng file.)  The original underexposed version was displayed is PS.  When Ctrl-S was used to save the file, a file entitled Lightroom Processed-Edit.tif was automatically saved in the same folder and imported into LR.
    I copied the Develop Settings from Lightroom Processed.dng to LIghtroom Processed-Edit.tif and the numeric exposure setting was displayed as +5.00 BUT there are slight differences in appearance and in the histogram for the .dng and .tif versions.  The .tif version is very slightly darker than the .dng version.
    I opened LIghtroom Processed-Edit.tif in PS.  This time I was prompted to "Edit a copy with Lightroom adjustments" along with the other two options for opening a copy without adjustments or opening original. I selected "Edit a copy with Lightroom adjustments".
    I can't believe that one cannot process a raw file in Lightroom and then open it in Photoshop without having the processing one does in Lightroom carry over into Photoshop.  I've never had this problem using Bridge and Camera Raw.  What am I doing wrong?
    Thanks in advance to all who can help with this problem.

    @willard, moving from a Photoshop Bridge-ACR workflow to an Lightroom workflow there are a couple important differences to be aware off.
    a. ACR/Bridge uses .xmp sidecars to read and write changes to raw files(in the case of DNG files the .xmp data is stored within the file header). ACR/ Bridge cannot read the data stored in the Lightroom Catalog. The info is in the file.
    b. Lightroom by default uses a Catalog file to read and write all that you do in Lightroom. The info is in the Catalog. There is also the option to have Lightroom also write info to a sidecar .xmp file or within the file header of DNG, TIFF or JPG files. This can also be achieved by using the CTRL/CMD-S.  This info in the .xmp or DNG files is used by ACR/Bridge.
    c. In your case the xmp data written by LR 5 which uses the equivalent of ACR 8.4 will not be fully understood by PS CS4 which uses ACR 5.x.
    d. So if you open a DNG file directly in PS CS4 there will not be full compatibly. (you may have requested Lightroom to write to the DNG file but PS CS4 cannot read it all)
    Quote "(There was no prompt for "Edit a copy with  Lightroom adjustments".  I'm assuming it was because it was a .dng file.) "
    In the Lightroom Preferences General tab> Prompts> select Reset all warning dialogs.

  • Adobe myth on nondestructive editing!!!

    Recently shifted from RAW+XMP combination (when it was easy just to kill XMP) to DNG format in CS3. Unfortunately discovered that crop or retouch actions under ACR4.1 with DNG files are NON REVERSIBLE. Lost several nice shoots :( Be careful!

    igor:
    NOTHING is "ruined" about your DNG files. You just have no idea how to use the Camera Raw user interface. If you calm down, and ask questions rather than "warning" others (using three exclamation points) about how Adobe is lying to the world, you would make a lot more progress (rather than just making a complete fool of yourself).
    1. To remove a crop, click and hold the mouse button down on the crop tool icon. A menu will appear. Pick the "Clear Crop" item from this menu.
    2. To remove retouch spots, select the retouch tool. A tool options bar will appear at the top of the image. Press the "Clear All" button.
    If you have manually been deleting sidecar XMP files, you have been wasting a huge amount of time. There is absolutely no reason to do this just to clear crops and retouch spots.
    Warning to others: When creating a new topic, be really careful to be accurate in your statements. If you are not absolutely sure of something, it is much safer to ask a question. There are no stupid questions--just stupid statements.

Maybe you are looking for