BlendIf-Desaturate problem in Photoshop

leidan_37 · 19-03-2010, 01:17 PM

I have a little problem and I hope that someone here may be able to help me.

I found a nice image on CgTextures (Search for #3829) and then placed it over my DiffMap in PS. I figured out how to use the BlendIf function to get rid of everything but the rust in that image so that I can place just the rusty patch over everything else.

(My Rusty patch overlayed onto my DiffMap. All fine and dandy, except that I want it desaturated)

Then, after taking a long, critical look at it, I decided that it was a bit too saturated so I added a Hue/Saturation Adjustment. I clipped it to the layer underneath so that it wouldn't modify all the other layers, and that's where the problems started.

(Layer Clipping)

Now when I adjust the saturation, it seems to modify the layer BEFORE the BlendIf does it's work. In other words, I adjust the saturation, and the effect from the BlendIf changes. So what I need is that the saturation get's taken into account AFTER the BlendIf and I haven't the foggiest notion how to do that. I've been messing around for a while, searched online, but with no success.

(Note, I don't know if this has anything to do with it, but If I don't clip the adjustment to the layer underneath it works fine, but then all the other layers get desaturated as well, and of course that won't work.)

The Layer Desaturated:

A similar though inverse problem happens when I bump the saturation up:

Ex-Ray · 19-03-2010, 03:44 PM

After you have desaturated it to a level you like go back to the Blendif sliders and re-adjust. If you can't get it to the coverage you like add a levels adjustment layer and bring the levels up and you should start seeing move coverage being exposed.

When you desaterate you end up 'darkening'/lowering the luminance? And the blendif functions from these values hence why it gets affected (as far as I'm aware, I maybe wrong though)

leidan_37 · 19-03-2010, 04:05 PM

That's a thought, I guess I could do it that way. But there's no way to desaturate nondestructively and use BlendIf?

leidan_37 · 23-03-2010, 03:49 AM

FOR THE RECORD:
If you want to 'apply' your BlendIf, you need to create an empty layer below it (Shift-Cntrl-N), then merge your original layer down.

I found out that the original solution presented to me worked with desaturation, but if I wanted to create normals (with the nvidia plugin) from that layer, it would break it again.
I'm really glad I finally figured this out. Hopefully this thread can be helpful for some other newbies like myself.

19-03-2010, 01:17 PM	#1 (permalink)
leidan_37 New Member 51 - 1	[Solved] BlendIf-Desaturate problem in Photoshop I have a little problem and I hope that someone here may be able to help me. I found a nice image on CgTextures (Search for #3829) and then placed it over my DiffMap in PS. I figured out how to use the BlendIf function to get rid of everything but the rust in that image so that I can place just the rusty patch over everything else. (My Rusty patch overlayed onto my DiffMap. All fine and dandy, except that I want it desaturated) Then, after taking a long, critical look at it, I decided that it was a bit too saturated so I added a Hue/Saturation Adjustment. I clipped it to the layer underneath so that it wouldn't modify all the other layers, and that's where the problems started. (Layer Clipping) Now when I adjust the saturation, it seems to modify the layer BEFORE the BlendIf does it's work. In other words, I adjust the saturation, and the effect from the BlendIf changes. So what I need is that the saturation get's taken into account AFTER the BlendIf and I haven't the foggiest notion how to do that. I've been messing around for a while, searched online, but with no success. (Note, I don't know if this has anything to do with it, but If I don't clip the adjustment to the layer underneath it works fine, but then all the other layers get desaturated as well, and of course that won't work.) The Layer Desaturated: A similar though inverse problem happens when I bump the saturation up: Last edited by leidan_37; 20-03-2010 at 01:07 AM.

19-03-2010, 03:44 PM	#2 (permalink)
Ex-Ray Senior Member 279 - 132	After you have desaturated it to a level you like go back to the Blendif sliders and re-adjust. If you can't get it to the coverage you like add a levels adjustment layer and bring the levels up and you should start seeing move coverage being exposed. When you desaterate you end up 'darkening'/lowering the luminance? And the blendif functions from these values hence why it gets affected (as far as I'm aware, I maybe wrong though) Last edited by Ex-Ray; 19-03-2010 at 03:46 PM.

Bookmarks
Digg	del.icio.us	StumbleUpon	Google

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

19-03-2010, 04:05 PM	#3 (permalink)
leidan_37 New Member 51 - 1	That's a thought, I guess I could do it that way. But there's no way to desaturate nondestructively and use BlendIf?

23-03-2010, 03:49 AM	#4 (permalink)
leidan_37 New Member 51 - 1	FOR THE RECORD: If you want to 'apply' your BlendIf, you need to create an empty layer below it (Shift-Cntrl-N), then merge your original layer down. I found out that the original solution presented to me worked with desaturation, but if I wanted to create normals (with the nvidia plugin) from that layer, it would break it again. I'm really glad I finally figured this out. Hopefully this thread can be helpful for some other newbies like myself.