XMP files batch reset?

Hi all, a friend of mine is a photojournalist and is having an emergency. He's telling me that the XMP files for all the RAWs he edited of a particular story have somehow been batch reset, so his edits are gone and he has no idea how this could have happened. Is there any way this is possible? Please help!

Did he copy the images from one drive to another? Depending on the preferences set in Camera Raw: to save xm edits in the ACR database or in sidecar files, the chance of loosing edits exist if you have the prefs set to save in the ACR database and then move tose to a new computer.
Ih he had the prefs set to the ACR database, he should be able to open ACR and change the the prefs to save in an external .xmp file. The key will be to select all the images and make some really, really minor change in ACR (like a +1 Hue or Sat adjustment then click done in ACR. That should force the writting of all the settings to a new .xmp file. He could even go back and change the setting back and re-click done to undo the temp change.
After that, as long as the raw files and .xmp files are both copied to a new drive/computer then he settings should be retained.

Similar Messages

Batch RAW conversion: no sidecar XMP files

When I open and save a RAW file as a JPEG by hand, I always get a XMP file that tells me the RAW settings. Actually the XMP is generated as soon as I "open" the RAW file in PS. When I do the exact same steps in a batched action, no XMP files result. I just painfully batch converted 4000 RAW files, no XMP files showed up. Ran some test cases, manually doing the steps result in a XMP file, batching them doesn't. Why doesn't PS generate the XMP files?
One thing I worry about is what RAW settings were applied to my files. Without the XMP files it's very hard to check. Some settings, like noise reduction and saturation, are pretty subtle and hard to determine w/o a "with" and "without" comparision. In theory the XMP files would let me detemine exactly what settings were applied.
This is for Windows XP, CS3, latest RAW update downloaded a few days ago.

For the case of DNG files with both internal XMP and a sidecar file, Camera Raw picks the file with the newer OS modification date/time.
Adobe does not support sidecar XMP files for JPEG or TIFF files.
It is fairly trivial to write computer programs to exact XMP from files, so yes, it is "possible". You can save the XMP out of any opened file in Photoshop CS3's get info dialog in advanced mode (see the save button at the bottom).

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)

Batch extract file resolution from image xmp file

Hi all, I am looking for a batch process that extracts the X & Y pixel dimensions for a bunch of TIFF files. I find the data in the XMP file when I save out the file: <rdf:Description rdf:about='' xmlns:tiff='http://ns.adobe.com/tiff/1.0/'> <tiff:XResolution>3000000/10000</tiff:XResolution> <tiff:YResolution>3000000/10000</tiff:YResolution> <tiff:ResolutionUnit>2</tiff:ResolutionUnit> </rdf:Description> I do not know if I need to start with the XMP file or if I can start with the source TIFF file. Ultimately I would like to save the dimensions to a database. Any help would be great

It looks like every time I capture an image of a vm, a snapshot is taken of each disk and then a vhd object is also created. So can I convert the vhd's to a disk without going through the create-a-vm-from-image process? Going even further, if I just took
snapshots of my vm's, can I turn those snapshots directly into disks?

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?

Camera Raw 6.7 does not save XMP files

I am running Camera Raw 6.7 on a Windows XP machine.
In the Preferences under "General" I have the "Save image settings in" set to "Sidecar ".xmp" files.
And in the DNG File Handling, I do NOT have the "Ignore sidecar ".xmp." file check-box checked in.
But still when I alter a raw file and press Done the DNG file changes date/size and no XMP-file is
created in the directory. Also when Ioad the picture and "reset" it to "Camera Raw Default" and
press Done, the next time I open it is in the "Image settings" state anyway
Anyone have any idea what the problem could be ?
Regards,
Klas

Noel Carboni wrote:
Adobe has taken the decision to ALWAYS write metadata into file types they know the structure of.
Personally I find this approach apalling...
And you were accused of being an Adobe "fan-boy" only hours ago...
+1 vote for sidecar option - all file types...

*.xmp files are incomplete.

I am running Bridge CS5.1 on OSX Lion.
I am shooing RAW (*.CR2) on a 600D with FW 1.0.2
My workflow is to copy the files from the card to the internal HDD with finder. Then browse the files in Bridge, opening them in Camera RAW when edits need to be made.
This was working until I reset bridge recently due to some cache corruption (which was resolved by the reset). Now, on my latest import when I open the files in Camera RAW, make changes and press done an *.xmp is created, however this file does not contain the changes I made (to white balance, exposure, sharpness, cropping etc). As a result of this, the icon which indicates changes does not show in bridge and when I open the file in Camera RAW again the changes are missing.
Oddly, this problem is only applicable to my latest import - the files which I had imported previously still work within the same workflow. So it appreas there's possibly something wrong with the permissions on the newly created files.
I understand this thread (http://forums.adobe.com/message/4102902#4102902) is addressing a similar problem, and it remains unresolved.
This is a link to an *.xmp file which is holding the changes - http://dl.dropbox.com/u/14483853/IMG_3825.xmp
And this is a link to one which is not - http://dl.dropbox.com/u/14483853/IMG_3832.xmp
Any help would be greatly appreciated.

The XMP files contain information about the last conversion you did on a particular raw file. If you delete it your conversion parameters will revert to defaults next time you open the raw file, instead of Camera Raw using the last conversion parameters.
Go into Edit - Preferences - Camera Raw... and you'll see that you could choose to save the conversion parameters in a central database if you don't like the sidecar XMP files showing up. If you DO choose the central database, consider upping the max size from the default of 1 GB.
-Noel

Why is Bridge creating XMP files in CS6?

I'm using the CS6 beta on a new set of photos. All I've done so far is batch rename all the files (all raw, all CR2) and edited the IPTC metadata - to add my name, the project name, etc. Now I've got a side-car file for every photo. CS5 just included this stuff in the original file, why not CS6?

Hi,
The 'Camera Raw Database' is written to a local directory on your machine, and won't travel (without an extra step) if you copy the CR2 file to another machine. If you use DNG then the metadata will be stored in the file.
If you store the camera raw settings in the Camera Raw database and plan to move the files to a different location (CD, DVD, another computer, and so forth), you can use the Export Settings To XMP command to export the settings to sidecar XMP files.
You may have been using, and wanting, sidecar .xmp files, but just had them hidden in previous Bridge versions. To hide the .xmp file from the Content panel's display, go to View> Show Hidden Files and toggle the checkmark OFF, by selecting it.
regards,
steve

CS3 misses .xmp files from PSE4

I have used PS Elements 4 on Windows for a couple of years. Most of my photos are in RAW (from a Rebel XT). I have it set to save RAW adjustments in .xmp sidecar files. When I look in the directory with Windows Explorer, the sidecar files do, in fact, exist.
I just bought & installed PS CS3. I intend to continue to use PSE4 organizer because I have a lot of collections, tags, etc. I have configured PSE4 to use PS CS3 as its external editor. CS3 is configured to use .xmp files.
When I open a RAW file in CS3 via the PSE4 organizer, the file opens, but the adjustments are not used--it's as if I never adjusted the image.
If I open the file from CS3 Bridge, or directly with PS CS3, it works right. If I adjust a file in CS3, then save it, and re-open it from PSE4 organizer, it works right.
How do I get it to work right when I open a previously adjusted RAW file from PSE4 organizer?

Thank you for taking the time to respond Mr. Castaneda.
Using Bridge in this context, while obviously an effective work-around, only serves as an unnecessary resource hog.
The simple issue is this: What used to take half a second in keyboard taps now requires either the use of an additional program (Bridge) or several additional steps in Finder.
I can't help but to suspect that there is some way to configure my system to behave in the desired manner.
I do use Bridge regularly, but when all I want to do is process hundreds of RAW files in the largest batches possible, I don't see the need to waste resources on it. And it does slow things down noticeably.
I like to use Bridge for sorting, renaming, editing, labeling, etc. But to use it just to open up files seems a little inefficient.
Maybe I'm picking at nits here, but I'm just baffled that this system behaves differently than the one I used a few days ago (same OS, programs, and updates).
Many thanks!
Best regards,
Michael

Import error on XMP files when bringing in image sequences to AE cs6

Hey everyone,
I'm having difficulty getting AE 6 to import my still image timelapse sequences. It throws an error called-unsupported file type extension. I did not have this problem with cs 5.5.
My workflow goes as follows.
-bring RAW stills into bridge and batch edit them in camera raw.
-move stills to LR timelapse and de-flicker them
-import still sequence into after effects.
The xmp files should change as I edit them in camera raw and in LR timelapse but they will not import into AE cs6.
Any help would be greatly appreciated,
Thanks for your time.

They are still pictures that were shot in RAW on a still camera. It calls them cr2 files in windows explorer. They are raw image files brought into bridge and when edited in camera raw-the metadata is saved to an xmp file that accompanies each image. Then you bring the images into LR timelapse and it just adjusts the xmp(metadata) files to deflicker them. Much in the same way that camera raw works. You do not have to export the still at all because all of these changes are saved in the metadata. Then you drop the still sequence into AE and export it as video. It just wont let me export them into cs6 with these xmp files.
The raw files are called cr2 files and without the xmp file-they will import into AE. I tried importing some other camera raw files (NEF files) into AE with the xmp's and it worked. For some reason it does not like these RAW cr2 files with the xmp metadata.
Thanks for your time and help,

Xmp files open with textedit, can I make it stop?

Greetings,
I've gotten into the habit of opening up dozens (or hundreds) of RAW files directly from Finder, with a quick command+A, command+O. On previous machines this has been fine. On my new machine (new to me), doing that causes TextEdit to open up all of the XMP files as well.
I have tried repeatedly to use the "get info" function to set XMPs to open with PS or even with nothing at all. So far I am failing miserably and am forced to take additional steps to either avoid this or to close a ton of XMP files.
I know I can use Bridge, or sort the file types then select just the raw files, but that, for me at least, is quite a bit slower, and I do this every day, so, I'm open to any suggestions.
I'm using a dual 2.3 G5 Power PC, OSX 10.4.10, and CS3 with the latest updates.
Many thanks in advance to anyone who can offer some guidance.
Best regards,
Michael

Thank you for taking the time to respond Mr. Castaneda.
Using Bridge in this context, while obviously an effective work-around, only serves as an unnecessary resource hog.
The simple issue is this: What used to take half a second in keyboard taps now requires either the use of an additional program (Bridge) or several additional steps in Finder.
I can't help but to suspect that there is some way to configure my system to behave in the desired manner.
I do use Bridge regularly, but when all I want to do is process hundreds of RAW files in the largest batches possible, I don't see the need to waste resources on it. And it does slow things down noticeably.
I like to use Bridge for sorting, renaming, editing, labeling, etc. But to use it just to open up files seems a little inefficient.
Maybe I'm picking at nits here, but I'm just baffled that this system behaves differently than the one I used a few days ago (same OS, programs, and updates).
Many thanks!
Best regards,
Michael

Photoshop CS6: removing XMP files

Hi!
In order to use PSD files in another program called Elvis (to archive), it is necessary to remove all XMP files from the PSD document. I'm using Photoshop CS6, with windows 7 (64-bit). This is necessary, because the archive program Elvis reads the XMP files, and than sees every PSD item as a linked item. I tried to remove the XMP files within File>fileinfo> reset all XMP changes and tried to configure the info dialog to delete internal properties. But it didn't work. Is it possible to standardly remove XMP files from a PSD document? And if it's possible, how can i do that?
Thanks in advance!
Greetings,
Irene Poort
Image Editor RTL Nieuws / Editie NL
RTL Nederland

I think if the xmp files are ACR sidecar files they would be important for processing the image's RAW camera file more then any other image file format. For the other image file formats should have the information in the xmp files in their metadata. Also for jpeg files this data xmp data in meaningless as Raw data is not present nor are layers and the same is true for gif files. Only PSD, PSB and Tiff formats support layers and may have embedded raw files in smart objects layers. These smart object layers should also have their own copy of the ACR settings used for the embedded raw file.

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

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!

XMP files batch reset?

Similar Messages

Maybe you are looking for