Skip to main content
rjs55483519
rjs55483519
Participant
August 7, 2017
Answered

Can't write to XMP in Bridge in CC2017 and PS CS6

  • August 7, 2017
  • 1 reply
  • 443 views

How do I fix this?

On OSX, Yosemite, some files won't let me write to the xmp space using Bridge.

The files are on a Linux box, running Xinet. But moving the files to the desktop doesn't fix the problem.

I've tried changing the perms to rwx-rwx-rwx, and removing the @ when that is in the perms (xattr -l).  Re-saving the file doesn't help, nor changing from .psd to .tif. That removes the extended attributes (@), but the problem remains.

What does work is to flatten the file and resave without layers.

Not all files have this problem. Some, but not all of the problematic files don't show a preview, even after re-saving and changing the perms. Saving as a copy or changing the filename doesn't help.

Some of the files that I can't add keywords to already have previously applied keywords. And I can add keywords to the file info box. Just not in Bridge.

Thanks in advance.

This topic has been closed for replies.
Correct answer Stephen Marsh

I have seen this once before, without any hard answer as to why/how - it appeared to be some form of data corruption.

You may need to work on copies, flatten, add metadata and move the layers back in from the originals and ensure that previews, metadata etc. an all be written to the new files. I would not trust the old ones if they have this behaviour.

Always copy files to the local drive and work there and then move them back to networked storage using the OS.

1 reply

Stephen Marsh
Community Expert
Stephen MarshCommunity ExpertCorrect answer
Community Expert
August 7, 2017

I have seen this once before, without any hard answer as to why/how - it appeared to be some form of data corruption.

You may need to work on copies, flatten, add metadata and move the layers back in from the originals and ensure that previews, metadata etc. an all be written to the new files. I would not trust the old ones if they have this behaviour.

Always copy files to the local drive and work there and then move them back to networked storage using the OS.

rjs55483519
rjs55483519Author
Participant
August 7, 2017

Seems like a possible workaround; PITA, but effective.

The files in question are mostly finished work,  so I may not add back the layers.

FWIW, in 20+ years of a server based workflow, this is the first time I've had file corruption issues for files on the server. I'm not quite ready to assign blame!

Thanks!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices