Skip to main content
Participant
June 19, 2022
Question

Issue with Custom Camera Profiles in Lightroom Desktop & Lightroom Mobile

  • June 19, 2022
  • 1 reply
  • 1306 views

When a custom camera profile is created for raw photos and imported into Lightroom CC it functions correctly in Lightroom CC. However if that synced photo is then opened in Lightroom Mobile you get an error 'Missing Profile' which takes up about 1/3 of the iPhone screen which means you cannot conveniently even view the photo, let alone edit it. If you tap the 'Continue' button in this error message the photo does appeare full screen but it changes the Profile to 'Adobe Standard' and syncs that change back to the cloud immediately.

 

I realize that because these profiles work on raw images and Lightroom Mobile doesn't (normally) handle raw images that it might be difficult to properly allow editing of these photos in Mobile without changing the profile to one of the standard ones that are supported in Mobile. But the way these images are handled now is very annoying and even destructive.

 

If Lightroom Mobile cannot handle these custom camera profiles then I would suggest that the Mobile app behavior be changed to at least make viewing the images better/easier. My suggestions would be to either:

 

1. When a photo is openeed in Lightroom Mobile that uses a profile that cannot be handled display the photo using a default profile but do not show the big error message (maybe a small error icon that could be clicked to display the larger message), and DO NOT sync a profile change back to the cloud! Then if the user makes any edits to the photo locally display a message informing them that the profile has been changed for local display and asking them if they want to sync their change (including the profile change) back to the cloud or leave the photo as is. You could even give them the option of syncing whatever active change they made but leaving the profile as is.

 

Or, less user friendly:

 

2. When tapping on an image in Lightroom Mobile that uses an unsupported profile open it in a 'read-only' mode using a default profile without the large error message but with a small 'Edit' button that if tapped would give the user the option of continuing on to edit the photo but warning them that the profile will be immediately changed and synced to the cloud.

 

Or some better User Experience option that I have not thought of but allows the user to at least view all of his/her images without a big dialog box in the way or having their cloud image quietly changed without being properly informed.

 

Also, ensure that the cloud image is at least displayed properly on all devices using the custom color profile assigned, even if that means having to include a second preview image with the profile already applied.

This topic has been closed for replies.

1 reply

Victoria Bampton LR Queen
Community Expert
Community Expert
June 20, 2022

Lightroom mobile is fully capable of editing raw files. The glitch is it downloads profiles on demand rather than downloading every profile from the cloud. If you return to the photo a few minutes later, it should have downloaded, although I still believe that dialog should have a download now button rather than picking a default profile.

Victoria - The Lightroom Queen
Participant
June 17, 2023

I had the same issue.  I had previously been able to have specific camera profiles downloaded into Lightroom mobile.  However, I could not get my latest camera profile to download.  I ensured that this profile was loaded into Lightroom CC, Camera Raw and Lightroom desktop.  All were synced appropriately with the cloud. The profile still did not automatically update in the mobile versions as per online instructions.  I contacted the Adobe help desk.  They suggested I uninstall the mobile version and reinstall.  This worked and the camera profile is now there and the annoying missing profile error is gone.  Further, it took only a few minutes for photos to be available for editing in Lightroom mobile.

StuartBerman
Participant
September 27, 2024

I have the same problem. I tried this and it did not fix it for me.