Color Management View Transforms no longer reflected in the Compositor Backdrop #86219

New Issue

Harley Denham · 2021-03-03T02:03:03+01:00

Harley Denham commented

2021-03-03 02:03:03 +01:00

System Information
Operating system: Windows 10 20H2
Graphics card: Nvidia RTX 2080 Ti

Blender Version
Broken: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: 02948a2cab, type: Release
Worked: 2.91.X

Short description of error
Color Management View Transforms / Look settings are not reflected in the compositor backdrop, preventing working visualisation of output.

Exact steps for others to reproduce the error
Render any image.
Display "Render Result" in Image Editor alongside Compositor with the Backdrop enabled.
Apply/change the View Transform + Look in the Color Management panel to see discrepancy.

**System Information** Operating system: Windows 10 20H2 Graphics card: Nvidia RTX 2080 Ti **Blender Version** Broken: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: 02948a2cab44, type: Release Worked: 2.91.X **Short description of error** Color Management View Transforms / Look settings are not reflected in the compositor backdrop, preventing working visualisation of output. **Exact steps for others to reproduce the error** Render any image. Display "Render Result" in Image Editor alongside Compositor with the Backdrop enabled. Apply/change the View Transform + Look in the Color Management panel to see discrepancy.

Harley Denham commented

2021-03-03 02:03:03 +01:00

Added subscriber: @qxoko

Sebastian Koenig commented

2021-03-03 12:17:58 +01:00

Added subscriber: @sebastian_k

Sebastian Koenig commented

2021-03-03 12:17:58 +01:00

I cannot confirm that, it works here, both in 2.93 and in 2.92. Can you post a blendfile where it happens?

Sebastian Koenig commented

2021-03-03 12:18:06 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Harley Denham commented

2021-03-03 16:33:39 +01:00

I've created a brand new file with 2.92.0-release and attached it, with a screenshot to demonstrate as well.

I've backed up and checked several scenes in a commercial project created in 2.90/2.91 and all scenes are affected in 2.92 as well. At least for me, it is not a one-off issue.

T86219_color_bug.blend

I've created a brand new file with 2.92.0-release and attached it, with a screenshot to demonstrate as well. I've backed up and checked several scenes in a commercial project created in 2.90/2.91 and all scenes are affected in 2.92 as well. At least for me, it is not a one-off issue. ![T86219_color_bug.png](https://archive.blender.org/developer/F9862740/T86219_color_bug.png) [T86219_color_bug.blend](https://archive.blender.org/developer/F9862737/T86219_color_bug.blend)

Sebastian Koenig commented

2021-03-03 20:44:17 +01:00

Added subscriber: @Jeroen-Bakker

Sebastian Koenig commented

2021-03-03 20:44:17 +01:00

This is interesting. I can indeed reproduce that behavior with your file. However, if you go to a different workspace and create a compositor there, the backdrop reacts to color management just fine. Your compositing workspace seems to be broken somehow, but I have no idea how. Maybe @Jeroen-Bakker has an idea?

Harley Denham commented

2021-03-03 23:14:10 +01:00

Huh.

(I actually did attempt it in a reset-to-default copy of 2.92 and it still occurred, but I now realise I was only trying existing files with that workspace inside).

Also It seems for my installation, loading a new Compositor preset from the Add Workspace menu (see screenshot) carries this behaviour for me — it's not just the original Compositor that's open by default, the actual presets embedded in the startup file are "corrupted" too.
If I just go to any other workspace type and manually switch a zone to a Compositor as Sebastian suggests, those display correctly.

I've attached my startup file in case it helps track down the issue. I want to say it was created in 2.81 or 2.82 when I made the leap from 2.7x and has been carried over updates ever since. I do also wonder if a file created fresh in 2.8x and immediately re-opened in 2.92 might exhibit this behaviour?

T86219_startup.blend

Huh. (I actually did attempt it in a reset-to-default copy of 2.92 and it still occurred, but I now realise I was only trying existing files with that workspace inside). Also It seems for my installation, loading a new Compositor preset from the Add Workspace menu (see screenshot) carries this behaviour for me — it's not just the original Compositor that's open by default, the actual presets embedded in the startup file are "corrupted" too. If I just go to any other workspace type and manually switch a zone to a Compositor as Sebastian suggests, those display correctly. I've attached my startup file in case it helps track down the issue. I want to say it was created in 2.81 or 2.82 when I made the leap from 2.7x and has been carried over updates ever since. I do also wonder if a file created fresh in 2.8x and immediately re-opened in 2.92 might exhibit this behaviour? ![image.png](https://archive.blender.org/developer/F9863525/image.png) [T86219_startup.blend](https://archive.blender.org/developer/F9863553/T86219_startup.blend)

Harley Denham commented

2021-03-17 16:03:33 +01:00

Update for @sebastian_k — It seemed to still be occurring randomly in scenes created with my new startup file, but I've found the culprit.

Auto-Offset in the View menu.

I have it disabled by default in my old startup file and I forgot to do that with the new one. The colour profile is dropped instantly as the checkbox is changed and comes back if re-enabled. In my in my original startup file, Auto-Offset was always disabled in the default Compositor. I've also confirmed the behaviour it in the production scenes I was working on when I originally logged the bug, as well as some previously completed shots I have not opened with 2.92 until now.

Update for @sebastian_k — It seemed to still be occurring randomly in scenes created with my new startup file, but I've found the culprit. **Auto-Offset in the View menu.** I have it disabled by default in my old startup file and I forgot to do that with the new one. The colour profile is dropped instantly as the checkbox is changed and comes back if re-enabled. In my in my original startup file, Auto-Offset was always disabled in the default Compositor. I've also confirmed the behaviour it in the production scenes I was working on when I originally logged the bug, as well as some previously completed shots I have not opened with 2.92 until now.

Philipp Oeser commented

2021-03-17 16:24:16 +01:00

Changed status from 'Needs User Info' to: 'Needs Triage'