Page MenuHome

Isolate File Encoding Colour Management
Open, NormalPublic


Currently, a pixel pusher with the correct view set for an Apple Display P3 Display, ends up baking in the Display P3 transform into file encodes due to the way Blender encodes the file based off of the currently selected view.

Solution is to isolate the file encoding from the other output contexts such as displays and views.


To Do

Event Timeline

Brecht Van Lommel (brecht) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.EditedDec 5 2018, 6:35 PM

This is not a bug per our bug tracker policy, nor does it have the required information:

If you want to create a design task and work on this area that's fine, but it's not clear to me what your intent is here.

Intent is that a person who saves a file using a proper transform doesn't end up with the proper file.

That's a bug, no?

Brecht Van Lommel (brecht) raised the priority of this task from Needs Information from User to Normal.EditedDec 5 2018, 6:59 PM
Brecht Van Lommel (brecht) changed Type from Bug to To Do.

No, it's a limitation of the color management implementation, more of a to do item.

The design for this is not obvious as well, which settings are shared between display and output, which OpenColorIO settings or color spaces to use.