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 13, 2022

@Anisha GuptaIm' sorry to report that updating Camera Raw has no effect on the keyword change times.

 

The timed test is on 156 JPG files in a single folder, raging from 250 KB to 650 KB. The entire folder is just 66 MB.

 

With ACR 14.2, I did a Select All on the files and unchecked a single keyword that was previously set for all of them. The time required on a Studio Mac Pro with 64 GB was 00:05:47.

 

No I've downloaded and installed ACR 14.3. This version doesn't yet appear in the CC app, so I downloaded the installer from the Adobe page and ran it, letting it use all its defaults.

 

I repeated the timed test. With ACR 14.3 the time was 00:03:26, so a saving of more than 2 minutes (41%). That's certainly an improvement, but waiting 3.5 minutes for 156 small JPGs to update doesn't feel like professional software. By comparison, Photoshop can SAVE AS… on a 150 MB 26 layer file in less than 30 seconds.

 

Given the number of messages in these forums over the past couple of years that related to the keyword update speed, and given the new Mac hardware and prevelence of SSD, it would be great to see the Bridge team take a hard look at this issue, as it is a true problem for anyone who wants to rely on Bridge and also on keywords.

 

I can tell you that the issue likely sits in the threading or some hitch with the file system. I watched closely today and sometimes one file of about 450 KB would require 6 seconds to modify, and other times 5 or 6 files of about the same size would modify in the same amount of time. At the end, the final 14 files updated all at once, after about a 3 second delay. Thus it seems reasonable to expect that the bottleneck(s) could be found and addressed.

 

Let's hope!

Flexigav
Known Participant
April 28, 2022

The only thing that comes to mind for me is that many programs use a dedicated cache of memory as a scratch pad to hold temporary processing data that is released and deleted automatically when finished with. If that resource is limited, data processing is slowed down. Bridge has Cache and 'Media Cache'. While the cache size can be limited and the location can be assigned from the Bridge preferences (Cache Management), the 'Media Cache' is a different story. It's location can't be assigned from within Bridge.

 

Now I am not sure if one of these caches is dedicated to that scratch pad function, but if it is and it is getting full because it is shared with other file information that accumulates until it is cleaned out, then that might provide a path of investigation. It seems data generated for and used in program processes might be gobbling up valuable resources—a configuration mismatch possibly, that might require a software update solution. I'm sure the M1 chip is not slow, but rather waiting for data caught up in some bottleneck due to the way Bridge is configured on that new technology. This might be a job for the Adobe tech team.

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