There is a problem with color space conversion in compositor #71408

Closed
opened 2019-11-07 16:13:59 +01:00 by maylog · 8 comments

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.12

Blender Version
Broken: version: 2.82 (sub 1), branch: master, commit date: 2019-11-03 23:35, hash: e45cfb574e
Worked:色彩空间算法问题.blend

Short description of error
In the compositor, the SRGB image is converted to a linear color space after passing the lnvert node, and cannot be restored to the original SRGB state after conversion using the gamma node. This will generate a non-user-required error when processing the inverted Color image using the compositor. It is recommended to add the corresponding node of the color space conversion.

Exact steps for others to reproduce the error
ssadas.jpg

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.12 **Blender Version** Broken: version: 2.82 (sub 1), branch: master, commit date: 2019-11-03 23:35, hash: `e45cfb574e` Worked:[色彩空间算法问题.blend](https://archive.blender.org/developer/F7975740/色彩空间算法问题.blend) **Short description of error** In the compositor, the SRGB image is converted to a linear color space after passing the lnvert node, and cannot be restored to the original SRGB state after conversion using the gamma node. This will generate a non-user-required error when processing the inverted Color image using the compositor. It is recommended to add the corresponding node of the color space conversion. **Exact steps for others to reproduce the error** ![ssadas.jpg](https://archive.blender.org/developer/F7975744/ssadas.jpg)
Author

Added subscriber: @maylog

Added subscriber: @maylog

Added subscriber: @frameshift

Added subscriber: @frameshift

I think your expectations are incorrect. Your sRGB image is always linearised, the second you indicated that its file encoding is indeed sRGB. Behind the scenes of the compositor, this removes the sRGB OETF and turns the image into a display linear sRGB buffer.

In the top part of your split viewer, you invert that linear buffer, apply a 2.2 gamma to it, and then display it through (I'm assuming) a Filmic view transform.
In the bottom part of the viewer, you simply flip the linear buffer, and your view is again transformed by (I'm assuming) Filmic.

In short, there's more happening than you think. What you're doing in the top part is essentially a double transform, especially if your view is set to Standard rather than Filmic.
It's also important to note that you should always composite in a linear space, which the Blender compositor does.

It is recommended to add the corresponding node of the color space conversion.

This would indeed be a useful node, but not here. Input Image nodes do this conversion automatically.

I think your expectations are incorrect. Your sRGB image is *always* linearised, the second you indicated that its file encoding is indeed sRGB. Behind the scenes of the compositor, this removes the sRGB OETF and turns the image into a *display linear sRGB* buffer. In the top part of your split viewer, you invert that linear buffer, apply a 2.2 gamma to it, and then display it through (I'm assuming) a Filmic view transform. In the bottom part of the viewer, you simply flip the linear buffer, and your view is again transformed by (I'm assuming) Filmic. In short, there's more happening than you think. What you're doing in the top part is essentially a double transform, especially if your view is set to Standard rather than Filmic. It's also important to note that you should always composite in a linear space, which the Blender compositor does. > It is recommended to add the corresponding node of the color space conversion. This would indeed be a useful node, but not here. Input Image nodes do this conversion automatically.

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2019-11-07 16:37:30 +01:00

The compositor works in scene linear color space by design, and the Invert node does not change the color space.

If you want to do a perceptually linear color inversion, you can put a Gamma node before and after the Invert node to convert to sRGB and back.

The compositor works in scene linear color space by design, and the Invert node does not change the color space. If you want to do a perceptually linear color inversion, you can put a Gamma node before and after the Invert node to convert to sRGB and back.
Author

So, ask a question, what can I do to get the same SRGB inversion color as in Photoshop??

So, ask a question, what can I do to get the same SRGB inversion color as in Photoshop??

In #71408#807777, @maylog wrote:
So, ask a question, what can I do to get the same SRGB inversion color as in Photoshop??

Set your Blender view transform to Standard, and use only an invert node.
Do know that Photoshop strictly works in a display-referred space, while Blender works in a scene-linear space + view transform. Only that 'Standard' view transform is going to yield results comparable to your sRGB input.

> In #71408#807777, @maylog wrote: > So, ask a question, what can I do to get the same SRGB inversion color as in Photoshop?? Set your Blender view transform to Standard, and use only an invert node. Do know that Photoshop strictly works in a display-referred space, while Blender works in a scene-linear space + view transform. Only that 'Standard' view transform is going to yield results comparable to your sRGB input.
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
3 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#71408
No description provided.