On Tue, Oct 23, 2018, 10:41 AM Brecht Van Lommel <[email protected]> wrote:
> On Tue, Oct 23, 2018 at 7:25 PM Troy Sobotka <[email protected]> > wrote: > > Does this refer to saving a render in log color space for loading into > software that does not support OpenColorIO? I think it is using the Look > feature for something it was not designed to do, to work around > limitations. The proper solution would be to allow saving images in a > specified color space directly (Filmic Log in the current config?), without > being affected by the display device or view transform. > I don't disagree that we need a file encoding transform stack, much like a texture box has a stack of texture elements. The current implementation is unworkable. Default could simply default to the current behaviour, with an "Advanced" cascade panel that exposes the transforms. All of that said, the design of the configuration is perfectly in line with OCIO's design. The reference encoding is the Filmic Base Log, and the rest are aesthetic twists on it. This has been confirmed multiple times via OCIO folks. _It is using the Look precisely as it was designed_. The Blender implementation of colour management should mature a little, but sadly we are strained for developers. Short term, an OCIO node solves 99.95% of the issues. I'm reasonably certain that folks like Sebastian would agree it is a crucial node to mitigate the Blender shortcomings in the short term. T _______________________________________________ Bf-committers mailing list [email protected] https://lists.blender.org/mailman/listinfo/bf-committers
