Sidecar .xmp for a DNG file ...

Photoshop CS6 Reference says that "When a DNG file is processed in Camera Raw, the settings are stored in the DNG file itself, but they can be stored in a sidecar XMP file instead." How can I store the changes made to a DNG file in a sidecar file? Thanks.

Complete paragraph: "When a camera raw image file is processed with Camera Raw, the image settings are stored in one of two places: the Camera Raw database file or a sidecar XMP file. When a DNG file is processed in Camera Raw, the settings are stored in the DNG file itself, but they can be stored in a sidecar XMP file instead. Settings for TIFF and JPEG files are always stored in the file itself."
And it adds at the end of the same page: "If you want to store all adjustments to DNG files in the DNG files themselves, select Ignore Sidecar “.XMP” Files in the DNG File Handling section of the Camera Raw Preferences dialog box."

Similar Messages

Batch Import .XMP info into DNG Files

I have a few thousand Canon 5D RAW files that have accompanying XMP files created by PS CS2 containing of a lot of metadata that I manually typed in for each photo.
Because of some better ICC profile features in DXO Optics Pro 4.x, I want to batch process my Canon 5D raw files (with XMP EXIF data) by DXO Pro into DNG. My problem is how to batch incorporate the XMP data into the resulting DNG file. It doesn't appear
I found a way I can manually import the data in CS3 for a single photo. However, that's no good for 3000 photos.
Does anyone have a simple batch method that will do what I want? The XMP files are all named the same as the RAW files, so matching up the files is a piece of cake.
Could I create an action that would somehow open the new DXO generated DNG file, and import the XMP file using some type of filename matching process?

Why not simply run the DNG Converter on that folder? It will merge the XMP sidecars into the resultant DNG files.

Problems reading xmp data into dng files

Hi there,
I am working on a Mac and have exported files as lossy dng for colour correction externally. They have done the work for LR 5 process (I am using CC) and returned xml files. I cannot seem to read this data into the dng files for further editing in Lightroom. I have tried re-importing them and I have tried reading metadata from file. Any help would be appreciated as I usually simply read the xmp to the original RAW but the RAW files are currently on an external drive in another country!!!
Thanks,
Andy

Moominman wrote:
I am basically trying to export xmp files from a set of low resolution dng files so that I can access my Lightroom edits in the RAW files. I have separated the RAW and dng files in different folders
Hi Andy,
I dunno how best to get extracted xmp files into the raw folders, but if you are comfortable with exiftool, you can use it to extract xmp sidecars from DNG files.
If you want a turn-key solution which does not required you to futz with exiftool, then consider a free plugin I wrote:
robcole.com - xEmP
It will allow you to create xmp sidecars with all your DNG adjustments and metadata (which can then be applied to the non-dng raw files).
However, if you won't need the DNGs in your catalog afterward, then the easiest way is to convert them back to proprietary raw format using this plugin (also free, and I wrote it):
robcole.com - UnDNG
Conceptually, you can think of it as converting the DNGs to proprietary raw format, but note: it doesn't convert anything, it just allows existing raw files that are NOT in the catalog, to replace the DNGs that are in the catalog. All adjustments and metadata and everything else will be preserved (just like when you convert a proprietary raw to DNG format).
Rob

AE not reading all the XMP data from DNG files

I'm working on a very large time-lapse for a construction company - I have a sunset that is broken between two folders and rendering the folders seperately makes Quicktime unhappy during playback and I get an ugly jump in sunset exposure.
So I combined the two folders in Lightroom (LR) from my RAW files (NEF) and exported the entire sequence as DNG files with simpler numbering. The sequence is about 1560 files and constitutes about 22 GB of data. I created a new LR library from the DNG sequence to make sure it all looked good and it does.
I imported the same DNG sequence into AE, checked a few frames in the preview and sent it out to render. Two thirds of the way through the QT movie, exported in H.264 at 30 fps, I start seeing problems. Huge sections look like the XMP data has not been read, then there's a good section and then bad again. I matched the movie time to preview in AE and indeed saw the same problems in the AE preview. So the problem begain in AE's reading the files from the folder, not in rendering.
I went back to LR for file comparison. There was no problem in LR. All the DNGs look great.
I'm on a MacBookPro Retina with 2.8 GHz Intel processor, 16GB 1600 MHz DDR3 Ram and NVIDIA GeForce GT 650M 1024 MB graphics
I have the standard 69GB cache on an external drive and have 11GB RAM available for AE.
Installed CPUs =8
CPUs reserved for other apps = 2
RAM allocation per background CPU = 1GB
Actual CPUs that will be used = 6
I have the latest AE from the Adobe Cloud, although I haven't done the most recent update yet.
My thought was to break the folder up into smaller segments for rendering, but that's not the problem. I see the XMP hasn't been consistantly read in preview. To me it doesn't make sense that the folder is too large for preview because it's not even rendering it there, just reading the files...?
Any insight, solutions?
Thanks,
Dennis

Moominman wrote:
I am basically trying to export xmp files from a set of low resolution dng files so that I can access my Lightroom edits in the RAW files. I have separated the RAW and dng files in different folders
Hi Andy,
I dunno how best to get extracted xmp files into the raw folders, but if you are comfortable with exiftool, you can use it to extract xmp sidecars from DNG files.
If you want a turn-key solution which does not required you to futz with exiftool, then consider a free plugin I wrote:
robcole.com - xEmP
It will allow you to create xmp sidecars with all your DNG adjustments and metadata (which can then be applied to the non-dng raw files).
However, if you won't need the DNGs in your catalog afterward, then the easiest way is to convert them back to proprietary raw format using this plugin (also free, and I wrote it):
robcole.com - UnDNG
Conceptually, you can think of it as converting the DNGs to proprietary raw format, but note: it doesn't convert anything, it just allows existing raw files that are NOT in the catalog, to replace the DNGs that are in the catalog. All adjustments and metadata and everything else will be preserved (just like when you convert a proprietary raw to DNG format).
Rob

How do I update Date Time Digitized to match an updated Capture Time for a DNG file?

I am updating capture time based on GPS Time (a bit OCD, I know) but when I change Capture Time the Date Time Digitized value does not change. This in in LR 4.3 and is not affected by whether on not the Catalog is set to 'Write date or time changes into proprietary raw files'. Maybe this is a problem for DNG files only.

GreSep wrote: I saw another LR discussion that said that with LR 4.3 updating Capture Time would also update Date Time Digitized but it does not do so for me on my DNGs (and as of last month ALL my images were converted to DNGs).
One or two intermediate versions of LR 3 (perhaps Lr 3.6) set DateTimeDigitized when you gave the Metadata > Edit Capture Time command. But for people managing scans in which the capture time of the original image was different than the scan time, this behavior overwrote their scan times, so Adobe backed out of that change. Before and since those versions, the Metadata > Edit Capture Time command just changes the EXIF:DateTimeOriginal and related fields in XMP and IPTC.

My Bridge update 5.2.0.4 has wrecked previews for all DNG files. They appear only sideways and small and I can't open Camera Raw in Bridge. Anyone else have the same problem?

I updated Bridge yesterday. CS6 5.2.0.4. Mac OS 10.9.5
Now all previews (DNG files) in Bridge appear sideways and only small thumbnail size.
Also Camera Raw has been disabled.
I have tried purging cache for the folders as well as purging entire cache.
I have also spent over an hour on the phone to tech support which mainly involved being switched between departments and trying to understand anyone on the phone.
Can anyone help?

Your Performance preferences screen capture reveals you have a single hard drive with little available space to accommodate both the Photoshop scratch file and the swap files of the OS.
It's obvious that Bridge finds itself at times with insufficient space to build its cache.
However, it's unclear why that should affect only DNG files and not other type of image files. Puzzling, unless the DNG files are the only large image files you have.
Parts of the following may illustrate what happens when the scratch file is on your boot drive:
The rule of thumb I follow to figure out scratch space says to figure on 50 to 100 times the size of your largest file ever multiplied by the number of files you have open. I have seen the scratch file exceed 800 GB once, an admittedly rare occurrence, but it often exceeds 200 GB when stitching large panoramas and the like.
As an example—and stressing that I'm aware that others have even more scratch space than I do—I keep two dedicated, physically separate hard drives as my primary and secondary Photoshop scratch disks and a lot of GB free on my boot drive for the OS. I also have 16 GB of RAM installed.
Additionally, if you only have a single HD, i.e. your boot drive, you'd need it to be large enough to accommodate both the swap files of the OS as well as Photoshop's scratch.

EXIF Data Lost for Edited DNG Files

I'm having an issue where my photo's EXIF data is lost when I export the picture from iPhoto. This only happens after I edit a RAW (DNG) file and export it. If I export the RAW file before editing the EXIF data is fine. Is this a bug?
System Info:
iPhoto v.7.1.3
RAW format type is Adobe DNG.
Camera is Pentax K10D
Mac OS X v.10.5.2.

I've been having the same trouble for a few months now. All EXIF is lost, including GPS and focal info. It only occurs when you edit a RAW/DNG file and have the "save edits as 16-bit tiffs" selected in the preferences. Please, Apple, help! This is a significant issue when exporting photos! That info is essential.
thanks,
Brett

Using DNG SDK for 10bit DNG files

Is there any simple way one can use DNG SDK to write 10bit DNG files?
From what I have seen, DNG SDK can only validate/read/write 8 or 16bit files. I have quite a lot of 10bit raw data to be saved and performing a 16 bit conversion would be both time and space consuming.
If there is no simple workaround to achieve this, is there any chance for future SDK versions to support nonpower of 2 pixel bit depth?
Thank you for your time.

> See these specifications for more information on TIFF and TIFF-EP
I do know that specification. However, DNG deviates from the normal TIFF in enough points to warrant explicite specifications, particularly because several cameras' raw data is compressed in like but not identical ways.
> I'm curious if CR will open 10bit DNG....
The Pentax K10D creates 12bit, uncompressed DNG in this packed format and that will be processed by ACR correctly, so I guess you won't have any problem.
On the other hand, it is interesting, that the DNG converter stores 12 and 14bit data in 16bit form, thereby avoiding the issue; a huge waste of space.

Lightroom 32bit mode for 32bit DNG files

When I open 32bit (floating point) TIFF files in Lightroom (5.7.1) it opens them as expected - in 32bit mode - and allows me to adjust the exposure slider in the range of -10ev to +10ev.
However, when I open 32bit (floating point) DNG files, it opens them in 16bit mode and allows the exposure slider to range only from -5ev to +5ev.
Does anyone know why it works this way?
Is there a way to open 32bit DNG files in 32bit mode?
Note that a 32bit DNG file can be converted to 32bit TIFF using "dng_validate.exe -3 <output.tif> <input.dng>"
This way I can convert my 32bit DNG files to TIFF, but I lose the control over WB and I end up with huge TIFF files.
I'm obtaining my 32bit DNG files using HDRMerge. This can be used as a reference:
https://dl.dropboxusercontent.com/u/21642925/PC211276-211280.dng
I also tried 32bit DNGs that were created by CeroNoice and I get the same result (LR opens them in 16bit mode rather than 32bit and restricts the exposure slider to -5ev - +5ev).
It could be that HDRMerge or CeroNoice do not produce the DNG correctly. However, I tried to run the output of HDRMerge through a DNG to DNG conversion using Adobe DNG Converter and it didn't help either.

Thanks for taking a look at this.
I think that converting 32bit tiff files to dng only changes the wrapping. So in a way it's understandable that they are opened in 32bit mode. I still don't understand why normal 32bit dng files can't.
Thanks for the top about the GND filter. I thought about using a brush all over the frame, but a GND can also be used. I suspect that if LR opens my dng file in 16bit mode than it uses a narrower pipeline for the tone curve and color manipulation so the result will be inferior compared to a 32bit tiff file (developed with the same settings). That's why I'm trying to find a way to open the dng files directly in 32bit mode.

Recovery for corrupt DNG files?

I have many DNG files that are showing as corrupt--files copied from a failing hard drive. The file sizes seem right--around 26MB each, shot with a Canon 5DMIII and converted to DNG via Lightroom.
The bad hard drive is dead now, I can't run recovery software on it, but I do have the files on a healthy drive.
Anyone know of software that might be able to open corrupt DNG files? Some of the photo recovery software I've used in the past works by scanning media, but I have thousands of media files on the drive--I'm looking for recovery software that will let me open specific files and try to recover them. I'm on a Mac. I've tried Photoshop CC, and LR 5.6. When I try to open the .dng files, I get: "Could not complete your request because Photoshop does not recognize this type of file."

Sorry, they're dead.
There's a plugin that will extract your Lightroom preview as a jpg. It won't get your raw files back, but the jpegs ought to be good enough to print.
Best practice says that you need to keep at least two copies of your originals. On separate physical devices.
Hal
p.s. That website I referenced also points to a more full featured program that does the same thing.

Saving .dng files in raw with sidecar

I loaded raw images as .dng -- edited the photos -- and am trying to export as "File Settings / Format: Original" (with the attendant side car XMP). The export folder still contains .dng files and I do not understand what else must be done. I'm a iMac user. Thanks for the help.
Chuck N+13

Chuck,
One other method to extract the XMP from the DNG would be the following:
In LR, Save Metadata to File on all your DNGs
Make your DNG Files read only
Open them in ACR (e.g. using PS)
Make a trival change to the image and then reverse it (e.g. change WB from what it is to something else, then back)
Click Done in ACR
ACR will try to write the XMP data into the DNG, but because it's read only, it will write a sidecar XMP for it.
Step 4 might not be necessary to achieve a write-back of the XMP.
Of course, you still need to get your RAW from somewhere ...
Beat Gossweiler
Switzerland
Message was edited by: b_gossweiler

Editing XMP metadata in Bridge for checked-out files?

Our custom connector does not implement the WRITE_XMP_METADATA Capability because we do not want to change the XMP of a file in our DAM system without checking in a new file version.
However, when a file is checked out through Adobe Drive, we would expect to be able to edit its XMP metadata in Bridge just like we can for local files.
It looks like this is still not possible with Adobe Drive 3, i.e. if your connector does not implement the WRITE_XMP_METADATA Capability you cannot edit XMP for checked out files either.
It seems weird that you can edit XMP metadata for checked out files with regular CS applications but not with Bridge. Is this something that is expected to be fixed in a future version?
Thanks

In our design, editing XMP data in Bridge and in regular CS applications is different, the former one will be routed to SetXMPHandler in you connector, in the latter case, CS applications take the normal file writting ways to embed XMP data in the file content.
The purpose of this design is to offer similar user experience for normal users when they edit XMP data for AD assets and local file assets, they don't need to check-out files first.
To address your issue, I think you can add some codes in SetXMPHandler to auto check-out files before real XMP operation, and check-in them before exiting the handler
We will consider to make some enhancements for this part, that's, to allow editng XMP data for the checked-out files in Br, in the next release, thanks for this advice.

Develop settings lost after re-importing folder of DNG files

I've been using LR for several months, and - after getting accustomed to its peculiararities - love the program.
This evening I re-imported a folder of DNG files that I had previously removed from LR - using the "add" import option. When going to the Develop module, I noticed that my original develop settings were no longer applied.
Aren't these settings incorporated into the DNG files? How could they get lost? Are they over-written when re-importing the files?
I always backup my catalog before closing. Does the catalog backup contain the original develop settings for these DNG files?
I know I must have done something wrong! Please advise & explain. Thanks.

Seven_D wrote:
Thanks. I do have autowrite to XMP checked. - I learned that lesson a few months ago!
I will see if I can use an older backup to recover the settings. I have never done that before, but I know where my catalog backups are located. If you can give some advice on that, I would appreciate it. I don't want to lose other DNG edits in the process.
Correct me if I'm wrong - but it appears that if I ever do want to remove a previously imported folder from LR for whatever reason - I should just edit the RAW files without converting to DNG. I know DNGs are more compact, but at least the sidecar files associated with the RAW files will always be there! This is more important to me than conserving disk space!
just try it on one or tow files to test. Also look at "Read Metadata from file" in the current catalog first with ine file to see if that helps. Did you have a Prest applied when importing like Zeroed?...... None is the best for importing files with dev settings already applied.
I use DNG exclusively and haven't experienced your issue so review your import settings as mentioned.

To update a DNG file?????

Lightroom v1.1 has the following in its Help File----
Save metadata changes to the file manually
* Select one or more photos and choose Metadata > Save Metadata To File.
* In Grid view, click the down arrow icon in a thumbnail image to save (update) the metadata in the file.
Note: The Save Metadata To File command does not update metadata in a DNG file. To update a DNG file, choose Metadata > Update DNG Preview & Metadata.
My 1st question is--
If one maintains their photos in DNG format, based on the above statement does it make ANY sense to check the option File->Catalog Settings->Automatically write changes to XMP?
Taken literally, it seems to me that LR DOES NOT write changes (either manually or automatically) to XMP in a DNG file, unless one specifically uses the "Update DNG Preview & Metadata".
My confusion comes from the process in v1.0 for DNG metadata changes. v1 would save metadata, but you needed ACR 4.X to separately update the JPG.
Which leads me to my 2nd question-
Is Adobe using Preview and embedded JPG as the same thing? I'm assuming :) that what's being updated is the embedded JPG in the DNG and perhaps also any preview in the database.
Obviously, any comments would be appreciated.
Dave

GreSep wrote: I saw another LR discussion that said that with LR 4.3 updating Capture Time would also update Date Time Digitized but it does not do so for me on my DNGs (and as of last month ALL my images were converted to DNGs).
One or two intermediate versions of LR 3 (perhaps Lr 3.6) set DateTimeDigitized when you gave the Metadata > Edit Capture Time command. But for people managing scans in which the capture time of the original image was different than the scan time, this behavior overwrote their scan times, so Adobe backed out of that change. Before and since those versions, the Metadata > Edit Capture Time command just changes the EXIF:DateTimeOriginal and related fields in XMP and IPTC.

Dng. files from LR to PS CC ok Can't open in Camera Raw?

I have LR 5.7 and can edit my dng. files in PS CC but I can only get Camera Filter not full camera raw w/ all the tools. I am a PC user, BTW.
How do I open full Camera raw for a dng. file?
Thanks, very frustrated.
Chris

Because it was edited in lightroom first, photoshop knows enough to bypass camera raw since the controls are identical. If you open the dng file using the normal way like any other format, then it would open in camera raw first.
Keep in mind if you already did any editing in lightroom, those edits needs to be saved to that dng file before you can do the above otherwise camera raw and photoshop will not see the edits you did.
To save a file in lightroom select the file in the library and use ctrl-s to save.
If you do the above, lightroom will not automatically see the changes done in camera raw or photoshop. In library view there will be an icon in the thumbnails corner. This appears when changes to the metadata do not match that of lightroom's database. Clicking the icon should provide a dialog box asking if you want to update lightroom or leave it unchanged.
If you do a folder full, you can sync that folder to update all of them. Keep in mind syncing overwrites your changes in lightroom so make sure that is what you want to do.
I personally try to make it a habit to save all the images from lightroom, just so I don't get any surprises when syncing. There is an icon in the corner of those that need saving.

Sidecar .xmp for a DNG file ...

Similar Messages

Maybe you are looking for