Bridge: Unneccesary Bridge thumbnail and preview extraction

  • 11
  • Problem
  • Updated 4 years ago
  • Solved
  • (Edited)
I understand that Bridge always show the contents of files by generating cached previews and thumbnails at first encounter. These previews enable Bridge to display files quickly, as they are already prepared, and do not require an application to generate a preview on the fly. If a file is updated, Bridge updates the cache with a new version.

So, why is it then, that Bridge often feels the need to regenerate a number of Previews and Thumbnails, when viewing an old folder?

These repeated extractions put quite a load on a computer, and it makes viewing large collections of images slow-going. Surely, if it's been done once, it shouldn't need doing again, unless develop settings have been updated?
Photo of Yammer

Yammer

  • 54 Posts
  • 4 Reply Likes
  • frustrated

Posted 7 years ago

  • 11
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
Have you tried increasing the Cache size (Edit > Preference > Cache)? Perhaps newer thumbnails for other files have pushed these older ones out of the way and Bridge is moving them back to the front of the line. Also, on the subject of Preferences, have you tried using "Automatically Export Caches to Folders When Possible"?
Photo of Yammer

Yammer

  • 54 Posts
  • 4 Reply Likes
Yes, tried that.
I have 20,400 raw/xmp, 9,000 jpg, 250 tif and 500 psd in 1,200 folders. I don't know how the figure is calculated, but there are just over 25,000 jpg in each cache folder; my cache size setting is just under halfway - 5F-B7-03-00 in the registry (243,551?)
In the past, I've had the slider fully to the right, and it still regularly regenerated previews. I've completely purged the cache a few times, and even relocated it to different internal drives.

It often decides to regenerate a handful of previews, rather than most/all. I tried to work out which, and thought it might be something to do with crop settings. Unfortunately, the larger the selection of images in the content panel, the more extractions occur, and the longer it takes to get up to speed.
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
I've asked a Bridge engineer to intervene, but until then, have you reviewed the information here: Manage the cache | Adobe Bridge CS4, CS5?
Photo of Yammer

Yammer

  • 54 Posts
  • 4 Reply Likes
Thanks. I am familiar with that stuff. I've been using Bridge for about 4 years.
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
The Bridge team has looked into it and they are able to reproduce. Bad news, the issue is legitimate. Good news, they can start working on a fix.
Photo of Yammer

Yammer

  • 54 Posts
  • 4 Reply Likes
Future releases?! You're kidding, right? This is a bug, and we're hoping for a fix for CURRENT software.
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
Everything is a future release: updates, new product versions, etc. I don't even know what the release plan is.
Photo of Yammer

Yammer

  • 54 Posts
  • 4 Reply Likes
Okay. Fair enough. It's good to know that it's been addressed at least.
I thought you meant we were going to have to pay for a fix for a minute there. :-/
Photo of Yammer

Yammer

  • 54 Posts
  • 4 Reply Likes
I had a bit of a breakthrough yesterday. I worked out that the repeat extractions (at least for up to ACR 7.2) were being set off by making crops which touch the edge of the image. You might do this after using transform tools and cropping to maximum area.
While Adobe decides if, when and who they might roll out a fix to (if one actually exists), I recommend adding space around maximal crops or removing non-essential crops from your images.
Photo of Yammer

Yammer

  • 54 Posts
  • 4 Reply Likes
Whilst the crop bug has been fixed in 8.2, the other similar bug (introduced in 7.3) is still present in 8.3. The only reliable way to stop it is to disable Lens Profile Corrections in all files.
Can you please report if the ACR team is any closer to a fix?
Photo of Dave Cox

Dave Cox

  • 1 Post
  • 0 Reply Likes
This issue is really bad. It slows my Mac up to the point that I just can't do anything for 10 to 20 minutes every time I look into a different folder in Bridge (one that hasn't been looked at for a few days). Is there any sign of a fix?
Photo of René Damkot

René Damkot

  • 37 Posts
  • 1 Reply Like
Same here.
Bridge CS6 (on OSX 10.6.8) is extracting thumbnails and/or previews *every single time* I open a folder.
Photo of TRULS OLAF LIE

TRULS OLAF LIE

  • 1 Post
  • 0 Reply Likes
We all are sitting waiting, so Brigde is not the right program.
Any other suggestion to preprocess a lot of video files?
Photo of Sean Smith

Sean Smith

  • 1 Post
  • 0 Reply Likes
Work like the wind Adobe engineers! Please fix this soon :)
Photo of Yammer

Yammer

  • 54 Posts
  • 4 Reply Likes
Can those who forgot, please +1 this Problem?
Photo of Jack Higgins

Jack Higgins

  • 6 Posts
  • 1 Reply Like
Yep, I am encountering this as well...
Photo of Kieren13

Kieren13

  • 6 Posts
  • 0 Reply Likes
[QUOTE] I worked out that the repeat extractions (at least for up to ACR 7.2) were being set off by making crops which touch the edge of the image. You might do this after using transform tools and cropping to maximum area.[/QUOTE]

It's been a while since I visited this topic. While I was pretty sure it had to do with transform tools, the "crops touching the edge" factor had eluded me. I think that well may be the last piece of the puzzle.

Good work, Yammer!
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
Brett,
Heres an additional piece of puzzle to add. I sent a DVD to a friend, also on Win7 and CS6, but updated to Raw 7.3. I sent two folders, one of 25 'virgin' Raw files w/o .xmp files and another of 16 images that had my own .xmp files accompanying them. When she created .xmp files herself for my Canon raw images, they did not regenerate. when she opened the folder with my .xmp files, they did. I am shooting with a canon 7D
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
OMG...I just realized this is not MY posting to the bug report forum from today but someone elses and that it had been reported A YEAR AGO. How Interesting that the tech person in India at 6 am this morning couldn't find anything on the report and said it had not been reported. I was all set to download CC and now I have put it off yet again.
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
Brett,
If you are still around and associated with Adobe can you please explain what is going on. Why has this problem not been fixed. How is it the Adobe technical department in India had absolutely no knowledge of this report which started a year ago. And most importantly, what is being done to fix this.

Now. Today.

People who are now being asked to tether themselves to a cloud version of Adobe for far more than they paid for the boxed version truly deserve better than what has gone on for so very long. And frankly, those of us who have been posting, testing and reporting deserve to have someone within Adobe who knows the product and has resources working on this.

Why has this not happened?
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
Brett,
I got an email from Steve G this morning saying he planned to contact you. He has tested the problem, has replicated it from more than one person and says it is NOT fixed in CC. Please contact him.

Here is what he sent me just an hour ago:
I need to call Brett and go over the history of his comments from 1 year ago.

Yammers case is different than yours, in at least the triggering go the thumbnail regeneration status message. His is clearly related to having a crop in ACR set, which your files don't have. However, his case may be pointing to the underlying logic problem and the ACR team is currently looking at that particular area. I'm going to contact the ACR QE working on this and make sure he's aware of the case you have and see if it is the same root cause.

As for Bridge CC and ACR 8.1, they still have the problem so there's no point in trying that configuration out for solving this issue alone. If we can get to the bottom of these problems, my hope is that the fix will be made in an ACR update and that will be made available to both CS6 and CC versions free of charge. I can't guarantee that will the end result, but is the simplest route to addressing the problems.
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
Good to know. This whole issue isn't my area of expertise, I just stumbled upon it and tried to get the right people involved.

My comments from a year ago aren't anything special, just that I found a bug in our database that seemed to match what was described here. It seems we have multiple bugs that have similar end results but different root causes. So one root cause has been addressed and another has not.

Seems Steve G is more connected to this than I am (not surprising).
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
If not you, if not Steve, then who? And how do you/we get this problem into the hand of the right people to fix it?
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
I didn't say NOT Steve. I said YES Steve. So, go Steve.
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
yes, I have done this. hopefully it will get to the right people.
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
Oh yes, and one more question...how is it EVERY time I try to post to this forum, I am asked to sign in again, no matter how many times I tell it to remember my sign-in information and no matter which browser I use (and yes, I have told it to remember on all the browsers, every way I can figure to). Another bug, no doubt. One among so very many.
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
Couldn't answer this question. This isn't our web site, we are just piggy-backing on another site called Get Satisfaction. I'm guessing there is probably an issue with the cookies that are being generated. Most likely they are not being saved or are being saved with invalid information. Try deleting the cookie from this site in your browser cache and see if a new, working one can be generated.
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
Is this not the adobe bug reporting forum? I went to the link supplied and jumped through more hoops than I thought reasonable to get here. And now I am told this isn't really the bug reporting site. Then what is? This was the link given to me by the person in India.
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
No, this is the bug reporting site. But we don't host it, we don't code it.
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
good to know it's the right forum. thks
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
OMG!!! It's fixed. At least for now.
I just signed up and downloaded the single app photoshop cc and my bridge regeneration is...GONE.

I opened Bridge and clicked on a couple of folders. It did the standard generation ... and stopped.

Okay, crazy theory #275 (or whatever). Somehow in Bridge it had been set to create 100% previews in my CS6. I unclicked it. It was not clicked in CC Do you think...????
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
All seems to be working fine. One odd quirk, which I can live with. All raw images that were created/worked on in CS6 now show up in CC's bridge 'camera calibration' 'process' as having been processed under the 2010 parameters with that little icon on the lower right. If I click on that, it then brightens the image and says 2012. These were images processed as '2012,' not 2010. Strange.

Thought you all should know. It isn't a serious problem for me since these images are history. As an experiment, I created a new folder within the main folder with the 'old' images and when opened in raw, they were labeled as 2012.

Okay, it just got crazier. On my D drive which is non SSD the raw images all say 2010. On my SSD drive, they come up as they should...2012. Since the SSD drive is where I do all my initial work, the problem on my D drive is honestly a non issue.
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
cautious yay from me
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
Just an update. While the regeneration problem is not entirely solved, it is now manageable. I downloaded CC and made sure that in Bridge, only 'always high quality' was check in the thumbnail preview selections. Somehow, in my old Photoshop CS6 program, 'create 100% previews' had been checked. Now, in CC with folders that have raw files with metadata, I get a single cycle of regeneration, sometimes half the images,sometimes only a few, sometimes only one. But it then stops. In CS6, the regeneration cycled again and again and again.

The other interesting development is that if the folder has any tiff images or jpegs in it, the regeneration problem doesn't happen.
Photo of Yammer

Yammer

  • 54 Posts
  • 4 Reply Likes
It has not been "solved" at all, as far as I'm aware. I'm still waiting for someone at Adobe to say it's really been addressed. I had to remove crops from thousands of images to get my fast new computer to behave like one. Far from ideal.

CS6 is still a current product, so I hope that Adobe acts quickly to fix the regeneration problems which were first reported in 2011. Lots of people have no intention of buying into CC just yet, if at all.
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
You are absolutely right. It is not solved. I should have said it is partially solved ... for me. And probably only because I basically was forced by this problem to sign up for CC. Adding to the puzzling situation here is the fact that some people have had this problem since 2011 (so I'm guessing back to CS5) while for me, it didn't show up until November of 2012 with CS6. And in my case, the problem didn't seem to be affected by crops. It was just there.
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
Odd...I just got a prompt for a new comment from Yammer saying that the regeneration problem is still ongoing and can be stopped by disabling lens profile corrections. Yet when I open the forum, the latest comment I can see is mine from 7 months ago.

At any rate, I have lens profile corrections enabled and don't have the problem. So, as with all of this, there IS something going on but...what????
Photo of PECourtejoie

PECourtejoie, Champion

  • 792 Posts
  • 285 Reply Likes
Yvette, he discussions here are threaded. Yammer replied to the 5th message from the top.
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
and i guess i should have replied here. it's all an ongoing learning process.
Photo of Yvette Cardozo

Yvette Cardozo

  • 27 Posts
  • 0 Reply Likes
Thanks. The way this site now appears to me has changed radically so I wasn't following how things were working since it's been quite a while since I had been on the forum. I now see where he commented.
Photo of Michael Decker

Michael Decker

  • 38 Posts
  • 0 Reply Likes
If I adjust 200 pictures using Bridge, then it start to generate 400 thumbnails. And then I start again with ten pictures, two, one, two...