Cycles ignores Texture Tab Color Space setting #63572

Closed
opened 2019-04-13 14:32:52 +02:00 by Jose · 8 comments

System Information
Operating system: Windows 7 SP1, 64-bit, i7-4670K
Graphics card: NVIDIA GeForce GTX 1070

Blender Version
blender-2.80 branch

Short description of error
Cycles ignores Texture Tab Color Space setting (IDT) and burns the Display ODT into the image (tested on EXR format output)

Expected Behavior
Cycles should import the pre-transformed Texture from its [Color Space IDT ](URL = https://developer.blender.org/T63571) to Scene Working Space (scene referred space declared in OCIO configuration) and apply the Display ODT only in the Render Framebuffer (Display ODT option is also lacking in the Render Framebuffer).
Currently if you feed pre-transformed maps (at least for EXR format textures) it works as expected. Below a descriptive graph of the current chaotic behavior between 3D viewer and Cycles.

Blender non-Color Management.png

**System Information** Operating system: Windows 7 SP1, 64-bit, i7-4670K Graphics card: NVIDIA GeForce GTX 1070 **Blender Version** blender-2.80 branch **Short description of error** Cycles ignores Texture Tab Color Space setting (IDT) and burns the Display ODT into the image (tested on EXR format output) **Expected Behavior** Cycles should import the pre-transformed Texture from its [Color Space IDT ](URL = https://developer.blender.org/T63571) to Scene Working Space (scene referred space declared in OCIO configuration) and apply the Display ODT only in the Render Framebuffer (Display ODT option is also lacking in the Render Framebuffer). Currently if you feed pre-transformed maps (at least for EXR format textures) it works as expected. Below a descriptive graph of the current chaotic behavior between 3D viewer and Cycles. ![Blender non-Color Management.png](https://archive.blender.org/developer/F6939962/Blender_non-Color_Management.png)
Author

Added subscriber: @Dogway

Added subscriber: @Dogway

Closed as duplicate of #63571

Closed as duplicate of #63571

Added subscriber: @brecht

Added subscriber: @brecht

Note this bug tracker is strictly for bugs, suggestions to improve the implementation are not tracked here.

Note this bug tracker is strictly for bugs, suggestions to improve the implementation are not tracked here.

Note that non-color data image files do have a color space and should not get any color transform applied at all. That's the point of them, they're things like normal or displacement maps. So it's not clear to me why a non-color EXR should be fixed with an IDT in your graph.

Note that non-color data image files do have a color space and should not get any color transform applied at all. That's the point of them, they're things like normal or displacement maps. So it's not clear to me why a non-color EXR should be fixed with an IDT in your graph.
Author

Color Space setting that is broken. (See also #63571). So a solution is to fix it or remove it (hopefully the former). Currently the only practical implementation for OCIO is as a tonemapper which is a sad end for such a robust color framework.

non-color is a Blender-only term. The proper IDT for what you call non-color data is "Utility - RAW" in a proper OCIO workflow. This is what this ticket is about. Get rid of ambiguous color settings and rely on a proper OCIO implementation. Not saying that I'm a coder able to make it happen, but before closing both tickets it could be better if some discussion could be going on.

*In my graph there's not RAW images ("Utility - RAW" is a proxy for no-op), but a sRGB image that Cycles ignores to pre-transform from the IDT, the red note is what I think should be fixed, probably in #54659 as I found on your other comment.

Color Space setting that is broken. (See also #63571). So a solution is to fix it or remove it (hopefully the former). Currently the only practical implementation for OCIO is as a tonemapper which is a sad end for such a robust color framework. non-color is a Blender-only term. The proper IDT for what you call non-color data is "Utility - RAW" in a proper OCIO workflow. This is what this ticket is about. Get rid of ambiguous color settings and rely on a proper OCIO implementation. Not saying that I'm a coder able to make it happen, but before closing both tickets it could be better if some discussion could be going on. *In my graph there's not RAW images ("Utility - RAW" is a proxy for no-op), but a sRGB image that Cycles ignores to pre-transform from the IDT, the red note is what I think should be fixed, probably in #54659 as I found on your other comment.

Non-color is a term from the original SPI configurations. In those configurations the Raw color space has a different meaning, and it does in Blender too. This is not Blender-only, but comes from the creators of OpenColorIO.
http://opencolorio.org/configurations/spi_vfx.html

So if you report a bug you really should use the exact Blender terminology and provide .blend files, because otherwise it's going to be really confusing. I can't guess which other application's terminology you might be using.

Non-color is a term from the original SPI configurations. In those configurations the Raw color space has a different meaning, and it does in Blender too. This is not Blender-only, but comes from the creators of OpenColorIO. http://opencolorio.org/configurations/spi_vfx.html So if you report a bug you really should use the exact Blender terminology and provide .blend files, because otherwise it's going to be really confusing. I can't guess which other application's terminology you might be using.
Author

Sorry for the confusion I was using aces 1.0.3 variant terminology from last year compared to spi-vfx which is like 7 years old.
Aren't there plans to update to a more modern aces variant OCIO framework?

If this ticket complies to #54659 it can be kept closed, tomorrow I will provide blend files and instructions.

Sorry for the confusion I was using aces 1.0.3 variant terminology from last year compared to spi-vfx which is like 7 years old. Aren't there plans to update to a more modern aces variant OCIO framework? If this ticket complies to #54659 it can be kept closed, tomorrow I will provide blend files and instructions.
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
2 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#63572
No description provided.