Ignoring XMP File in PS "Automate" Function

I have an action that converts RAW (CR2) files to JPEG files while adding several water marks to each file. I use the File-->Automate command to do this. The RAW files are put in a separate folder which then contains both the CR2 and XMP files. The Automate command runs fine but at the end of the Automate run, I get an error message that essentially says that the action could not process the XMP files. That's not a big deal because the RAW files were correctly converted, but is there a way to keep "Automate" from trying to process the XMP files (which MUST be in the folder with the CR2 files in order for my edits to take effect.)? I would like to keep the XMP files as "side car" rather than embedded.

In the automate>batch dialog, at the bottom where it says:
Log errors to file, change this to stop for errors and see if that
helps.
If that does not work, you might try the image processor, under the scripts menu.
If you use the image processor, uncheck the save step in your action.
You can specify a save format in the image processor dialog.
MTSTUNER

Similar Messages

Fix for Camera Raw 5.7 ignoring .xmp files?

I have a problem, some people seem to have: From a certain date on, every sidecared .xmp gets completely ignored. Camera Raw as well as Bridge seem to ignore them. They get created, whether I open them with Bridge or CR. Someone suggested I could fix this problem by associating the CR2 Format with Bridge or Photoshop (CS4), it worked for a while... if I opened it with the Windows Explorer. Opening a CR2 with Bridge netted in the same result: .xmp gets created, but gets ignored by Bridge and Camera Raw. Now even that fix doesn't seem to work: Neither CR nor Bridge want to acknowledge the files.
Is there a fix for that I'm unaware of?
€:
It seems I have found the problem: Someone mentioned it might have something to do with the timestamp of the files not being correct. I checked the date and time of my camera and realised I haven't changed the time, as Daylight-saving changed. Now the .xmp files read correctly. Perhaps that is some use for other people.
€, Update2:
I checked several things: If the modified time of the file lies in the future (here 1hr.), Bridge and Camera Raw have a problem recognizing the .xmp cause it seemed to have been created before the Photo was shot/modified last time. I took the pictures at 01:05pm (the were timed at 02:05pm). CR and Bridge ignored all .xmp-files created before 2:05pm. After 02:05pm, everything worked fine again.

Good to hear that the matter is acknowledged.
I had such cases. I think it was the renaming of old files. Not sure.
Many things can go wrong. Whatever triggers it. It woulld be great to have the option (checkbox) to enforce the (re-)synchronisation of an existing xmp file with a given Raw and/or dng file.
Best regards, Peter

Bug: DNG Converter 8.6 ignoring XMP files

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

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

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)

XMP files remain with NEF files in my folder. Camera Raw suddenly reset leaving my edits gone. Will XMP files enable me to resume with those lost edits?

XMP files remain with NEF files in my folder. Camera Raw suddenly reset leaving my edits gone. Will XMP files enable me to resume with those lost edits?

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)

"Automatically Write Changes into XMP" Not Saving XMP Files

I tried finding some other discussions on this but I couldn't seem to find anything...
I recently checked the "Automatically Write Changes into XMP" setting in my "Catalog Settings". However, as I continue to add pictures to my library and make changes, I do *not* see the XMP files being written to the location of the pictures (Nikon NEF files located on my hard-drive). In fact, I can't find the XMP files anywhere. If I want to output the XMP files I have to do a Ctrl + S (Photo --> Save Metadata to File).
I did notice that when I unchecked the setting and re-checked it, *some* of the XMP files showed up. However, in my import of 24 photos, only 14 had XMP files. I had to manually "Save Metadata to File" to get the XMP sidecar files to show.
Am I doing something wrong? Is something not working right? I'm a bit confused. I assumed it would automatically export the sidecar files.
How often should it be outputting XMP sidecards? If I import a new image should the XMP sidecar file be created? Or is it created the first time I change an original picture?
I am using Adobe Lightroom 2.0 (Camera Raw 4.5) on a Mac OS X 10.5.5.
Thanks,
-Leftquark

@Eric: hitting cntrl+s works but can be tedeous on large galleries. I've been doing this but it can be a pain.
@Jeannine: different topic than this thread but to answer anyways... Lightroom automatically saves all changes into your catalogue. You never need to dave your changes (here's the kicker though) as long as you do not move the original file. If you
move the file than lightroom won't know that it's the same image as the one you've edited. Once you are done editing your image you will need to "export" the image to a new file (you don't wan to overwrite the original). If you don't export than only lightroom will have your edits. Lightroom is "non-destructive" Which means that it doesn't touch your original photo. Lightroom keeps a text file containing the instructions on what you did to make the edited version. Since your changes are just text inatryxtions you have to "export" the image to get your final image in a version you can put online, print, etc. But to answer your original question, I think you prob moves the original image. If not, could you give us more info?

Sidecar .xmp files ignored when importing all files from a card

Hello,
I've noticed what I think is a bug. This is my workflow:
* I shoot pictures as Raw (in .nef format)
* I run a program on them to add sidecar .xmp files with some GPS metadata
* When I import the .net into lightroom I click on "import" on the left panel.
* The import dialog box shows up, with 2 choices : import all pictures from card / select which images to import
1) If I choose to manually select the files to import, the XMP metadata are successfuly taken into account (I choose to convert the NEF to DNG and the GPS data are well imported)
2) But if I choose "import all pictures from card", the GPS metadata are ignored.
Can you advise, please?
Thanks!

Are the XMP sidecars actually on the card?

How do I get Lightroom 4 to automatically create an xmp file?*

How do I get Lightroom 4 to automatically create an xmp file?*

Assuming you have RAW photos
Edit->Catalog Settings > Metadata then check “Automatically Write Changes to XMP”
Not RAW photos ... the same setting causes the metadata to be written into the files, but does not create an xmp file

My Bridge CC has stopped functioning. Think it may have to do with lost XMP files

In a moment that I lost track, I deleted some XMP files from a large file of Photoshop CC files. Now Bridge doesn't open. What to do?
Amy_Wong@

You may get better help in Bridge General Discussion
The Cloud forum is not about using individual programs
The Cloud forum is about the Cloud as a delivery & install process
If you will start at the Forums Index https://forums.adobe.com/welcome
You will be able to select a forum for the specific Adobe product(s) you use
Click the "down arrow" symbol on the right (where it says All communities) to open the drop down list and scroll

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
感谢你和亲切的问候

Acrobat X save metadata to XMP file problem

I am having no luck saving metadata from a PDF to an XMP file using Acrobat X. This has worked properly for me in previous versions of Acrobat, but since upgrading to Acrobat X 10.1.7 the XMP file is given no name automatically, and when saved is zero K and contains no data. I am running on a Mac Pro 3,1 using OS X 10.7.4. I have found only one other mention of this problem in the forum, but it was not answered clearly. Is anyone else having this problem?
Many thanks for any assistance with this!
2014 Update: Still no solution to this. Am I alone with this problem?

Hi Steve,
Thanks for your time on this. Our workflow includes having to repurpose xmp metadata from existing PDFs and apply it to new PDFs. This involves going to the "Document Properties" dialogue, selecting "Description", then "Additional Metadata". From the sidebar of the Additional Metadata dialogue, we would choose the "Advanced" option, which would then allow us to either "Save" the xmp data to a file, or "Replace" the PDF's current metadata with data from an existing xmp file.
This worked perfectly up until we moved to Acrobat X, at which point we were no longer able to save the xmp data to a file. We are able to use the Replace function, but it's critical that we also are able to Save the data.
As David noted, we are also able to successfully Save an xmp file using Acrobat XI Pro running on Windows 7. However, all our production work is done on our Macs, so we hope to regain this capability on the Mac version of Acrobat X Pro or XI Pro.
Cheers and thanks.

Photoshop Elements 6 won't open RAW with XMP file.

Hi,
I searched for an answer but, could not find an answer.
I edited a RAW file with Photoshop Elements 6 (mac). I saved the file and closed the program. Next day I fire up PSE6 and open the same RAW file; the file is unedited. How can I open the RAW file with the edits I made the day before? I see the xmp file in finder.
I'm still on the trial version. Camera is a Canon 50D. I can open and edit the RAW with out problem. When I start PSE6 Adobe update fails and gives me the options: Ignore,Relaunch,Send report to Apple.
After that PSE opens for me
Help me Obi Wan Kenobi; you're my only hope.
Thanks.

Are you hitting the save button? That is creating a DNG file someplace. If you just want to save your edits, that should happen automatically when you click Open or Done. If it doesn't, try going to your username>preferences folder and deleting the Adobe Camera Raw preferences.

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?

Ignoring XMP File in PS "Automate" Function

Similar Messages

Maybe you are looking for