toggle quoted messageShow quoted text
In our case, it's not embedded in the meta data of the filename but tied more generally to either the shot/sequence/show...we then modify the source_setup (as you had suspected) based on the filetype.
On Fri, Jun 22, 2012 at 2:43 PM, Jim Hourihan <jimho...@...>
Hi all, I'm looking into full OCIO integration into an upcoming version of rv. I was wondering if people could describe some of their workflows and/or how they might want to use OCIO in rv ideally.
* Specifically for facilities that use OCIO with nuke or other software, how is file colorspace communicated to the application? Are you using sony's method of incorporating that meta data into the file name? Right now its looking like rv's source_setup would need to handle this but I'm probably missing something.
* Beyond file data linearization and display correction what would the priority be of using OCIO for e.g. multiple looks, per-shot CDL, changing the context, etc.
I also have a few questions for developers:
* On the GPU path how is a prelut (aka shaper lut) generated and used? In the ociodisplay example's main it looks like there was an intention to have one but the example doesn't use it.
* Is the GPU path fully functional compared to the CPU path?
-- JORDAN SOLES
Chief Technology Officer | Producer
Office: 514 397 9999 x 400
514 699 0414