Skip to main content
Participant
July 12, 2023
Question

Why has Bridge Become unusable slow, will Adobe ever overhaul/fix it?

  • July 12, 2023
  • 1 reply
  • 188 views

I have been using adobe/bridge for over 15 years. Over the years I have seen it get progressively slower and slower when trying to scroll through thumbnails of smart collections to the point it is no longer pracital or usefull and is now more of an impedemant. Despite upgraging my PC every few years (currently running an amd 16core threadripper with nvme m.2 ssd), bridge gets slower year by year.

 

It dosen't matter WHAT is tried, (I have tried it all) from purching the cache, to changing the thumbnail settings.

 

Currently, for a few thousand images found in a smart catalog, each page of thumbnails takes a second to load which when you have 100s of pages to scroll through is impractical.  I remember in years past scrolling through the thumbnails was a fluid real-time scroll effect.

 

It seems as though the underlying Bridge engine is just inherently bloatware and it needs a fundamental overhaul like adobe did to Illustrator years back.  Will this ever happen? Is adobe even aware of the fact at just how slow and unsuable Bridge is?

This topic has been closed for replies.

1 reply

Jay@TeamPurple
Known Participant
July 13, 2023

The current Bridge (2023) is unusable.  I'm running it on multiple machines and experiencing the same problems:

  • VERY SLOW
  • Metadata tagging is essentially impossible now.  While I can batch embed my templated info without issue, when I go to batch-embed fields like Keywords, or Headline, or Sublocation, etc. into DNG files, Bridge will just stall and stall and eventually I'll see the "Writing metadata" status at the bottom, but after a few minutes the text I added into any or all the fields will just go blank and nothing will actually have been embedded.
  • When I use the tab key to move down the fields, pressing the tab key will occasionally randomly move the cursor and active field UP rather than down
  • Persistent text shows up in some fields.  For example, I'll batch embed a Title in a folder of 400 DNG files.  Then move to a completely different project folder and select an image (or batch-select several images) to update the metadata and while the most of the other fields will show the metadata for the new file, the Title field will often show the Title for the previous project and won't let me embed or replace the Title with new text until I force-quite Bridge and navigate back to that folder
  • Batch re-naming files in even a small folder with 30 or 40 images used to be immediate.  Now it will take 5 minutes or longer and frequently does not recognize or follow the preferences in the dialog box for where to save the newly renamed files.  For example, I may tell Bridge to copy the re-named files to a different folder, but Bridge will just re-name everything in the source folder regardless.
  • Right now, I have a folder of 400+ images for which I've batch-tagged with a set of keywords (all images = same keywords) and when going back to batch-select specific images (in this case, different speakers at a podium), Bridge is telling me that the multiple files I've selected have different keywords and will not allow me to enter the additional name keyword.  If I select each individual image, I can see the same set of keywords in each image and append the additional name keyword, but only one-at-a-time.  I used to be able to batch-select dozens of images with identical keywords and see the list of keywords.  Now I can't.  And this is not a matter of there being an extra space or typo somewhere that makes Bridge think the content is different.  These are all images batch selected and batch tagged as a group in a single pass.
  • I could go on with all sorts of things like this which are broken in Bridge 2023 and worked in all prior versions.  I'm VERY frustrated.