ACR 4.3 .xmp file problem

Would appreciate help on this if anyone has seen the problem.
I use ACR 4.3 on windows XP Pro with CS3, 4 gig ram.
My normal practice is to copy my CF cards to folders on the desktop, then
drag each folder to Bridge to rough select the keepers.
I then open the remaining images in ACR and make further deletions if
necessary.
When I delete images from the ACR screen, the X appears as normal but the
sidecar.xmp file is not been deleted, only the NEF deletes.
I can't recall having this problem before I upgraded to ACR 4,3 from 4,2.
Perhaps it's a bug or I may have disturbed a setting in the preferences etc
when I upgraded.
Any ideas?
Regards
Michael

Ramón G Castañeda wrote:
> Camera Raw 4.4.1 contains new profiles for all cameras and fixes.
That's right. And it also can read the updated DNG 1.2 file format. Camera Raw 4.3 cannot; it will read DNG 1.0 and 1.1 only ... or to be more precise, it
i can
read DNG 1.2 files but only the 1.0 and 1.1 parts of them.
And DNG Converter 4.4 and 4.4.1 will write DNG 1.2 files.
-- Olaf

Similar Messages

ACR not using .xmp files after 03/09/2011

I'm using ACR 6.4.1.145 and Bridge CS5 on a Windows 7 x64 Pro machine. Canon S95 and G12 CR2 files created before 04/09/2011 behave exactly as they should: changes aved in .xmp files are recognized and applied in Bridge thumbnails and when the image is re-opened in ACR.
Images created on 04/09/2011 and any later date (tested by altering the file dates) have their changes saved in an .xmp file, but this file is not applied to the thumbnail in Bridge, the Bridge thumbnail does not indicate the .xmp file exists, and the .xmp changes are not applied when the image is reopened unless the .xmp file is loaded manually.
I have purged the cache, restarted Bridge, and restarted Windows. I've moved the images to a different directory, then a different drive. I've loaded the images from the SD card several times now. The problem persists.
All assistance appreciated.

Thanks Thomas.
I am pretty sure the CR2 files don't contain any .xmp data. For one thing, the problem only occurs on my installation. If I use another computer, everything works as it should.
The problem has returned, however. I just tried to make changes in ACR to images created today, and although ACR saves the .xmp, it does not recognize it when I open the image again. I have to load the .xmp manually.
I will bet that tomorrow, the problem has gone away. That would make it somehow time/date dependent. More important to you and anyone else trying to help, it seems to happen only on my installation of CS5. Something has gotten corrupted, I think. If the problem persists, I will probably try a re-install, but I hate the patching proces that follows.

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.

XMP file problem

As a photo archivist at a museum I need to be able to fill in the description fields of the xmp file before the image is created. My work flow is exceptionally inefficient due to wait time as the scanner creates the image file. Short of using two scanners and two computers is there a function or step within photoshop that will allow me to create an xmp file out ahead of the image file?

I'm wondering if Photoshop version is going to make a difference from the point of view of image size. Have we always been able to paste a layer bigger than the canvas for instance? I am pretty sure the answer is yes.
But Noel's idea would work perfectly, and I suspect the OP's version of Photoshop is too new to support TWAIN.
So there you are. Create a new document and start filling in the EXIF data in Bridge. Then duplicate the scanned artwork into that document and flatten.

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!

ACR 4.3 xmp problem

Sorry to repeat this request but its very important to me and I've had no replies on this topic.
Am I to assume its just me and everyone thinks I should be aware of this situation or is it a problem no one has encountered?
It would be very simple for someone to duplicate if you have a little free time. It's happening on two different machines.
Problem
Would appreciate help on this if anyone has seen the problem.
I use ACR 4.3 on windows XP Pro with CS3, 4 gig ram.
My normal practice is to copy my CF cards to folders on the desktop, then
drag each folder to Bridge to rough select the keepers.
I then open the remaining images in ACR and make further deletions if
necessary.
When I delete images from the ACR screen, the X appears as normal but the
sidecar.xmp file is not been deleted, only the NEF deletes.
I can't recall having this problem before I upgraded to ACR 4,3 from 4,2.
Perhaps it's a bug or I may have disturbed a setting in the preferences etc
when I upgraded.
Any ideas?
Regards
Michael

Ramón G Castañeda wrote:
> Camera Raw 4.4.1 contains new profiles for all cameras and fixes.
That's right. And it also can read the updated DNG 1.2 file format. Camera Raw 4.3 cannot; it will read DNG 1.0 and 1.1 only ... or to be more precise, it
i can
read DNG 1.2 files but only the 1.0 and 1.1 parts of them.
And DNG Converter 4.4 and 4.4.1 will write DNG 1.2 files.
-- Olaf

HELP. ............Hi folks hope some one can help me please.Having a problem in Bridge I open my images in ACR, as I open files in a folder and lets say they are labeled in yellow they are all going back to the camera raw default , in other words no ma

HELP. ............Hi folks hope some one can help me please.Having a problem in Bridge I open my images in ACR, as I open files in a folder and lets say they are labeled in yellow they are all going back to the camera raw default , in other words no matter what work I have done, inc cropping they all go back to ,as they came out of camera. What on earth is happening? I am on PS CS6. I might point out everything was working normally up to yesterday, when this first started.
I recently changed computer to 64bit from 32bit, not sure if this causing the problem or not. Any help would be appreciated.

Robert,
Would you be so kind to rephrase your question with concise, precise information and without any "let's say that" hypotheticals? Sorry, I can't quite follow you.
Also please give exact versions of Photoshop CS6 (13.what.what), of Bridge and of your OS.
Thanks.
BOILERPLATE TEXT:
If you give complete and detailed information about your setup and the issue at hand, such as your platform (Mac or Win), exact versions of your OS, of Photoshop and of Bridge, machine specs, what troubleshooting steps you have taken so far, what error message(s) you receive, if having issues opening raw files also the exact camera make and model that generated them, etc., someone may be able to help you.
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Thanks!

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 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

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

FotoStation wipes ACR settings from .xmp

My employer has recently decided we need to use FotoStation (mostly because we work over a network, and FS is good for that... anyway) to organise, and apply metadata to, our photographs and videos. I do still use Bridge for previewing, ratings and making adjustments via ACR.
I have noticed that when I have updated the metadata via Fotostaion, it removed ratings and ACR information from the .xmp file in Bridge (not the file itself, just the specific ACR/ratings data within). I made sure that, when I made the changes in FotoStation I selected to "Append new text to existing text" (the other option is to "Replace the existing text"). It definitely removes the ACR information because I tested it out by opening an image in ACR, editing it, clicking done (definitely clicked done not cancel, changes seen in Bridge) then updated the metadata via FotoStation, went back to Bridge and the ACR changes were gone. I opened the "File Info" and read the "Raw Data" before and after the FS edit and the info was there before and gone after.
SO is there a way to not allow this to happen? FYI I will be posting this to the FotoStation forum as well, I just want to cover both bases. FotoStation doesn't feel it is necessary to have a forum apparently. I'll provide camera and application information below.
Windows 7 x64
Working over a network
Adobe Bridge CS6 (v5.0.2.4)
Camera Raw 8.4
FotoStation 7.0 (Build 459)
Canon EOS 5D (.CR2 files)
No I cannot work off the network, or get newer versions of applications (at this current time); what I have there is all I have to work with at this point in time.
I will, for now, simply add the metadata using Bridge but I would still like to see this issue resolved if possible as it is the preferred method utilised by my employer and not my decision to change. My input is not required

I don't have FotoStation b459 only b60*. I can confirm that you need to rebuild the thumbnails in FotoStation to see metadata changes done in Adobe Bridge. This forces FotoSation to re-index the image.
There should be no unintentional metadata lost when going back and forth between FS and Bridge. However, you should check that your FotoStation metadata configuration includes the Adobe and IPTC name spaces and fields you need. If not you can create them manually or import from an image. The FotoStation documentation shows that this is easy to do.
As an aside I find that Adobe CS5 deletes metadata information in fields that are deprecated or no longer belong to the Adobe name space. This is a potential serious problem for digital images generated using legacy software and hardware.
As a FotoStation user for the last 4 years, in my opinion, your employer is correct. FotoStation is one of the best software for metadata and digital asset management. Good luck!

Camera Raw does not read previously saved XMP files (Canon 60D)

Hi,
I want to ask if it is a real problem or just me doing something wrong.
I open RAW files made with Canon 60D (Photoshop CS5, Camera Raw 6.6), then I do what a do (cropping, exposure changes, sharpen ... etc.), then I click the Done button. Camera Raw saves XMP files along with the RAW files. After this I want to do some more editing, I open the RAW files, but Camera RAW does not "remember" what it did just minutes before. I suppose that it is not reading the XMP files that it created.
So is it me or it is some kind of bug?
I don't have this problem when editing RAW files made with Canon 400D.
Thanks for your time!

Bo LeBeau wrote:
If I understand correctly the issue is not viewing in Bridge, but rather that ACR doesn't remember the changes.
There is a discussion in the Camera Raw forum about this issue of not always reading the changes after clicking Done in ACR.
But no solution.
http://forums.adobe.com/message/4096784#4096784
Yes, ACR doesn't remember/show the changes I made.
It seems that I have the same problem as the other forum member from the link. I tried to recreate the issue, but this time all went well and ACR displayed the changes I made ...
It is strange because I had the issue numerous times on two different windows PC's ...
Message was edited by: Orhan Chakarov

Can I save PS edits in an xmp file to be read by LR?

The reason I ask this is I have hundreds of photos that were taken on a 5D with a scratched filter, so I am treating the marks as dust bunnies and getting rid of them in the same way, using spot healing and for the scratches, whtever the feature is called where you use the spot healing brush but you 'draw lines'.
However I am one of the many who suffer appalling performance in Lightroom edits so after maybe 20 spot heals the computer slows down so much so as to be unusable. So I then send the file into PS/CS6 as the same doesn't happen there.
I quickly fix all my spots and scratches and then I appear to only have the option of saving the file as a TIF back to LR.
What I'd love to do is save the xmp file, and then have LR update the image given those xmp changes.
Is this possible or do I have to continue to have the extra TIF file?

Hmmm I can't replicate what I did now. The problem with using ACR is that the spot removal tool is just that, a spot. It doesn't allow the removal of scratches, which is the whole point of what I'm doing. If I hit 'Done' after healing a spot it does indeed write to the xmp file, but then I hvae to delete the preview and refresh in order to see the change. I could cope with that if the ACR spot removal was the same tool as in LR, where you can do scratches as well.
Oh well, I'm halfway there so should be grateful for that. Cheers.

Local adjustment brush, not in XMP file

Local adjustment brush, not in XMP file
I shoot everything on location and make minor edits while on location. My location edits usually transfer with the XMP file. I used the new local adjustment tool while on location, however when I got back to my main workstation and transferred the images the local adjustments were not there. Can this be fixed somehow, as it would be nice to only make those edits only once? I do not use as a catalog program, once the job is complete it is removed from the lightroom catalog so again those local adjustments are gone.
Thanks
Mark

The problem may be and I am only guessing here that because no other program
currently supports the adjustment brush options that that information is not
added to XMP file. Not even Photoshop or ACR supports that as of yet. Though
I honestly would have expected that information to be there anyways it would
just be ignored by programs that don't know what to do with (basically
everything but LR 2.0).
Have you tried using DNG files. From what I understand an XMP file it not
needed as the information that is normally in a XMP file in kept inside of
the DNG file. This maybe another reason to go with the DNG format.
Good luck.

ACR 3.7 White Balance Problem

I have just installed Photoshop Lightbox 1.0 on my Windows (XP SP2) PC. After importing a few hundred adjusted DNG files into this software, I noticed that many of the images had severe (thankfully easily spotted) pinkish colour casts indicating a serious white point shift. Viewing the same images in Bridge using ACR 3.X (3.2?) revealed no problems. Now I am a bit confused here. Lightbox claims to use ACR 3.7, which is supposed to be a shared resource with Photoshop. However my version of Photoshop CS2 indicated it was using an earlier version. Anyway, I then upgraded my ACR plugin to v3.7 and low and behold the same problem appeared in Bridge / ACR 3.7.
The problem does not affect all images. It seems, though I am not sure, that it is only those images where the white balance had been set to a custom value that are affected. Other settings: exposure, contrast etc, seem to be unaffected. It is possible to fix the problem in the Bridge + Photoshop + ACR 3.7 environment using the previously saved "fixed" images as references. However the problem remains in Lightroom, presumably because the RAW adjustments are stored separately, and is not so easily fixed, as it does not seem to be possible to have two different images side by side while carrying out fine white-point adjustments.
Anyway, to cut to the chase, I am quite furious that this could have happened at all, as it raises serious questions about the backward compatibility of the software and/or the ability of RAW (DNG) files to preserve adjustment information securely against changes in the software environment. What has occurred should be impossible, but evidently is not. Maybe these digital negatives are not so safe after all.
Anybody got any idea what went wrong and how to fix it? Is there a way to reset Lightroom to the externally applied RAW adjustments?

Actually the product I am talking about is ACR 3.7, which is common to Photoshop CS2, Bridge and Lightroom. The Read Me! notes accompanying my installation of Lightroom clearly states that it uses ACR 3.7 (and that upgrading ACR 3.7 in Photoshop would be necessary to ensure consistency, which I have done). The reference to Lightroom was important, as unlike the Photoshop ACR, in my setup, Lightroom does not store the adjustment settings in sidecar XMP files, or, in the case of DNG files, within the files themselves. The problem manifested itself inside Lightroom first, and then, only after I upgraded Photoshop to ACR 3.7, did the problem occur within Bridge and Photoshop. This clearly demonstrates that the problem is ACR 3.7, and not some feature of Lightroom. [It might help therefore, if, in future, you forgot I mentioned Lightroom.]
To answer your next question, the DNG files were created in my camera (Pentax K10D firmware v1.0 & v1.1). ACR defaults are as out of the box except that sharpening is set to be applied in preview only. Data are "written to XMP" rather than a database.
The auto settings may have changed. However, the fault, when it occurs, is a major, and very obvious, shift of white point, not the sort of thing one would expect from a tweaking of the default/auto settings. Anyway it is only adjusted whitepoint settings, not auto ones, that have changed.
I cannot be sure that the problem is specific to DNG, though I suspect it probably is. My older PEF (Pentax RAW) files are unaffected.
I do not think it is acceptable that changes to software should cause changes to the rendering of an image, particularly where that rendering may have been created by careful adjustment. This is a fundamental issue of backward compatibility.

ACR 4.3 .xmp file problem

Similar Messages

Maybe you are looking for