Skip to main content
Known Participant
July 20, 2023
Under Review

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

  • July 20, 2023
  • 43 replies
  • 2891 views

Lightroom Classic 12.4 / Camera Raw 15.4

Just imported a dozen Fuji X-T5 raw files. White balance and tint value is slightly different for all of them as they were shot in 'Auto WB' on the camera.

 

Wanted to adjust the tint value on all images but retain their existing WB value.

 

Selected all, made sure Auto Sync was on in Develop mode, and moved the Tint value to 5. 

 

Expected result: all selected images should now have a Tint value of 5, while retaining their original WB value.

 

Actual result: the WB and the Tint value for the main image was applied to all selected images, even though I had not adjusted WB at all.

Did an Undo, went through all images to confirm they all had different WB and tint values. Selected a different image. Did a Select All, Auto Sync on. This time I set the WB value for my main image.

 

Expected result: all selected images should now have the same WB as the main image, but their Tint values should be unchanged.

 

Actual result: again, the adjusted WB and unadjusted Tint values for this image were applied to ALL selected images.

 

Have recreated the issue with every shoot currently waiting to be edited. This is a relatively new issue as I'm used to being able to adjust these values independently of each other across Auto Synced images.

 

43 replies

johnrellis
Legend
July 29, 2023

"I'm pretty sure that this worked correctly before"

 

I just tested LR 10.4, and it behaves the same as LR 12.4.

 

I've had a longstanding feature request to enhance the Copy Settings plugin to allow Temp and Tint to be copied separately. Not sure when I'll be able to get to it.

TomReesFramer
Known Participant
July 20, 2023

I'm once again experiencing a new version of the same bug in LR classic. When auto syncing White Balance across multiple images, both the Temp and Tint are being synced, even when only the temp is being adjusted in the source image.

This behaviour is intermittantly experienced with multplie develop settings. HSL & Crop exhibit the same behaviour intermittantly and are already well documented bugs.

Why aren't these issues being investigated and fixed? Lightroom classic seems to have more and more bugs with every release.

This particular bug is serious issue for wedding photographers and photographers working with large volume adjustments.

12.4
Mac OS

GoldingD
Legend
July 20, 2023

Hmm, try this

Select any photo, select to copy the develop settings, in the dialog box that appears, deselect all the boxes, (perhaps tint was involved) close that. Now try your normal auto sync method.

Not a fix.

Community Expert
July 24, 2023

I haven't the ability to check just now - could the Quick Develop panel be a method to consider? (in Library)

 

With AutoSync.

 

A nudge of (say) Tint  could produce the same visual change on several highlighted images: NB unlike working in Develop, this operates relatively onto images' current values for the parameter in question so a slight change of workflow habits is required.

 

Other ideas for bulk adjustment, assuming OP is open to other means and is not dead set on altering the WB in particular: 

  • HSL panel (e.g. hue shift)
  • Calibration panel manual colour response sliders
  • Tone Curve panel
  • Grading panel

 

OR sticking with WB, syncing across images a local adjustment mask - or applying that via a Preset - which affects the entire image area and adds a certain WB tweak of Tint alone.

owen-bAuthor
Known Participant
July 24, 2023

@JohanElzenga good point well made, I've been using 'WB' to describe the temperature slider. My bad. 

JohanElzenga
Community Expert
Community Expert
July 24, 2023

Just as a side note: The White Balance is set by the combination of the Temperature and Tint sliders. There is no WB slider.

 

-- Johan W. Elzenga
owen-bAuthor
Known Participant
July 24, 2023

@Rikk Flohr: Photography "That would be incorrect"


Understood, but that just makes the design choice to lock WB and tint together for Auto-Sync adjustments even more confounding a decision. I genuinely would ask them how they think people use LRC, and why they think WB and tint always work relative to each othr. They don't, there are many very good reasons why a working professional would want to mass-adjust tint or WB without the other value being adjusted to match the source.

Genuinely bemused.  

Rikk Flohr_Photography
Community Manager
Community Manager
July 24, 2023

From @GoldingD "Sounds like the team misunderstood"

That would be incorrect. 

Rikk Flohr: Adobe Photography Org
GoldingD
Legend
July 24, 2023

"Note: The team has advised this is currently as-designed behavior. I've moved this post into the feature requests forum for possible future enhancement. "

 

Sounds like the team misunderstood, OP is not selecting a WB preset, such as Daylight as opposed to As Shot, OP is adjusting only the Tint Slider.  If Auto Sync, or Sync moves both, then that is lousy as designed operation.

 

So, bad design decision, I call this a Bug.

owen-bAuthor
Known Participant
July 24, 2023

@JohanElzenga agreed, it doesn't come up every shoot that I need to adjust tint and WB across multiple images independently of each other, but enough that when I tried to do it on a recent shoot I instantly noticed they're now locked together and it was an issue. So this has got to be a relatively new change and I can't understand the reasoning. Light just doesn't work like that universally, WB and tint are not always in a direct relationship with each other.

JohanElzenga
Community Expert
Community Expert
July 24, 2023

@Rikk Flohr: Photography I'm pretty sure that this worked correctly before, so how can this faulty behavior suddenly be 'as designed'?

 

-- Johan W. Elzenga
owen-bAuthor
Known Participant
July 24, 2023

Oh wow, seriously?!

That is a TERRIBLE choice. There are many examples I can cite where I need to bulk adjust one of these but not the other. What practical reasons does Adobe have to believe that they should be linked?