I think I remember reading somewhere on here that if the timestamp of the XMP file is older than the timestamp of the corresponding raw file, the XMP file will be ignored; however, I don’t recall if it is a timestamp inside the XMP file or one of the file-system timestamps.
Is there a problem with your computer’s date/time vs. the camera’s? Did it start happening when daylight savings time ended?
Yeah, like I said...the problem disappeared an hour later, as time catched up with the picture. My cam still was set to daylight-saving, so the difference broke the link. Fixing daylight-saving fixed the problem.
Thanks anyways :)
I replied to your original message I received via e-mail, and am not sure when your updates about having found the problem were added. At least we came to the same conclusion and you’ll be able to chime in the next time someone posts about XMPs being ignored.
We're looking into some related issues here. The main thing is that if ACR determines the sidecar is "older" than the raw (for some definition of "older") than it ignores the sidecar. Of course, the sidecar could legitimately be associated with the raw (i.e., the sidecar should have the same timestamp) but depending on your workflow, it is possible their timestamps will get out of sync. Something to watch out for ...
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
Eric, a side question, is it a tecnical matter or matter of policy (like you have to use Bridge if you want that and not a 3rd party file browser, so it is political) that you can't pass a name of a file (raw or tiff/jpg) to PS w/ a specific option in command line saying - open (attempt to open) that file in ACR no matter what ?