Lightroom Classic CC: Inconsistent application of preset with Auto Settings

  • 1
  • Problem
  • Updated 11 months ago

I do a lot of bulk adjustments and am really liking the output from the new auto, a big improvement on the last one, but I also find images lack a little contrast that applying a medium contrast curve helps with.

 

I created a preset to do both but I'm seeing some odd behaviour.  

Steps taken:

 Develop module, brand new image.

Apply Medium Contrast tone curve from the tone curve module.

"Add new preset"... check the auto settings box and the tone curve box, save.

 

This generates this preset:

s = {id = "B72CCADC-283F-462B-AFB2-6CADC1D73E1C",
internalName = "Auto with Med Contrast Curve",
title = "Auto with Med Contrast Curve",
type = "Develop",
value = {
settings = {
AutoBrightness = false,
AutoContrast = false,
AutoExposure = false,
AutoShadows = false,
AutoTone = true,
ParametricDarks = 0,
ParametricHighlightSplit = 75,
ParametricHighlights = 0,
ParametricLights = 0,
ParametricMidtoneSplit = 50,
ParametricShadowSplit = 25,
ParametricShadows = 0,
ToneCurveName2012 = "Medium Contrast",
ToneCurvePV2012 = {
0,
0,
32,
22,
64,
56,
128,
128,
192,
196,
255,
255,
},
ToneCurvePV2012Blue = {
0,
0,
255,
255,
},
ToneCurvePV2012Green = {
0,
0,
255,
255,
},
ToneCurvePV2012Red = {
0,
0,
255,
255,
},
},
uuid = "49EEBDB0-7DAD-4A48-B44E-AD184C3C3015",
},
version = 0,
}
 


The preset aligns with the content of built in presets for "Auto Settings" and "Medium Contrast Curve".

 

Maybe 8 times out of 10 the preset does what I want but then I get an oddity.

One example - open an existing image with no previous adjustments in develop module...

Apply the preset.... the only thing that happens is the contrast gets adjusted by a small amount.

Reset the image....

Apply the preset again.... behaves as expected.

 

Here's a video cap:

 

 Previously posted here:

https://forums.adobe.com/message/10052617#10052617

Photo of CR10818

CR10818

  • 2 Posts
  • 0 Reply Likes

Posted 11 months ago

  • 1
Photo of Don Hodapp

Don Hodapp

  • 34 Posts
  • 3 Reply Likes
The new "Auto" feature works well for a starting point.  However, I don't think you can include the "Auto" feature in a preset.  It looks to me like "Auto" analyzes the image and then sets various basic points.  After you add "Auto", add Tone Curve, and then create the preset, you're creating a preset with the specific settings that "Auto" used for that specific image.  This preset, when applied to a different image, will use the "Auto" calculations from the original image - it is not recalculating "Auto" for the subsequent image.

What I have done is to use "Auto" on each image - one at a time.  I've created a preset that adds the Tone Curve, some sharpening, and noise reduction, that doesn't interfere with "Auto" adjustments.  Unfortunately, this doesn't help with your situation of wanting to apply it to a batch.  It does not appear to me that "Auto" will work in a preset for batch production as that button must recalculate for each image.

Others may understand this much better than me.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3697 Posts
  • 968 Reply Likes
"After you add Auto, add Tone Curve, and then create the preset, you're creating a preset with the specific settings that Auto used for that specific image."

Presets containing Auto Settings don't work that way.   By design, when a preset has Auto Settings checked, applying that preset to a photo has the same effect as clicking the Auto button in the Develop panel, calculating adjustments specific to that photo. 

You can try this yourself.  Create a preset with Auto Settings checked, select a photo, go into Develop, apply the preset, and compare the results to clicking the Auto button. Repeat with another photo.

By examining the contents of the preset (as posted above), you can see that the preset doesn't contain the actual develop adjustments for the original photo.  It contains the line:

AutoTone = true,

but doesn't contain any lines for Exposure, Contrast, Highlights, etc.

There are bugs, however, causing the results of applying presets with Auto Tone to be intermittently unpredictable.  See my other post: https://feedback.photoshop.com/photoshop_family/topics/lightroom-classic-cc-inconsistent-application...
Photo of CR10818

CR10818

  • 2 Posts
  • 0 Reply Likes
Thanks, yes the built in auto preset works great, just me being lazy and looking to eliminate a step :)
Photo of John R. Ellis

John R. Ellis, Champion

  • 3869 Posts
  • 1023 Reply Likes
I think this bug is related to another long-standing bug: applying Auto Tone to a batch of photos can lose subsequent develop adjustments: https://feedback.photoshop.com/photoshop_family/topics/applying-auto-tone-to-a-batch-of-photos-loses...

Internally, it appears that when you apply Auto Tone to a photo, LR defers the calculations of the actual settings until they are actually "needed", and then it calculates them concurrently with other activities.  Some parts of LR that "need" the settings aren't properly waiting until they are fully calculated, resulting in race conditions such as observed here.

I couldn't reproduce this bug, but that's the nature of race conditions-- they're intermittent by definition and usually dependent on processor and disk speed, the size of photo, other processes running on the computer, etc.
Photo of Don Hodapp

Don Hodapp

  • 34 Posts
  • 3 Reply Likes
I have tested the Auto Tone and find they work exactly the way I described.  When I create a preset after using only Auto the tone sliders are precisely the same on all subsequent images where the preset is applied - regardless of the tonal quality of the image.  Creating a new preset from a different image with different sliders settings will then make all subsequent images exactly like the image.

After applying only Auto Tone my preset shows each of the sliders set individually.

Photo of Don Hodapp

Don Hodapp

  • 34 Posts
  • 3 Reply Likes
One more time.  I see where John is right.  I'd not had the Auto Settings button checked, just the tone setting button.  Sorry 'bout that.