DNG/XMP AppendProperties/ApplyTemplate

I downloaded the latest DNG SDK (1.3) and XMP Toolkit SDK (CS6).  The DNG SDK expects "AppendProperties", while the XMP has replaced that with "ApplyTemplate".
I then tried an earlier version of the XMP Toolkit (4.4.2), but then multple Quicktime SDK linking problems arose.
Are there any DNG/XMP versions which are compatable, or method of converting the function?
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.

Similar Messages

  • DNG, XMP, and Exporting

    The following pertains to Lightroom 1.1 (and possibly only to the Mac version on an Intel Mac with OS 10.4.10).
    I have searched Lightroom 1.1 Help, the knowledge-base, this forum, and elsewhere for simple instruction on how to do either of the following:
    Task #1: Create a separate XMP sidecar file from a DNG file for which the metadata relating to picture adjustments made in the Develop module has been embedded in the DNG file or stored in the Lightroom database.
    Task#2: Export a DNG file (for which the development metadata has been embedded in the DNG file or stored in the Lightroom database) while at the same time creating a separate XMP file that contains the development metadata.
    I did some experimenting relating to Task #2:
    In Lightroom, I set the exposure of a DNG file to +4.00 in the Develop module, then switched to the Library module and clicked on the menu item "Metadata > Update DNG Preview & Metadata", and then exported with "Original" selected as the file format. Immediately after this, I set the exposure to -4.00, without updating, and then exported with "Original" selected as the file format. Immediately after this, I exported with "DNG" selected as the file format.
    Here's what I found:
    1. Looking at the thumbnail preview for each in Mac OS 10.4.10's Finder window: Exports 1 & 2 look like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Export 3 looks like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). Opening any of these files within Mac OS X's Preview application shows the original state of the file without ANY of the development adjustments made before exporting.
    2. Looking at the pictures in Adobe Camera Raw 3.7 (because I have only Photoshop CS2): Export 1 looks like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Exports 2 & 3 look like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). No subsequent changes occur by going on to open the files within Photoshop CS2 after they are displayed in ACR 3.7.
    3. Looking at the pictures after re-importing into Lightroom: Export 1 looks like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Export 3 looks like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). For a few seconds, export 2 looks like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Then it switches to look like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). It seems this has something to do with thumbnail previews being already embedded in the files and with Lightroom displaying them temporarily before updating them.
    4. All three exports, when re-imported into Lightroom, begin with two snapshots already in the Snapshots panel of the Develop module: "Import" & "Import 2". "Import" is the original file condition when the file was first imported into Lightroom (before any of my export experiments). "Import 2" is the state of the file at the time I exported it, not the state when I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. "Import 2" is with -4.00 exposure) EVEN IF THE CATALOG IS DELETED AND A NEW ONE CREATED BEFORE IMPORTING THESE, THE SAME THING OCCURS.
    In none of these scenarios was an XMP file created. This had me wondering whether XMP files were possible at all in conjunction with DNG files. On to...
    Task #1:
    Now, as I was beginning to think that the only solution for creating XMP files from DNG files was to have Lightroom set up to maintain metadata in XMP files instead of in its own database (i.e. full-time XMP files as opposed to XMP files created only when exporting), I tried to alter settings in Lightroom's preferences, clicking menu

    (to Lee Jay: Yes, as I found out.) Here's the rest of my post:
    ...items and buttons in this sequence: Preferences > General > Go to Catalog Settings > Metadata. Nothing I tried with the settings there would induce Lightroom to create XMP files alongside DNGs.
    AFTER MORE WORK WITH JPGs AND CANON RAW FILES (.CR2), I FOUND THAT I COULD CREATE XMP FILES FOR THE CANON RAW FILES ONLY.
    My conclusions are:
    1. Lightroom writes separate XMP sidecar files for 3rd-party proprietary RAW formats only. This view is supported by the verbiage under these headings in Lightroom Help: "About metadata and XMP" and "Synchronize metadata with Adobe Camera Raw and Bridge".
    2. This means that, for other formats, enabling the following catalog settings under Preferences does not result in separate XMP files: "Write develop settings to XMP for JPG, TIFF, and PSD", "Automatically write changes into XMP".
    3. Also, for the other formats, enabling these catalog settings either does not alter the files at all or else alters them in a way that shows up only within Lightroom, Photoshop CS3, and any other applications that use Adobe Camera 4.0 or later. My additional export/re-import experimentation with JPGs in Lightroom suggests the latter is the case.
    4. In Lightroom settings and documentation, "to XMP", "into XMP", etc. mean "to the XMP data embedded within the file", "into the XMP data embedded within the file", etc., except for those cases in which the associated file format is 3rd-party proprietary RAW, where these phrases mean "to a/the separate XMP sidecar file", "into a/the separate XMP sidecar file", etc.
    5. The problem that seems to remain is that, apparently, not all non-Adobe software that can read DNG files is able to view changes made to these files by Lightroom (e.g. Mac OS X Preview).

  • Exporting Ratings, Labels, and Keywords to DNG/XMP

    I am a long-time Lightroom user in search of an efficient iPad rating and labeling solution.  I've recently found PixelSync which provides an amazing UI just for that, but syncing to Aperture.  So I got that to see if I can export my ratings, labels, and keywords, and also compare Aperture with Lightroom.
    Following Peter Krogh's excellent workflow idea. I prefer to sync my metadata edits back to DNG specifically for the purpose of using it as the package tying the RAW iimage and ratings, keywords, etc.  Lightroom syncs such data back to DNG upon demand (a menu choice).
    Aperture has a menu item to sync IPTC data back to master, and I see a DNG is updated in some way.  Yet I don't see the rating, not label, updated, when syncing to Media Pro (or any other EXIF viewer which reads DNG).  There are also some presets which have checkboxes next to IPTC fields; selecting Rating and Label as checked in several of them did not lead to them appearing in the DNG though.
    I've bought the Lightbox XMP export plugin, but that wants to run in 32-bit mode, and though does its job, you have to select the location for the export.  Similarly, exporting master from Aperture, I could do IPTC4XMP, but then again I have to select the location and I don't care about the RAW.  Export Metadata menu item again asks for output location and exports in plain text.
    While all this seems scriptable, I wonder is there a way to just sync back to DNG?
    Cheers,
    Alexy

    OK -- the problem was with my EXIF viewer, Media Pro.  When I checked the DNGs in Adobe Bridge, I see the ratings are in fact exported from Aperture vie the Metadata=>Write IPTC Metadata to Master.  Keep in kind that I found all possivle "IPTC presets" dialogues and checked Rating and Label checkboxes in them, so I'm not sure it will work out of the box.
    Now there's a great rating workflow with DNG=>Lightroom AND Aperture=>iPad rating=>Aperture=>DNG=>Lightroom.

  • DNG & XMP: True Lovers or "Taking a Break?"

    A simple question for which I cannot find a clear answer:
    Does Lightroom write metadata into DNG files automatically?
    I've read the FAQ at Lightroom Extra and it seems to imply XMP metadata is stored in a sidecar, even for DNG files. This seems odd to say the least given one of DNGs benefits was the ability to not need side car files. If the FAQ is correct then I have another question for the Lightroom developers.
    Why do I have to deal with sidecars to benefit from interoperability between Adobe applications when I'm using Adobe technology designed to avoid just that?
    Thanks

    "Does Lightroom write metadata into DNG files automatically?"
    Automatically? When the preference is ticked, yes it does and directly into the file, with no sidecar. When the preference is not ticked, it doesn't.
    I prefer to write the metadata when I choose, using Metadata > XMP > Export, and not automatically. This is because I want to choose when to take any hit (eg let's say I mistakenly apply an adjustment to lots of images, I'd have 2 sets of writing out the metadata), and I can use the Edit Time to sort the library and find those that need changing.
    Hopefully Alexander's software can exclude file types (On Windows TrueImage does so) because there is so little point in backing up DNGs that have merely had new metadata appended. The image data needs backing up when the files are new, and then the volatile information is the library which needs backing up daily or often.
    John

  • 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.

  • Importing DNG+XMP from Beta 4

    I originally tried Lightroom in December 2006 and ended up buying it this summer.  I just got around to trying to import a few thousand photos I had in my beta Lightroom library and have run into a little problem unfortunately.
    I saved all my photos in DNG format.  They all have at least some keywords and a caption in the XMP sidecar files which Lightroom wrote.  Many also have develop adjustments I made (I am pretty certain I used lightroom for the adjustments on the DNG ...).
    The beginning of the XMP file reveals its version: Adobe XMP Toolkit 3.3-016
    When I import a DNG file from this old collection, Lightroom imports it as well as the metadata as far as keywords, captions, etc. are concerned.  However, the photos no longer seem to have the develop changes I made.  Opening with CS3's ACR shows the same photo as what Lightroom shows, so neither pick up on the adjustments in the XMP sidecar.
    For example, exposure in one of my XMP files:    -1.00
    but when opened in Lightroom or ACR, the exposure slider is at 0.00.  :(
    Is there a utility I can use to convert this old XMP data into something ACR4.1 or Lightroom 1.2 can use?
    Thanks for your help and time.

    Thanks. I think I may have nuked it on accident when my old user account on my machine was lost :( -- oops.
    The good news it that I can get the changes by using an old ACR (3.4) to open the DNGs -- it looks in the XMP files and sets the settings on the sliders correctly.
    The only downside is then I don't really have the originals anymore, so I guess I will just retweak the photos from the trip which I'd put in my beta lightroom. It will be time-consuming, but probably worth it anyway -- color management and monitor calibration wasn't part of my vocabulary at the time, so I should be able to do a better job this time around anyway.
    Thanks again for your help.

  • B4.1 to V1.0 Migration with possible corrupt DB?

    Hi,
    I'm using B4.1 OK on Mac, but it takes over 3 minutes to load - splash screen with a spinning beach ball mostly, then unresponsive for a further couple of minutes until library shows up.
    I also get an odd console message about the LR database, but all seems to work OK once loaded.
    I'm wondering if it's going to be better to junk my existing library and start again with V1, rather than risk converting a potentially corrupted database.
    I have always used the Write XMP Sidecars option, and imports from memory card have always been to DNG, so can I just start again by reimporting the whole photo store disk, and the DNG/XMP data will rebuild everything thats needed?
    I'm not worried about collections/structure, but I do want to save the metadata etc.
    Is there anything in the B4.1 database that I am going to need?
    Cheers
    d.

    Not really. Save out the XMPs or create DNGs and start from scratch. The time taken will be a one off hit.
    v1 will try to convert the database format, and it also has an integrity checking routine. You might try this first.
    John

  • Showing Blown highlights (and/or shadows)?

    I got a new camera, and it has a nice feature of showing the blown
    highlights on the LCD after the picture is taken. It also can show the
    histogram. So, the histogram is basically the levels dialog. Is there a
    way I can duplicate the blown highlights screen in PSE 3.0 or 4.0? I
    have a LOT of pictures from my older camera, and I am having trouble
    adjusting (especially for shiny faces of the kids) skin tones. I now
    think it because there is actually no data on those shiny faces.
    I'm sure it's probably either a hue/saturation adjustment layer or a
    contrast adjustment layer that I need, but I don't have time to try it
    out. Any quick tips? I'm not talking about flashing the
    highlights/shadows or anything like that. Just a quick adjustment layer
    I can add and then slide the sliders and see where the highlights are
    bad and then turn on/off visibility for the "flash" effect :)
    Thanks,
    Trish

    Colin,
    These "guys" are essentially one guy, who has finally hired one more guy
    to help him :) . If you are wanting to do "creations" you have to buy
    other programs. IMatch supports full IPTC editing and most camera RAW
    versions, DNG, XMP, etc.
    The scripting capability is really handy. Someone wrote a web gallery
    script, which I use. You can modify the templates, or add you own very
    easily (unlike PSE 4.0). On the IMatch forums, people regularly share
    scripts and help each other out. So far, the 3 friendliest forums I have
    found are this one, Nikonians and IMatch.
    The big thing right now is Mario is redesigning IMatch. That will be a
    brand new release rather than a patch. We've been anticipating it for a
    long time (over a year), but Mario won't give us any time frame. So, it
    will be like going from Elements 3.0 to 4.0 and cost some $$$. However,
    with all the new RAW formats coming out all the time, that has delayed
    him quite a bit. He has a service pack that will come out here shortly
    to fix another couple of bugs and add RAW support for the Nikon D200.
    Sorry, I'm rambling on. If you are a power user, want IPTC editing
    capability, etc, IMatch is the tool for you. He doesn't gear it towards
    the "mom and pops" type, but there are plenty of us who use it.
    Definitely try the evaluation version. 30 days, no charge - can't hurt.
    -Trish

  • CRSS : Camera Raw Saved Settings - documentation ??

    Hello,
    I generated a DNG from Lightroom, and I get a XML tree using a crss (Camera Raw Saved Settings) schema.
    Where could I get about this ?? I didn't find aything with Google.
    Thanks.

    Panoholic wrote:
    I guess the meaning of "open standard" is, that it is open to anyone to write the documentation.
    Well, considering that "Camera Raw Saved Settings" are not specifically a function of DNG I think that comment is inaccurate and unfair. XMP allows new and custom name spaces and fields as part of the XMP specification (which is not directly tied to the DNG spec). The fact that Adobe has chosen to extend (XMP = EXtensible Metadata Platform) the XMP fields to include CRSS (Camera Raw/Lightroom "Snapshots") is more a proof oc concept of the usefulness of XMP metadata and less am indictment of DNG's "openess".
    Snapshots in ACR/LR are proprietary and thus are prolly intentionally "undocumented", don't ya think?
    If you want to see what _IS_ stored in DNG/XMP, the "crs schema" should be able to enlighten you...

  • XMP files not being created with DNGs...

    I'm used to using Bridge with ACR to process Nikon NEFs. But a recent camera update has me experimenting with converting the D3's NEFs to DNG files and editing them with CS2 and Bridge 1.04 which works better on my system. I've also experimented with CS3 and Bridge 2.1.1.9 with the same DNG files.
    In both cases XMP files are not being created when working with DNG files. I have enabled "Save image settings in : Sidecar ".xmp" files" turned ON. But they do not seem to be generated and I assume the ACR adjustments are being embedded in the DNG file. Meanwhile doing edits on NEF files continues to create .xmp files as expected.
    I find .xmp files to be very useful and I'm wondering why they're missing with DNG files? Are they hiding somewhere other than in the same folder that the images reside in?
    Thanks.
    Russell

    > The information contained in the XMP file is stored in the DNG file so there is no need for a separate file.
    Aww, yuck!! That's a real drag...
    When editing lots of files (yesterday's shoot produced 8GB) I back everything up to off-line storage and then, after doing all my edits and crops in ACR, I only have to copy over the small XMP files which takes no time at all.
    So if I re-edit the DNG with ACR I have to re-copy ALL the files again to the off-line storage.
    I used to sometimes even save 2 versions of the xmp files when I needed 2 different crops of the same images, such as doing a wide screen 'cinema' crop for a corporate client's Intranet presentation of their event, as well as more standard crops to be used for their newsletters.
    Guess I won't be using DNG any more..
    Thanks for the help Kees :-)
    Russell

  • 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.

  • How to add to a DNG file, the XMP metadata that transforms it into Cinema DNG ?

    Hello,
    I would like to know how to convert a series of DNG files into Cinema Dng ? What I read is that Cinema DNG has more XMP metadata than DNG. Is there a tool to add this kind of metadata ?

    It seems that the thumbnail created by adobe DNG converter is a source of problem for Da Vinci Resolve, to recognize a series of DNG as Cinema DNG. So if we could have a solution to remove this thumbnail, hallelujah !

  • I am considering CS6. I worry about "backwards compatability." I am in a windows-only environment.  Some files were antiquated mac computer.  Files are: psd doc eps tif indd otf ai jpg RW2 xmp pm7 bmp fh9 fh10 dng pm6 and ps. Rick

    I am considering CS6. I worry about
    "backwards compatability." I am in a windows-only environment.  Some files were antiquated mac computer.  Files are: psd doc eps tif indd otf ai jpg
    RW2 xmp pm7 bmp fh9 fh10 dng pm6 and ps. Rick

    Backward compatibility FROM what TO what?
    CS6 to older, or newer to CS6?
    For specific answers, you most likely need to check in the forums for specific programs
    The Cloud forum is not about using individual programs
    The Cloud forum is about the Cloud as a delivery & install process
    If you will start at the Forums Index https://forums.adobe.com/welcome
    You will be able to select a forum for the specific Adobe product(s) you use
    Click the "down arrow" symbol on the right (where it says All communities) to open the drop down list and scroll

  • Option to store xmp metadata outside of DNG file

    This would serve to improve differential backups, as the xmp file format is text based and easy to tell differences.

    Walt,
    No, you totally misunderstood what I meant. I'm not talking about LR catalog backups, I'm talking about backing up scores of dng files completely outside of LR, from the OS or some other external tool. With my suggestion, the xmp file would be right next to its dng file, and i would be backing up the whole directory hierarchy that hold my files. One of the benefits of LR over Aperture is that I can access, manipulate, and/or backup my files outside of the app rather than having them locked up in a vault which must be backed up in one huge blob.
    If I change the brightness of 500 dng files using LR, then back up all my dng files using rsync (for example), I will be copying 500 large binary files around. If my edits were saved in separate text files (xmp), then my backup program could only copy the DIFF of each of the text files (one line added to each file, so one line, or five in a normal unified diff format, is all that needs copied around). This would be exponentially faster.
    Embedded xmp edits is not a good practice, from an OS-level backup point of view. Since not everyone will agree on that, I'm asking for a checkbox option - I'm fine with it being embedded by default.
    With xmp data being stored inside the dng file, and LR changing the dng file every time I edit something, LR is hardly non-destructive from an OS-level point of view when dng files are used.
    No where in the spec does it state that xmp changes data MUST be stored in the dng file. I'm simply asking for the option to store that data outside of the DNG file, so that the dng file only needs backed up once or rarely, rather than every time I make an edit.

  • Bug: DNG Converter 8.6 ignoring XMP files

    There seem to be a severe bug in Version 8.6 of the DNG Converter.
    It just does not take over XMP data from sidecar files anymore into the generated DNGs.
    As a result the previews embedded into the DNGs are flat as well, any former edits are not being applied.
    Up to version 8.5 everything worked as expected, this behavior is new in 8.6.
    I don't know, if this is the right place to ask - but Adobe, please fix this ASAP! Thank you!
    Best Regards
    Gunther Wegner

    Thank you Rob and done: Bug in DNG Converter 8.6 - XMP data does not get applied

Maybe you are looking for