Color Channels are different between Materials and Color pickers #82619

Closed
opened 2020-11-11 14:43:08 +01:00 by Dailly · 12 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: AMD Radeon R5 235 ATI Technologies Inc. 4.5.13399 Core Profile Context 15.201.1151.1008

Blender Version
Broken: version: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: 3e85bb34d0
Worked: (newest version of Blender that worked as expected)

Short description of error
The Color value ouput of an Object Info node is different from the one assigned in the Color property of the Viewport Display. It seems that a math function is applied as the range is "compressed" toward the 1 extremity.

Exact steps for others to reproduce the error
Give a material to an object, whose color is indexed by the Viewport Display color. Assign 0.51 to the Viewport Display value. Fix a 0.5 threshold in a Color Ramp of the material. The object then appears with the color below the 0.5 threshold in the Color Ramp.
This is also reproduced in the 2.83 version.

ObjectInfoColorBug.blend
ObjectInfoColorBug.png
The simple attached .blend exhibits the problem, illustrated by the .png capture. It only contains a cube and a material whose color is indexed by the Viewport Display color property.

Thanks to all of you.
If my little contribution can help...

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: AMD Radeon R5 235 ATI Technologies Inc. 4.5.13399 Core Profile Context 15.201.1151.1008 **Blender Version** Broken: version: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: `3e85bb34d0` Worked: (newest version of Blender that worked as expected) **Short description of error** The Color value ouput of an `Object Info` node is different from the one assigned in the Color property of the `Viewport Display`. It seems that a math function is applied as the range is "compressed" toward the 1 extremity. **Exact steps for others to reproduce the error** Give a material to an object, whose color is indexed by the Viewport Display color. Assign 0.51 to the Viewport Display value. Fix a 0.5 threshold in a Color Ramp of the material. The object then appears with the color below the 0.5 threshold in the Color Ramp. This is also reproduced in the 2.83 version. [ObjectInfoColorBug.blend](https://archive.blender.org/developer/F9259920/ObjectInfoColorBug.blend) ![ObjectInfoColorBug.png](https://archive.blender.org/developer/F9259924/ObjectInfoColorBug.png) The simple attached .blend exhibits the problem, illustrated by the .png capture. It only contains a cube and a material whose color is indexed by the Viewport Display color property. Thanks to all of you. If my little contribution can help...
Author

Added subscriber: @PhDailly

Added subscriber: @PhDailly

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Added subscribers: @Jeroen-Bakker, @lichtwerk

Added subscribers: @Jeroen-Bakker, @lichtwerk
Member

This is PROP_COLOR_GAMMA vs PROP_COLOR.

Workaround: introduce a gamma node after the Object Info Node (with value 1/2.2)

@Jeroen-Bakker: you seem to be diving into the ColorManagement realm: opinions?

This is `PROP_COLOR_GAMMA` vs `PROP_COLOR`. Workaround: introduce a gamma node after the Object Info Node (with value 1/2.2) @Jeroen-Bakker: you seem to be diving into the ColorManagement realm: opinions?
Member

IMO this is confusing, but not a bug. Value in the color picker is in Display Space (sRGB), the value in materials are in Linear Scene Reference Space. I will mark this as a known issue as the solution needs an approved design and could lead to a large project. It impacts painting, color management, user interface, themes and many other areas.

We don't have a module for colors as it is really basic stuff but will add User Interface to the module...

IMO this is confusing, but not a bug. Value in the color picker is in Display Space (sRGB), the value in materials are in Linear Scene Reference Space. I will mark this as a known issue as the solution needs an approved design and could lead to a large project. It impacts painting, color management, user interface, themes and many other areas. We don't have a module for colors as it is really basic stuff but will add User Interface to the module...
Member

@Jeroen-Bakker: according to https://wiki.blender.org/wiki/Modules, Color management is Render & Cycles realm...

@Jeroen-Bakker: according to https://wiki.blender.org/wiki/Modules, Color management is `Render & Cycles` realm...
Jeroen Bakker changed title from Color Output value in Object Info node is not the same as Color property value in Viewport Display to Color Channels are different between Materials and Color pickers 2020-11-12 10:32:42 +01:00
Member

The behavior is documented in the manual (https://docs.blender.org/manual/en/latest/interface/controls/templates/color_picker.html#color-picker) But can understand that it isn't read or understood by users. Color management is typically a difficult subject.

For any non gamma baked colors the HSV in the color picker is in sRGB, the RGB values are in Linear Scene Reference Space and the Hex representation is in sRGB. The HSV in the material are in Linear Scene Reference Space.

The reason behind it is that the color picker is converted to a perceptual linear value (what we see) and the colors in materials to how they would act in nature/real life.

The behavior is documented in the manual (https://docs.blender.org/manual/en/latest/interface/controls/templates/color_picker.html#color-picker) But can understand that it isn't read or understood by users. Color management is typically a difficult subject. For any non gamma baked colors the HSV in the color picker is in sRGB, the RGB values are in Linear Scene Reference Space and the Hex representation is in sRGB. The HSV in the material are in Linear Scene Reference Space. The reason behind it is that the color picker is converted to a perceptual linear value (what we see) and the colors in materials to how they would act in nature/real life.
Member

Added subscriber: @pablovazquez

Added subscriber: @pablovazquez
Member

Isn't this now fixed by f193b1afb313?

Isn't this now fixed by f193b1afb313?
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Philipp Oeser self-assigned this 2020-12-22 14:25:20 +01:00
Member

In #82619#1080469, @pablovazquez wrote:
Isn't this now fixed by f193b1afb313?

Yes, this should be resolved, will close.
@PhDailly : please report back if there are still issues in a fresh 2.92 build from https://builder.blender.org/download/

> In #82619#1080469, @pablovazquez wrote: > Isn't this now fixed by f193b1afb313? Yes, this should be resolved, will close. @PhDailly : please report back if there are still issues in a fresh 2.92 build from https://builder.blender.org/download/
Author

Hi everybody,

Now that I can run 2.92 (blender-2.92.0-af316d276144-windows64.zip) on my old PC, I confirm that it works as I supposed to be expected.
Perfect !

Thank you to everyone involved in development. Great job !
PhDy

Hi everybody, Now that I can run 2.92 (blender-2.92.0-af316d276144-windows64.zip) on my old PC, I confirm that it works as I supposed to be expected. Perfect ! Thank you to everyone involved in development. Great job ! PhDy
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#82619
No description provided.