#Cache adobe bridge windows#

It's an apt icon: 'Going around in circles.' And then I go to a previously cached folder and see that little cache-building wheel spinning. In searching the Web, I've found a lot of complaints about the CS3 cache, but no real explanation of how it works (or doesn't).

In particular, I'm wondering if Bridge (a) must have the files cached centrally, even if I opt to export to folders and (b) has to keep re-caching because this central cache is limited to a size smaller than needed to cache all my images. So I'm wondering if CS3 is different from CS2 (where the latter truly had a distributed cache). I'm confused, because I've built caches for all these files before, but when I randomly check the folders in Bridge, it often starts the slow process of rebuilding the cache. What is the role of the central cache in all this? Is it just a 'scratch' area where the cache is first built, then exported? I could go into Bridge Tools and tell it to build and export the cache for that drive and all its subfolders, which would take at least overnight, but then it would be done. I have about 60,000 raw files (Canon and DNG) on a hard drive. So if my cache was successfully built for a folder, and I go back to that folder in Bridge in 6 months, should the thumbnails and previews be 'instantly there' because Bridge reads them from the external cache in that folder? After this is done it then exports them to the folders Bridge Cache files. It is also true that it always uses a central cache even with this setting but only when you first generate thumbs or if you add pictures to a folder. This constant rebuilding of the cache is very annoying. Because if it does, what happens when the cache gets 'too big?' I had hoped that one advantage of exporting the cache was that the size of the central cache became a non-issue. This seems to be a change from how (I thought) it worked in CS2 with the 'Distributed Cache.' How does this work vis-a-vis the exported cache files? I would hope that Bridge doesn't go to the central cache without relying on the exported cache. I've read elsewhere that Bridge CS3 *always* uses a central cache, even if you export the cache.

I assumed that exporting the cache to the folders meant that, once built, the cache was 'instantly there' the next time I went to that folder. Maybe I'm confused about how this should work. This seems to work for awhile, but then something happens and (at least for some folders where I know I previously built the cache) Bridge repeats the cache building again (I assume that's what's happening, because the little wheel starts spinning, the percentage quickly goes from 0-100% and then the percentage very slowly goes from 0-100% as the thumbnails change in appearance one by one and my face turns increasingly red). Automatically export cache where possible

#Cache adobe bridge windows#

Is that possible? I'm on Windows Vista and XP, with the images on hard drives.

I would like Bridge CS3 to build a cache for a folder (usually containing Canon raw or DNG), and I only want to go through this time-consuming process ONCE for that folder (assuming I don't add more images, etc.).