Store keyword in DNG file

I would like to have Lightroom store the Keyword information back into the file so that it's also available in other Software. I used iView before and it had a function to sync annotation information with the original file. Does Lightroom offer that possibility?
Thanks

Wolf,
Don't use the export module if you already work on JPGs. Go into Library module, then Menupath: Metadata->XMP->Export XMP Metadata to Files.
However even if you work with RAW files and use the Export function to create jpgs the keywords are added in the XPM container residing within the jpg file. I can see the keywords in Bridge, Photoshop, PS Elements and also in IRFANView (as IPTC data) and exiftool
regards
Chris

Similar Messages

Is it possible to embed keywords assigned in Lightroom 4 into DNG files?

Keywords I assign to photos in Lightroom do not show up as "tags" when I view the photo's properties in Windows Live Photo Gallery. Is it possible to embed keywords assigned in Lightroom to the properties of the photo file?

Thanks very much for your response. Ctrl-S saved the keywords to the DNG file properties. However, my original question was wrong. I should have asked how to save the keywords assigned in Lightroom to the properties of a TIFF file. Ctrl-S in Lightroom does not seem to embed keywords assigned to a TIFF file. When I check the properties of a TIFF file in Windows Live Photo Gallery after I have assigned keywords in Lightroom, the keywords assigned in Lightroom do not appear as "tags." Do you have any additional suggestions?

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.

Pushing Keyword and Descriptions in PE4 to DNG files

I have a quetsion on assigning keywords to files. I use DNG files and want the descriptions and keywords I assign in the PE4 organizer to flow to the metadata of a DNG file. (I would like to use the organizer in PE4 becuase its well feature offers advantages over the Bridge CS2 options.)
When using DNG files in Adobe Bridge the keywords and captions posted in the metadata of the DNG file flow directly to the PE4 organizer.
When using PE4, I think I would need to go to the File Edit mode to change metafile properties. Saving this information in this mode creates a second file -- something I don't want right now. Does anyone have expereince in pushing keyword and captions/descriptions from PE4 organizer to the metadata of a DNG file? (I am a convert to DNG becuase it does not use sidecar xmp files, rather the metadata is embedded in the image file itself.
Thanks in advance to any thoughts or suggestions.
Douglas Meredith.

Dear Colin:
Thanks for the suggestion; however, I have tried to use the File/Write Tags for both DNG and JPEG photos and the metadata for the original photo file did not change.
So, my quest continues.
Douglas.

Option to include personal-LR-keywords into DNG (or/and into jpeg) files ?

Is there an option, or a way to
include personal-LR-keywords into DNG (or/and into jpeg) files ?
Or, sorry, did not check it out.. : maybe it's allready automaticaly the case that a DNG (dng, by definition, also incorporates xmp, right?), when opened/imported in someone-elses computer/lightroom.. will positivaly respond to the creator's keywordings of that image?

The place option is usually not available for 16 bit files, so when editing images in acr
change where is says Depth to 8 Bits/Channel or after you open a 16 bit file, go to
Image>Mode>8 Bits/Channel.
MTSTUNER

What is the difference between Topic Keywords and Index File Keywords?

What is the difference between Topic Keywords and Index File Keywords? Any advantages to using one over the other? Do they appear differently in the generated index?
RH9.0.2.271
I'm using Webhelp

Hi there
When you create a RoboHelp project you end up with many different ancillary files that are used to store different bits of information. Many of these files bear the name you assigned to the project at the time you created it. The index file has the project name and it ends with a .HHK file extension. (HHK meaning HTML Help Keywords)
Generally, unless you change RoboHelp's settings, you add keywords to this file and associate topics to the keywords via the Index pod. At the time you compile a CHM or generate other types of output, the file is consulted and the index is built.
As I said earlier, the default is to add keywords to the Index file until you configure RoboHelp to add the keywords to the topics themselves. Once you change this, any keyword added will become a META tag in the topic code. If your keyword is BOFFO, the META tag would look like this:
<meta name="MS-HKWD" content="BOFFO" />
When the help is compiled or generated, the Index (.HHK) file is consulted as normal, but any topics containing keywords added in this manner are also added to the Index you end up with. From the appearance perspective, the end user woudn't know the difference or be able to tell. Heck, if all you ever did was interact with the Index pod, you, as an author wouldn't know either. Well, other than the fact that the icons appear differently.
Operationally, keywords added to the topics themselves may hold an advantage in that if you were to import these topics into other projects, the Index keywords would already be present.
Hopefully this helps... Rick

Importing, copyping raw files as DNG files - copy to location choice, and more ???

First:
When I copy raw files as DNG files, the right hand pane shows where the copies will be placed. (I use Windows 7) I do not have much of a choice, and cannot set a default. The default choice is "My Pictures" on the C: drive. I have an Solid State Drive, SSD, and do NOT store my photos on that small, 256Gb drive. I store my images on an internal hard drive.
All i want to do is set the default "Copy To" location to where I store my images. I would like to copy them to the original folder, in a separate folder (for example, LR DNG). Instead, I have to open the SSD, find the files, and copy them to my preferred location. This is very irritating.
Second:
Worst, it appears that the Copy function puts the copied images into multiple folders. I had 11 images from raw files that were put into three separate folders. That seems quite silly to me. It causes me to do more work opening the folders and copying them to the root folder. That is very irritating. What is going on here?
can these two issues be resolved? Thanks, in advance.

My apologies. I thought it would open the selected folder and reveal the images to be converted. That would be the most obvious thing to do, but it does not behave that way. I made a couple folders with test images, CR2 and RW2, and the converter converted them.
Again, the navigation was funky, inconvenient, but it works. i complain because we pay a lot of money to use Adobe products, they have huge resources, and they seem to release products that have obvious flaws, especially navigation. Maybe they just hate Microsoft. Sorry for the rant.
Thanks for getting me to use DNG converter.

Convert RAW Files in Your Aperture Database to Adobe DNG Files

The following describes how to convert all the RAW images in your Aperture database from manufacturer formats, such as Sony's ARW and Canon's CR2, to Adobe's DNG while retaining all the Adjustments already applied to your RAW files. In the example below I am assuming that your Aperture Library has ARW and CR2 files. These steps work with the latest version of Aperture, being Version 3.3, and have not been tested with earlier versions (in fact, it probably will not work because the database structure changed in 3.3 - however, this means that the steps below can also be applied to your iPhoto library). The steps are:
1. Within Finder select the Aperture Library and Secondary Click to bring up the Shortcut Menu. From this select "Show Package Contents"; this will open a Window showing all the files/directories contained within your Aperture Library.
2. Drag the "Masters" folder out of the Package and place it on your Desktop. The purpose of this step is so that Applications, such as Adobe DNG Converter, can "see" the "Masters" folder, which they cannot do if it is located within the Aperture Library Package.
3. Run the Adobe DNG Converter, select the above "Masters" folder with the "Select Folder" button, make sure you have selected the option "Save in the Same Location", it is also a good idea to select the option "Skip source image if the destination already exists", check your Preferences then select the "Convert" button.
4. Adobe DNG Converter will now convert all the RAW files to Adobe DNG files and save them in the same location as your existing RAW files. Once complete, take a note of (a) the number of files converted and (b) the types of files converted, such as if the conversion includes ARW, CR2, NEF files etc. In this example I will assume that the converter only found ARW and CR2 files; if your system is different then modify the steps below to make sure it covers all the RAW file types converted in your particular system.
5. Select the "Masters" folder and in the Finder Window Search Field search for all the files that end in .ARW and .CR2 (this filename search list should match the types of files found by the Adobe DNG Converter in step (4)(b) above). The number of files returned by the search must match the number of files recorded by the Adobe DNG Converter in step (4)(a) above. Do NOT put the .DNG files in your search criteria. Select all the files found in the search and move them to the Trash. This will delete all the original manufacturer's RAW files from your Aperture Library leaving behind all the new DNG files.
6. Move the "Masters" folder on your Desktop back to the root directory of the Aperture Library Package Content directory.
7. Select the Finder Window containing the Aperture Library Package Contents.
8. If there is a file called "ApertureData.xml" then open it with a text editor. Search and Replace ".arw" with ".dng", ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (note, do not use the " marks in your search). Make sure you cover all the file types incorporated in your particular system. Save the "ApertureData.xml" file.
9. Traverse to the Database/apdb directory. Select the "BigBlobs.apdb" file and open it with a Hex editor. In this example I will use Hex Fiend by Ridiculous Fish (see http://ridiculousfish.com/hexfiend/). Once the file is open perform a Find and Replace ensuring you are finding and replacing Text and not Hex. In Hex Fiend this means selecting Edit/Find from the menu and then selecting the "Text" button to the top/left of the window. In your Find/Replace field you will need to find ".arw" and replace it with ".dng", make sure you select "Replace All" (note, do not use the " marks in your search). Do exactly the same for ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (and whatever particular RAW files were in your system).
10. Perform exactly the same steps in (9) for the files "History.apdb", "ImageProxies.apdb", "Library.apdb" and "Properties.apdb".
That is it, your Aperture Library now contains DNG files instead of your original manufacturer files while still retaining all the Adjustments originally made in Aperture to those manufacturer files. Of course, you can repeat the same step and replace your DNG files with the original RAW manufacturer files if you wish. This process works because:
1. Aperture does not store the Adjustments in the RAW files, it keeps these in its internal SQLite database.
2. By using a Hex Editor you (a) don't have to play with SQLite to gain access to Aperture's data and (b) because you are replacing text that has exactly the same number of characters you are not invalidating the format of the underlying data file - this is why you use a Hex Editor instead of a simple text editor.
Think of Aperture as being a repository that holds Adjustments which then link to the original RAW source. Therefore, the above process simply replaces your RAW source and therefore all the Aperture Adjustments are still valid; same Adjustments, new source. In case you ask, no, you cannot transfer Adjustments in and out of Aperture because there is no standard to transform adjustments between different photographic applications.

A rather involved method, David.
I am sure it works, and compliments for figuring it out, but I think one critical step is missing in your workflow: Before you begin - backup, backup, backup!
And I think, all the edits in your database that you are doing so diligently, is what you bought Aperture for to do for you, why do it yourself?
I convert selected raw files this way - without manually patching the Aperture Library:
Export the originals of the raw images that I want to convert.
Run dng-converter.
Import the converted originals back, flag them, and move them to the project they came from.
Sort the project by capture date, so that identical images are show side by side.
Then I use the Lift&Stamp tool to transfer all adjustments and tags from the original raw to the dng copy. I check, if some edits are left to do, then delete the original.
It may take a little longer than your method, but this way all edits in the library are done by Aperture, and I am protected from accidental slips when editing the property list files. That requires a very careful work.
Patching the database files inside the library may be justified as a last ressort, when you need to fix and recue a broken Aperture library, and none of the provided tools is working, but not as a routine operation to do batch conversion of image files. It is very error prone. One wrong entry in the library files and your Aperture Library may be unreadable.
Regards
Léonie

DNG files created with LR4 no longer display thumbnails w/ FastPictureViewer & Win7

I've been using the FastPictureViewer Codec pack so that DNG and camera RAW files show as thumbnails in Explorer for quite some time. Upon upgrading to LR4, DNG files no longer display as thumbnails, but as the generic Windows icon for an image.
Upon researching the issue, and upgrading the Codecs from the supplier (which still did not fix the issue), the supplier tells me the following:
What we solved [in the update] was a crash with the new files. Adobe did not document their
changes, so there is not much we can do except ignore the files. This is
what happens when owners of proprietary formats decide to change stuff
without notice
If you turn off the "fast load" and "lossy" options the DNG will still be
created following the published 1.3 specification and will work with 3rd
party software including ours.
The "new DNGs" are for Adobe private use only at the moment. We don't know
(beyond vague promises on employees personal blogs) if they will ever
document what they did and publish an updated specification, they are
certainly under no obligation to do so. The decision they took not to
release updated DNG specs even before LR4 came out was a deliberate one.
While I resolved the problem by turning "fast load" off, I find it highly disturbing that Adobe has made undocumented changes to the DNG format that break 3rd party software. I thought the whole idea of DNG was that it was an OPEN FORMAT and was to prevent situations such as this. At least this is how they sold it to the public and their argument against "proprietary camera manufactuer RAW formats" that could "change at any time".

JS4653 wrote:
The "new DNGs" are for Adobe private use only at the moment. We don't know
(beyond vague promises on employees personal blogs) if they will ever
document what they did and publish an updated specification, they are
certainly under no obligation to do so. The decision they took not to
release updated DNG specs even before LR4 came out was a deliberate one.
Actually JS, RAW files converted to DNG with fast load checked from LR4.0 are read, thumbnails and full images are displayed in preview and with Finder in OSX Lion 10.7.3, along with keywords, EXIF data etc. I don't know whether the preview is the RAW or the fast loaded jpeg
Not that it helps you
Adobe mentioned that they will be making the 1.3 data specs available in the next couple of months, I canna remember the link offhand, and it was a formal post, not an employee blog
Life changes, things upgrade, that is the way of things, but it is very frustrating.

Bridge does not accept Keywords for video files

Lately, when I try to add a Keyword to a video file (.mov Quicktime) in Bridge, I get the following error message, "The file (name) cannot store XMP metadata. No changes will occur." How do I fix this?
Thank you!

This could be an OS permission issue. Is this an internal or external drive? I can add keywords of .wmv files.

Metadata in .dng file but not catalog

I use a plugin to sync my pictures to Alamy. Suddenly, the Alamy references and keywords have gone missing.
If I open the .dng file in a text editor, I can see that the references, for example the Alamy reference, are there. If I 'sync to file', they do not appear.
I can't face manually inserting the Alamy reference on several thousand images so that I can have the plugin re-sync but unless the plugin has the reference it can't sync images to the remote site, of course.
Any ideas?

John,
Not sure about C3.0, but C3.5 is able read chapter markers that have been created in FCPX – and using the DVD encoding presets. And those markers can, in turn, be read by DVDSP.
If you bring your master file into C3.0, apply the DVD presets, and open the preview window, do the markers appear on the timeline?
Russ

DNG file modification date not changed by writing metadata?

I use LR 2.7 on Windows XP.   To my surprise, I just noticed that writing metadata updates (e.g., new keywords) from LR to the DNG files does NOT appear to update the file modification date, which suggests obvious issues for backup strategies (yes, I understand that a changed modification date introduces other backup issues).   I have verfifed that the metatdata does indeed change in the DNG files, so I am mystified.   Can someone shed some light on this?   Thanks.
js
www.johnshorephoto.com

Yes, I explicitely invoke "save metadata to file".   Furthemore, I have checked the behavior by (a) modifying DNGs in LR; (b) saving the metatdata to the DNG; (c) creating a new LR catalog and importing the revised DNGs.    The metadata changes do show up in the re-imported DNGs (and the metadata field "Metadata Date" correctly shows the recent change). Morevover, the file sizes do change (wth the metadata changes) even though the modification dates shown in windows explorer do not change.
However, I just redid the experiment to double check, and discovered an important clue - the mysterious behavior occurs when the DNG files are on a NAS device (in particular a Netgear ReadyNAS Duo.   To summarize:
     - When the DNG files are on a local hard drive, the file modification dates change as expected
     - When the DNG files are non local (i.e., on the network but on a NAS device), the file modification dates do not change even though the file sizes do change;
What's more, I see the same behavior when accessing the DNGs via Adobe Bridge (CS5) - i.e., if I change the metadata, I'm asked if I want to apply the metadata changes to the DNG, and I say yes (and confirm by looking via Bridge at a copy of the changed file).   On a local disk, the file modificaiton dates change (as do the modification date displayed in Bridge), but if the files are on the NAS, the modification dates do not.
Any additional thoughts?
js

How can I import DNG files into iPhoto 8?

Shooting with a Canon Rebel XT, I've downloaded RAW files onto my hard drive, edited them in Adobe Camera Raw (ACR) and saved them as digital negatives (DNG) with the .dng extension. Bridge and iPhoto work with these just fine, but iPhoto doesn't seem to want to import them.
Aside from saving them as jpegs or TIFFs, is there any way to get these files to play nice with iPhoto 8?

I'm having the same problem with iPhoto after editing my images in Bridge and converting the files to DNG before importing to iPhoto. The metadata on the DNG file will not show up in iPhoto when I import DNG files. Yet, if I convert the DNG files to JPEG and import the JPEG files into iPhoto all the metadata and keywords in the original DNG files is imported. I use Bridge and CS3 for editing but want to use iPhoto for asset management.

LR4 and develop settings in DNG files

I spent a day developing a set of DNG images in LR4 and then used Bridge to rename all the files. When I sync'ed the folder in LR the develop settings in the DNG files were not there, all zero'ed out. I thought the develop settings were stored inside a DNG file by default? Do I need to tell LR to do that? I don't see where that setting might be.

In Lr, I think the default is to store develop settings in catalog only.
To store in DNG files, hit Ctrl/Cmd-S, or enable auto-save xmp in prefs.
Edit Menu -> Preferences -> General Tab -> Catalog Settings -> 'Automatically write changes into XMP'.
I prefer the manual method for a variety of reasons, but others prefer the automatic method (mostly so they don't forget I guess).
Cheers,
Rob

Why DNG files are bigger when converting from TIFF?

When I shoot in RAW, my normal workflow is to convert all images to DNG and start editing in Lightroom. But as you know, there are some photos that need extra editing in pixel based software such as Photoshop.
When I right-click a DNG in Lightroom and chose "Edit In... » Edit in Adobe Photoshop", the photo will be opened in Photoshop as an 8-bit TIFF file for editing. For demonstration of my issue, let's assume I don't do any changes and just save the file as it is. A new TIFF file will be created next to the source DNG with "-Edit" in it's name.
Back into Lightroom, both files are almost the same, one is DNG, the other in 8-bit TIFF. From this point (assuming I did change something in Photoshop, otherwise what would be the point in opening it there) I should do my further editing in Lightroom in the TIFF and not the DNG one. Let's say I'm done with the work and export the final edited TIFF file back into a DNG (I like this format and I like to keep all metadata changes so I can easily revert back to the original). I've also exported the original DNG file for comparison.
And now I realize the following:
DNG to DNG » ~7Mb (basically the same as the original DNG)
TIFF to DNG » ~15Mb
Why such a big difference?
I didn't do any editing either in the original DNG or the Photoshop converted TIFF. Any techincal reason for this that I'm not aware or am I doing something wrong?

I did a little bit of research and:
1) The embedded previews are always JPEG files (medim or full size, doesn't matter). But now that I think about it, I don't think you were talking about the previews when you mentioned the TIFF being embedded.
2) I did a quick EXIF lookup on 3 files exported to DNG: a) Original DNG b) 16-bit TIFF converted to DNG c) 8-bit converted to DNG. Here's the EXIF results:
a)
SubfileType                     : Full-resolution Image
ImageWidth                      : 3736
ImageHeight                     : 2772
BitsPerSample                   : 16
Compression                     : JPEG
PhotometricInterpretation       : Color Filter Array
SamplesPerPixel                 : 1
b)
SubfileType                     : Full-resolution Image
ImageWidth                      : 3648
ImageHeight                     : 2736
BitsPerSample                   : 16 16 16
Compression                     : JPEG
PhotometricInterpretation       : Linear Raw
SamplesPerPixel                 : 3
c)
SubfileType                     : Full-resolution Image
ImageWidth                      : 3648
ImageHeight                     : 2736
BitsPerSample                   : 8 8 8
Compression                     : JPEG
PhotometricInterpretation       : Linear Raw
SamplesPerPixel                 : 3
This probably means something like you said... The embedded files are different and some take more space than the others. The first one is 7.220Kb, the second one (16-bit TIFF) is 44.030Kb and the third one (8-bit TIFF) is 15.284Kb.
It makes sense I guess, but I still would love to hear a more technical explanation for it but it's obvious it has something to do on how the pixels are saved in the DNG file. The keyword is probably the PhotometricInterpretation.

Store keyword in DNG file

Similar Messages

Maybe you are looking for