Split toning with the colour balance tool
Here's a feature I discovered by accident. It appears to be new in v11.
If you convert an image to black and white using the tools on the B&W tool tab - enable black and white, adjust the various colours to get the B&W look you want, etc - you can then go to the colour balance tool and use the three colour wheels to do split toning. In fact if you wanted you could do three way split toning, which you can't do with the split toning feature on the B&W tab.
Ian
If you convert an image to black and white using the tools on the B&W tool tab - enable black and white, adjust the various colours to get the B&W look you want, etc - you can then go to the colour balance tool and use the three colour wheels to do split toning. In fact if you wanted you could do three way split toning, which you can't do with the split toning feature on the B&W tab.
Ian
0
-
This 'feature' doesn't work when using engine v10.
With the v10 engine it works like a color filter on B&W film.
With the v11 engine it works like split toning.
So the question is: is this meant to be this way?
Regards,
Hans0 -
I believe it is meant to be that way. It's the result of changing the order of the "image processing pipeline" apparently.
Ian0 -
I'll ask support about it. Not that I cannot do it another way, but I do like the combination of the 'Color Balance' tool with the 'Color Sensitivity' sliders in engine v10.
Regards,
Hans0 -
Are you using layers Ian? 0 -
SFA wrote:
Are you using layers Ian?
Not in this instance, Grant. Just an image with enable B&W turned on in the B&W tool, colour sliders adjusted in that tool to taste, a bit of a curve for contrast, then use the highlights and shadows wheels on the colour balance tool.
Ian0 -
I believe that it's meant to work this way. I used the tool in V10 to lighten and/or darken selective color in the shadows, mid-tones, and highlights in B&W images, and it did that without adding and color. In v11 beta, all my B&W images that had that correction applied acquired a tint (with the V11 engine), so I submitted a bug report. It was never answered and clearly wasn't fixed, so my guess is that it's intended behavior.
Yet another reason not to blindly upgrade the engine on all images...0 -
Yep, confirmed by support as an intended feature.
A little change in my B&W workflow from now on.
Oh, and I always(!) use cloned variants when upgrading the engine.
Regards,
Hans0 -
HansB wrote:
Yep, confirmed by support as an intended feature.
A little change in my B&W workflow from now on.
Oh, and I always(!) use cloned variants when upgrading the engine.
Regards,
Hans
Me too.
That said, using sessions and so long as the older version of CO is still installed and in a runnable state (taking into account OS changes, drivers and so on) in theory it should work so long as you still have the relevant Settings folder for the version in place and populated with the work done at the time. And you create a new session for the new version.
But to compare side by side within C1 without processing to Output the variant option is a clear winner.
Grant0
投稿コメントは受け付けていません。
コメント
8件のコメント