We've now got an ftp site setup at spi for large file posting. If you want to post files > 10MB email me and I'll send you the login info.

Exactly. Clients apps will automatically have support for all lut formats. (It's about time!) To an end user, this should feel pretty automated. Apps shouldn't need ebd user options / dialogs,

Neat. So just to clarify, the big idea is that any app that uses your color library properly will, by extension, understand ALL of these luts (whichever happens to be available/used at the facility

Blake was kind enough to a google doc spreadsheet of lut formats: http://spreadsheets.google.com/ccc?key=0Avn2cZhY9jaYdF9qTHYteU1MUDYtdnFkSDJQdHpaU1E&hl=en I'll try to edit it to keep it up to date.

Thanks! I do have the houdini docs, but if you could send me known good examples luts that would be helpful as well. If the files are small (under 10 MB) just post them to this as files to this

I can send the specs for the Houdini .lut (ASCII) and .blut (bin) formats, if you need that. They're also in the HDK documentation, if you have access to that.

Ah, there is a 10MB per-file limit to uploads on google groups. Let me whip up an alternative... wrote:

80 Megs or so of data seems to have confused Google. Anyother way? b -- Bruno Nicoletti

Hi Jeremy, these are the ones we support in Nuke... .vf Nuke native vector field vfz gzip compressed .vf files .cub(e) Truelight 1D or 3D LUT .cube Iridas LUT .csp Cinespace LUT .3dl

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

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

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

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

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

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.

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

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

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

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

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