by ctaulbee » Thu Apr 04, 2019 5:18 pm
I don't know if this will help or not and might have nothing to do with your problem but one thing I have found with Photoshop that can cause unexpected results and is hard to find the cause, is the order in which it renders things.
It's not always logical like one would think.
So in special case where it matters if one effect or adjustment is rendered before another in the Photoshop kernel the resulting output can look odd while each layer if viewed on it's own would be fine.
This particularity true with layer effects and clipping masks or so I have seen.
One thing one can try is nesting items into smart objects, I have found this to be effective in certain cases.
It's like when writing code sometimes you need a function to occur before the next and you can't physically put it first so you put it in parentheses to force the compiler to process it first even though it appears later, that type of thing.
Smart objects can do that for you by making all the things inside them get rendered before the rest of the effects above it are processed.
or
A smart object layer with effects inside it, then applied as a clipping mask can insure that is all rendered before it is applied as a clipping mask to the layer or group it's clipped to.
Just things to think about, your situation may be none of that and I'm sure there are other things like this that Photoshop does that we don't think about because it does not affect anything we normally do, it usually takes unique combinations of things to highlight logic processing issues and this is likely that in some way.
I don't know if this will help or not and might have nothing to do with your problem but one thing I have found with Photoshop that can cause unexpected results and is hard to find the cause, is the order in which it renders things.
It's not always logical like one would think.
So in special case where it matters if one effect or adjustment is rendered before another in the Photoshop kernel the resulting output can look odd while each layer if viewed on it's own would be fine.
This particularity true with layer effects and clipping masks or so I have seen.
One thing one can try is nesting items into smart objects, I have found this to be effective in certain cases.
It's like when writing code sometimes you need a function to occur before the next and you can't physically put it first so you put it in parentheses to force the compiler to process it first even though it appears later, that type of thing.
Smart objects can do that for you by making all the things inside them get rendered before the rest of the effects above it are processed.
or
A smart object layer with effects inside it, then applied as a clipping mask can insure that is all rendered before it is applied as a clipping mask to the layer or group it's clipped to.
Just things to think about, your situation may be none of that and I'm sure there are other things like this that Photoshop does that we don't think about because it does not affect anything we normally do, it usually takes unique combinations of things to highlight logic processing issues and this is likely that in some way.