Skip to main content
Aurora Imaging
Participant
December 20, 2022
Question

The Camera Raw settings could not be applied because there were no Camera Raw files or selected fil

  • December 20, 2022
  • 3 replies
  • 1647 views

New folder of NEF files and go to open in Bridge but get this:  “The Camera Raw settings could not be applied because there were no

Camera Raw files or selected files were read-only.”

 

Any suggestions or workarounds to this gli8tch?  I tried rebooting  but the same.

 

This topic has been closed for replies.

3 replies

davidw41374660
Participant
June 1, 2024

Forget about adobe support on weekends.  I did all the stuff i heard about and finally opened up time machine on my mac, pushed the up down button to 2 days prior, selected applications then (with bridge and photoshop closed restored both apps to as they were, the opened up bridge and photoshop and Voila!!  Normal!!  But you have to have time machine.

PECourtejoie
Community Expert
Community Expert
December 22, 2022

Hi, did you check if the files are not read only as stated by the message (strange as ACR/Bridge will not affect the files)?

Which camera produced the files? is it the latest version of Bridge, with the latest update of Camera Raw?

Are the filesstandard NEF files? Full resolution, etc?

 

Aurora Imaging
Participant
December 28, 2022

Yes in answer to all those questions. So I used LR instead, not so intuitive but it did them all, then long wait to save them all as DNG. One job later, and all the NEFs seen by Bridge and CR with no problems. So pleased a passing glitch.

Thanks for the help anyway guys, Mark

gary_sc
Community Expert
Community Expert
December 20, 2022

Were these files on an external drive or the Desktop?

 

Have you given Bridge permission to access these other areas? (This is a Mac OS thing, not an Adobe issue.)

Aurora Imaging
Participant
December 21, 2022

Yes all the files had been copied from the camera card to the desktop's drive. I've always followed the same method so something in the Adobe software or a glitch in the OS is surely responsible?