Skip to main content
Known Participant
December 14, 2017
Question

Tone "Auto" button consistently gives severely underexposed pictures

  • December 14, 2017
  • 5 replies
  • 3027 views

Hello, I have updated to the latest version of the LightRoom CC Classic (version: 7.1 [ 1148620 ]). When I first used the new "Auto" (AI based) button, I was very pleased with the results. When I returned to the LR next day, the "Auto" button started consistently produce severely underexposed pictures. Have I screwed some setting? The button is supposed "to learn" from my actions - as far as I understood. Can I reset all that it "learned"? Does somebody else experience the same problem?

Lightroom Classic version: 7.1 [ 1148620 ]

Language setting: en

Operating system: Windows 10 - Business Edition

Version: 10.0.15063

Application architecture: x64

System architecture: x64

Thanks,

Alexander

    This topic has been closed for replies.

    5 replies

    fns_video
    Participant
    April 18, 2019

    I've got the same issue. I built a new computer and installed the most recent version of Lightroom Classic CC. I use to always click the Auto Tone button to start my developing process and it would usually do a very good job, requiring a couple tweaks. But now clicking the Auto Tone button makes the picture severely underexposed.

    For example, on a recent photo it dropped the exposure setting to -1.48, but when I would manually fixed the exposure, it ended up being +1.67.

    I would love a solution/fix for this issue.

    Mark

    dj_paige
    Legend
    April 18, 2019

    Are you using an older process version? (perhaps that's the default in a develop preset applied to your photos?)

    fns_video
    Participant
    April 18, 2019

    No... it says I am using Version 5 (Current). It also doesn't have anything to do with photos processed in my previous installation of an older version of Lightroom because this is happening to any photos I'm trying to Auto Tone, whether preexisting or a new import.

    Participating Frequently
    March 27, 2018

    If you have photos that were previously edited in a several-years old version of Lightroom, be sure to select them all and use "Develop module > Settings > Update to Current Process" to make available the latest editing capabilities for Auto, Shadows, Highlights, Brushes, etc.

    Participant
    January 4, 2018

    Hi,

    Any luck on fixing this problem? I am currently having the same problem with the auto tone and I agree that the auto tone makes the picture worse than it was unedited and severely underexposed. I just recently subscribed to the premium couple of days ago and was using the trial version beforehand which tells me my trial has expired, hence thought that is the reason why the auto tone doesnt work, obviously something is amiss. Thanks.

    johnrellis
    Legend
    December 14, 2017

    The button is supposed "to learn" from my actions - as far as I understood.

    I haven't read that anywhere -- what I've read is that the algorithm is trained on thousands of pics adjusted by professional photographers.  But perhaps you read something different?  Do you have a link?

    shmuglakAuthor
    Known Participant
    December 16, 2017

    My bad. Apparently it was my too liberal interpretation of the passage: https://theblog.adobe.com/announcing-december-update-lightroom/

    "Using an advanced neural network powered by Adobe Sensei, our artificial intelligence (AI) and machine learning platform, the new Auto Settings creates a better photo by analyzing your photo and comparing to tens of thousands of professionally edited photos to create a beautiful, pleasing image."

    from here: Announcing the December Update to Lightroom | Adobe Blog

    Anyway, my own pictures become anything  but beautiful and pleasing after using the "Auto" button.

    dj_paige
    Legend
    December 14, 2017

    Perhaps you have photos that are older process versions, in which case the Auto Tone button will work as it was previously.

    shmuglakAuthor
    Known Participant
    December 16, 2017

    @dj_paige Actually, it works worse than it was previously...