Luminous Landscape Forum
Raw & Post Processing, Printing => Digital Image Processing => Topic started by: Rajan Parrikar on February 12, 2020, 04:18:28 pm
-
Anyone else experiencing this?
It no longer picks up the custom profile specific to a camera body.
-
Anyone else experiencing this?
It no longer picks up the custom profile specific to a camera body.
yes look here...
https://forum.luminous-landscape.com/index.php?topic=133917.0
i am afraid you have to make new ones - or go back to the older version...
-
Anyone else experiencing this?
It no longer picks up the custom profile specific to a camera body.
Check the NEW preset preferences for this.
-
To be clear, you don't need to create new camera profiles, you just need to save new develop defaults per camera. Your old develop defaults got blown away by the upgrade.
Unless of course your problem is the camera profiles not showing up in the profile menu. But it doesn't sound like that.
-
Thank you, all.
I'm working in Bridge, not in LR. I know the underlying RAW engine is shared by the two. In Bridge/ACR the available cameras field is greyed out. See attached screenshot.
-
To be clear, you don't need to create new camera profiles, you just need to save new develop defaults per camera. Your old develop defaults got blown away by the upgrade.
Unless of course your problem is the camera profiles not showing up in the profile menu. But it doesn't sound like that.
Correct. The custom profiles are visible under the "Browse" tab but the default is messed up. Earlier I had it set up to match the profile to camera serial number.
-
Update: I figured it out, thanks to Julieanne Kost -
https://blogs.adobe.com/jkost/2020/02/how-to-create-custom-raw-defaults-in-adobe-camera-raw-v12-2.html
-
Update: I figured it out, thanks to Julieanne Kost -
https://blogs.adobe.com/jkost/2020/02/how-to-create-custom-raw-defaults-in-adobe-camera-raw-v12-2.html
Adobe has made a mistake in communicating this change to the fact we need her blog and other third party bloggers to understand how it works...
It is not only Adobe, Apple is champion: it just works... yes, if you know how... and if you work just as we think is best for you.
mrs Kost writes at the end: Note: For customers that have set custom default settings in the past,...
So that means almost everybody i would think.
-
Adobe has made a mistake in communicating this change to the fact we need her blog and other third party bloggers to understand how it works...
It is not only Adobe, Apple is champion: it just works... yes, if you know how... and if you work just as we think is best for you.
mrs Kost writes at the end: So that means almost everybody i would think.
Also broken is the Working Spaces in the Colour Settings in Photoshop. You have to reset it to your preferred working space.
-
Also broken is the Working Spaces in the Colour Settings in Photoshop. You have to reset it to your preferred working space.
Thanks for the heads up. Sometimes Adobe just amazes me. Love their programs, not their communications ability.
Rand
-
Also broken is the Working Spaces in the Colour Settings in Photoshop. You have to reset it to your preferred working space.
I had no such issues on Mac OS (Catalina).
-
I had no such issues on Mac OS (Catalina).
Must be a Windows only issue, perhaps. I can confirm that my working color space in Photoshop was reset to sRGB.
Rand
-
No, I’m in macOS Catalina, too, and it reset the working space to sRGB.