← All ideas

Port the Color Space node from the compositor to the shader editor?

my colleagues and I are trying to switch to ACES, we are however experiencing difficulties since we make a lot of use of procedural materials and nodes that do not start from imported textures. one node that I think could help us would be the "Convert Colorspace" node. 28137916-13B9-4DD9-9439-55DDBCE32E06.png

if it were available in the shader editor it would give us more flexibility in using some nodes, such as sky texture an RGB node

100%

Development Status: Open

Upvote 4 Downvote 0
massimiliano.granello
9 Oct 2022

2 Comments

illasera1

A.)Tell your people not to use ACES unless you are only using it as a data transfer method and not to actually display stuff with it.

B.)To your suggestion, That is a massive issue in blender that developers are aware of , and requires a whole re-writes for it, Something they don't have a plan or schedule on how to tackle such a task.

(Read in devtalk.blender on all the inner hacking infesting colorspace handling, even the color picker doesn't work correctly for non sRGB color-space)

References pointing to the problems related to your suggestion : devtalk.blender.org/t/blender-support-for-aces-academy-color-encoding-system/13972

devtalk.blender.org/t/filmic-and-aces/22408

There is a lot of reading, sorry, BUT! you might learn something from that; that could be useful in the industry, some big authorities on the subject of colorspaces and post production are talking there.

massimiliano.granello Author

Thank you for your comment and the links. Yes our target is to get a streamline workflow between blender and after effects. Unfortunately the default filmic OCIO Config file of blender doesn’t work really well with the only plugin that allows after to handle OCIO. fnordware.blogspot.com/2012/05/opencolorio-for-after-effects.html I think it has to do with the fact that this plug in doesn’t handle OCIO V2 very well. I’m also aware of the main issue that holds back blender from getting a more flexible management of OCIO config files Taking all this into consideration I think this node could be a handy temporary solution to a whole set of annoyances caused by this less than ideal system