![]() I have over 100,000 pics spread in different collections gut I don't browse all of them on a regular basis. The slider goes from 10,000 to 500,000 with no scale. Probably time to nuke Bridge entirely and re-install. If it still appears to freeze with nothing to do, you've likely got a different (non-cache) problem. Then, when you re-launch Bridge it has nothing to do. Often, an update to Bridge and Adobe Camera Raw will make Bridge think the thumbnails are not current, and massive regeneration occurs.Īnother tip: Before you close Bridge, navigate to an empty folder. I suspect it is dependent on system clock speed. ![]() Some people suffer this problem, some don't. There are several threads on Adobe forums about this, dating back 10+ years. Thumbnail generation takes a lot of time. If it thinks they are not current, it will regenerate, even if they are current. A lot faster than regenerating thumbnails.īridge still sometimes gets confused about whether the thumbnails in cache (main or exported) are truly current. That's a fairly fast step, even on folders with 1,000+ images. When you navigate to a folder whose image thumbnails are not in the main cache, Bridge copies them from the exported cache file to the main cache. That results in a lot of disk used for the exported cache files, but results in a clean and dependable operation. Bridge will then build a clean, empty, virgin cache. Close Bridge, nuke the cache, re-open Bridge. Don't bother with "Purge all Cache" inside of Bridge. Periodically "nuke" the main cache by deleting it outside of Bridge. Locate the main cache on a disk separate from your images.Ĥ. Tick "Automatically Export Cache to Folders."ģ. Set the Cache Size low, to the minimum of 10,000 or close.Ģ. After years of experience, I came up with the following cache management scheme.ġ. Even after navigating through several folders with 100 to 1,000 images each. It never goes over 500 megabytes of memory, as reported by Task Manager. My Adobe Bridge is currently Version 8 on Windows 10. Bridge is notorious for cache problems, and those problems are often system dependent, i.e., can't be easily reproduced on a different system.
0 Comments
Leave a Reply. |