Error loading lut using environment variables


Simon Björk <bjork...@...>
 

Thanks Sean! I'll have a look at this and do some tests. Seems like it could do the trick :).



-------------------------------
Simon Björk
Compositor/TD

+46 (0)70-2859503

2017-03-16 18:38 GMT+01:00 Sean Cooper <se...@...>:


On Tue, Mar 14, 2017 at 8:33 AM, Sean Cooper <se...@...> wrote:
Per-shot colorspaces are generally handeled by the OCIOLooks not OCIOColorspace. Additionally, with Looks you are able to use conditionals (atleast on unix, Id have to try it on other systems) 

So if you had a Look called "perShot" with a file transform pointing to /path/to/$SHOW/$SHOT.lut  you can then apply the Look using a conditional like "perShot|" where if perShot fails it will do the pipe/OR and instead do nothing. You can even do more complicated combinations like "+look1|+look1+look2|". 

This is pretty specific to Looks that modify the view, but that's usually how shot-specific transforms are used. You might be able to use this for other purposes if that isnt your use case. 



On Mar 14, 2017 12:33 AM, "Simon Björk" <bjork...@...> wrote:
Thanks Kevin, seems like it would work.

However (if I'm not misunderstanding) this would require all shot luts to be named the same and also be in separate directories? In my case I would prefer to have the luts named shot01.cube, shot02.cube etc and store them in the same directory (i.e /show/luts/shot_luts/).

I guess I can just create a dummy lut if it doesn't exist as a pre launch process.

/Simon



-------------------------------
Simon Björk
Compositor/TD


2017-03-13 10:35 GMT+01:00 Kevin Wheatley <kevin.j....@...>:
Create a null lut is about the best you can do, combined with the search path you could do

search_path: path/to/${SHOT}:path/to/null

then use a name like "mylut.cube" if you squint hard you can make this do sequence level as well as show wide level, by suitable nesting of directories in search paths.

Kevin


--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Sean Cooper <se...@...>
 

On Tue, Mar 14, 2017 at 8:33 AM, Sean Cooper <se...@...> wrote:
Per-shot colorspaces are generally handeled by the OCIOLooks not OCIOColorspace. Additionally, with Looks you are able to use conditionals (atleast on unix, Id have to try it on other systems) 

So if you had a Look called "perShot" with a file transform pointing to /path/to/$SHOW/$SHOT.lut  you can then apply the Look using a conditional like "perShot|" where if perShot fails it will do the pipe/OR and instead do nothing. You can even do more complicated combinations like "+look1|+look1+look2|". 

This is pretty specific to Looks that modify the view, but that's usually how shot-specific transforms are used. You might be able to use this for other purposes if that isnt your use case. 



On Mar 14, 2017 12:33 AM, "Simon Björk" <bjork...@...> wrote:
Thanks Kevin, seems like it would work.

However (if I'm not misunderstanding) this would require all shot luts to be named the same and also be in separate directories? In my case I would prefer to have the luts named shot01.cube, shot02.cube etc and store them in the same directory (i.e /show/luts/shot_luts/).

I guess I can just create a dummy lut if it doesn't exist as a pre launch process.

/Simon



-------------------------------
Simon Björk
Compositor/TD


2017-03-13 10:35 GMT+01:00 Kevin Wheatley <kevin.j....@...>:
Create a null lut is about the best you can do, combined with the search path you could do

search_path: path/to/${SHOT}:path/to/null

then use a name like "mylut.cube" if you squint hard you can make this do sequence level as well as show wide level, by suitable nesting of directories in search paths.

Kevin


--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



Sean Cooper <se...@...>
 

Per-shot colorspaces are generally handeled by the OCIOLooks not OCIOColorspace. Additionally, with Looks you are able to use conditionals (atleast on unix, Id have to try it on other systems) 

So if you had a Look called "perShot" with a file transform pointing to /path/to/$SHOW/$SHOT.lut  you can then apply the Look using a conditional like "perShot|" where if perShot fails it will do the pipe/OR and instead do nothing. You can even do more complicated combinations like "+look1|+look1+look2|". 

This is pretty specific to Looks that modify the view, but that's usually how shot-specific transforms are used. You might be able to use this for other purposes if that isnt your use case. 



On Mar 14, 2017 12:33 AM, "Simon Björk" <bjork...@...> wrote:
Thanks Kevin, seems like it would work.

However (if I'm not misunderstanding) this would require all shot luts to be named the same and also be in separate directories? In my case I would prefer to have the luts named shot01.cube, shot02.cube etc and store them in the same directory (i.e /show/luts/shot_luts/).

I guess I can just create a dummy lut if it doesn't exist as a pre launch process.

/Simon



-------------------------------
Simon Björk
Compositor/TD


2017-03-13 10:35 GMT+01:00 Kevin Wheatley <kevin.j....@...>:
Create a null lut is about the best you can do, combined with the search path you could do

search_path: path/to/${SHOT}:path/to/null

then use a name like "mylut.cube" if you squint hard you can make this do sequence level as well as show wide level, by suitable nesting of directories in search paths.

Kevin


--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Simon Björk <bjork...@...>
 

Thanks Kevin, seems like it would work.

However (if I'm not misunderstanding) this would require all shot luts to be named the same and also be in separate directories? In my case I would prefer to have the luts named shot01.cube, shot02.cube etc and store them in the same directory (i.e /show/luts/shot_luts/).

I guess I can just create a dummy lut if it doesn't exist as a pre launch process.

/Simon



-------------------------------
Simon Björk
Compositor/TD

+46 (0)70-2859503

2017-03-13 10:35 GMT+01:00 Kevin Wheatley <kevin.j....@...>:

Create a null lut is about the best you can do, combined with the search path you could do

search_path: path/to/${SHOT}:path/to/null

then use a name like "mylut.cube" if you squint hard you can make this do sequence level as well as show wide level, by suitable nesting of directories in search paths.

Kevin


--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Kevin Wheatley <kevin.j....@...>
 

Create a null lut is about the best you can do, combined with the search path you could do

search_path: path/to/${SHOT}:path/to/null

then use a name like "mylut.cube" if you squint hard you can make this do sequence level as well as show wide level, by suitable nesting of directories in search paths.

Kevin



Simon Björk <bjork...@...>
 

I'm trying to add a colorspace that is using a $SHOT env. It all works as expected if the shot lut exist. If the shot lut does not exist an error is thrown:

The specified file reference  '${SHOT}.cube' could not be located. The following attempts were made: D:\ocio_test\luts\sh001.cube

If I start Nuke i get an error saying it can't load the config file.

Is there anyway to get around this (without creating "dummy" luts)? Can if/else statements be used in the config somehow? It would be great if there was a way to skip the colorspace if the evaluated file doesn't exist.

/Simon



-------------------------------
Simon Björk
Compositor/TD

+46 (0)70-2859503