Auto-tone not matching between Lightroom Classic CC 7.4 and Lightroom CC (iPad)

  • 1
  • Problem
  • Updated 2 months ago
For me it looks like Lightroom Classic and Lightroom CC (ipad) do not use the same algorithms in the develop module since Classic 7.4. I noticed that with auto-tone feature. Since Classic 7.4 auto-tone gives for at least have of my images different values on Classic and Mobile.

I use mainly Lightroom Classic and sync Smart Previews to Lightroom CC. 

I have another issue, that might be related:  https://feedback.photoshop.com/photoshop_family/topics/default-development-setting-does-not-sync-fro...

And there is another unanswered topic, that might be related as well: https://feedback.photoshop.com/photoshop_family/topics/clipping-warning-inconsistency
Photo of tpnotes

tpnotes

  • 51 Posts
  • 7 Reply Likes
  • frustrated

Posted 2 months ago

  • 1
Photo of Yves Crausaz

Yves Crausaz

  • 219 Posts
  • 29 Reply Likes
Hello, I'm doing the test 5 minutes ago:
Import on LR Classic 7.4 (macOSX 10.13.6) Default profile = Adobe Color.
Synchronizing the collection on my iPad Pro LR CC v.3.3.1 FB4961 (IOS 11.4.1), Profile and Adobe Color as it should be.
On the iPad changes the profile for Camera Matching, Change OK on LR Classic
idem for AUTO-TONE

Import in LR CC withe a preset Appareil Mis en sourdine


Import ok, synchro on iPad OK, change Auto-Tone on iPad, synchro OK, Auto-Tone ok on LR Classic.
(Edited)
Photo of Yves Crausaz

Yves Crausaz

  • 219 Posts
  • 29 Reply Likes
In addition, do not forget to synchronize your predefined parameters via LR CC (the PC or Mac application) to be able to apply them directly from your mobile devices!
Be careful the old presets may not be suitable due to the change of mode from the LR CC v7.3 !!!!


Photo of john beardsworth

john beardsworth

  • 1042 Posts
  • 239 Reply Likes
I would expect that the difference is due to LrClassic processing the full res raw file, and LRiOS processing the smart preview.

You could test this by uploading a raw file - eg by importing it directly into LRiOS or drag and drop into LrWeb - and seeing what results Auto produces.  Alternatively, generate a smart preview in LrClassic, rename the original in Explorer/Finder, and then try Auto.
Photo of Yves Crausaz

Yves Crausaz

  • 219 Posts
  • 29 Reply Likes
This is what I did in my demonstrations above.
Loaded with the sdcard in LR Classic, auto, sync to LR CC, the sliders all have the same values, so no problem. Then I loaded the same photos on iPad, LR CC, auto, sync to LR Classic, the sliders have exactly the same values! Same for the Profiles.

It is necessary to make the same experiment on your installations and if difference imperatively to specify the versions of the software and the OS, otherwise at Adobe they will not be able to reproduce the problem!

Photo of john beardsworth

john beardsworth

  • 1042 Posts
  • 239 Reply Likes
I am not sure they (or I) will see it as a problem. You can see something similar with AutoSync in LrClassic if you have the smart preview option enabled which means the most selected photo's Auto is based on the raw data while the others get Auto based on the smart preview image data. This results in differences which are usually small, and while in theory it would be nice to have Auto calculated for each raw file based on raw data, in practice I can live with the compromises. Overall, Auto saves time overall, even if it isn't always "right" - whatever that means for an Auto button.

Photo of tpnotes

tpnotes

  • 51 Posts
  • 7 Reply Likes
Thanks for your input. I have tested it and it seems to be an issue of using smart previews. I considered them to be more reliable, especially with quite similar images.