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 /

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: http://groups.google.com/group/ocs-dev/su

<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 application c

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 bei

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

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 wan

On May 5, 2:30 pm, brunobignose <bruno.j....@...> wrote: > What is you internal representation? > - we know you want to present this as a black box but we would like > to know some technical details M

Ah, there is a 10MB per-file limit to uploads on google groups. Let me whip up an alternative... On May 24, 9:15 am, Bruno Nicoletti <bruno.j....@...> wrote: > 80 Megs or so of data seems to have conf

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.

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 group.

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. (

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 us

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, all of

I'm fleshing out support for additional lut formats, and have a question on 3d. There's a 1D shaper lut at the top of the file, and the 3D component further on, all of which use integer types. Simple

Regarding 3dl -- The lore I've been fed is that Mitch Bogdonowicz formerly of Kodak wrote (invented? burped?) the 3dl "specification" when he was at Kodak as a quick and dirty solution of 3D LUT ASCII

Cool, thanks for the info. So it sounds like when we want to write a .3dl exporter, we'll need to specify which flavor of .3dl to write. However, on the import side it still sounds like we'll be able

Yes. Agreed. The importer can use the fuzzy greater-than-1/2-max heuristic for guessing the bit-depths of A and B. ...and be correct most of the time. -blake

Folks, We've made a lot of progress on Open Color Space, and decided to post our first cut. This is first code drop of many; we will try to post the trunk either every week or every 2 weeks. (And soon

This one will actually build on other people's machines... please see INSTALL file for instructions on how to build the Nuke example (posted here as well): Make a build directory, cd into it: > mkdir