P: Decouple Tint & Temperature Sliders in Auto Sync/Sync/Copy & Paste workflows

Yesterday I confirmed that I am experiencing the same issues with Auto-Sync of the white balance changes in LrC 12.4. However, I subsequently decided to do more tests with the Auto-Sync of other basic edits with LrC 12.4.

My expectation for the Auto-Sync feature with multiple images selected and the Auto-Sync activated each and every edit applied to the most selected image gets applied to the other selected images. The edits are specific so if you add +10  to the exposure, if the exposure for the most selected image was +5 it would increase to +65, if the exposure of one of the other selected images was -35 it would be increased to -25.

What happens in LrC 12.4 is that it is copying the resultant exposure of +65 from the most selected image. 

Some irrelevant info was deleted, Denis.

This information is not correct see the response from Johan below.

Images deleted no longer relevant.

@johnrellis , I arrived home yesterday. I have checked on my system, LrC 12.4 and macOS Big Sur and can confirm I experience the same result.

Ok will check on my system when I return home.

Will also check the Copy/ Paste- Sync option.

In my tests, I wasn't auto-syncing As Shot.  Here's the exact sequence of steps:

1. Both the source and target photos are set to WB: As Shot.

2. Enable Auto Sync.

3. Change Tint of the source photo, and WB immediately changes to Custom.

4. Both the Tint and Temp from the source photo's Custom settings are copied to the target photo, which changes to Custom.

My only thought here is "As Shot" is Adobe's setting for it's interpretation of the Camera WB settings and is image specific. WB i.e. actual color temperature changes as you capture images.

When you make any change it becomes custom settings to copy and apply, if you copy "As shot" to another image it just retains the "As shot" settings for that image.

"As shot" has been a got-ya since inception.

@johnrellis , this is strange and not what I would expect. I will check on my system when I return home next Thursday as I only have my iPad with me on vacation over the past three months.

Quote "I can't think of a good design reason why Auto Sync would ever copy Temp when Tint is changed or why in older versions there's a difference in behavior between WB: As Shot and WB: Custom." A big ?.?.

@johnrellis This is excellent researhc, John. Frankly I'm astonished it's been this way for so long and I haven't noticed. I suppoose they would say that's evidence it's fine the way it is. But frankly it's absolutely incomprehensible why these two sliders are locked together like this. It suggests to me that Adobe don't care how professionals use their software. 

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

"If this is designed behaviour then it has been designed in the latest version as these sliders were previously decoupled."

I did more thorough testing, and the behavior of Auto Sync of Tint changed two years ago in LR 11.0.

In all versions going back to LR 6.14, when the source and target photos have WB: As Shot, Auto Sync of a change to Tint copies Temp as well.

Prior to LR 11.0, when the source and target photos have WB: Custom, Auto Sync of a change to Tint copied Tint only, not Temp.  But starting with LR 11.0, it copied Temp also.

Here's a summary of whether Auto Sync copies Temp as well as Tint, by version:

Note that the bezel that appears always says "Tint updated", regardless of whether Temp is also updated:

This is misleadingly inconsistent with the actual behavior (i.e. a bug).

I can't think of a good design reason why Auto Sync would ever copy Temp when Tint is changed or why in older versions there's a difference in behavior between WB: As Shot and WB: Custom.

Typically, when the developers pronounce a behavior "as designed", they won't explain the design rationale and they won't change their minds. It may in fact have been an explicit design with some rationale, or it may be that, as it appears all too often in recent years, the behavior wasn't explicitly intended, and "as designed" is an excuse to avoid changing complicated code that is no longer well-understood by the current developers (and an easy way to meet management incentives to reduce the number of formal bugs).

If this is designed behaviour then it has been design in the latest version as these sliders were previously decoupled. Why would the Temp and Tint be coupled if the HSL sliders are not when auotsyncing? I've been using Lightroom for 10 years and adjusting Temp only using Autosync the entire time. It's part of the reason I use auto sync over the dialogue box regular sync option.

Also....why would you suddenly have so many people posting about this issue if it was intended behaviour prior to recent times?

Maybe it was longer ago than I thought. Before the xmp presets were introduced in version 7.3, you could create a preset for white balance and then simply remove either the temperature of the tint setting using a text editor. Since the presets changed to xmp that no longer works. So perhaps this auto sync behavior changed at that time too.