1. Ocio-Dev
  2. Topics

Accommodating per-shot grades

Blake Sloan <bsl...@...>
 

Hi OCIO developers,

First, apologies if this is not strictly a dev question.

I have a real-world case for per-shot grade LUTs in an application
that uses OCIO color management (Katana).

Reading over some of the dev mail about per-shot grades, it isn't
clear to me whether OCIO (from within Katana) provides the ability to
apply a per shot grade *and* a show-specific film-emulation LUT
(without copying a bunch of duplicate files to every shot directory).

From mail threads, I gather OCIO has a Context object that can contain
the sequence and shot info. Is this Context available from within a
show-wide config file? Or perhaps there's a way to access environment
variables from within the config file?


I'd prefer not to change the show's OCIO env var to point to a shot
path, as that would require copying the show's film-emulation
transform to multiple locations.

Thanks in advance,

-blake

--
as seen on T.V.

Jeremy Selan <jeremy...@...>
 

Yup, it can definitely do this. (apply a per-shot grade without copying around files unnecessarily).  I'll try to write up a little document on how to handle per-shot grades, and post it to the list (and website) by monday. Will this work?

-- Jeremy

On Fri, Dec 16, 2011 at 2:10 PM, Blake Sloan <bsl...@...> wrote:
Hi OCIO developers,

First, apologies if this is not strictly a dev question.

I have a real-world case for per-shot grade LUTs in an application
that uses OCIO color management (Katana).

Reading over some of the dev mail about per-shot grades, it isn't
clear to me whether OCIO (from within Katana) provides the ability to
apply a per shot grade *and* a show-specific film-emulation LUT
(without copying a bunch of duplicate files to every shot directory).

From mail threads, I gather OCIO has a Context object that can contain
the sequence and shot info. Is this Context available from within a
show-wide config file? Or perhaps there's a way to access environment
variables from within the config file?


I'd prefer not to change the show's OCIO env var to point to a shot
path, as that would require copying the show's film-emulation
transform to multiple locations.

Thanks in advance,

-blake

--
as seen on T.V.

Malcolm Humphreys <malcolmh...@...>
 

@blake is this documentation unclear?


If it is it would be great to know so we can improve on it.

It shows the usage of env vars inside of ocio profiles
eg.
- !<FileTransform> {src: ${SHOT}.cc}
- !<FileTransform> {src: grades.ccc, cccid: ${SHOT}}
.malcolm


On 16/12/2011, at 11:58 PM, Jeremy Selan wrote:

Yup, it can definitely do this. (apply a per-shot grade without copying around files unnecessarily).  I'll try to write up a little document on how to handle per-shot grades, and post it to the list (and website) by monday. Will this work?

-- Jeremy

On Fri, Dec 16, 2011 at 2:10 PM, Blake Sloan <bsl...@...> wrote:
Hi OCIO developers,

First, apologies if this is not strictly a dev question.

I have a real-world case for per-shot grade LUTs in an application
that uses OCIO color management (Katana).

Reading over some of the dev mail about per-shot grades, it isn't
clear to me whether OCIO (from within Katana) provides the ability to
apply a per shot grade *and* a show-specific film-emulation LUT
(without copying a bunch of duplicate files to every shot directory).

From mail threads, I gather OCIO has a Context object that can contain
the sequence and shot info. Is this Context available from within a
show-wide config file? Or perhaps there's a way to access environment
variables from within the config file?


I'd prefer not to change the show's OCIO env var to point to a shot
path, as that would require copying the show's film-emulation
transform to multiple locations.

Thanks in advance,

-blake

--
as seen on T.V.


Jeremy Selan <jeremy...@...>
 

Oh yah, I forgot about that page!

The only other thing I'll add to that is an example using multiple dirs in the lut search paths (combined with envvars). This is how we do per-shot luts at SPI, and it lets you handle fallback cases (not have a special lut for a shot/sequence) gracefully.   Oh - and we should also how how to use looks in the display monitor options, and how to do a context override in nuke.

-- Jeremy


On Sat, Dec 17, 2011 at 2:00 AM, Malcolm Humphreys <malcolmh...@...> wrote:
@blake is this documentation unclear?


If it is it would be great to know so we can improve on it.

It shows the usage of env vars inside of ocio profiles
eg.
- !<FileTransform> {src: ${SHOT}.cc}
- !<FileTransform> {src: grades.ccc, cccid: ${SHOT}}
.malcolm

On 16/12/2011, at 11:58 PM, Jeremy Selan wrote:

Yup, it can definitely do this. (apply a per-shot grade without copying around files unnecessarily).  I'll try to write up a little document on how to handle per-shot grades, and post it to the list (and website) by monday. Will this work?

-- Jeremy

On Fri, Dec 16, 2011 at 2:10 PM, Blake Sloan <bsl...@...> wrote:
Hi OCIO developers,

First, apologies if this is not strictly a dev question.

I have a real-world case for per-shot grade LUTs in an application
that uses OCIO color management (Katana).

Reading over some of the dev mail about per-shot grades, it isn't
clear to me whether OCIO (from within Katana) provides the ability to
apply a per shot grade *and* a show-specific film-emulation LUT
(without copying a bunch of duplicate files to every shot directory).

From mail threads, I gather OCIO has a Context object that can contain
the sequence and shot info. Is this Context available from within a
show-wide config file? Or perhaps there's a way to access environment
variables from within the config file?


I'd prefer not to change the show's OCIO env var to point to a shot
path, as that would require copying the show's film-emulation
transform to multiple locations.

Thanks in advance,

-blake

--
as seen on T.V.



Brendan Bolles <bre...@...>
 

On Dec 17, 2011, at 2:00 AM, Malcolm Humphreys wrote:

http://opencolorio.org/userguide/contexts.html#per-shot-grades

If it is it would be great to know so we can improve on it.

I see that the the machinery for handing per-shot LUTs (aside from environment variable hacks) seems to be there in the form of "Looks", with functions in OCIO::Config for getting a list of looks and OCIO::DisplayTransform has functions using them. Is there a sample configuration available with looks set up?


Brendan

Paul Miller <pa...@...>
 

On 12/19/2011 1:22 PM, Brendan Bolles wrote:
On Dec 17, 2011, at 2:00 AM, Malcolm Humphreys wrote:

http://opencolorio.org/userguide/contexts.html#per-shot-grades

If it is it would be great to know so we can improve on it.

I see that the the machinery for handing per-shot LUTs (aside from environment variable hacks) seems to be there in the form of "Looks", with functions in OCIO::Config for getting a list of looks and OCIO::DisplayTransform has functions using them. Is there a sample configuration available with looks set up?
I used the ociodisplay example code and the Sony vfx sample config to get my looks/views stuff hooked up.

1 - 6 of 6