Whereas if some other app builds thumbnails much faster then maybe the cause is something Adobe-specific. If non-Adobe apps also are incredibly slow then it points to something in the operating system or hardware. Canon DPP or Nikon Capture NX or anything else.
#How much is adobe bridge cs6 code
This factor by itself shouldn't be enough to trigger LR to take 12+ hours to catalog ~2600 images, but it might be a contributor.Īs another cross-check to rule out whether there is some piece of Adobe code that might be common between Bridge and LR causing this problem, do you have any other image management apps that build thumbnails that you can use to test whether performance is acceptable or not? E.g. Where is your Photoshop scratch drive configured? And/or the equivalent of that in Lightroom, if it has a scratch drive config setting? Putting all of this information on a single volume will definitely slow things down if physical memory runs low and all the apps start competing with each other and the operating system to page their temp data on & off of the D: volume.
#How much is adobe bridge cs6 windows
From looking at the screenshots above, the disk to look at in SpeedFan should be HD1 this corresponds to "Disk 1" in the Windows Disk Management app.Īs a minor point, I notice from the screenshots that your machine is configured to store the Windows pagefile on the D: volume, along with the image app caches and catalogs. If you can look for SMART errors on whichever disk is the D: volume, that would be useful.
Something on your machine is definitely abnormal, and if it only started relatively recently then it's because something has gone wrong. If none of the image data is on the C: RAID volume then it's probably not related to whatever is going on. That's why I was asking where the Bridge & LR data is kept whichever drive is holding that information is the one that needs to be looked at in more detail. Okay, forget the RAID stuff for now then. Here's the link to screen clips taken during the blow-by-blow of the above process. I've tried all that I can think of - defrag daily, running MSE, Malwarebytes, updates current. I'll try to include them in this post, but I don't currently see an option to do that now.Īny suggestion to fix whatever is causing this behavior would be greatly appreciated. I have screen clips along showing progress (or lack thereof) for most of the timelines above. It opened almost instantly with no NR or other cliches. (bridge7,jpg)ġ1:38 clip of Taskmgr showing system performance (bridge8)ġ1:47 finally opened and started building thumbnails and export cacheġ1:55 I keyed Ctrl-a, Ctrl-r and all 120 images opened quickly and ACR seemed to perform normallyġ1:56 closed out that folder and opened a different folder, then returned to the folder detailed above. Here's a blow-by-blow of the behavior that causes the Not Responding error to occur with resulting very slow progress.ġ1:14 clicked on folder (Page AZ) and Bridge started building criteria.ġ1:15 filter info opened showing sub-foldersġ1:16 Non Responding flashed off/on (blue system progress circle present while NR error present) clip 3ġ1:21 Br progress circle moving and no NR errors noticedġ1:22 Filter panel showed up showing 126 entries, 104 Thumbnail extractions, 1 cache exportġ1:25 Finished thumbnail extraction and cache exportġ1:25 clicked on sub-folder - NR error progress circle not active.ġ1:30 some thumbnails appeared along with Building Criteria. I can detect no other slow behavior with other programs I use, although photo processing is all that really taxes the machine.
Once Bridge builds the cache for the images in a folder, it behaves normally. Cache size has been set to almost 1/2 way on slider. Bridge cache preferences set to Keep 100% and export to folder. Still no help, except it took longer for it to rebuild cache. Then CSA and also checked to delete cache. Tried Ctrl-Sh-Alt on startup and selected delete preferences - no help. Can't ID any change to associate with the problem. Until a couple of weeks ago, system was fairly responsive. Running CS6-64 (and now CC, but problem started before CC) on Win7-Pro, i7-920, 12 G mem.
0 kommentar(er)
