I have two Canon 60D bodies. When I process the photos from one of them, the .CRW file will not save or show the processing I did in Camera Raw, even though there is an .XMP file saved in the folder with the .CRW file. It works just fine with photos from the other camera body. Both camera bodies have been reset to factory defaults, firmware updated exactly the same, and are otherwise identical. When I process a .CRW file in Camera Raw, and click Done, the preview in the Content window and the Preview window don't show the adjuatments, and the little Develop Settings icon isn't shown next to the image in the Content window, but the .XMP file is in the folder with the image file. When I open up the the .CRW file in Camera Raw again, the settings are all at zero as if I have not made any processing adjustments. Even if I save the Develop Settings as a preset and apply them to a .CRW, they will not apply to the photo in Bridge, unless I open up the file in Photoshop from Camera Raw, then it displays the adjustments. With the photos from the other camera body, it works perfectly. What could possibly cause this?
I take the cards out of the cameras and put them in the card reader in my laptop. I have even switched up the cards between cameras, but it is still the one camera that makes .CRW files that won't take the .XMP no matter what card is used. I have formatted both cards many times in the computer and in the camera. Still no luck.
This seems really stange to me as well. Since you are using the same computer, software, card reader, and card the only variable is the camera. By processes of elimination it is beginning to look like a camera problem to me.
I have to bump this, because Archie360 is having the same problem with a 7D in Bridge CS5 on a Mac.
First restart Bridge holding down option key (Mac) or Ctrl key (Windows) and choose reset preferences, then try again.
Well what do you know! That actually worked. Thanks.
Now, here's the question: What is making it do that with one of my 60D bodies, but not the other? And, why does resetting Bridge fix the problem?
What is making it do that with one of my 60D bodies, but not the other?
I honestly don't know, Bridge is often a mystery to me when it comes down to such behavior
And, why does resetting Bridge fix the problem?
All I know is that it sets back some preferences to default, don't know which or what. I'm not programmer nor a doctor but a pref reset is first aid and it often solves many problems (at least regarding to Bridge..)
I'm updating this thread with the solution that was discussed in another thread about the same problem, just in case this comes up in a search, then you don't have to read through two threads...
The date/time setting in your camera needs to be set correctly. This problem started happening to me when we switched to daylight savings time, and one of my 60D's was now one hour ahead. My other 60D was one hour behind, and it wirked fine. So somehow the date/time in the EXIF data stops Bridge from applying the .XMP file to a photo that was taken in the future.
Here is the link to the other thread.
I posted about a similar issue two days ago on the Camera Raw forum... after searching a bit I found this thread!
Bingo!!! Setting the correct time on the camera solved it. I can not being to say how relieved I was. Thanks guys.
Europe, Middle East and Africa