Camera Profile - Set as default for this camera does not work

Answered

Follow

Wolfgang Riegler

• November 02, 2022 18:38

I have several camera profiles, both from an Abdobe DNG converter installation or from a .DNG file.

They are visible, they work, but I´m unable to "set as default for this camera"

Whenever I open the next RAW, "Luminar Default" is chosen as profile again.

 

I tried automatic DCP recognition from the installation or copied them manually into the Luminar folder or imported them from a .DNG. All is fine to work with them, but:

Set as default does not work

Drives me mad to set this over and over again manually

 

0

• Official comment

  

  Elena O'Brien

  • November 03, 2022 16:49

  Hi Wolfgang Riegler,

  Please try installing the latest Camera RAW update: https://helpx.adobe.com/camera-raw/kb/camera-raw-plug-in-installer.html#13_x

  If your camera is supported, color profiles will appear under the Develop tool.

  Let us know how it goes.

  Looking forward to hearing from you.

  Best wishes,

  Comment actions Permalink
• 

  Wolfgang Riegler

  • November 04, 2022 14:40

  Looks like nobody is really reading this, or at least nobody who knows the software..

  TAs written above: The profiles are there! I can work with them!

   

  BUT I can´t set them to default!

   

  If I open the next RAW, profile is set to Luminar Default again... not the camera profile:

  

  0

  Comment actions Permalink
• 

  Elena Blum

  • November 05, 2022 07:14

  Hi Wolfgang ,

  Kindly mind that in Luminar Neo you can view all the settings and undo all the adjustments in the Edits tab 

   

  The sliders under Tools will be set to their default settings after exiting them.

  0

  Comment actions Permalink
• 

  Wolfgang Riegler

  • November 08, 2022 11:19

  Let´s make it easy: What should the red marked menu item do? Because it does nothing, it does not set a profile as default.....This does not work!

   

  

  0

  Comment actions Permalink
• 

  Kate Williams

  • November 08, 2022 15:04

  I'm sorry for the confusion, Wolfgang.

  I've checked it, and it looks like this is a known issue that should be addressed in one of the following updates. 

   

  0

  Comment actions Permalink

Please sign in to leave a comment.