Cache problem on Bridge CS4

As digital photo librarian one of my tasks is to keep Bridge on my four machines constantly indexed and updated: three have admin level and one a simple user level. I call these my benchmark machines since they are the ones by which I measure all the other users' machines in the department. Typically, they the most accurate and up-to-date for searching; they include two PCs and two Macs.

Back in July of this year, Bridge on one of my two benchmark Macs displayed the feared "purge the central cache" message:

There is no workaround and no alternative but to purge the central cache and completely reindex the machine from scratch.

Last Friday the same thing happened to my other benchmark Mac, a laptop.

And no, we don't know why this happens: the cache size remains at normal levels:44 gbs with 380k+ items (July) and 40 gbs with 306k+ items (September). No unusual activity at the server end and so far no one else in the department has experienced this problem. Of course, that last observation leads me to suspect that it does have something to do with cache size but this remains far from clear. and anyway, I've had a cache as large as 55 gbs on my laptop with no problems.

Oh and one other thing I've learned recently: Apple's Time Machine does not back up Bridge's caching system -- in fact it doesn't back up the User library's cache folder at all. Curious, eh?

"Error writing metadata to file"

I've talked about this problem early on in this blog since it started happening soon after the library went live some two years ago. And while it's not as catastrophic as a corrupted or damaged cache, it is still annoying and sometimes downright aggravating. I want to revisit the issue now because I've noticed a pattern of sorts and can't figure out what that means (if anything). Anyway, my hope is that someone reading this may have figured out what the problem is and how to fix it:

Here's what happens:

1. I go into a folder of images in our library on the server and select a block of images to modify the metadata. 
2. I make the metadata change(s), typically in either keywords or the description field.
3. Bridge begins to modify the files -- note that my files are usually sorted by filename (lowest to highest number) but Bridge commences its "retagging" from highest to lowest. 
4. It's at this point that Bridge appears to stall and soon brings up the above-noted error message on the first file; I click OK and the same thing happens with the next file; I click OK and then Bridge is off and running tagging all the remaining files just fine without any intervening error messages.
5. I then go back to retag the files that Bridge refused to tag, one-by-one, and the updating works just fine -- no error message.

The frustrating aspect of all this if you are trying to modify a large block of images and the error message keeps repeating there is no way out of the cycle other than to force quit Bridge (no "escape" if you will).

Oh and by the way if I attempt to modify the metadata in the search results window instead of the actual folder, more often than not I'll get the error message far more frequently and across more images in the selected group.

The problem has occurred

• with various file formats (but typically with JPG since those make up the bulk of our library)
• with few if any additional programs open (no pattern noticed)

I've noticed this on two benchmark (fully indexed) Macs:

• a desktop running Leopard 10.5.8 and 
• a laptop running SNow Leopard 10.6.8
• no, I haven't tried tested to see whether it occurs on a PC

Adobe Bridge and an image library - a case study

Every so often I get pinged with an email from someone seeking answers to one of life’s greatest puzzles: “How can Adobe Bridge help me build and maintain a large image library?” (Where’s Einstein or Darwin when you really need them, eh?)

Such queries always come from individuals who are serious, determined and totally perplexed by the task facing them: creating and maintaining a large photo library on the cheap. And such was the case with H____. With her permission I post our email conversation here, as a way of sharing her rather daunting predicament with those of you quite likely facing the same set of concerns. I should say that subsequently we had a long phone conversation that explored several follow-up points in greater depth.

“I have avidly been following your blog,” she wrote last week, “in which you describe the way in which you detail arranging a shared library via Adobe Bridge. I am doing a similar thing, but on a smaller scale and am reaching out to you for some guidance. I have a pretty good idea of what I am doing, but as I read your blog I recognized that there are certain pitfalls that I want to avoid and be prepared for - specifically with the cache and ensuring that all files maintain their metadata.”

In my follow-up email I asked six questions, to which she quickly replied:

1. How many individuals will be using Bridge? Bridge is going to be used by a handful of people - but with potential to be searched by more in the future. There is also the hope that people unfamiliar with Bridge or CS software would be able to search for images through spotlight (we’re all on Macs ).
2. What version of Bridge do you have? We are using Adobe Bridge CS5.
3. How many images do you have? The images right now are less than 10,000 but growing daily - I am aware of the limitations of Bridge - and at some point I am sure that a more robust and secure DAM system will be put in place - this system is to carry them over and make the workflow more manageable until then.
4. Do you have a keywording strategy in place? We have outlined a master keyword list. I consulted with those who have to use and search for photos daily, and their preference is simplicity and less is more - it will be imported into Bridge and modified as needed - however in testing it has proven to be a bit conflicting. I am in the midst of figuring that out - also the "Bridge Search" in the upper right hand corner is letting me down as it is not invoking hierarchy and will only allow a one-word search.
5. Is there an IT dept involved? IT is not involved....
6. Do you have a metadata gatekeeping policy? The gatekeeping policy will be more solid as the system comes to fruition - but in general only the people sourcing and dealing with images daily would be able to make adjustments- right now that is only 2 or 3 people.

Use these questions and compare your answers to the ones above.

As a postscript, I should note that one of the really crucial issues in this particular exchange concerns question no. 4: I wish that Adobe would remove that little search box in the upper right corner of the UI. It looks so much like the Mac finder and is too tempting to use. Bridge’s real strength lies in its incredibly robust search features accessed from “Edit>Find” from the main menu or “Command/Control+F” from the keyboard.

Otherwise, H____ is right on track. She has a solid plan in place, a good process in motion and a firm grasp of the strengths and weaknesses of Adobe Bridge.

Do you?

"Bridge encountered a problem. . . "

The moment we've all dreaded has arrived this morning. I turned on my computer, launched Bridge and straightaway saw this on my screen:

"Bridge encountered a problem and is unable to read the cache. Please try purging the central cache in Cache Preferences to correct the situation."

Before taking any action, however, I wanted to review my cache size: (User>Library>Cache>Adobe>BridgeCS4). I soon discovered that it consumed 44 gigabytes of space and contained slightly more than 364,000 items.  Since the maximum number of items allowed is 500,000, that didn't seem too extreme. However, I did notice that there were more than 1200 cached folders in the 256 thumb folder but more than 1300 folders in the 1024 preview folder. (Even though the image library contains only a fraction of that number of folders, I use Bridge for moving files/folders around and prepping images for their eventual migration to the photo library.)

The difference between the two numbers seemed a bit odd since both folders should be the exact same size. I wonder if the cache crashed simply because of the number of folders of cached items.

Whatever the root cause, this event reminded me of the importance of tracking Bridge's cache size -- and it would probably be wise to occasionally run the Optimize Cache in Preferences as well:

Bridge>Preferences>Cache>Optimize Cache.

Have you experienced similar problems?

Expression Media 2 now Media Pro 1 and Photoshop User Trashes Bridge

Expression Media 2 is gone, replaced by a totally redesigned program called Media Pro 1 -- and with it any support  for the older program as well. Phase One, who purchased EM2 from Microsoft last year, is selling an upgrade to the photo cataloging program for $59 for EM2 users ($69 for iView users). There can little doubt now that the "new" program is designed to integrate with the company's powerful Capture One RAW converter and image editing tool. A good deal for Phase One users and certainly a smart move from a corporate perspective to be sure -- but what about the rest of us?

I suspect future versions will quietly integrate into the Capture One system, eventually serving as their version of Adobe's Bridge product (but catalog-based, not browser-based). It just makes sense, after all. But if you don't use the entire package, well. . . .

Any thoughts?

So, the alternatives to Bridge get fewer and fewer.

And to top it off, in the latest issue of Photoshop User magazine (published by the National Association of Photoshop Professionals), under "NAPP Community," is a short note pointing the reader to www.photoshopuser.com where they will find "100 Ways Adobe Lightroom Kicks Bridge A$$ for Photographers." Think I'm joking? Check it out, with video tutorials no less.

Where is this leading, I wonder?

Using Adobe Lightroom 2 to catalog our library: backstory

While we have no immediate plans to migrate away from using Adobe Bridge CS4 to manage and maintain our image library, as I've noted in an earlier post we must be prepared for that eventuality. Bridge is not and has never been designed to allow easy access to such an enormous image library. That is has worked so far is a testament to the possibilities under the program (hint, hint Adobe) and to the willingness of our designers and writers to stay on top of reindexing their cache folders so that they may effectively search the image library.

OK, so why Lightroom? As I have said earlier, I tested Expression Media 2 last year and found it a very nice interface but have serious concerns about its future. Extensis Portfolio is too rigidly structured and allows little flexibility: one user,  three-user or enterprise-level configurations. I have experienced problems with their importing metadata from Adobe as well.

So, I tested importing our library into Lightroom 2  (1) to give me a complete visual record of what we have in the image library, (2) to allow me to work offline on tagging modifying image metadata and (3) to test whether a catalog-based system would work for us.

I should also say that setting permissions is, for us, the key selling point in any program. Working with our IT department we created a two-tiered permissions system for our present library: myself and three others on the team have admin access to the library, that is we can add, delete and modify files and metadata; everyone else who has access to the system can only read the files and in order to manipulate images must copy the files to their own machine.

Whether we can maintain the dual level of access to the library with a catalog-based system like we presently have with Bridge remains to be seen and tested.

Another consideration to bear in mind is that Lightroom 2 cannot import CMYK files -- but this problem has, I'm informed, been resolved in Lightroom 3. I'll soon be able to confirm this since I'm planning to upgrade to LR3 this next week.

Confusion at Phase One about Expression Media 2?

I just posted this on Peter Krough's DAM forum:

I had a disturbing conversation with one of the sales people at Phase One yesterday regarding EM2.

Backstory: I had called earlier in the day and left a voicemail at their generic sales number in the US explaining that i was looking for updated information on the future of EM2. I explained I was the digital photo librarian for a large university in New England and that we had been using Bridge CS4 for nearly two years to archive and share our large image library (140k+ photos among 18 workstations) and I felt the time was running out on using Bridge. After researching catalog software -- and spending no little amount of time with the DAM Book and here on the various fora -- I had tested EM2 on my own image archive last year and found it a very impressive tool indeed.

Unfortunately, the person from Phase One who called me back left me with the distinct impression that there is uncertainty underlying the future of the software. I had heard from an acquaintance here on my team that he suspected they were going to integrate EM2 into their Capture One software system -- which does make some sense I grant you.

Anyway, the fellow who called me -- horrible connection so I never did get his name right -- I asked if any future upgrade was planned and if so would it be free to existing users. At first he said, "The upgrade was supposed to have already happened," but then he backpedaled right away and said it was going to happen soon, and then probably pretty soon. . .  I asked if it would be free to existing users and he said there would be a fee charged then right away he said it might be free but there would perhaps be some kind of charge. I asked about new features in the "upgrade" and he finally admitted that he didn't really know anything about the future of the product and very little about the product itself.

Finally, I inquired about notification for updates and he said "check back on the website from time-to-time."

Well, you get the picture.

None of this was very reassuring about the future of EM2 as a standalone and certainly not for multiple users.