In his latest quick tutorial, Gleb Alexandrov looks at color management in Blender.
In this tutorial we'll take a look at Color Management in Blender. Testing the 'looks' of the image is fun using film simulation, RGB curves and other processing.
You're blocking ads, which pay for BlenderNation. Read about other ways to support us.
About the Author
Bart Veldhuizen
I have a LONG history with Blender - I wrote some of the earliest Blender tutorials, worked for Not a Number and helped run the crowdfunding campaign that open sourced Blender (the first one on the internet!). I founded BlenderNation in 2006 and have been editing it every single day since then ;-) I also run the Blender Artists forum and I'm Head of Community at Sketchfab.
13 Comments
Smooth explanation
у мну тормозит это меню, очень.
So I've always been curious, what is the advantage of using the color management panel vs doing the same in the compositor?
Time
Have more difference beyond "time"
With node compositor is possible apply several "color management" and mix differents look on the same image, apply differents effects in diferents areas of image and apply this effects in photo or videos too, and not only the image renderized (or could, if "filme response" still existed, but this was removed 2.70, I do not know the reason, but I would love if "filme respose" in node editor can be back in 2.71 is very very usefull and differents situations that "color management" can't do)
It actually happened during the SVN -> GIT migration... I emailed campbell about it and he mentioned that he discussed it with brecht and they both agreed that it was duplicate functionality...Slightly disappointing...
That being said you can still use (well last time i checked) the same plugin from before, you just need to copy and paste it from the scripts folder
Great explanation, until now I had never seen that part of Blender :O......
i like this tutorial.
thnx
For everyone reading, this is not what you want to do with the Color Management option...
CM defines controls on how to read input imagery, not how to transform imagery to achieve a desired look.
Well, yeah, Color Management in general is more about ensuring that the color quality of an image, when viewed across several image-displaying devices, all look the same.
Though still, there's no rule saying one can't use the Color Management options to achieve image-editing look development.
If anything, I would think Blender's implementation might have such an implied duality in mind. They're primarily for Color Management as any other image-editing application would use, but are flexible enough to use for some Look Development.
While it is true you can use a color management pipeline to create
looks, this video implies that it's use is primarily for that giving
users the wrong idea of how to use color management in any application.
This is very very dangerous if you're working in a team where every
render can potentially destroy an image.
It's ok to use it like Gleb Alexandrov uses it but as long as you know why that system is there for in the first place.
I don't know a lot about blender's compositor but does it work in linear light RGB internally or does it use R'G'B' ?
Also it isn't really clear to me where the Render option in the Color Management property list is applied in the pipeline. Is it used just before any image gets displayed on your screen? And it also seems weird that you can adjust the RRT. The RRT is meant to be fixed, non-adjustable. You output through the RRT to any other output medium and thus makes it default. So what does the option Default mean then?
Don't get me wrong. I love the fact that Blender incorporated OpenColorIO into the software but it's still a bit unclear how it fits in the workflow.
internally, blenders compositor works in linear light rgb at 32bit float.