Skip to main content
New Participant
March 29, 2022
Answered

**HORRIFYINGLY SLOW BRIDGE AFTER GETTING M1**

  • March 29, 2022
  • 5 replies
  • 2263 views

hey all!

 

any ideas or remedies for BRIDGE having an absolute stroke when trying to do incredibly basic tasks like batch renaming 10 WHOLE photo files? i have to force quit after every task. last i spoke with support when i first got this new macbook, they said they basically 'speak different languages' are that they were working on it.

 

one year later.

 

curious if anyone had actual advice in the meantime...

truly appreciate your time!

This topic has been closed for replies.
Correct answer PECourtejoie

Hi, check out the beta version of Bridge that offers native Apple Silicon support: more info on how to get it: https://community.adobe.com/t5/bridge-discussions/the-adobe-bridge-beta-is-now-available/m-p/13128712/thread-id/35392

5 replies

PECourtejoie
Community Expert
November 28, 2022

Hi, Bridge 13.0.1 offers native M1 suppport, you should upgrade to that version, but be informed that while it supports a modern UI with multiple content tabs, it has for the moment lost the multiple windows feature. It might be wise to keep a copy of V12 if you need that feature.

PECourtejoie
PECourtejoieCorrect answer
Community Expert
October 10, 2022

Hi, check out the beta version of Bridge that offers native Apple Silicon support: more info on how to get it: https://community.adobe.com/t5/bridge-discussions/the-adobe-bridge-beta-is-now-available/m-p/13128712/thread-id/35392

blankframes.com
New Participant
May 6, 2022

I'm having the same issues with Bridge. Generating previews on M1 Max with 32GB of RAM takes AGES and is totaly unusable. I used to fly through my images on 5y old MBP15, but this now has to be fixed since the M1 processors are already 2 years old..

Adobe Employee
April 13, 2022

Hi,

 

Thanks a lot for your feedback.
Please try updating to ACR 14.3 release, that should fix the issue.

Let us know if you still face the same.

 

Thanks,

Bridge Team

Justin Other
Inspiring
April 28, 2022

@Anisha GuptaI'm providing another repeatable test with more informaiton on the issue. As you get to the bottom of the post, I think you'll find the problem and have a good idea about how the team can investigate it further.

 

As a reminder: my setup is the 64 GB RAM Mac Studio. The files are on the internal SSD. There are hundreds of gigabytes of free disk space and Bridge can be the only app running. I don't believe that the hardware matters at all. The problem is software-based, as I've detailed below.

 

Recently I exported 2000 images into a single folder, directly from the Apple Photos app. As opposed to my earlier tests, Bridge handles this directory like a champ. I can change a keyword on all 2000 files and it completes in about 5 seconds. Meanwhile keyword changes on any file in the original, problematic directory of 156 images is always slow as molasses, taking 3–4 seconds for each file.

 

I moved the slow directory to reside as a sibling for the fast directory. No change in keyword processing speed for either. I moved 10 of the slow JPGs to the fast folder. Now updating the keywords on the 2010 JPGs takes about 40 seconds longer than before.

 

Here's the latest info that I think the Bridge team will find most interesting: I realized that even though all the 156 slow files also came from the Photos app, unlike the 2000, they were not exported using the "Unmodified Original" option. They were exported after having their color settings edited from within Photos. They also were exported from iCloud, not from the Photos local cache.

 

So my best guess became that the file data format in an edited version is not the same exact file data format in an unmodified original, when exported from Apple Photos. But it turns out we can prove the difference. Here's how:

 

An experiment was set up by grabbing 10 photos in the Photos app that were already locally stored, and not sitting on iCloud. I exported them twice. The first time used the Export > Unmodified Originals option, the second was the standard Export > 10 Photos option. These were exported to the same folder, so the name clashes were resolved by the system to append a "1" to the end of the second set of files. No big deal.

 

Now I opened Bridge and located the new folder with the 20 freshly exported JPGs. I did a Select All and clicked to set a single keyword. Then I quickly switched to the Finder to watch the Date Modified column inside this folder, to see what happens as Bridge processed the keyword edit.

 

All the unmodified originals update instantly. All the modified JPGs take 3–4 seconds apiece.

 

This should be enough information to help Adobe investigate and find a final fix for the issue. No doubt the Apple Photos app has been around long enough and has a large enough user population to warrant it.

 

I can't wait to see what they find and then enjoy being able to use Bridge after they fix it. @Flexigav Thanks for the thoughts. As you can see, it definitely is an issue for the Adobe Bridge engineering team.

Flexigav
Known Participant
May 4, 2022

I am convinced Bridge modifies files through a temporary representation of them in a cache and that is a cause for delays and inconsistencies. When the cache is cleaned out Bridge will reload it again with a new temporary representation of the files being viewed regardless of where the physical files reside. Bridge tends to work with the cached representations rather than the physical files directly... all changes to the cached representations are applied to the physical files in the background. This could be a source of delays! I feel at times the cache of temporary files does not fully represent the actual store of original files until the cache has been cleared and reloaded. After time, differences appear again and the process needs repeating. It appears all this is to speed up the viewing and editing processes by reducing the number of slower hard disk calls, however this might not be so relevant since the evolution of SSD technology, but never-the-less, still used by many applications. This is only food for thought.

Justin Other
Inspiring
April 11, 2022

Recent Mac Studio upgrade and I'll vouch for the OP. Bridge is unusably slow on this Mac with 64GB RAM and sppedy drives connected directly to the Mac.

 

Adding a single keyword to 49 files has exceeded 5 minutes and counting as of now. Worst of all, after it completes, it has skipped over some of the selected files and not added the keyword!

 

This is a big bug for Adobe and a black eye for the Bridge team. Perhaps this app isn't as important as PS or Illustrator or ID, but if you're going to offer it to the market, it ought to be as close to perfect as humanly possible. Sadly, Bridge has collapsed under the weight of an improved CPU and increased memory lol