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.

Similar Messages

Physcially export XMP files

Hello,
I have lightroom 5 on windows 7. My boss and I couldn't get smart previews to work a few days ago so he sent me his NEF files with XMP files. I imported them, made my edits, and sent the XMP back to him again. I have the option "automatically write changes into XMP" checked and I have done "cntrl -s" several times to force Lightroom to write the changes. However, when my boss syncs the XMP there are no edits that I have made. Can I physially make Lightroom generate new XMP with my changes?

Ideas of what might be wrong:
You’re doing Save Metadata to File (singular) rather than Save Metadata to Files (plural). Right-clicking on one of the selected thumbnails in the thumbnail bar or library grid is enough to do all Files, not just the image right-clicked on.
The permissions of the files are not read/write for your user, due to how the copy was done, so the XMP files cannot be updated. I would expect an error message in this situation but I’m not sure if LR does or not.
My #1 guess would be that the type of import you did was not an Add, which it should have been, but a Copy, and as such the images and XMPs you’re looking at are still his original files rather than your copy of them that got moved to another location. You can right-click on one of your images and do Show in Explorer and see where yours are.
Do an Export with Original as the filetype with your copy of his images selected to some other folder in and see if you get better XMPs this time.

Possible to export XMP files only?

I want to be able to export the metadata (captions, keywords and ratings) as XMP sidecars alongside my referenced RAW files.
Currently the only way I can see to do this is to export the RAWs with an XMP file - i.e. I have to duplicate all my RAW files! Is there a way to get Aperture simply to generate the XMP files, without creating a new RAW?
Julian

I've not tried this - because I've no need for XMP data at the moment - but I just came across this tool "Lightbox XMP" today: http://www.lightboxsoftware.com/aperture/index.html (the name of the author of Lightbox seemed familiar, so I followed a link from elsewhere...)
I think it might be the sort of thing you're after, and is certainly a neat way to bridge the gap until Apple provide XMP-only export.

What happened to .xmp files?

I have noticed recently that my Bridge program (cs4) has not been automatically exporting .xmp files into the folder where I store my images. I have been doing a lot of reading, but still can't seem to find a solid answer as far as what to do.
I have figured out how to export .xmp files into another folder, but what's the point of that? I want the metadata for my images to stay with my images. When I move them from folder to folder using Bridge, the xmp files used to move also, so I never lost my metadata.
I also empty my cache fairly often. I noticed that Bridge was no longer exporting xmp files when I emptied my cache and ALL my metadata that I had added to my images was gone, just like that.
I am a photographer and need that information to go somewhere permanent automatically, not in the cache which is supposed to store temporary file information.
Anyone have any idea?
Thanks so much!

Tai Lao wrote:
Your post #29 is completely blank
Strange, I responded using email and this normally functions well, maybe the chance in formatting and quoting did not get through?
I don't want you to think I'm ignoring you.
How could you think of that...
here is a copy of the mail, hope the formatting keeps clear!
>> Omke Oudeman wrote:
>>
>> As far as I understood the producing of magenta colorcast is a fault by
>> Pentax and the recovery utility does only work on original Pentax DNG, the
>> PEF files already have some compression and don't display all the sensor
>> data, Right?
>
> Wrong, very wrong. But that is definitely off topic.
It is what I understood (after briefly scanning through page) from this post that advices to shoot in K20 generated DNG instead of the PEF format.
http://www.pentaxforums.com/forums/pentax-dslr-discussion/67532-how-use-k20s-black-pixels- hidden-dngs.html
>> Omke Oudeman wrote:
>>
>> …I did something else, I opened 2 files in ACR, one the original CR2 and the
>> other the DNG conversion of it. ............ I could not find one single >>difference between both files…
>
> That is irrelevant. The issue is that there is some information inside the
> raw files that is not currently used either by the Pentax software or by
> Adobe, but that a third party (Gordon B. Good in this case) was able to
> utilize in order to improve the quality of certain converted raw files.
For your files in certain conditions at high iso this seems to be the case, the DNG files converted by Adobe DNG converter do miss the border pixels needed for the script from GordonBGood.
I tried to download that application but it seems only for Windows, how do you manage to use it?? Thought you have given up on Windows long time ago??
Nevertheless I also tried the apply image method you quoted from Bruce Fraser in an other post, using subtract with offset 128 and both perfectly the same.
I do agree that Raw converters from nowadays can get more out of the Raw data then they did 8 years ago, trying an 8 year old raw file gives a much better result (but then you also have to keep in mind that our knowledge and skills in Digital imaging have grown in combination with better color management understanding and good calibration soft and hardware is also due to this!)
Also I'm not afraid my benefit from the future Raw converters will differ if I use DNG instead of the original Raw, but that is my personal believe. The result I get nowadays for combination of DNG and PS are already more then satisfying, and sure it will be better in the future but for that I have also faith in DNG :-)
> Yes, I use PSDs exclusively. However, if you don't think TIFF will be around
> in 15 years, why do you think DNG will? After all, *+Adobe owns the TIFF
> format+* as well as the PSD format.
>
> If you trust Adobe to keep the DNG alive for 15 more years, why don't you
> trust that same corporation to keep supporting TIFF, a format for which they
> paid darned good money to acquire?
That is just a question of the market, as you could see that our young friend that started this post never uses it and I do hear more voices saying they don't use it or don't see the use for it. Eventually there will be no need for letting seldom used formats taking space in menu's and applications.
DNG however is still talk of the town, whether you like it or not. And therefore more likely to be around in 15 years time. But you are right, If I was to know about what was going on in 15 years from now I would not be a photographer but a fortuneteller and in my free time bathing in countless money :-) :-)
> Another one of the reasons why I don't like DNGs is, number one, that they
> take an awful lot longer to open than the raw files.
That I still can't understand unless you have chosen to use the original raw file included and created a double size for the file. But as stated in earlier post, not the case on my system.
> Not that any of this—or anything else in the world for that matter—should be
> an issue for me then.
Statistically you have lived the greatest part of your life and knowing your health is not something to be jealous of (to put it mildly) your statement about this also is something only time will learn.
Let's wish we still can have a long period for our little chats, agreed or not.
I will give up on getting you to DNG (for now as it is...) :-) :-)
Vriendelijke groet,
Con cordiales saludos
感谢你和亲切的问候

Export Raw Files and keep XMP data

Hi,
I can export files from Lightroom to a folder and select original and I will get the raw file along with the xmp file. I therefore have any adjustments I made there with it. If I , however , export files to a folder and select original and chose Burn Files to Disc, the xmp files dont end up on the disc so I effectively lose all the work I have done to them in light room. Is there a way to fix this. Of course I can just export to a folder and then burn from there , but , I really like the way lightroom just burns disc after disc with no hassle. Burning discs from a folder is a hassle.
Any suggestions?
Thanks for your help in advance !

Hi, Gary. Have you tried converting to DNG, with xmp data embedded in it, then export & burn this?

After importing a Light Room catalog, the files I export, export smaller than the originals - with every option of file ending. I want to export them as DNGs but the files are reduced from around 5000 pixels to about 1700 pixels in length.

Hi All ~ Thanks in advance for your help!
I have been on a support chat with Adobe for 2 hours now and they can't figure this out but hopefully one of you can!
I exported my files as a LightRoom Catalog
I zipped the catalog and the smart previews together
I sent the zipped folder via Dropbox to a photo editor
Editor edited the photos
Editor exported the files as a Lightroom Catalog and zipped them
Editor sent the LR Catalog back to me via Dropbox
I opened the Lightroom Catalog in LR (the pixel dimensions are the same as the originals)
I exported the photos as DNG's (which does not allow for any file size changes - I also tried JPGs and the same thing happened)
     Camera Raw 7.1 and later (I tried them all just to see - and they all rendered the same result)
     Embed Fast Load Data (checked on)
     Embed Original Raw File (check on)
I checked the Pixel dimensions on my exported photos and they are smaller
The original pixel dimensions are:
4912x7360 and the new size (after exporting) is: 1709x2560
But here's the real kicker! WHEN I UPLOAD A PHOTO TO LIGHTROOM FROM MY COMPUTER DIRECTLY (not from a LR catalog), AND EXPORT THAT FILE, IT EXPORTS AT FULL SIZE with no change in the pixels dimensions!

Hi All ~ Thanks in advance for your help!
I have been on a support chat with Adobe for 2 hours now and they can't figure this out but hopefully one of you can!
I exported my files as a LightRoom Catalog
I zipped the catalog and the smart previews together
I sent the zipped folder via Dropbox to a photo editor
Editor edited the photos
Editor exported the files as a Lightroom Catalog and zipped them
Editor sent the LR Catalog back to me via Dropbox
I opened the Lightroom Catalog in LR (the pixel dimensions are the same as the originals)
I exported the photos as DNG's (which does not allow for any file size changes - I also tried JPGs and the same thing happened)
     Camera Raw 7.1 and later (I tried them all just to see - and they all rendered the same result)
     Embed Fast Load Data (checked on)
     Embed Original Raw File (check on)
I checked the Pixel dimensions on my exported photos and they are smaller
The original pixel dimensions are:
4912x7360 and the new size (after exporting) is: 1709x2560
But here's the real kicker! WHEN I UPLOAD A PHOTO TO LIGHTROOM FROM MY COMPUTER DIRECTLY (not from a LR catalog), AND EXPORT THAT FILE, IT EXPORTS AT FULL SIZE with no change in the pixels dimensions!

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

I am able to 'create a new version from original' but when I try to export the original, I only get a .jpg with the XMP file. The original is obviously there but why can't I access it please?

In Aperture 3 when I right click on an image I am able to 'create new version from original' which suggests that the original is there. When I try to export the original I only get a .jpg with the XMP file. These particular images are from 2010, has the RAW file become disconnected somehow? Please, how do I get access to the RAW file for editing in Ps? Thank you. Thomasrevil.

Sorry leonie, 'Use RAW as Original' is not an option for the image shot with the Canon.
Then your Import settings must have been different, when you imported the Canon photos.
You can check, if there is still a hidden raw file somewhere. If the image has been imported as a pair, you should see the "J" badge in Browser and Viewer, if you enable badge overlays. This indicates a pair, with the jpeg as original.
Select one of those images, and then relocate the original files "File > Relocate original" to a folder, where you can inspect it. Use "File > Show in Finder" after ward. Look, don't touch .
Then put it back, using "File > Consolidate".
Do you see your raw files in the folder, or is only a jpeg there?

Context right-click to export XMP metadata to file

I'd like to have the right click context menu include the option to "Export XMP Metadata to Files" in the Library grid or filmstrip. Currently an annoying trip to the Menu bar is required to invoke this function.

It was there for B4.1. The Contextual Menus are getting crowded, so maybe that's why they took it out.
I like lots of Contexual Menus,too. But they get a little useless if too crowded, so maybe they need ot be user configuarable for what one uses the most.
Maybe by V1.5?
Don
Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.8 & Win XP, Pentax *ist D
http://donricklin.blogspot.com/

Export xmp as seperate file

Hi
I'm exporting a mxf file from after effects. I would like to include a xmp file, but not in the mxf file. I would like to have it as a seperate file. Is that possible?
Jakob

Don't think so. AE specifically tries to use the media formats' native options for timecode and metadata nad when using Dynamic Link it also uses the media cache to store additional info. you should look into capturing all information with a script. it's the only way to be 100% everything ends up where you want it.
Mylenium

RAW + old photoshop generated .XMP file conversion to DNG

I have a set of camera raw files (.mos) and .xmp side car files that were generated in photoshop several years ago. I am thinking about converting all of the files and side cars to DNGs because Leaf Capture software is no longer being updated.
Before I do I want to confirm that Lightroom can read both the raw AND the corresponding side car files and convert them into single dngs. I also want to know if the .xmp information is extractable after the dng is created in the same way that the raw/original file is extractable.
I've been trying to test lightrooms ability to read .xmp files on my own. I added a .mos file in a folder with a corresponding .xmp file and a .mos file in a folder without a corresponding .xmp file. Lightroom reads similar adjustment information for both images but only generates a preview that more closely resembles a finished retouched .PSD of the added .mos file that does not have the .xmp file in the folder it was added from. I'm at a bit of a loss regarding how to proceed.

nonovsco wrote:
Upate on situation: I followed up with the individuals that created the files and found out that the side car files were in fact generated by leaf and not photoshop. i tried another test and it looks like the folder with a .mos +.xmp file is now reading differently than a .mos file by itself. both suggest that changes were made to the files with modulations in the "develop" section of lightroom.
You can view the XMP file data in Notepad or any other text editor, just select 'Open' and select 'All File Types' so you can see the XMP files. It should be possible to store both C1 and LR develop settings in the same XMP file, but there may be some naming conflcts. Review of an XMP file with both C1 and LR develop settings saved to it should show the two different develop data sets in Notepad. Conversion to DNG should save ALL XMP data, but you may lose some of the (edit) Leaf proprietary data that may be in the raw file's metadata. For now I'd hold onto the raws + XMPs, even if you do convert to DNG.
You can use EXIFtoolGUI to examine the metadata in the new DNG files and compare it to the original XMP file's data. My Canon DSLRs appear to have all of the manufacturer's 'Makers Notes' copied over from the raw file into the DNG metadata.
http://freeweb.siol.net/hrastni3/foto/exif/exiftoolgui.htm

Do I need to keep my xmp files after converting my raw files to dng?

I originally set up Lr to automatically build xmp files. Recently, I decided to go with dng files and have converted all my raw files to dng. Can I now delete all my xmp files and change my Lr setting so xmp files are no longer automatically produced?

WDKlein1000 wrote:
I think I've got this straight. My goal is to keep the xmp data with the image file (embedded into the file in the case of dng files) as well as in the Lr catalog. I still need to auto (or manually) save xmp files in order for Lr to save the xmp data internally to the dng file. Right?
Perfectly right.
WDKlein1000 wrote:
I've been converting to dng after I have done my initial Lr processing of the raw files and the sidecar files have already been produced. When I convert to dng, the side car files aren't automatically deleted.
I *think* if you say: do not delete previous raw, it keeps both xmp and original raw files. However, if you say: delete original raws upon conversion, it will delete both raw files and xmp sidecars. In other words, they are treated as a unit. So I suspect your raw files are not being deleted either, right? Note: if this is the case, then whenever you sync your folders, it's gonna wanna pull in all the original raws again. If it were me, rather than deleteing the xmp and leaving the sibling raws, I'd move both to a backup.
WDKlein1000 wrote:
I wonder if the sidecar files would ever be produced if I imported with the option to convert to dng and then wouldn't ever be editting the raw files?
They would not. If you know you are going to prefer DNG, it seems prudent to convert upon import.
WDKlein1000 wrote:
I know the sidecar files are relatively small, but I guess it wouldn't hurt to go back and delete them once the xmp data is embeded in the dng files. Right?
Right again - delete away...
UPDATE: I didn't see AR's previous post when I wrote this, sorry for redundancy.
Rob

I edited RAW files as DNG's and need the xmp files- are they embedded in the DNG files?

I was editing for someone else and the like the xmp files to see the RAW adjustments- I edited them as DNG because that is how I'm used to doing it. Now I know but they want me to supply the xmp files which did not write. Is there a wat to do this or do I need to re edit them as RAW's?

DNG files don't have XMP sidecar files. Everything is written to the header of the DNG. And as far as Lightroom goes, It will be necessary for you to specifically write the data to XMP files. Otherwise the adjustments will only be stored in the catalog.

Exporting XMP metadata sidecar files by themselves.

Is there a way to export sidecar files without exporting another master somewhere? I run a referenced library referenced to an archive on my HDD that I can easily back and manage. I may want to export sidecar files for the pictures as a yearly thing or so. As far as I can tell you can only creat sidecar files when exporting a new master which would then created an IMG_1(1) master and double the store space usage. By using the export metadata function you end up with a single text file.
Right now I just plan to manage and backup my metadata via a Vault but the option would be nice to be able to export sidecar files separately from a new master. Maybe I'm asking too much and just need to use the app as it is designed...

Sorry I can't answer that, the script was written a while ago and came from here..
http://www.creativescripting.net/BridgeScripts/barredrock.html
It might be best to write one from scratch, but that would mean knowing what fields were required and what file types.

XMP Files from MAC Not Reading On PC

My question is two-fold, so I apologize that this is long, but it will be best with the backstory:
I shoot Raw on a Canon 5DMIII and import my images into Lr5 on my PC as CR2 files. I am beginning to work with an editor for the post production of my images and upload my files to her via Dropbox. In effort to keep the files as small as possible (and upload/download times shorter), I export my images as DNGs. Specifically, I ensure the 'Use Lossy Compression' option is checked and the 'Embed Original Raw File' is unchecked. I then resize the image to 2000 pixels on the Long Edge and the overall file is under 1MB.
She then imports the DNG files into her iMac for editing also in Lr5. Prior to my exporting, I will edit a few images as sneak peeks for my clients, flag them as a 'pick' and code them as 'red'. When she imports my DNGs, she can see the 'red', but she cannot see the flagged images. Fine, this is something I can live without. She does her editing, also flagging them as a pick and coding them red. She then exports as the original file.
She then uses ExifTool, opens the terminal application and write in: "exiftool -xmp -b -w xmp -r", drags in the DNG files and exports the XMPs. She then sends the XMP files back to me, I place them into my folder with my original RAW files, tell my PC to 'replace' the XMP files that are already in the folder. Then in Lr5, I highlight all my files and select 'Read Metadata From File'.
Now, initially, nothing happens. I am unable to see any images flagged or coded red. However, I do see the 'attention' icon (I'm sure that is not the right name for it) on the upper right corner of the images she has edited when in the library module. If I click on it, it tells me that the MetaData has conflicting information and do I want the file or catalog to be primary. I click on the 'file' option and only then do I see her edits, including the 'red' coding (but not flagged as 'pick').
Part 1 Questions: Why when I am instructing it to 'Read the MetaData From File' is it not automatically picking up her edits? Am I doing something incorrectly when I put the XMPs back in the original folder with the RAW images and have the XMPs replace the originals? Is it normal for the 'pick' flags to not transfer?
Part 2 Questions: When she edits my images, she creates a virtual copy and creates one color and one b+w of each image for my clients. As such, she sends me back two XMP files for one image. How do I get these 2nd XMPs to map to the virtual copy within my library, as I am only creating the virtual copy of an image once I know it is one she selected for the final gallery. If I create a virtual copy of an image she edited after-the-fact, the b+w XMP cannot locate it.
Any guidance is appreciated! Thank you!

I never tried this, but I'm pretty sure that with DNG files, Lightroom will ignore xmp files, even when you instruct Lightroom to "Read Metadata from File". Lightroom expects all the metadata to be in the DNG file, not in the xmp file.
Pick flags, as far as I know, are never written to xmp file; nor are they written to DNG files.
If you're going to make this transfer procedure work, you need to do it by either (a) embedding the metadata in the DNG file and send those back and forth; or (b) use RAW and xmp and then sending the xmp files back and forth (plus I guess you have to transfer the original RAW once to your editor)

Export XMP Files + DNG?

Similar Messages

Maybe you are looking for