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

Participating Frequently
October 24, 2025

@johnrellis I appreciate the reply. Just concerning that this bug has been present for years, and every comment gets shoved under the carpet here in this thread - minimizing the number of people who can see them and verify to Adobe that this does indeed negatively affect a huge number of users, and doesn't positively affect even one single user. It's also incorrectly being classified as an "idea" and not a bug.

johnrellis
Legend
October 24, 2025

@julius_s: "Looking for an update on when this is going to be resolved."

 

Unfortunately, Adobe rarely indicates ahead of time when bugs and feature requests might get resolved.  LR 15 is almost certainly due next week during Adobe Max, so one can hope.

Participating Frequently
October 24, 2025

Looking for an update on when this is going to be resolved. I understand that at some point there was some communication that this was intended behaviour, but there was no explanation provided as to why it would be intended when it is exclusively detrimental to a large number of users' workflows, and it is objectively a bug. If dev team is stating that this is intended behaviour I would propose that the issue was not adequately communicated to them.

Participating Frequently
October 2, 2025

@Rikk Flohr: Photography it's been more than two years since your note that this is intended behavior, with no explanation as to why it is intended or how it could possibly, in any situation, ever be helpful to anyone, and you've been sidelining peoples' legitimate frustrations about this issue into this dead end thread ever since. Will this ever be given serious consideration, or does Adobe just not care about wedding and event professionals? What can we do as users to bring attention to this issue?

Participating Frequently
October 2, 2025

@mattkurasho Same! I've tried to switch so many times but indeed there are features that I keep coming back to - the dramatic shift in a workflow I've refined over many years has been difficult to overcome. But I'm extremely unhappy having built my business workflows around Adobe software only to feel like they have completely abandoned me as a customer. The assertion Adobe that this is good design is antagonistic toward any competent professional user of this software. Maybe Mr Flohr could explain to us the dev teams reasoning as to how this design decision could possibly be, by any stretch of the imagination, helpful to anyone in any scenario.

Participating Frequently
October 1, 2025

Thank you @johnrellis , very helpful!

Participant
October 1, 2025

Well described, @julius_s. I'd like to add that it should not matter how much 'Adobe is insistent that WB is one entity not two', and it baffles me which of their customer demographic the team is so keen on looking out for when they say that they believe this should remain a 'designed behaviour'. From my experience, Lightroom Classic is an application used by working professionals for predominantly batch photo editing, and this behaviour is a hinderance in its ability to do so when working with photo collections from inconsistent lighting conditions. Please, feel free to maintain your definition of what white balance means to you, Adobe, but I have ten's of thousands of photos to edit each month and a little UI chainlink checkbox to decouple temp/tint would keep me from searching for LRC alternatives as often as I have been the last couple of years.

johnrellis
Legend
September 30, 2025

@julius_s, while waiting for Adobe to implement this feature request before the next ice age, consider using the Copy Settings plugin, which allows you to copy/sync Temp and Tint separately.

skyrunr
Inspiring
June 11, 2025

Upvoting isn't working on this page, I've even tried two different web browsers.  Is it working for anyone else?  I really wish these threads were easier to read, and that comments were indented under the original post.  If anyone wants to see the best forum layout and design ever, check out DPReview.  I'd pay good money to have Reddit and other forums look and function like DPR!  LOL

Community Expert
December 19, 2024

thanks for the explanation on presets, seem Adobe is insistent that WB is one entity not two. Personally I do tend to treat it so: any correction of WB in my own practice more or less guarantees both numbers must reconsider together.

 

Tint slider does offer hue-shifting of sorts, but there are many other ways to achieve substantially that same effect which are not tied up with WB per se.