XMP files in LR4

I am having diffictuly getting LR4.2 to read several xmp files from a LR3 catalog. 98% of the xmp files loaded properly, however the other 2% just won't work. I have reloaded it several times. Does anyone have any suggestions how to fix this?

Sure thing. I was given a LR3 catalog to edit. The images were broken down into 8 folders. Some of the photos were already edited and the photographer wanted me to use her histories for toning purposes. Unfortunately in 1 of the 8 folders, the histories will not show up in LR 4. The xmp files exist, but the histories just won't show up. I didn't have this problem in any of the other folders. So I removed the xmps from the folder in question. I made copies and replaced them into the folder and then told LR4 to look for them in the appopriate place. No dice.
Thank you for taking the time to help me with this problem.
Tom

Similar Messages

Cannot get LR4 to read xmp files from a Nikon D4, Reads the D3S xmp files fine.

I am doing some editing work for a magazine. The lead editor had issues with adobe camera raw viewing some of my edits. The xmp files are there but for some reason they are not loading. We narrowed it down to just the Nikon D4 files. I just had her download a trial version of LR4 and we are getting the same issue. The xmp's are there in the same folder as the .nef files. Import into Lightroom, and all D4 files do not show my edits.
We are both running Lightroom 4.3, Camera Raw 7.3.

LR may or may not have up-to-date XMP files if you haven’t explicitly written them.
I have not encountered the XMP-ignored-if-timestamp-before bug but I believe it is the actual Windows/Mac file-modification timestamp, not something inside the file.
My suggestion is to write all the XMP files, again, and resend those to her. That way you’ll know their contents is current and that their timestamp will have been updated to something after the raw files timestamp. If the images are all in oen or a efw folders then the easiest way to update all their XMPs is to right-click on a folder in Library and choose Save Metadata. If the photos are more scattered but you can select them all in the Library grid view just right-click on one and choose Save Metadata to Files—make sure it says Files not File.
I assume both of you are on Windows, not one on Windows and one on a Mac?

Photoshop Elements 10 not importing GPS data from xmp file

PSE 10 is not importing GPS information from the xmp file. Lightroom correctly records the
GPS data but this info in not brought in when I add the photo to the PSE 10 catalog. Has anyone experienced
the same problem?

The Google map module and geotagging have only just been added to LR4, released this week. There is no longer a map feature in Elements since Adobe dropped the earlier tie-up with Yahoo. Adobe reserves the right to change and amend partner services and this has disappointed many users of previous versions of PSE. It’s possible that the map could be re-introduced into future versions of PSE but don’t count on it and given the significant price cut on LR4, the decision could be strategic.

Exif and gps-data in xmp-file overwritten, sometimes

I have a problem where LR4 on import seems to rewrite the xmp-files, and in that process data is lost, notably GPS-data, is lost.
My workflow:
Create xmp-file with Exiftool from CR2-files (sets copyright etc)
Geocode with Geosetter
Color labels with Photo Mechanic
Import to LR4
After import geo data is gone for around 30% of the files. It seems like files that have recieved a color label by PM is not affected, and many files without color label are correctly imported.
I never loose any data before importing to LR4.
Anyone have any suggestions about what could be going on?
I use a Canon 7D, Exiftool and Geosetter are updated to latest versions, LR version is 4.3.
I couldn't find how to attach files, but if anyone is interested in seeing how the xmp looks before and after LR4 import, I could copy-paste the code in an answer.
Best regards,
/Pär

Hi Pär,
Do I understand correctly that you have an xmp-sidecar present to your CR2-raws, when importing into Lightroom?
Then LR should read it during import.
Maybe the format standards are not clear, maybe Geosetter does not write the xmp-parts where LR expects the data?
But to save your original xmps: change your catalog preference settings, to NOT automatically write xmp to files.
Then you will have time, because then LR just reads the xmps on import, but does not write anything, unless you invoke it by selecting images and hitting <ctrl> s.
Which you would only do once you have assured that everything from your original xmp has arrived in LR's catalog.
Maybe it does not work reading that just during import, but possibly on a 2nd read after?
You could check, once you have disabled auto-xmp-writing, by invoking another explicit Read Metadata from File.
...just a wild guess, to rule out a potential bug there...
Cornelia

Adobe XMP Files not deleted with Raw Files in ACR

I am using Photoshop CS3 on a Windows XP platform. My camera raw files are mostly kept on a Windows 2003 file server, which has a gigabit connection to my workstation. However, I have the same problems when using PS CS3 on my Windows XP laptop.
I take many hundreds of 'technical' photographs using an Olympus E1 and Canon G9 cameras. I usually bracket the exposures on the E1, specially when photographing white painted yachts, and then rate and select the images that I want in ACR 4.1.1. Unwanted images are deleted at this time.
The problem I am having is that the associated *.xmp files are not always deleted with the camera raw files, with the result that I now have literally thousands of these 'orphaned' files cluttering up the server. The only options I have are to delete the files manually, which is a pain, or to leave them on the server, wasting unnecessary space.
I have the same issue with Canon and Nikon raw files, so this problem is not specific to Olympus files.
This is a long standing problem, and I would be grateful if anyone has any answers?
If any Adobe programmers are watching, it would be handy if you could provide a simple utility to delete orphaned *.xmp files, or at least compress them into some kind of archive.
Thanks,
Nigel.

[quote] As far as Photoshop and ACR go, ALL raw files are treated as read-only.
Your original raw files remain untouched, no matter what you do to them.
Any adjustments you make to a raw file are kept only as metadata (flags, if you will) in that XMP side-car file. Every time you want to re-open that raw image file, ACR will reach for the XMP file and apply the adjustments automatically, transparently. [/quote]
That is not quite correct. Camera RAW files can be permanently deleted from within Adobe Camera Raw. The problem with ACR 4.1 to 4.4 4 was that the XMP files were left behind. This now seems to have been rectified in the latest version (ACR 4.5).
Thank you Adobe!

Bridge doesn't recognize its own .xmp files

Using Bridge CS3 on Mac OS 10.5.8. I edit RAW (.nef) files in ACR. When I click done, save, or open image, an .xmp sidecar file is generated and saved in the same folder as the .nef. However, changes made in ACR do not show in the preview thumbnail in Bridge, and when I re-open the file in ACR, my changes are lost. The .xmp file is still there, it's just not applied. It's like Bridge doesn't know the .xmp file is there. The icons in Bridge indicating altered develop settings or crops do not appear after adjudstments are made. Star ratings made in Bridge remain. When this issue began, it would ignore sidecar files for some images, but not others. It is increasing in frequency, or may now be consistent. (If I open the file into Photoshop or save an image file out of ACR, the changes are applied to the developed image file, they are simply ignored by Bridge in regards to the Raw file.)
Files that were adjusted before the problem began still synchronize with their sidecar files. Looking at the sidecar files in a text editor shows that they contain the adjustments made.
There were no changes in any installations/updates to software or OS at the time of the problem's onset.
I've tried using a Camera Raw database instead of sidecar files, and the changes are still lost. I've tried purging caches for Bridge and for ACR. I've tried resetting and dumping preference (.plist) files.
Anyone have ideas on what I can do to salvage this program as my RAW library manager?

Matthew,
Same problem here. But I'm using CS5 in Win7.
Bridge cannot find its XMP files. Bridge does not see its XMP files. XMP files do not work. Camera Raw settings do not show in thumbnails. ACR settings lost.
I just now figured out the problem/solution.
In my case, the association between CR2 files and Bridge was usurped by Canon DPP (the Canon raw converter) which I just installed this afternoon. When I installed it, there was no immediate problem. But when I started a new work session tonight, Bridge acted as if the XMP files weren't even there.
Solution: In Windows, to set a file association, you just right-click on a file (in this case the CR2 file) and select "Open With", and then navigate to Bridge (in my case Bridge CS5). That re-establishes the link between Bridge and its own XMP files. Then simply purge your cache and let Bridge rebuild it using its XMPs (which it can now find again) to rebuild the cache with the adjustments that are stored in the XMPs.
I don't know how to do this on a Mac, but the principle is the same.
I hope this solves your problem.
Dave

How can I use an old XMP file on a new set of images??

I have an older XMP file that contains settings used to retouch some previous images in a particular way. I'd like to apply those same settings to a new set of images. How can I use that older XMP file on a new set of images in Lightroom?
The contents of the XMP file are as follows:
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 4.2-c020 1.124078, Tue Sep 11 2007 23:21:40
">
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description rdf:about=""
xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/">
   <crs:Version>6.0</crs:Version>
   <crs:ProcessVersion>5.7</crs:ProcessVersion>
   <crs:WhiteBalance>Custom</crs:WhiteBalance>
   <crs:Temperature>4700</crs:Temperature>
   <crs:Tint>+4</crs:Tint>
   <crs:Exposure>-0.35</crs:Exposure>
   <crs:Shadows>5</crs:Shadows>
   <crs:Brightness>+50</crs:Brightness>
   <crs:Contrast>+25</crs:Contrast>
   <crs:Saturation>-8</crs:Saturation>
   <crs:Sharpness>25</crs:Sharpness>
   <crs:LuminanceSmoothing>0</crs:LuminanceSmoothing>
   <crs:ColorNoiseReduction>25</crs:ColorNoiseReduction>
   <crs:ChromaticAberrationR>0</crs:ChromaticAberrationR>
   <crs:ChromaticAberrationB>0</crs:ChromaticAberrationB>
   <crs:VignetteAmount>0</crs:VignetteAmount>
   <crs:ShadowTint>-1</crs:ShadowTint>
   <crs:RedHue>0</crs:RedHue>
   <crs:RedSaturation>0</crs:RedSaturation>
   <crs:GreenHue>0</crs:GreenHue>
   <crs:GreenSaturation>0</crs:GreenSaturation>
   <crs:BlueHue>0</crs:BlueHue>
   <crs:BlueSaturation>0</crs:BlueSaturation>
   <crs:FillLight>0</crs:FillLight>
   <crs:Vibrance>+5</crs:Vibrance>
   <crs:HighlightRecovery>24</crs:HighlightRecovery>
   <crs:Clarity>+8</crs:Clarity>
   <crs:Defringe>0</crs:Defringe>
   <crs:HueAdjustmentRed>0</crs:HueAdjustmentRed>
   <crs:HueAdjustmentOrange>0</crs:HueAdjustmentOrange>
   <crs:HueAdjustmentYellow>0</crs:HueAdjustmentYellow>
   <crs:HueAdjustmentGreen>0</crs:HueAdjustmentGreen>
   <crs:HueAdjustmentAqua>0</crs:HueAdjustmentAqua>
   <crs:HueAdjustmentBlue>0</crs:HueAdjustmentBlue>
   <crs:HueAdjustmentPurple>0</crs:HueAdjustmentPurple>
   <crs:HueAdjustmentMagenta>0</crs:HueAdjustmentMagenta>
   <crs:SaturationAdjustmentRed>0</crs:SaturationAdjustmentRed>
   <crs:SaturationAdjustmentOrange>0</crs:SaturationAdjustmentOrange>
   <crs:SaturationAdjustmentYellow>0</crs:SaturationAdjustmentYellow>
   <crs:SaturationAdjustmentGreen>0</crs:SaturationAdjustmentGreen>
   <crs:SaturationAdjustmentAqua>0</crs:SaturationAdjustmentAqua>
   <crs:SaturationAdjustmentBlue>0</crs:SaturationAdjustmentBlue>
   <crs:SaturationAdjustmentPurple>0</crs:SaturationAdjustmentPurple>
   <crs:SaturationAdjustmentMagenta>0</crs:SaturationAdjustmentMagenta>
   <crs:LuminanceAdjustmentRed>0</crs:LuminanceAdjustmentRed>
   <crs:LuminanceAdjustmentOrange>0</crs:LuminanceAdjustmentOrange>
   <crs:LuminanceAdjustmentYellow>0</crs:LuminanceAdjustmentYellow>
   <crs:LuminanceAdjustmentGreen>0</crs:LuminanceAdjustmentGreen>
   <crs:LuminanceAdjustmentAqua>0</crs:LuminanceAdjustmentAqua>
   <crs:LuminanceAdjustmentBlue>0</crs:LuminanceAdjustmentBlue>
   <crs:LuminanceAdjustmentPurple>0</crs:LuminanceAdjustmentPurple>
   <crs:LuminanceAdjustmentMagenta>0</crs:LuminanceAdjustmentMagenta>
   <crs:SplitToningShadowHue>138</crs:SplitToningShadowHue>
   <crs:SplitToningShadowSaturation>13</crs:SplitToningShadowSaturation>
   <crs:SplitToningHighlightHue>0</crs:SplitToningHighlightHue>
   <crs:SplitToningHighlightSaturation>0</crs:SplitToningHighlightSaturation>
   <crs:SplitToningBalance>0</crs:SplitToningBalance>
   <crs:ParametricShadows>0</crs:ParametricShadows>
   <crs:ParametricDarks>0</crs:ParametricDarks>
   <crs:ParametricLights>0</crs:ParametricLights>
   <crs:ParametricHighlights>0</crs:ParametricHighlights>
   <crs:ParametricShadowSplit>25</crs:ParametricShadowSplit>
   <crs:ParametricMidtoneSplit>50</crs:ParametricMidtoneSplit>
   <crs:ParametricHighlightSplit>75</crs:ParametricHighlightSplit>
   <crs:SharpenRadius>+1.0</crs:SharpenRadius>
   <crs:SharpenDetail>25</crs:SharpenDetail>
   <crs:SharpenEdgeMasking>0</crs:SharpenEdgeMasking>
   <crs:PostCropVignetteAmount>0</crs:PostCropVignetteAmount>
   <crs:GrainAmount>0</crs:GrainAmount>
   <crs:ColorNoiseReductionDetail>50</crs:ColorNoiseReductionDetail>
   <crs:ConvertToGrayscale>False</crs:ConvertToGrayscale>
   <crs:ToneCurveName>Medium Contrast</crs:ToneCurveName>
   <crs:ToneCurve>
<rdf:Seq>
<rdf:li>0, 0</rdf:li>
<rdf:li>32, 22</rdf:li>
<rdf:li>64, 56</rdf:li>
<rdf:li>128, 128</rdf:li>
<rdf:li>192, 196</rdf:li>
<rdf:li>255, 255</rdf:li>
</rdf:Seq>
   </crs:ToneCurve>
   <crs:CameraProfile>Adobe Standard</crs:CameraProfile>
   <crs:CameraProfileDigest>3DA8CE4A626CE36A1D0C55BF157793C9</crs:CameraProfileDigest>
   <crs:HasSettings>True</crs:HasSettings>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>

I’m pretty sure Adobe NEVER intended for someone to copy an XMP file from one photo to another outside of LR as a way to replicate settings.   You can make a preset from a photo, as discussed, or if you don’t want to do that, copy-paste the settings from a representative photo that you initially select to one or more new photos. You could have a special LR folder that holds standard photos to copy/paste from. Of course creating a Develop preset from the representative photo is the “normal” way to handle such situations, but maybe you have hundreds of different situations to copy settings from and don’t want to create presets for each one, but I’d argue that you could create a complex folder hierarchy for your presets and still have them findable without that much problem.
As far as the mystery about why some photos show Reset and some show From Metadata, is the Process Version (down in Camera Calibration) of the photo before reading the settings the same between the two situations? And in general, are these virgin photos newly imported into LR or have some been modified in LR, already? Does an XMP file already exist for any of these, where that XMP is being overwritten by your external-to-LR copying? Or do you have auto-write-XMP enabled and your hand-copied XMP is getting overwritten by LR, automatically, before you have a chance to read in anything?

How do I reconnect my xmp files in PE9?

After moving and copying photos between two internal and one external hard drive I find I have a lot of xmp files in the Recycle bin. Can I "reconnect" these files to the images and video clips they belong to? The dates are messed up and tags are missing from a lot of my stuff after all the moving.
Tim K

dsf,
Not sure exactly how you moved your library but this link may help
http://www.ilounge.com/index.php/articles/comments/moving-your-itunes-library-to -a-new-hard-drive/

.XMP files no longer appear as sidecars--how to clear metadata?

Photoshop CS2 ver 9.0.2
Bridge ver 1.0.4.6
ACR ver 3.7
eMac G4 800 MHz
Mac OS X ver 10.4.9
1 Meg RAM
12 GB available disk space
Bridge and Photoshop are set to save metadata in .XMP sidecar files, but sidecar files no longer appear. That is, up till a few days ago, .XMP files appeared when I opened raw files, but no longer. The drop-down menu is still set to save metadata in sidecar files.
Cannot clear metadata in Bridge. I can select "Camera Raw Defaults" in ACR, but that doesn't clear cropping.
1) How do I return already-stored metadata to .XMP files?
2) How do I get PSCS2 to store future metadata as .XMP files?
3) How do I clear metadata currently stored in ACR/PS database?
4) What did I do to cause system to store metadata in ACR/PS database despite being set to save in sidecar files?
Thanks.
--HC

Noel,
Excellent point. I have no idea. Maybe this was only working for
.PSDs/etc. (which contain the metadata embedded in the file itself[,
right?]). I may have been deluding myself this whole time. It's
possible that it never really worked the way I thought it did to begin with.
But, more specifically, here's the current question: If I have this
file (which is a backup from long ago):
J:\backup of M90\Documents and Settings\philipt\Application
Data\Adobe\CameraRaw\Database
...assuming that drives are currently mapped (by drive letter) the same
way they were when that backup was made), can I just replace the current
file:
C\Documents and Settings\philipt\Application Data\Adobe\CameraRaw\Database
...with the one from J: and expect it to work correctly?
What's the worst that can happen if I do this?
BTW, the file on J: is 2,569 Kb; the (new) one on C: is 2,754 Kb. This
doesn't seem to bode well, since the old one (J:) should have much, much
more data in it (assuming that the "Database" file per se is where the
metadata is stored): the older file has complex,
multi-tiered data for 10s of 1000s of images. "??"
Thanks again for your willingness to help with this!!
Aloha,
-pt

How can I make metadata saved to xmp file stay saved?

When a raw file badge shows that the file has been changed, I use Metadata Save to File & for the large majority of my images, the badge goes away and Metadata Status Changed does not show the file. For some of my files, however, the Save to File command doesn't work properly. If I am only displaying files with changes, the file briefly disappears, then returns. Even if I go to Windows Explorer and delete the xmp file, then again Save metadata to file, it pops up again with the badge saying it needs to be saved. Can anyone tell me what I might be doing wrong, or is there a bug? I'm using Lightroom 4.3 64 bit on Windows 7.

I have determined one definite cause for this problem, documented (see 2nd post) here:
http://feedback.photoshop.com/photoshop_family/topics/lightroom_4_4rc_metadata_needs_to_be _saved_status_not_cleared_by_saving_metadata
As has been mentioned, following metadata save with metadata read is a work-around.
Note: you can see exactly, everything, the difference between metadata in catalog and metadata in xmp on disk, using ChangeManager's "Compare Catalog to Disk" feature; hint: choose 'No Exclusions' to see the "inconsequential" differences too. Reminder: this does a bunch of stuff involving xmp file copying and saving xmp / reading metadata / restoring afterward... - which presents lots of hoops to jump through, at first, in Windows, and forever, on Mac, but if you tough it out, you will get the pot of result gold at the end of the hoop rainbow...
Cheers,
Rob

4.1.1 SDK Problems with missing xpacket tags in sidecar XMP files

The current 4.1.1 SDK has problems with sidecar XMP files that don't have the xpacket headers and trailers, i.e:
<?xpacket begin='ï»¿' id='W5M0MpCehiHzreSzNTczkc9d'?>
<?xpacket end='w'?>
is missing. Now, unfortunately Adobe Bridge CS2/CS3 does not export these xpackets in sidecar XMP files.
The standard, http://www.aiim.org/documents/standards/xmpspecification.pdf, is also very vague about it all:
● Write external metadata as though it were embedded and then had the XMP Packets
extracted and catenated by a postprocessor.
The grammar is strange(past tense had) and the spec implies that the xpacket should be extracted and again catenated... Someone should review this document and clearly state if xpacket statements should be in sidecar files or not. I suspect myself that they should be there, but the standard is very vague.
Anyway, there are two places in the SDK code where changes might be needed:
XMPFiles::Initialize has XMP_Asserts in case the xpacket header/trailer is missing, but the underlying assert is only active in debug builds.
XMPScanner::PacketMachine::FindNextPacket () also has in its truth table the assumption that the xpackets exist.
There could be even other places in the code that assumes that the xpacket tags are present in all files, which includes text XMP sidecar files.
Anyway.
a) Shouldn't bridge export the xpacket tags? Same with any other application?
b) If the spec is vague, then the SDK should not assume that the xpacket tags are present.
Any comments? Has someone already fixed this issue as I suspect a lot of apps using the the XMP SDK would break concerning reading XMP sidecar files? Thx, Kent

I was able to work around the problem by creating a mapped view of the .xmp file (this creates an array in memory backed by the file on disk, so there's no need to read the file into a separate internal buffer), and constructing the SXMPMeta object directly from the buffer. (The ctor for that class calls ParseFromBuffer, so this is the same thing as was suggested by other messages in this thread.)
It seems that Adobe needs to do one of these things:
(1) say that Bridge CS3 has a bug, and agree that Bridge CS3 should include a proper xpacket header when writing xmp sidecar files
(2) say that the XMP Toolkit has a bug, and that the SDK should be able to parse sidecar files without an xpacket header, and agree to fix the toolkit
(3) say that Bridge CS3 and the XMP Toolkit behave as expected, but then provide a sequence of steps by which users of the XMP Toolkit are expected to read xmp sidecar files written by Bridge CS3
Does Bridge CS4 write an xpacket header to the xmp sidecar files?
Maybe what I could do is create a custom file handler for .xmp sidecar files, so I could use the SXMPFiles for everything, instead of having to special-case .xmp files.
My needs are pretty modest though, and it might be just as simple to use the MS DOM-based XML parser for load the xmp sidecar file. I bet I could get the data I need (only the "Rating" for now) using a simple XPath expression.
-Matt

Bridge stops recognizing it's own .xmp files from Canon 5DMKIII

I use Bridge to add keywords to my RAW files. I use both a Canon 1D MKII and a Canon 5D MKIII camera. I use Canon's "Digital Photo Professional" (DPP) to process my RAW files because I prefer the colors (I am a picky perfectionist, so don't try and convince me to use ACR to process my RAW files!) When I make changes to my RAW files shot with the 5DMKIII in DPP and "save" the changes to the RAW files, Bridge suddenly doesn't recognize the file's associated .xmp file, and my keyword association is lost. If I simply open the file in TextEditor and re-save it, suddenly Bridge recognizes the file again. RAW images shot and processed with this same procedure from my Canon 1D MKII don't exhibit this problem.
This thread from a couple years ago is the same problem I am experiencing:
http://forums.adobe.com/message/2933287#2933287
Is there any other solutions to this? I shoot several thousand images per weekend, and opening each file in TextEdit and saving is NOT an option!
Please help!
P.S., I'm using Bridge CS5.1 v 4.1.0.54

Wes Duenkel wrote:
I am a picky perfectionist, so don't try and convince me to use ACR to process my RAW files!
Birds of a feather you and I, except that (with the help of a very nice forum member here) I have actually managed to get the same color out of Camera Raw that I get from Canon, so that is now my default in Camera Raw. Unfortunately, we created a profile for a different camera than you have (I use a 40D), so it is not applicable for you. But I just wanted to comment to say that I know EXACTLY how you feel.
Sorry, I don't have much to offer re: help for your .xmp issue.
-Noel

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)

I can't import RAW files in LR4.4?

Hi, i'm using LR4 updated to the latest version LR4.4, I tried to import my RAW pictures from my NIKON D3300 (.NEF) but I can't. it says the following;
'The files are not recognized by the raw format support in lightroom'. What does that mean? and how do I import those RAW files in LR4?
I can see the images preview, can't open them and can't import them. Help please?!

First, you don't have the latest version, and you need at least Lightroom 5.4 to open these photos.
If you don't want to upgrade (which costs money) to Lightroom 5.4, you can download the FREE Adobe DNG Converter (version 8.4 or later) and then use that software to convert your RAWs to DNG, and then import them into Lightroom 4.4.

Metadata & XMP files in Bridge CS3 under Windows XP

Question regarding Bridge CS3, 2.1.1.9, on a computer running Windows XP Pro, Service Pack 3:
A useful feature seems to have disappeared from my installation of Bridge. In Horizontal Filmstrip view, I used to see a little icon over the thumbnails showing the CR2 files that I had opened and processed in Camera Raw. The icon was a small circle with a downward-pointing triangle, if I recall. The CR2 files that I had never opened in Camera Raw did not show that icon. Now I never see the icons, even for those CR2 files for which the XMP file is present in the same folder as the CR2 file.
Is there a way that I can get Bridge to display those icons again?
Thanks.

CS3 does have a symbol for a modified RAW thumb. This differentiates if from the unmodified RAW thumb. A circle with 2 arrows in it I believe.

XMP files in LR4

Similar Messages

Maybe you are looking for