I opened a bunch of images shot with a Canon 7D through the Raw Processor in Bridge CS5. AFter making adjustments I clicked the "Done" button thinking the XML files would be upgraded. Nothing happens. What am I doing wrong. With all my other files this works perfectly.
Bridge is CS5 for OSX running 10.6.8 Ver 126.96.36.199
Raw Processor is 188.8.131.529
From what I understand I'm all up to date without moving to Lion or up to CS6 but it works great with all my other CR2 files. Only with problems with the ones from my 7D which I rarely use for stills.
It acts like the XML files are locked but they are not.
Thanks for checking this out, I'm stumped!
First with all other CR2 files I do see the icon that indicates changes having been made. But when you open the file either in the Raw Processor in Bridge or the Raw Processor in Photoshop the adjustments are nowhere to be found.
I think I am out of ideas. Suggest you post in Camera raw forum http://forums.adobe.com/community/cameraraw?view=discussions
Post results when you get them.
OK I'll do it. Been slamming on a deadline and just had to save it all as jpegs to edit with. Really appreciate your help. I'm really curious why only these files won't work. The 1d's work, the 5D's work, All the little rangefinders work. Just not the 7D. Very strange.
Thanks again for your energy.
This won't answer why the xml/xmp is not being updated but it might get photo the job done:
Try opening one of the 7D raw files in acr, make your acr adjustments, then Save Image button in acr (instead of Done). Select <dng> in the save options (and other options to suit) then Save. This should produce a dng file with your acr adjustments. Cancel out of acr and try opening the just-saved dng in acr and see if it shows your adjustments.
The exact same thing is happening with one of my 60D in Bridge CS6 Camera Raw. I make my changes to my .CRW file in Adobe Camera Raw, I click done, and even though the .XMP file is in the folder, it does not get applied to the image in the Bridge preview window, and if I open up the image in Camera Raw again, the adjustments I made are not there. I have to apply a saved preset or start from scratch again.
The crazy thing is, with the other 60D, it works fine!
If I take the SD card out of the bad 60D and put it in the good 60D, they work from the good one and not the bad one.
So, it's not the card, and it's not bridge. There is something with the .CRW files from the ope camera that doesn't work in Adome Camera Raw, and Bridge CS6.
everyone that is having this problem I think I have solved it.
Short quick answer so you dont have to read further. Check your date/time setting on your camera, it's probably wrong.
I too have a Canon 7D and the other day I had taken some pictures of my son with santa and was experiencing the same problem. I could edit in camera raw, but the changes would not save. I would not get the little icon next to the image either.Every other image worked fine except for the ones I took that day. I was chalking it up to maybe a bad import of the images and maybe somethign was corrupting. but I was still able to open them and edit and save psd's so I wasnt too worried yet.
Today we went out and took some images of holiday lights and I came home downloaded the images and the same issue happened again. I went back to the santa pictures and I could edit them and the changes were saving now. So I googled and came across this post. Once I saw you too were having the same problem but it went away the next day, and another person was only having a issue with one camera I figured it had to be a setting in the camera.
And since the problem goes away with time I decided to check my time on my camera and it was set to 12/22 (today is 12/21). So I corrected the time took a test shot and downloaded it to the computer and it works perfectly again.
Hope this helps!
Sorry for the Holiday Delay (no quick replay thankfully). But after looking at the metadata, you nailed it. Bridge could (wondering why not, not that I agree with that) not ( a lot of nots here) write to the files because they were from (imagine how Spock must have felt) tomorrow. Wondering why the camera fell behind (just like the Mayan calendar deal) a day? Wondering why Bridge or the raw processor would use the date issue as a reason (kind of like the fiscal cliff) not to work?
Thankfully I rarely use my 7D for stills (will be less likely to do so in the future now) so was bewildered by this riddle. So simple in (drumroll the happy ending) the end.
Thanks for your thoughful reply and Happy Holidays,
Yes! Finally, a real solution! Thank Ponno!
The 60D that was having the problem was set to one hour ahead, which makes perfect sense. It was when we switched to daylight savings time that this problem strated happening. My 60D that was working fine was set to one hour behind the correct time.
So, why does Bridge refule to apply an .XMP file to a photo that was taken in the future? Well, obviously because that photo hasn't been taken yet. Duh.
Thank you so much, PonnoJonno! You literally made my week! I have been dealing with this issue longer than I'd like to admit. Fortunately, I found you post before I started doing anything wacky to my machine/software to correct it. I checked my camera date/time and it was set an hour ahead. Once I set it to the correct time, BAM! the files worked perfectly in Adobe Camera RAW.
So glad it was such a simple fix. Thanks for doing the extra troubleshooting leg work.