Photoshop: Completely slowing down during batch raw processing from bridge

  • 2
  • Problem
  • Updated 3 months ago
  • (Edited)
something went sidewise with the newest version of Photoshop (21.0.3) as it is slowing down during batch processing of raw images. My workflow is very computing-power demanding and recent version of photoshop is no longer interested in working fast. My workflow is like this: first in bridge/camera raw I prepare hundreds of raw files, exposure, white balance, local adjustments etc. Please note I shoot using 50 megapixel canon 5dsr. Then I batch open say 60 raws from bridge with starting action that creates adjustment layers etc on each file. It usually takes 10 seconds per each file and once done photoshop opens the next file and applies same action so on until all files are opened and ready for my final adjusting. I have very strong computer with plenty of ram and ssd scratch disk so the number of opened at once files was never an issue. Up till recently it was working fine, I could hear my mac's fans going on full speed till the end but recently after around 20 files photoshop is slowing down, it takes around 2 minutes per file, and in the activity manager I can see photoshop is doing almost nothing, the processors are idling. Please help. Thank you
Photo of Wojtek B

Wojtek B

  • 3 Posts
  • 0 Reply Likes

Posted 5 months ago

  • 2
Photo of Wojtek B

Wojtek B

  • 3 Posts
  • 0 Reply Likes
I have just uninstalled photoshop 2020 and installed 2019, also the bridge. now the old photoshop is working hard till the last file as it should.

hey Photoshop people, do something. I use photoshop all my professional life, since version 2.0
and this is the first time I write a complain. 
Photo of Wojtek B

Wojtek B

  • 3 Posts
  • 0 Reply Likes
a quick update, I just installed slightly newer version of ps 2020 (21.1.1) to see if the issue is gone and it is not. The same problem appears at the same moment. I am continuing using ps2019 for the time being. will keep you posted. fingers crossed it will be fixed soon!