"Error writing metadata to" when applying keywords

My result is that the renamed files throw the error, and the other files do not. Try this #2.

Mike,

Sorry to say but I can't reproduce your scenario. Tried the demo of PhotoMechanic (4.6.8) and used it together with my Bridge (version 4.0.5.11 on Mac OSX 10.6.8) as you stated in your post.

Not only did I have no problem to repeat the steps you are describing without problems or error messages. I also tried it with both apps open and changing rating and keywords on the go between them. They both reflect the given changes from one and the other without problems. I have to say PM does this faster then Bridge but I don't know how this will be after using as much files in PM as I did in Bridge

Leaves me thinking it has to do with your set up, either for Bridge or for your system regarding permissions or corrupted preference files.

What helped me often when in trouble with Bridge was:

Quit Bridge

From user library delete Bridge Cache (user/library/caches/Adobe/Bridge CS5) and from here delete both plug in and cache file

Same library preferences folder, delete the file called 'com.adobe.bridge4.plist'

Now start Apple Disk Utility and choose check and repair permissions (or use other maintenance software, I have Cocktail running on a daily base to repair permissions and clearing cache files)

Then restart Bridge holding down option key and choose reset preferences.

Try again.

And without rereading all info of this thread, I am using the files while they are on my main start up disk and not on an external drive or network, think you where using the same set up?

FWIW, in the Windows world, this is a long-standing (several versions of CS) and frustrating problem with Bridge for Windows, touched upon in this thread: http://forums.adobe.com/thread/888123 .

Although the symptoms are very similar between the Windows and Mac versions, it's quite possible that the causes are different. In the Windows version, we suspect that the Bridge database gets out of sync with the disk-based XMP data, and errors can be removed by trivial re-writes of XMP by Camera Raw. The task of rewriting all of the affected files every time this problem occurs however is far from trivial. Why the database gets out of sync, no one seems to know.

One thing is for certain, it is almost impossible to replicate the problem reliably. I have had files which steadfastly refuse to be keyworded, and sent them to Adobe, only to find they can be keyworded without problem. It's natural to assume some sort of system problem, but my suspicion is that Bridge's database is the key, and certain conditions cause its internal table data to conflict with the file system.

I can more or less guarantee to recreate the error with a few hundred files from a handful of folders in a Collection within a few minutes, and yet others can't manage it at all. Maddening.

In the Windows version, we suspect that the Bridge database gets out of sync with the disk-based XMP data, and errors can be removed by trivial re-writes of XMP by Camera Raw.

It seems indeed maddening.

What Disk based XMP data file you are referring to and you think Camera Raw get's involved in this while writing metadata? Could you specify your thoughts about that, I thought it only reads the new thumbnail after saving metadata to the newly saved filed after a keyword has been added.

And an other thought, you have to set the Camera Raw general section to save image settings to either side car XMP files or Camera Raw Database. Might this be of importance to set to either of the two for testing. That said, default is sidecar files and I don't see any benefit with saving in a central data base instead of having the settings traveling in (DNG) or beside (XMP sidecar)

Using the timeframe at the point I tried to replicate the error there has been activity in the Adobe PCD database  (root/library/appSupport/Adobe/AdobePCD) cache file at library on root level. I can find a KB document about this:

http://kb2.adobe.com/cps/512/cpsid_51260.html

But it seems more related to licensing of the application.

And also a change in Growl (com.Growl.GrowlHelperApp) in the user library caches folder. While Adobe also uses Growl the time is matching to Photo Mechanic activity.

As said in an earlier post, I have a longstanding and rare CacheT problem (which makes it impossible to use the option to export cache to folder) that still has no solution and also is not replicable on Bridge QE side. However missing the export cache to folder is not important for my workflow, not being able to write metadata would be a disaster.

Note: part of this discussion was off topic, but relevant to the forum, it has been branched to the following thread: http://forums.adobe.com/message/4196288#4196288

I just found a (better be temporary) work-around for this problem.  I keep a browser (Chrome) window open (on another monitor) while applying keywords in Bridge CS5 v 4.0.5.11.  Every time I get this error "Could not write metadata to", I simply click in the browser, scroll around abit, go back to Bridge and re-apply the keyword(s) and, VOILA!

Adobe, please get this fixed.  What a pain in the arse.  Plus a different, separate error popup for each image?  Come on, at least when applying a keyword(s) to multiple image,s just give me one error window so I don't have to keep closing each one!

mlundy wrote:

 

I keep a browser (Chrome) window open (on another monitor) while applying keywords in Bridge CS5 v 4.0.5.11.  Every time I get this error "Could not write metadata to", I simply click in the browser, scroll around abit, go back to Bridge and re-apply the keyword(s) and, VOILA!

And this works every time? Are you on Windows or Mac?

What are you browsing in Chrome? Anything? I can't fathom how using a browser would have any effect on Bridge.

It works EVERY time!  I am using Windows 7 Ultimate.  It matters not what URL is in the browser.  I cannot fathom it either, but I am EXTREMELY happy that it is this easy to get around until a fix is applied.