I know there have been several posts like this one on the forums, but I thought I'd start a new thread due to the fact that I tried a bunch of fixes that didn't work.
Specifically, I get the above-mentioned error when trying to add keywords to DNG files in Bridge CS5 220.127.116.11. The DNG files were created from Canon .CR2 RAW files using DNG Converter (both the latest version and the second-to-the-latest version).
Here's what I've done so far: I just updated DNG converter yesterday. I just updated the full suite, including ACR yesterday (6.3, I think). I just compacted my Bridge cache yesterday. I just restarted the computer. I just restarted Bridge. I just ran a full virus-check on my system. Latest Windows updates. Latest video card updates.
I've tried adding the keyword to the same file multiple times, all attempts meeting with failure. I've tried this with multiple files. Jpegs seem to work fine, DNGs don't in most cases. And that's the caveat: Sometimes, it works, but most of the time it doesn't. For example, I just added keywords to about 24 DNG files with no problem. When I tried doing the same to another batch, blammo. Problem. It seems really arbitrary, especially considering that all the DNG files were created with the same DNG converter version on approximately the same day.
Since this error is coming up only one day after updating, I'm thinking the update has something to do with it.
Should I submit this to Tech Support or does anyone have a nice fix he/she would like to suggest?
-Greg (Win 7, 64-bit)
Can you try open the Camera Raw Preferences dialog and see what's the current setting of "Save image settings in" option? I remember I met such issue when choosing "Camera Raw Database". Try the other option which is "Sidecar .xmp files".
I hit CNTRL when opening Bridge and did another reset of everything. That seemed to do the trick for the time being. I guess I just wish I could get some context in those error messages telling me why something went wrong.
I'll post another update here if I notice the problem again in the immediate future.
Tell me about it.
I was doing a lot of keywording a couple of weeks ago, and I came close to throwing the computer out of the window. It's VERY irritating, and, as you say, seemingly random.
As well as keywording new batches of photos, I also keyword collections made by searches and Smart Collections. The collections tend to cause more problems for me - especially larger ones. Here are some things I've worked out for myself...
If you get the metadata error, you can often overcome this by opening, modifying and closing the offending image's settings - it's almost as if the XMP file is locked. I've tried disabling my anti-virus software (ESET NOD32), but this has no bearing on the issue. At other times, I have found that this "lock" times out after a period of several minutes.
Once a collection of images is made, and all the progress indicators in Bridge have stopped spinning, you can often still see hard drive activity for some time afterwards. I have no idea what Bridge is up to, but you can see it accessing all the images in the collection in a file system monitor program. Obviously, with larger collections, this will take longer. I have found that updating metadata, while the hard drive light is still busy, increases the chance of getting the error.
IMHO XMP files written for RAW only.
Metadata are embedded in TIFF, JPEG and DNG, so either the images or some other files are locked for a moment, because another thread is working on them. Like some of the in the Bridge cache and there in "...\data\bridgestore" folder which collects keywords.
In the other thread you called it "cannot write metadata" - is this the same warning just summarized by you, or a totally different error?
just a guess, but it might be caused by a latency of your disk (fragmentation etc. pp.) especially when the cache's are on the system partition.
You can try if its makes a difference when you point Bridge's (and ACR's) cache to a dedicated partition on your fastes disks, and formate them with 64kb clustersize.Since you are on W7 you can easily shrink a partition and create a new one (start with 20-30GB), as long you have more than one disk. Copy Bridge's cache to it and tell Bridge where to find.
Yammer P wrote:
Don't bother, I already tried it.
Besides, we're not talking about the cache, we're talking about metadata.
I know you were talking about metadata
Nevertheless, metadata are also stored in different files on our computer, not only written to the images and XMP-files. Amongs others this is in Bridge's cache and the ACR database.
As I suggested in my former post, have a look to the files in Bridge cache folder, there in "..\data\BridgeStore", with a hex-editor, especially to "FileSystem_NodesMeta.MYD", "Keywords.MYD" or "FileSystem_Nodes.MYD".
Simplified: when you f.e. click an RAW, Bridge queries if there is embedded XMP and/or a XMP file and it also checks in ACR database and the files mentioned in Bridge's cache for XMP data.
I believe Bridge queries all this locations/files every time, means when creating previews but also when adding metadata. But when it was asked to add metadata, it also would have to merge metadata and rewrite the metadata blocks in all the "cache-files" (ACR database, XMP sidecar, Bridge's cache) and of course to the images, if possible.
This is a pretty old error message (bridge V1?) and even when there is a big chance that it might be related to other things, f.e. when images are located on network drives, there also is a chance that some of those files are locked.
It's interesting that this seems to happen to both DNG and raw with sidecars, and not to JPEG (unless anyone can say otherwise). When it happens to me, it says that it can't write to NEF, even though it's actually trying to write to XMP. Presumably this is by design, and the problem is really access to the XMP file. I can write to the XMP file and this usually removes the problem, but this is not practical when the message pops up on each image of a large batch.
I'm guessing that Bridge builds a table of images in memory for some reason, and prevents an image's XMP data from being modified until that image is removed from the list. I'm also guessing that Bridge either forgets to remove the image from the list, or the removal process takes too long for some reason.
I, too, am having problems with this Adobe Bridge CS5 "there was an error writing Metadata to...." my PSD files. Like everyone else, it works okay on the JPEGs, it's my PSD's that are a problem. I have problems when I am using my Mac. However, I have a PC and the Mac hooked (I'm computer challenged for the correct words...) or connected with a Synology system. I have tried the "lock" and "unlock" - called Synology (they say it's a Bridge issue). The one thing that it does to me, however, that I don't see elsewhere is that when I try to add a keyword to one of my PSD files, it DELETES the file competely from my Synology system. Thank goodness I found this out when I was trying to keyword just one file. I watched it disappear. I have since copied a file and tried again - and again it disappears. So...it's a double problem. At least I still have the "deleted" files on my PC which I can then recopy onto my Synology system. I'm a photographer - so - we're talking lots and lots and lots of images.
Any suggestions? Like someone I read earlier, I was pretty close to tossing everything out the window and going back to slides!!!
This also happens when trying to add keywords to jpegs, but I have a work around I use that does work for quite awhile before it happens again. I run the registry cleaner "CC Cleaner", a free app. For some reason, this fixes the the writing metadata error. Crazy, but it works every time.