Blender 2.80: The new changes to color profile handling are a bit of a mess
Just had a fiddle around with the current, bleeding edge version of 2.80 and they've changed how the colour space settings work for images. That little drop-down you click on an image to change it over from "Color" to "Non-Color Data" has now been switched to a lengthy list of colour spaces -- sRGB, Linear, Non-colour, etc -- and these settings are now specific to the image itself, rather than the texture node they're attached to. They've done this to apparently simplify maintaining colour consistency between Cycles and Eevee but it seems leagues more complex now and the implementation is bit... iffy, to say the least. Here are the issues I've encountered, and I encourage you to avoid the current release unless you're absolutely okay with them:
- Because they've changed where the data is stored, opening a file in the (as of right now) current version of 2.80 reverts ALL textures to sRGB, meaning all masks and normal maps go completely bananas and have to be set back to "non-color."
- If you were using a texture as both a base colour input and as a mask for something, with a separate node for each but using the same image data, you now can't set one node to colour and one to non-colour data since the setting is now image specific. Instead, you need to duplicate the image data and change the copy, which seems a bit counter-intuitive. Also, correct me if I'm wrong, but won't that use more memory?
- Whatever they've done under the hood seems to be having an odd effect on alpha channels: previously, colour information on fully transparent (or near enough) pixels wasn't discarded: if you viewed the colour output on its own, you could still see what the alpha channel would cut out of the picture. Now, with "Use Alpha" enabled, those pixels are completely black. You need to switch off the alpha channel to get them back and it's also causing an unpleasant black fringing around certain textures if you're combining multiple transparent textures together with a mix node. Even switching from "straight" to "premultiplied" alpha doesn't make the black fringing go away
This seems like a bit of a nightmare for backwards compatibility for such a small improvement.
Posted May 13, 2019, 8:21 PM UTC · edited
For a normal map you choose non-color. If your image was saved with sRGB or some other (and you know that) then you choose the appropriate one. Sounds sensible to me.
#1 definitly sucky bug.
#2 do you really need to set a node to non-color data when using the alpha channel??
#3 you're probably right
No. I mean if you need to use a texture in two different colour spaces -- say, sRGB for base colour and non-colour data so you can use it as a cheap roughness mask -- then in earlier builds you could just copy the node and change the colour space over to whatever you wanted. Now you can't, because the colour space data is part of the image data rather than the node referencing it. Instead, you have to duplicate the image and change the copy.
Non-colour isn't just for normal maps: you should be setting it for material masks too.
I'm a noob but I've never really noticed a difference. There's this one image I like using for roughness on metal ... I was about to say I never noticed a difference but I just checked and there is a difference, but it looks better as color instead of non-color.
Are color space and color profile the same thing? I'd imagine the only options for a color space should be RGB, CMYK, grayscale, indexed and then color profile would be things like Legacy RGB (gamma 1.8), Internet Standard RGB (sRGB), Apple RGB, Adobe RGB (1998), etc...
In Blender at least, yes. It seems to use them interchangeably. In general use I imagine there's more nuance, though.
As for colour versus non-colour for masks, you should be picking non-colour, otherwise Blender will gamma adjust the values. This is important, as gamma adjustment is meant to maximise the visual quality of limited colour space images, adjusting them to make the most of the visible range of tones. For instance, the human eye is more sensitive to differences in darker colours than lighter ones, so gamma adjustment gives more of the tonal range over to dark tones and clips the bright ones. Since a mask isn't actually contributing directly to base colour but instead being used mathematically to alter a property of the material you want to retain the even distribution of tones.
It's also helpful if you're looking to maintain visual consistency between Blender and game engines, like Unity, Godot, and Unreal Engine 4, as I believe all of these will not gamma adjust masks by default.
Speaking of masks, the "alpha blended pixels are black" issue causes trouble with specific types of masks. Ever heard of channel packing? It's the practice of combining several greyscale masks into one texture by putting one in each of the colour channels: one in R, one in G, and one in B. You can put an additional one in the alpha channel as well. You then just use a "split RGB" node to separate the channels. It's very popular with game engines at the moment, as it helps reduce the memory load for things like roughness and ambient occlusion maps. But here's the problem: if you've put a mask in the alpha channel then whatever is in R, G, and B will get changed to black, completely ruining your masks. Yargh.
[removed]