There's a flag set in the file which means "the color are in log colorspace". Of course, the goal of what I coded in Blender is to display the picture on screen, so in sRGB colorspace. The conversion from Log colorspace to sRGB colorspace is then mandatory.
With GraphicsMagick, you can override this flag to let GraphicsMagick think that the file are already in RGB colorspace. That's what they do with this command : gm display -define dpx:colorspace=rgb ref_output_image.0102.dpx About the OpenColorIO node, it seems that Jeroen Bakker has already planned to do it in his tile based compositor [1]. So I don't think it's worth losing time on that if someone is already working on it. [1] http://ocl.atmind.nl/doku.php?id=status:report_20110227&s[]=opencolorio#opencolorio 2011/5/19 Troy Sobotka <[email protected]> > I finished reviewing the thread you pointed at Julien. Great find. > > It appears that the consensus was that there is an implied transfer to a > film LUT within the file. > > The traditional -profile conversion appears to work in that instance[1]. > > Is that what is muddling the issue here? > > With respect, > TJS > > [1] http://osdir.com/ml/video.graphicsmagick.help/2007-03/msg00007.html > On May 19, 2011 9:12 AM, "Julien Enche" <[email protected]> wrote: > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
