Skip to main content
Zakery0D4C
Participant
August 22, 2021
Answered

Camera Raw on M1 Macbook has "Camera raw graphics acceleration is not supported" warning

  • August 22, 2021
  • 1 reply
  • 3884 views

Hello,

I'm on a 2020 M1 Macbook 13" with the latest update installed; Big Sur 11.5.2 and just updated all my Adobe apps. Bridge version is 11.1.185 and Camera Raw version is 13.4.0.872.

I have tried using 'Get Info' via the Mac's browser to launch Bridge using Rosetta 2, but the check-box option in the Get Info menu for Rosetta is not featured. I've attached a screenshot of the Camera Raw error message and another of my Preferences in Photoshop to demonstrate that all my other Adobe apps besides Camera Raw are not giving the error message. Please help if you can: Adobe Bridge is still one of the main tools in my workflow. Thank you

Correct answer Zakery0D4C

Update on this: I found another post within the community that looks to have resolved the issue. In short, I needed to delete file 'TempDisableGPU2' from the following directory: /Users/USERNAME/Library/Application Support/Adobe/CameraRaw/GPU/. I hope my late response to this thread may help your teams to resolve the issue for future users who may happen to come across it.

 

Here's the post I used: https://community.adobe.com/t5/bridge-discussions/enhance-requires-a-graphics-card-with-metal-support/td-p/12129873

1 reply

Sahil.Chawla
Adobe Employee
Adobe Employee
September 3, 2021

Hi there,

Sorry to hear about this. Could you please try reinstalling the Camera Raw Plugin and let us know if it helps? https://helpx.adobe.com/camera-raw/kb/camera-raw-plug-in-installer.html

 

Regards,
Sahil

Zakery0D4C
Participant
September 4, 2021

Hi Sahil,

Thanks for getting back to me on this. Someone from the Adobe customer service line worked with me a few days back to install/reinstall multiple Camera RAW plugins-- I think he went as far back as 12.1 but I can't recall exactly. Regardless, none of them appeared to make any change to the problem. I went ahead and reinstalled the latest plugin again, and it didn't solve the issue.