Lightroom Classic 9.0 Synced Album Color Management Broken in Web App

  • 2
  • Problem
  • Updated 6 months ago
  • (Edited)
Color management is no longer functioning properly in the Web app and Shared Albums using LR Classic 9.0 on Windows 10 Version 1903 Build 18362 with FireFox 70.0.1. Raw files appear over-saturated and non-raw JPEG and TIFF files appear correct. Both file types appear over-saturated when in the Web app Edit module (Edit this photo).


Photo of Todd Shaner

Todd Shaner, Champion

  • 1945 Posts
  • 653 Reply Likes

Posted 7 months ago

  • 2
Photo of Todd Shaner

Todd Shaner, Champion

  • 1945 Posts
  • 653 Reply Likes
I had a chance to investigate this further and it appears both the LR Web app and Shared Albums no longer work with custom camera profiles created using the ColorChecker Passport software or DNG Profile Editor. Instead the Adobe Standard camera profile is substituted. This was verified by exporting a raw file with Adobe Standard camera profile assigned to TIFF format and then uploading the TIFF file and the original raw file with a custom camera profile assigned. When the two are compared in the Web app or a Shared Album they appear identical, but inside LR the two are clearly different. LR Desktop 3.0 created albums do NOT exhibit this issue.

When viewed in the Web app's Develop module (Edit this photo) all images (raw, JPEG, TIFF) appear over-saturated on my wide gamut monitor. Changing the monitor's color mode to sRGB corrects the issue, which indicates the Web app Develop module is not using the display profile and assumes it to be sRGB. However, both the Web app and Shared Album Grid and Loupe view appear to use the display profile as JPEG , TIFF and raw image files with an Adobe camera profile assigned (i.e. Adobe Standard, etc.) display correct color. Both LR Classic 9.0 and LR Desktop 3.0 exhibit this behavior.
(Edited)
Photo of Andrew Rodney

Andrew Rodney

  • 1014 Posts
  • 219 Reply Likes
Not sure I fully understand what's wrong. What is the "LR Web App"? But I can state, on Mac OS, with a raw, with a custom .DCP profile, what I see in Library and Web Module match. Using a wide gamut display. 

Photo of Todd Shaner

Todd Shaner, Champion

  • 1942 Posts
  • 651 Reply Likes
Andrew, I'm referring to the Web app at lightroom.adobe.com and not the LR Classic Web module. To see the issue in LR Classic 9.0:

1) Assign a custom camera profile created with CCPP, DPE, or other DCP profile editing app to a raw file. (Choose a camera profile and image file that exhibits a significant difference in rendering between the custom camera profile and Adobe Standard. This will make it easier to see the issue when reviewing the files online in the Web app.)

2) Export the raw file to Prophoto RGB, 16 bit, TIFF file format to create a non-raw file reference image.

3) Create a virtual copy of the raw file, change the camera profile to Adobe Standard, and export the raw file copy to ProPhoto RGB, 16 bit, TIFF file format with a unique name (FILENAME_Adobe Standard).

4) Next select the original raw file and two TIFF export files, create a Collection, and in the popup check 'Include selected photos' and 'Sync with Lightroom.'

After syncing has completed in the upper left task bar go to lightroom.adobe.com, which will take you to your synced collections and any LR albums you may have created. The original raw file with CCPP profile should look identical to the TIFF file created from this raw file with CCPP profile assigned. Instead you should observe that it looks like the export TIFF file created from the virtual copy with Adobe Standard profile assigned. It appears the custom camera profile is treated as "missing" and instead the Adobe Standard camera profile is substituted.

Next in the online Web app album at lightroom.adobe.com click on 'Edit this photo' in the upper left hand corner. On my wide gamut display the image color becomes more saturated, indicating the display profile is not being used and assumed to be sRGB. So the Web app Loupe and Grid views are fully color managed, but Edit view doesn't use the display profile. This was confirmed by Adobe Engineering who is currently looking at fixes for both of these issues.

Please let me know if you can duplicate this behavior on your Mac system. Thank you.
Photo of Alex Dixon

Alex Dixon, Company Admin

  • 80 Posts
  • 47 Reply Likes
The issue here is that 3rd party and custom created Camera/Lens profiles applied in Lightroom Classic are not synced, which is a limitation of Lightroom Classic.

If you were to do the same in Lightroom CC, the custom/3rd party profile is synced for you account.
I'll follow up with the Lightroom Classic team to see if there's at least a way to add a warning about this scenario.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1942 Posts
  • 651 Reply Likes
Alex, all of my custom camera profiles have been synced to the Cloud using LR Desktop and they appear in the LR Web app edit panel.
When I view raw files in a LR Classic synced collection that have been assigned a custom camera profile they are rendered in the Web app grid and loupe views with Adobe Standard. When the Web app is switched to edit mode (Edit this photo) the LR Classic assigned custom camera profile appears in the Profile selector and is applied. So the custom camera profile has been synced to the Cloud and is available in the Web app. It's just not being utilized in the Web app Grid and Loupe views. Ditto for the system display profile in the Web app edit mode (Edit this photo). It also is simply not being used.

It shouldn't be too difficult to fix both of these issues.
Photo of Alex Dixon

Alex Dixon, Company Admin

  • 80 Posts
  • 47 Reply Likes
Apologies Todd -- I misunderstood the issue here. I'm following up further. Agreed that if the web editor is showing the right pixels we have a rendering bug here.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1942 Posts
  • 651 Reply Likes
Thank you Alex!