Skip to main content
Inspiring
July 24, 2019

P: Linear (non-standard) profile in LR Mobile

  • July 24, 2019
  • 37 replies
  • 4374 views

I have been, successfully, trying out linear profiles in LRC. They are very helpful for certain images. The problem is, when the image is posted to LR Mobile.

First, while reviewing the images, I get a pop up message that editing in Mobile will lose settings as it is not a standard profile. That would be ok, as I was just using LRM to display the images. The problem is, the image is not rendered as it was with the original linear profile…it is much brighter and washed out as if another profile (tone curve) had been used.

I had a mix of ‘Adobe Neutral’ and linear profile images. The ‘AN’ images rendered as shown on LRC, the linear were washed out.

LRC 10.4, Win 10
Is this a bug or ‘as designed’?

This topic has been closed for replies.

37 replies

jrsforumsAuthor
Inspiring
September 25, 2021

Thank you for the extra effort you are putting in to run this down!!

 

 

Todd Shaner
Legend
September 25, 2021

I ran another test by deleting the test collection and creating a new collection with the same image files. The rendering now was incorrect in Loupe view with Information panel open and Grid view. I was also seeing the same issue in LR Desktop. After applying an edit to the file in each app (LR Desktop & Mobile) the rendering issue was no longer present in any of the view modes. To be clear it was necessary to apply edits in BOTH the LR Desktop and Mobile app as editing in one app only fixed the issue in that one app.

 

Clearly, this would frustrate any user to no end, but I'm guessing most LR Ecosystem users aren't using custom camera profiles. What appears to be happening is that the Adobe Standard profile is being applied even when the custom camera profile is visible and applied in each app (LrC, LR Desktop, LR Mobile). It's only after applying edits that the custom camera profile is being used in all view modes (Grid, Loupe, Edit). In addition the linear camera profile being used by jrsfoums exhibits a much more obvious rendering difference compared to Adobe Standard. For more typical custom profiles such as ColorChecker PassPort calibration profiles the rendering differences will be more subtle and not as easily detected.

jrsforumsAuthor
Inspiring
September 25, 2021

Yes, that is what I was finding.  

No editing in Mobile would make the Loupe/grid views change permanently...they kept changing back to original wrong view.  I did try to make some edit changes in the browser, which had also the same bright, washed out look.  I also reviewed each of the images in LR desktop, where the images did seem to have 'accepted' the linear profile look.  One or both of these action seems to have changed the images in Mobile, which now look like they should.  Because of other commitments, I will be unable to test this again until at least late next week.

Todd Shaner
Legend
September 24, 2021

"Do you know if one gets a different end result if you start with a different profile, such as Adobe Color/Neutral or Camera Standard?"

The Adobe Color, Neutral, etc. are creative profiles that use Adobe Standard as the Base Profile. Since your issue is with non-creative profiles let's stay focused on standard profiles for this specific issue.

 

I downloaded the three RW2 raw files with XMP data files and your Linear-Panasonic DC-G9.dcp camera profile. My initial tests using LR Mobile for Android shows the same washed out low contrast rendering, even after I imported the linear camera profile using LR Desktop. I waited a few minutes to make sure the collection with your RW2 files and the linear camera profile were synced to the Cloud. I also tested CR2 raw files using Adobe Standard with a linear tone curve and with a ColorChecker Passport created custom camera profile. Using LR Mobile for Android the RW2 files render correctly with the synced linear camera profile in the Edit mode (i.e. Adjustments) and Loupe view with the Information panel open on the right side. In Loupe view with Information panel closed and Grid view the preview rendering is incorrect. The CR2 files exhibit the exact same behavior so it appears to be a bug when using ANY custom modified camera profile. Is this what you're seeing?

 

jrsforumsAuthor
Inspiring
September 24, 2021

I sent this to Todd.  I will let him reply with any findings he has...

Here’s a link to “LR linear” in my Dropbox:
https://www.dropbox.com/sh/gqu412rch14gn0x/AAAuUaeeFWIR9bB96fYHzCgza?dl=0

 

These are just outtakes I was playing with.  After seeing the results, I had converted all final images to jpeg to send for review.

 

I appreciate your looking at this, plus the research to find the other post on the subject.

I know you said you create a linear profile based on 'Adobe Standard'.  Do you know if one gets a different end result if you start with a different profile, such as Adobe Color/Neutral or Camera Standard?  

The link I gave you for my source of the linear profile(s) is run by Tony Kuyper who creates powerful Luminosity Mask plugins.  He just released his update TK8 with 50% discounts for updates., which crashed his site.  I knew it was down 6hrs yesterday, but was not aware it was still down...it is up now.

 

John

jrsforumsAuthor
Inspiring
September 24, 2021

DdeG.....it may be semantics.....but I call it a bug.

DdeGannes
Community Expert
Community Expert
September 23, 2021

@lrsforums, re your recent post. If what you are alluding to has merit if you use Lr (cloud-based) app on your computer to get the profiles to the cloud ecosystem then when you sync an image from LrC the profile should be recognized. Maybe there is a case for a feature reguest ?

 

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.0.1, PS 27.0; ) Camera Oly OM-D E-M1.
Todd Shaner
Legend
September 23, 2021

"Adobe may be correct that their future is the cloud, but, at least in the near term, the reality is images and performance on the desktop. Incompatibilities and inconsistencies like this make it a bit too troublesome. I believe this week's deliverable review will be via Smugmug."

 

From my limited expereince with the LR Ecosystem I have to agree with your assement. Here's a bug report I created from December 2019 concerning color mangement issues with the LR Web app. I just checked today and the issue is still present! You'll only encounter it when using a wide gamut display, but that's no reason for Adobe not to fix it.

https://feedback-readonly.photoshop.com/conversations/lightroom-classic/lightroom-classic-90-synced-album-color-management-broken-in-web-app/5f5f46214b561a3d42753fbd

 

I found this similar post as well.

https://community.adobe.com/t5/lightroom-ecosystem-cloud-based-discussions/custom-camera-profile-bug/m-p/11845099

 

I also ran a raw file test using Adobe Standard camera profile and a copy with a custom ColorChecker Passport camera profile. I exported both to Adobe RGB 16 bit TIFF file format and then synced all four in  a collection to the Cloud. Inside LR Mobile the Adobe Standard raw file and its companion TIFF file look idnetcial as expected and match the preview inside LrC. The custom ColorChecker Passport  raw file looks more color saturated than the preview inside LrC and its companion TIFF file. So it appears color management is broken when using custom camera profiles. Yes, the custom camera profiles have been ingested into LrC, LR Desktop and synced to the Cloud and LR Mobile.

 

If you can upload a raw file with your settings applied and CTRL/CMD S to save them to XMP I'll take a look at it on my Samsung Android tablet. Please upload the raw file, XMP file, and linear camera profile to Dropbox or other a file sharing site. Thank you.

 

jrsforumsAuthor
Inspiring
September 23, 2021

DdeG...not quite, I don't think.

 

LRC does not sync profiles, but it does seem to send a 'pointer' to the correct profile.  This is indicated, first, from the warning, when I had not loaded the linear profile to LR and, when the profile was loaded, on editing, it appeared the image was 'tagged' with the profile that had been used in LRC.

 

The initial problem, that I see, is that LRC does not sync the 'rendered' image shown in develop/libtray on desktop.  What is initially displayed in the cloud (mobile/browser) is using some other (stronger) profile.

 

second, the linear profile was able to be applied by tweaking each image in browser, but not on mobile.

 

A quick, but unconfirmed, test seems to indicate that opening the folder in LR desktop, seems to rollout the proper rendering.  Chasing this down will take some time, as I need to prepare for a weekend event I am shooting and, then, delivering early next week.

 

Adobe may be correct that their future is the cloud, but, at least in the near term, the reality is images and performance on the desktop.  Incompatibilities and inconsistencies like this make it a bit too troublesome.  I believe this week's deliverable review will be via Smugmug.  

DdeGannes
Community Expert
Community Expert
September 23, 2021

@jrsforums States in a post a short while ago.

Quote “So....it seems that LRC desktop is not originally sending(syncing) an image with the linear profile applied.”.

JohanElzenga indicated in the very first reply in the thread.

“Lightroom Classic does not sync profiles.”.

LrC syncs smart-previews to the Adobe Creative Cloud it does not sync profiles so it functions as designed. It is not a bug.

 Are we starting from the beginning again????

 

 

 

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.0.1, PS 27.0; ) Camera Oly OM-D E-M1.