Skip to main content
February 16, 2020
Question

Missing Camera Profile since 9.2 with Z6

  • February 16, 2020
  • 6 replies
  • 1124 views

Since the last update the camera profile of the z6 isn't imported anymore and is set to adobe colour by default. Is this a bug or just something to setup? Thank you for your help.

This topic has been closed for replies.

6 replies

Todd Shaner
Legend
February 24, 2020

Please add your 'Me To' vote and 'Follow' at the below report concerning this issue. Adobe has acknowledged the issue and adding your 'Me To' vote will help to get a fix prioritized.

 

https://feedback.photoshop.com/photoshop_family/topics/camera-specific-profiles-missing-once-updating-from-lightroom-classic-9-1-to-9-2

Participant
February 23, 2020

I'm having the same issue with my Z6 and the 9.2 update. This is absolutely and utterly annoying. I only shoot RAW and I have certain shoots that I applied profiles to while I was shooting and when I got to import those photos to Lightroom, the profile disappears and it isreplaced by some generic crap "adobe color" profile. Issues like this result in me eventually ditching the product and going elsewhere for an import and develop solution  

Todd Shaner
Legend
February 17, 2020

I can confirm there are 7 Adobe Raw and 31 Camera Matching profiles in LR 9.1. In LR 9.2 there are 7 Adobe Raw and 11 Camera Matching not including original (v1) camera matching profiles now under Legacy tab. The below 20 Camera Matching profilesare showing in LR 9.1. but not in LR 9.2. So these are the missing camera profiles. I suggest posting this as a 'Problem Report at the Photoshop Family forum, which is monitored by Adobe Staff. Place a link to this post in your report and a link to that report back here for others with the same issue.

 

https://feedback.photoshop.com/photoshop_family

 

DdeGannes
Community Expert
Community Expert
February 17, 2020

She this link from Julieanne Kost on how to work with the new Default Develop Settings and Presets with LR Classic 9.2. She goes into more detail than the other post.

 

https://blogs.adobe.com/jkost/2020/02/how-to-customize-lightroom-classics-default-develop-settings-v9.html

 

Regards, Denis: iMac 27” mid-2015, macOS 11.7.10 Big Sur; 2TB SSD, 24 GB Ram, GPU 2 GB; LrC 12.5,; Lr 6.5, PS 24.7,; ACR 15.5,; (also Laptop Win 11, ver 24H2, LrC 15.3; PS 27.0; ) Camera Oly OM-D E-M1.
DdeGannes
Community Expert
Community Expert
February 17, 2020

The Process for creating Default Develop Settings has been changed in LR Classic 9.2

See the link for further info and instructions.

 

https://community.adobe.com/t5/lightroom-classic/lightroom-classic-how-to-configure-default-settings-for-importing-raw-files/td-p/10925693?page=1

 

Regards, Denis: iMac 27” mid-2015, macOS 11.7.10 Big Sur; 2TB SSD, 24 GB Ram, GPU 2 GB; LrC 12.5,; Lr 6.5, PS 24.7,; ACR 15.5,; (also Laptop Win 11, ver 24H2, LrC 15.3; PS 27.0; ) Camera Oly OM-D E-M1.
Participant
February 17, 2020

Thanks for the feedback, I had read about that, however, why would 20 of the 31 camera matching profiles disappear from within the Develop module? It's nice to have this option for import, but you'd still certainly need the option to change the profile once you begin editing. 

Participant
February 17, 2020

Yeah same issue here, before update there was 20 more camera matching profile available and now you can only find eleven of them, though they are still showing on images that already had them selected on them, So looks like there still in there somewhere just not on the menu

Participant
February 17, 2020

I'm having the same issue with my Z6 files since updating to 9.2 on my MacBookPro with 10.15.1

DdeGannes
Community Expert
Community Expert
February 17, 2020

Matt, any reason you have not updated your macOS to 10.15.3 there are lots of bug fixes.

 

Regards, Denis: iMac 27” mid-2015, macOS 11.7.10 Big Sur; 2TB SSD, 24 GB Ram, GPU 2 GB; LrC 12.5,; Lr 6.5, PS 24.7,; ACR 15.5,; (also Laptop Win 11, ver 24H2, LrC 15.3; PS 27.0; ) Camera Oly OM-D E-M1.
Participant
February 17, 2020

No reason, however, this issue only started happening once I updated from 9.1 to 9.2. I downgraded to 9.1 and they are all back.