Skip to main content
Participant
Apr 4, 2025 1:46 AM UTC
Question

Hue/Sat bug

I had an image with a dog over a bluescreen background, isolated the dog to use over another background, added a hue/sat adjustment layer clipped to the dog layer, selected the blue color, adjusted the slider to include all blues/cyans, and shifted the color to a orange and desaturated it a good bit to control the blue spill. It desaturated the layers beneath the one it was clipped to as well, and then changing settings stopped making any changes visually. 

 

LOVE the look of the new HSL adjustment layer though. It's nice to click the color swatch rather than pull down and choose blues. Much more intuitive. 

6 replies

Known Participant
Apr 4, 2025 5:41 PM UTC

Just a sidenote:
you never needed to open the pulldown menu and choose a color. You could just take the "targeted adjustment tool" and hover over the color diretcly within the image itself and drag left or right.

Translate
Participant
Apr 28, 2025 3:53 PM UTC

Thank you.I use the targeted adjustment tool in curves all the time. Just never think to in hue/sat. In this case, it was a spill correction, so clicking on a blue pixel would have been harder than just making a choice within the hue/sat panel. 

Translate
Trevor.Dennis
Community Expert
Community Expert
Apr 29, 2025 5:34 AM UTC

Gary, Jesus Ramiriz has a useful tutorial on the new Hue/Sat tools on his Photoshop Training Channel.

Always the first stop for quality Photoshop instruction.

Translate
CShubert
Community Manager
Community Manager
Apr 4, 2025 2:36 PM UTC

Hi @garyh73196690 would it be possible to share a video of your workflow where you see this issue?  Happy to have the team look into this but we need to see what you are doing in what order to make sure we can recreate this issue.

 

It may help if we could see your Photoshop beta System Info. Launch Photoshop beta, and select Help >System Info...and copy/paste the text in a reply.  

 

Thanks,

Cory - Photoshop Product Manager

Translate
Participant
Apr 28, 2025 3:50 PM UTC

The beta update that came after that must have fixed this. It works as expected now. 

Translate