I'll be posting (anonymously) the previous comments on ver 0.1 so that new members will be able to easily track the comment history. -- Subscription settings:

... from an anonymous commenter, some excellent questions. (I'll be adding these to the FAQ). This system is complementary to Truelight / Cinespace. Although Truelight comes with a bunch of

Color Folks, Sony Imageworks is planning to open-source our color pipeline, and we'd like your feedback. Our hope is not to re-invent the wheel, but to help facilitate color interchange between vfx

---- Commenter 1 This all looks really cool. I don't know what your budget for getting this ready for a wider world is, but you may want to consider removing the STL from the code. Some people are

---- Commenter You mention rgb and rgba. How is alpha handled? Is there a policy? ---- Jeremy Current policy is that alpha is always passed unchanged. For applications which wish to be more

<Jeremy: this has been edited to remove 'personal' comments> Commenter: Answering your questions... * Is this project conceptually useful to your organization? Yes, we would love a cross

These are all excellent suggestions, thanks! We hope to address all of these major issues in the next version of the header (0.5.1). -- Subscription settings:

This addresses almost all major comments (I hope) with the prior header. The one (big) missing chunk is that it does not expose function for dynamically manipulating color configurations. (example

Is the ColorSpace "role" just a database sorting tag, or does the "role" impact the internal process of conversion? RGB

Random questions: What is the role of the 'direction' parameter to ApplyColorSpaceTransform? Why would the user not just reverse the InputColorSpace and OutputColorSpace parameter ordering to get

ApplyColorSpaceTransform does not use the roles. GetHWFilmlook does. For example, if the fStopExposure arg is specified, the exposure is adjusted internally in the SCENE_LINEAR space (as specified

Yah, the simple version is what we've had for 6 years. I added the direction parameter for completeness yesterday. On second thought, I'll drop it. ;) I'm just super used to working in CPython land

Addresses Larry + Rods comments (mostly). Coming soon, a mutable ColorConfig + better GLSL version-ness. (And after that, a library that builds) -- Subscription settings:

Hi All, this is a collection of questions that we came up with at The Foundry after sitting down with various product manager and techy types.... What is you internal representation? - we know you

wrote: My discussion of the internals as a 'black' box are meant to be from the perspective of a simple client application, not from folks interested in color management or to 'authoring' apps.

Oh, and one thing to keep in mind; the current version of this library already works great in Nuke. :) We've exposed 3 new nodes: ColorSpaceConvert / LogConvert / DisplayTransform. The 1st two are

Hi Jeremy, thanks for the reply. A few more questions.... These reference various .spiXXX files, are you going to open up the format of those files? Little CMS was the one mumbled about here. Not

Sorry for the delay! Progress on the library is going well, I hope to have a code drop ready in the next few weeks. To answer your latest few questions... Yes and no. We're going to open up the

Hello! I'm at the stage where I would like to get a survey of lut file formats (1d, 3d, matrix, etc) that folks actually use in the wild. If you commonly use a lut format at your facility, or define

Jeremy, There are two LUT formats I know of that are used in game development. One is a 2D image format (any lossless image format will do - we've used BMP, TGA and PNG) with a 2D representation of