On Sun, Jun 17, 2012 at 10:20 AM, Tobias Oelgarte <[email protected]> wrote: > Are there any plans to fix the various color management issues that > exist for over a year now?
Proper color management via OCIO will alleviate many, if not all, of the issues you have reported. > Examples: > * Any TextureNode in BI delivers the managed result, even if it is > supposed to be a bump or normal map. It doesn't have an linear/color > option like cycles does. Dealt with via a defined raw data OCIO config role. > * 8bit textures/images are treated differently as floating point > textures in texture slots or inside the image editor And let's not forget the Sequencer, which has a float representation of sRGB gamma transfer. How to deal with 8 bit per channel images is up in the air. Blender core developers will need to deal with the lazy allocation system concerns. > * the image editor displays float images right at the moment, but the > values written to the image are managed, giving wrong displacement. Proper input asset colorspace management will deal with the above issue you cite. > (could also need a button to let the user decide the color space) Much of this is dependent on which LUT package and OCIO configuration is established. Granular controls for artist needs is a given in a color managed system, and between Blender's integration and the flexibility that OCIO provides, the concerns you have above should be addressable. A larger issue might be education. With respect, TJS _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
