Date   

Re: ImageBufAlgo make_texture colorspace change

Larry Gritz <l...@...>
 

On Aug 19, 2016, at 11:38 PM, er...@... wrote:

 Still, I wish there was an error or a warning telling me I'm using colorspace names that don't exist. 


There is, you just weren't checking it:


import OpenImageIO

srcBuf = ImageBuf(src_path)
colorBuf = ImageBuf()
ok = OpenImageIO.ImageBufAlgo.colorconvert(colorBuf, srcBuf, 'sRGB', 'linear')
if not ok :
    print colorBuf.geterror()
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, colorBuf, dst_path)


--
Larry Gritz
l...@...



Re: ImageBufAlgo make_texture colorspace change

er...@...
 

I don't know where the ocio config could be coming from since I don't have an OCIO environment variable set, and I couldn't find any config files. When I run oiiotool --help it shows at the bottom:
 Known color spaces: "raw" (linear)                    
 Known displays: "sRGB"* (views: "Raw"*) (* = default) 
I was able to fix the problem by going to the OCIO website and downloading the default config files they provide. Then I set the OCIO environment variable to the Nuke config file. Still, I wish there was an error or a warning telling me I'm using colorspace names that don't exist. Or a way to find out what config file is being referenced.
Thank you Larry and Deke. I couldn't have figured this out without you.


On Friday, August 19, 2016 at 10:10:06 PM UTC-7, Larry Gritz wrote:
In OIIO 1.6, if OCIO is disabled (support not compiled at build time, or no OCIO configuration file is found at runtime), all it knows how to do is convert between sRGB or Rec709 and linear.

BUT... if OCIO support is compiled in and a config is found at build time, it 100% relies on OCIO for color space conversions, so if you use color space names not recognized by your OCIO config, it doesn't transform the values. 

I suspect that this is what's happening. You have an OCIO config file somewhere? (Presumably? Or else you probably wouldn't be asking about this on ocio-dev?)

If this is correct, I believe you have four choices:

* Use color space names corresponding to color spaces in your active OCIO config.

* Switch to an OCIO config that contains the color spaces you want to transform among.

* Disable OCIO by removing any config files and/or making sure you don't have an "OCIO" environment variable.

* Switch to OIIO master branch (the in-development 1.7 of the future), which has changed the behavior so that if OCIO doesn't recognize the color space names, it will still fall back on its inherent knowledge of sRGB <-> linear conversion. (This is not uncontroversial! But I think it's the common-sense thing to do.)


On Aug 19, 2016, at 7:14 PM, er...@... wrote:

I'm using OpenImageIO-1.6.14-cp27-cp27m-win_amd64.whl which I downloaded from here: http://www.lfd.uci.edu/~gohlke/pythonlibs/ . I found it too much of a pain to build the source for Windows. This didn't come with a config.ocio file, but I saw in the documentation: "If OCIO is not enabled (or cannot find a valid configuration, OIIO will at least be able to convert among linear, sRGB, and Rec709." 

I ran the oiiotool commands Larry suggested. 
For gray.tif,I get:
Stats Min: 0.500000 0.500000 0.500000 (float)
Stats Max: 0.500000 0.500000 0.500000 (float)
Stats Avg: 0.500000 0.500000 0.500000 (float)

For gray.exr, I get:
Stats Min: 0.500000 0.500000 0.500000 (float)
Stats Max: 0.500000 0.500000 0.500000 (float)
Stats Avg: 0.500000 0.500000 0.500000 (float)

So there is something wrong, but I don't know how to fix it.

On Friday, August 19, 2016 at 9:38:13 AM UTC-7, Larry Gritz wrote:
Phrases like "looks lighter in Nuke" always make me suspicious, there are too many ways things can go wrong.

Let's start from first principles.

oiiotool -pattern fill:color=.5,.5,.5 256x256 3 -o gray.tif
oiiotool -stats gray.tif

That should report min/max/average all 0.5.

Now run your conversion script on gray.tif, and 'oiiotool -stats' the resulting exr. What is the value? It *should* be 0.214041 everywhere if the conversion happened properly. If that is the case, then the problem is about how it is read or displays in Nuke.

There was a time when OIIO would, in cases where an OCIO config found, have color conversions *only* depend on OCIO. Color names that were not installed color spaces in your OCIO configuration would be errors and no color transformation would happen. If your output exr has values 0.5, that's probably the problem -- your OCIO configuration simply has no sRGB or linear color spaces defined.

IIRC, newer OIIO actually is a little smarter, in that if an OCIO exists but doesn't know how to do the requested transformation, it will see if the conversion is one of a few that it knows how to do regardless, and sRGB <-> linear is among them. But it needs to be a relatively recent OIIO for it to do that, if OCIO doesn't define those spaces.


On Aug 18, 2016, at 5:47 PM, er...@... wrote:

Hi,
I'm using the Python bindings for OIIO to convert images into textures. I'm having an issue converting a .tif into a .exr texture. The .exr is in sRGB colorspace instead of linear. The .exr looks lighter in Nuke than the .tif. I tried to force the colorspace change, but it didn't work either. Here are two ways I tried to make the texture:

import OpenImageIO

srcBuf = ImageBuf(src_path)
config = OpenImageIO.ImageSpec()
config.attribute('maketx:incolorspace', 'sRGB')
config.attribute('maketx:outcolorspace', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, srcBuf, dst_path, config)


and 

import OpenImageIO

srcBuf = ImageBuf(src_path)
colorBuf = ImageBuf()
OpenImageIO.ImageBufAlgo.colorconvert(colorBuf, srcBuf, 'sRGB', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, colorBuf, dst_path)


I don't get any errors, but nothing changes. Am I using the wrong colorspace names? I don't know where to find them since they aren't listed in the documentation.

--
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-d...@....
For more options, visit https://groups.google.com/d/optout.

--
Larry Gritz
l....@...



--
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+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Larry Gritz
l....@...



Re: ImageBufAlgo make_texture colorspace change

Larry Gritz <l...@...>
 

In OIIO 1.6, if OCIO is disabled (support not compiled at build time, or no OCIO configuration file is found at runtime), all it knows how to do is convert between sRGB or Rec709 and linear.

BUT... if OCIO support is compiled in and a config is found at build time, it 100% relies on OCIO for color space conversions, so if you use color space names not recognized by your OCIO config, it doesn't transform the values. 

I suspect that this is what's happening. You have an OCIO config file somewhere? (Presumably? Or else you probably wouldn't be asking about this on ocio-dev?)

If this is correct, I believe you have four choices:

* Use color space names corresponding to color spaces in your active OCIO config.

* Switch to an OCIO config that contains the color spaces you want to transform among.

* Disable OCIO by removing any config files and/or making sure you don't have an "OCIO" environment variable.

* Switch to OIIO master branch (the in-development 1.7 of the future), which has changed the behavior so that if OCIO doesn't recognize the color space names, it will still fall back on its inherent knowledge of sRGB <-> linear conversion. (This is not uncontroversial! But I think it's the common-sense thing to do.)


On Aug 19, 2016, at 7:14 PM, er...@... wrote:

I'm using OpenImageIO-1.6.14-cp27-cp27m-win_amd64.whl which I downloaded from here: http://www.lfd.uci.edu/~gohlke/pythonlibs/ . I found it too much of a pain to build the source for Windows. This didn't come with a config.ocio file, but I saw in the documentation: "If OCIO is not enabled (or cannot find a valid configuration, OIIO will at least be able to convert among linear, sRGB, and Rec709." 

I ran the oiiotool commands Larry suggested. 
For gray.tif,I get:
Stats Min: 0.500000 0.500000 0.500000 (float)
Stats Max: 0.500000 0.500000 0.500000 (float)
Stats Avg: 0.500000 0.500000 0.500000 (float)

For gray.exr, I get:
Stats Min: 0.500000 0.500000 0.500000 (float)
Stats Max: 0.500000 0.500000 0.500000 (float)
Stats Avg: 0.500000 0.500000 0.500000 (float)

So there is something wrong, but I don't know how to fix it.

On Friday, August 19, 2016 at 9:38:13 AM UTC-7, Larry Gritz wrote:
Phrases like "looks lighter in Nuke" always make me suspicious, there are too many ways things can go wrong.

Let's start from first principles.

oiiotool -pattern fill:color=.5,.5,.5 256x256 3 -o gray.tif
oiiotool -stats gray.tif

That should report min/max/average all 0.5.

Now run your conversion script on gray.tif, and 'oiiotool -stats' the resulting exr. What is the value? It *should* be 0.214041 everywhere if the conversion happened properly. If that is the case, then the problem is about how it is read or displays in Nuke.

There was a time when OIIO would, in cases where an OCIO config found, have color conversions *only* depend on OCIO. Color names that were not installed color spaces in your OCIO configuration would be errors and no color transformation would happen. If your output exr has values 0.5, that's probably the problem -- your OCIO configuration simply has no sRGB or linear color spaces defined.

IIRC, newer OIIO actually is a little smarter, in that if an OCIO exists but doesn't know how to do the requested transformation, it will see if the conversion is one of a few that it knows how to do regardless, and sRGB <-> linear is among them. But it needs to be a relatively recent OIIO for it to do that, if OCIO doesn't define those spaces.


On Aug 18, 2016, at 5:47 PM, er...@... wrote:

Hi,
I'm using the Python bindings for OIIO to convert images into textures. I'm having an issue converting a .tif into a .exr texture. The .exr is in sRGB colorspace instead of linear. The .exr looks lighter in Nuke than the .tif. I tried to force the colorspace change, but it didn't work either. Here are two ways I tried to make the texture:

import OpenImageIO

srcBuf = ImageBuf(src_path)
config = OpenImageIO.ImageSpec()
config.attribute('maketx:incolorspace', 'sRGB')
config.attribute('maketx:outcolorspace', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, srcBuf, dst_path, config)


and 

import OpenImageIO

srcBuf = ImageBuf(src_path)
colorBuf = ImageBuf()
OpenImageIO.ImageBufAlgo.colorconvert(colorBuf, srcBuf, 'sRGB', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, colorBuf, dst_path)


I don't get any errors, but nothing changes. Am I using the wrong colorspace names? I don't know where to find them since they aren't listed in the documentation.

--
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+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Larry Gritz
l....@...



--
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+u...@....
For more options, visit https://groups.google.com/d/optout.

--
Larry Gritz
l...@...



Re: ImageBufAlgo make_texture colorspace change

er...@...
 

I'm using OpenImageIO-1.6.14-cp27-cp27m-win_amd64.whl which I downloaded from here: http://www.lfd.uci.edu/~gohlke/pythonlibs/ . I found it too much of a pain to build the source for Windows. This didn't come with a config.ocio file, but I saw in the documentation: "If OCIO is not enabled (or cannot find a valid configuration, OIIO will at least be able to convert among linear, sRGB, and Rec709." 

I ran the oiiotool commands Larry suggested. 
For gray.tif,I get:
Stats Min: 0.500000 0.500000 0.500000 (float)
Stats Max: 0.500000 0.500000 0.500000 (float)
Stats Avg: 0.500000 0.500000 0.500000 (float)

For gray.exr, I get:
Stats Min: 0.500000 0.500000 0.500000 (float)
Stats Max: 0.500000 0.500000 0.500000 (float)
Stats Avg: 0.500000 0.500000 0.500000 (float)

So there is something wrong, but I don't know how to fix it.


On Friday, August 19, 2016 at 9:38:13 AM UTC-7, Larry Gritz wrote:
Phrases like "looks lighter in Nuke" always make me suspicious, there are too many ways things can go wrong.

Let's start from first principles.

oiiotool -pattern fill:color=.5,.5,.5 256x256 3 -o gray.tif
oiiotool -stats gray.tif

That should report min/max/average all 0.5.

Now run your conversion script on gray.tif, and 'oiiotool -stats' the resulting exr. What is the value? It *should* be 0.214041 everywhere if the conversion happened properly. If that is the case, then the problem is about how it is read or displays in Nuke.

There was a time when OIIO would, in cases where an OCIO config found, have color conversions *only* depend on OCIO. Color names that were not installed color spaces in your OCIO configuration would be errors and no color transformation would happen. If your output exr has values 0.5, that's probably the problem -- your OCIO configuration simply has no sRGB or linear color spaces defined.

IIRC, newer OIIO actually is a little smarter, in that if an OCIO exists but doesn't know how to do the requested transformation, it will see if the conversion is one of a few that it knows how to do regardless, and sRGB <-> linear is among them. But it needs to be a relatively recent OIIO for it to do that, if OCIO doesn't define those spaces.


On Aug 18, 2016, at 5:47 PM, er...@... wrote:

Hi,
I'm using the Python bindings for OIIO to convert images into textures. I'm having an issue converting a .tif into a .exr texture. The .exr is in sRGB colorspace instead of linear. The .exr looks lighter in Nuke than the .tif. I tried to force the colorspace change, but it didn't work either. Here are two ways I tried to make the texture:

import OpenImageIO

srcBuf = ImageBuf(src_path)
config = OpenImageIO.ImageSpec()
config.attribute('maketx:incolorspace', 'sRGB')
config.attribute('maketx:outcolorspace', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, srcBuf, dst_path, config)


and 

import OpenImageIO

srcBuf = ImageBuf(src_path)
colorBuf = ImageBuf()
OpenImageIO.ImageBufAlgo.colorconvert(colorBuf, srcBuf, 'sRGB', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, colorBuf, dst_path)


I don't get any errors, but nothing changes. Am I using the wrong colorspace names? I don't know where to find them since they aren't listed in the documentation.

--
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+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Larry Gritz
l....@...



Re: ImageBufAlgo make_texture colorspace change

Larry Gritz <l...@...>
 

Phrases like "looks lighter in Nuke" always make me suspicious, there are too many ways things can go wrong.

Let's start from first principles.

oiiotool -pattern fill:color=.5,.5,.5 256x256 3 -o gray.tif
oiiotool -stats gray.tif

That should report min/max/average all 0.5.

Now run your conversion script on gray.tif, and 'oiiotool -stats' the resulting exr. What is the value? It *should* be 0.214041 everywhere if the conversion happened properly. If that is the case, then the problem is about how it is read or displays in Nuke.

There was a time when OIIO would, in cases where an OCIO config found, have color conversions *only* depend on OCIO. Color names that were not installed color spaces in your OCIO configuration would be errors and no color transformation would happen. If your output exr has values 0.5, that's probably the problem -- your OCIO configuration simply has no sRGB or linear color spaces defined.

IIRC, newer OIIO actually is a little smarter, in that if an OCIO exists but doesn't know how to do the requested transformation, it will see if the conversion is one of a few that it knows how to do regardless, and sRGB <-> linear is among them. But it needs to be a relatively recent OIIO for it to do that, if OCIO doesn't define those spaces.


On Aug 18, 2016, at 5:47 PM, er...@... wrote:

Hi,
I'm using the Python bindings for OIIO to convert images into textures. I'm having an issue converting a .tif into a .exr texture. The .exr is in sRGB colorspace instead of linear. The .exr looks lighter in Nuke than the .tif. I tried to force the colorspace change, but it didn't work either. Here are two ways I tried to make the texture:

import OpenImageIO

srcBuf = ImageBuf(src_path)
config = OpenImageIO.ImageSpec()
config.attribute('maketx:incolorspace', 'sRGB')
config.attribute('maketx:outcolorspace', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, srcBuf, dst_path, config)


and 

import OpenImageIO

srcBuf = ImageBuf(src_path)
colorBuf = ImageBuf()
OpenImageIO.ImageBufAlgo.colorconvert(colorBuf, srcBuf, 'sRGB', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, colorBuf, dst_path)


I don't get any errors, but nothing changes. Am I using the wrong colorspace names? I don't know where to find them since they aren't listed in the documentation.

--
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+u...@....
For more options, visit https://groups.google.com/d/optout.

--
Larry Gritz
l...@...



Re: ImageBufAlgo make_texture colorspace change

Larry Gritz <l...@...>
 

Also, which version of OIIO?


On Aug 18, 2016, at 7:51 PM, Deke Kincaid <dekek...@...> wrote:

It depends on the colorspaces defined in your config.ocio file set by your $OCIO environment variable.  Which profile are you using from the examples or did you roll your own?

On Thu, Aug 18, 2016 at 5:47 PM, <er...@...> wrote:
Hi,
I'm using the Python bindings for OIIO to convert images into textures. I'm having an issue converting a .tif into a .exr texture. The .exr is in sRGB colorspace instead of linear. The .exr looks lighter in Nuke than the .tif. I tried to force the colorspace change, but it didn't work either. Here are two ways I tried to make the texture:

import OpenImageIO

srcBuf = ImageBuf(src_path)
config = OpenImageIO.ImageSpec()
config.attribute('maketx:incolorspace', 'sRGB')
config.attribute('maketx:outcolorspace', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, srcBuf, dst_path, config)


and 

import OpenImageIO

srcBuf = ImageBuf(src_path)
colorBuf = ImageBuf()
OpenImageIO.ImageBufAlgo.colorconvert(colorBuf, srcBuf, 'sRGB', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, colorBuf, dst_path)


I don't get any errors, but nothing changes. Am I using the wrong colorspace names? I don't know where to find them since they aren't listed in the documentation.

--
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+u...@....
For more options, visit https://groups.google.com/d/optout.

--
Larry Gritz
l...@...



Re: ImageBufAlgo make_texture colorspace change

Deke Kincaid <dekek...@...>
 

It depends on the colorspaces defined in your config.ocio file set by your $OCIO environment variable.  Which profile are you using from the examples or did you roll your own?

On Thu, Aug 18, 2016 at 5:47 PM, <er...@...> wrote:
Hi,
I'm using the Python bindings for OIIO to convert images into textures. I'm having an issue converting a .tif into a .exr texture. The .exr is in sRGB colorspace instead of linear. The .exr looks lighter in Nuke than the .tif. I tried to force the colorspace change, but it didn't work either. Here are two ways I tried to make the texture:

import OpenImageIO

srcBuf
= ImageBuf(src_path)
config
= OpenImageIO.ImageSpec()
config
.attribute('maketx:incolorspace', 'sRGB')
config
.attribute('maketx:outcolorspace', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, srcBuf, dst_path, config)


and 

import OpenImageIO

srcBuf
= ImageBuf(src_path)
colorBuf
= ImageBuf()
OpenImageIO.ImageBufAlgo.colorconvert(colorBuf, srcBuf, 'sRGB', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, colorBuf, dst_path)


I don't get any errors, but nothing changes. Am I using the wrong colorspace names? I don't know where to find them since they aren't listed in the documentation.

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


ImageBufAlgo make_texture colorspace change

er...@...
 

Hi,
I'm using the Python bindings for OIIO to convert images into textures. I'm having an issue converting a .tif into a .exr texture. The .exr is in sRGB colorspace instead of linear. The .exr looks lighter in Nuke than the .tif. I tried to force the colorspace change, but it didn't work either. Here are two ways I tried to make the texture:

import OpenImageIO

srcBuf
= ImageBuf(src_path)
config
= OpenImageIO.ImageSpec()
config
.attribute('maketx:incolorspace', 'sRGB')
config
.attribute('maketx:outcolorspace', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, srcBuf, dst_path, config)


and 

import OpenImageIO

srcBuf
= ImageBuf(src_path)
colorBuf
= ImageBuf()
OpenImageIO.ImageBufAlgo.colorconvert(colorBuf, srcBuf, 'sRGB', 'linear')
OpenImageIO.ImageBufAlgo.make_texture(OpenImageIO.MakeTxTexture, colorBuf, dst_path)


I don't get any errors, but nothing changes. Am I using the wrong colorspace names? I don't know where to find them since they aren't listed in the documentation.


Re: 6th annual Open Source VFX Beer of a Feather

Larry Gritz <l...@...>
 

Wednesday July *27*

Sorry for the mixup.



On Jul 19, 2016, at 10:24 AM, Larry Gritz <l...@...> wrote:

6th annual Open Source VFX Beer of a Feather

For those of you attending SIGGRAPH 2016 in Anaheim, we will be once again holding an event for developers and users of VFX-specific open source projects. It's a great chance to meet the people on the other end of the mail lists!

When: Wed. July 26, 2016, 5-7pm <----- yes, a little on the early side

Where: OC Brewhouse
Hyatt Regency Orange County <----- NOT "Hyatt Place"
11999 Harbor Blvd.

How: Sponsors have charged up a tab, and we'll be able to get drinks and hors d'oeuvre until the funding pool runs out (after which you're welcome to stay and buy your own drinks). With proper food and drink in hand, relax and enjoy the company of your fellow open source developers.

Your generous sponsors:

ACES (Academy Color Encoding System)
Ahead.IO
Autodesk
DigitalFish
Double Negative
DreamWorks Animation
Industrial Light & Magic
Luma Pictures
Method Studios
Pixar Animation Studios
Sony Pictures Imageworks
Walt Disney Animation Studios
Weta Digital

Please direct questions to: lg AT imageworks DOT com

Please feel free to forward to your developers and the appropriate mail lists for other open source VFX projects you participate in.

Also, if your organization is not one of the sponsors but you'd like to be, contact LG and there's certainly time to help charge up a bigger tab (no contribution is too small).


--
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+u...@....
For more options, visit https://groups.google.com/d/optout.
--
Larry Gritz
l...@...


6th annual Open Source VFX Beer of a Feather

Larry Gritz <l...@...>
 

6th annual Open Source VFX Beer of a Feather

For those of you attending SIGGRAPH 2016 in Anaheim, we will be once again holding an event for developers and users of VFX-specific open source projects. It's a great chance to meet the people on the other end of the mail lists!

When: Wed. July 26, 2016, 5-7pm <----- yes, a little on the early side

Where: OC Brewhouse
Hyatt Regency Orange County <----- NOT "Hyatt Place"
11999 Harbor Blvd.

How: Sponsors have charged up a tab, and we'll be able to get drinks and hors d'oeuvre until the funding pool runs out (after which you're welcome to stay and buy your own drinks). With proper food and drink in hand, relax and enjoy the company of your fellow open source developers.

Your generous sponsors:

ACES (Academy Color Encoding System)
Ahead.IO
Autodesk
DigitalFish
Double Negative
DreamWorks Animation
Industrial Light & Magic
Luma Pictures
Method Studios
Pixar Animation Studios
Sony Pictures Imageworks
Walt Disney Animation Studios
Weta Digital

Please direct questions to: lg AT imageworks DOT com

Please feel free to forward to your developers and the appropriate mail lists for other open source VFX projects you participate in.

Also, if your organization is not one of the sponsors but you'd like to be, contact LG and there's certainly time to help charge up a bigger tab (no contribution is too small).


Building problems on osx 10.11

Ben De Luca <bde...@...>
 

Hi,
I am building on osx 10.11 and receive the following error at
compile time building 1.0.9 from here
https://github.com/imageworks/OpenColorIO/archive/v1.0.9.tar.gz

In file included from
/tmp/extract/tmpKUwr7l/OpenColorIO-1.0.9/src/core/AllocationOp.cpp:29:
In file included from
/tmp/extract/tmpKUwr7l/OpenColorIO-1.0.9/src/core/AllocationOp.h:33:
In file included from
/tmp/extract/tmpKUwr7l/OpenColorIO-1.0.9/export/OpenColorIO/OpenColorIO.h:38:
/var/folders/h8/9ghw01cx65ldhgwpk9scbp480000gn/T/tmpBN8ZlT/export/OpenColorABI.h:59:10:
fatal error: 'tr1/memory' file not found
#include <tr1/memory>

Before I look further has any one come across it? I couldn't find
any references on the list. I imagine the home brew folks have hit it
and will look there.


Re: OpenColorIO stewardship

nick....@...
 

Hi,

On Tuesday, March 8, 2016 at 4:33:21 PM UTC-8, Mark Boorer wrote:

The current re-factoring work is regrettably still not finished, as my other day-to-day production tasks at DNeg have become more pressing of late. I have some time for dev work booked out in the coming weeks though, so hopefully I will have something more to show soon. My greater goal is to have everything out, feedback gathered, and tested before the SIGGRAPH 2016 deadline in order to make the changes available in the VFX platform for 2017.

We are in the process of publishing the draft VFX Reference Platform for CY2017 so please can you give an update on when you expect this next release to drop and, if it's in time for vendors to incorporate into their 2017 releases, what version number it's likely to be released under so we can include it.

Thanks,

Nick

 


Re: proper FileTransform usage

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

On 3/8/2016 7:01 PM, Mark Boorer wrote:
Hi Paul,

When you say your FileTransform results differ from Nuke's, is this from
using a Vectorfield node, or an OCIO FileTransform node, or perhaps an
OCIO Display node entirely? Also what format of LUT are you using?

(I'd also recommend using INTERP_TETRAHEDRAL where possible)
Actually, what we found was creating an actual OCIO config out of the LUT file transform produced the proper results. Not entirely sure what the actual difference is under the cover.


Re: ocio Aces 1.0 config

Haarm-Pieter Duiker <li...@...>
 

Hello Gene,

The ACES 1.0.1 OCIO config can be found here:

General information about ACES can be found here:

Regards,
HP Duiker



On Thursday, March 17, 2016, G C <gcdi...@...> wrote:
Dear OCIO

I am new to this and i am struggling to get my self around to find config for After Effects and FUSION using the `Ocio plugin need config where can i download the complete set or configurations smilier to the Nuke ocio integration IIF aces module and the rest 

How do i build my own config to for example cover an srgb to Aces cg to make clean transforms from sRGB to ACEs cg 

thank you in advance for helping me out and looking into this 

Best wishes

Gene 

--
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+u...@....
For more options, visit https://groups.google.com/d/optout.


ocio Aces 1.0 config

G C <gcdi...@...>
 

Dear OCIO

I am new to this and i am struggling to get my self around to find config for After Effects and FUSION using the `Ocio plugin need config where can i download the complete set or configurations smilier to the Nuke ocio integration IIF aces module and the rest 

How do i build my own config to for example cover an srgb to Aces cg to make clean transforms from sRGB to ACEs cg 

thank you in advance for helping me out and looking into this 

Best wishes

Gene 


Re: OpenColorIO stewardship

Andy Jones <andy....@...>
 

Thanks for the update, guys. Much appreciated, as well as all of the ongoing efforts with both ACES and OCIO!

If it seems like it would make sense in the long term to distribute ACES configs separately from the OCIO examples, I wouldn't have any problem with that.  I can see where it might make it easier to juggle ACES updates and OCIO library updates.  But it does seem like our best bet for getting ACES 1.0 into this year's releases might be to avoid rocking the boat too much and stick with the plan you guys outlined.


Re: proper FileTransform usage

Mark Boorer <mark...@...>
 

Hi Paul,

When you say your FileTransform results differ from Nuke's, is this from using a Vectorfield node, or an OCIO FileTransform node, or perhaps an OCIO Display node entirely? Also what format of LUT are you using?

(I'd also recommend using INTERP_TETRAHEDRAL where possible)

Cheers,
Mark

On Tue, Mar 8, 2016 at 5:52 PM, Paul Miller <pa...@...> wrote:
I need advice on the correct way to use a LUT file transform in an OCIO processor. My results when using a FileTransform look different than in Nuke, with whites appearing more subdued using the test LUT I have. Am I doing this right?

My normal OCIO processor looks like this:

  DisplayTransformRcPtr transform = DisplayTransform::Create();
  transform->setInputColorSpaceName(colorSpaceName);
  transform->setDisplay(displayName);
  transform->setView(lookName);
  transform->setLinearCC(gainTransform);
  transform->setChannelView(swizzle);
  transform->setDisplayCC(exposureTransform);

  processor = config->getProcessor(transform);

However, I also allow bringing in an external LUT file, and I use it like this in lieu of the DisplayTransform:

  FileTransformRcPtr fileTransform = FileTransform::Create();
  fileTransform->setSrc(path);
  fileTransform->setInterpolation(OCIO::INTERP_LINEAR);

  GroupTransformRcPtr group = GroupTransform::Create();
  group->push_back(gainTransform);
  group->push_back(fileTransform);
  group->push_back(exposureTransform);

  processor = config->getProcessor(group);

I'm using the same display shader for both.

--
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+u...@....
For more options, visit https://groups.google.com/d/optout.


Re: OpenColorIO stewardship

Mark Boorer <mark...@...>
 

Hi All,

Apologies Mark, I missed your previous request for an update, it's been a bit busier this year than I expected!

Andy, et al; As Haarm-Pieter put it, I am currently awaiting his final changes before I can merge his ACES 1.0.1 config into the repo. At the moment, the OpenColorIO-Configs repository is not versioned in lock step with the library, so I see no reason why this cannot go out immediately. Initially I'd had some reservations about the sheer size of the commits, and that the addition of other, non OpenColorIO related data would have an adverse effect on the usability / maintainability of the repository, but people seem keen to use this repo as a central ACES reference implementation, rather than just a place for OCIO configs, so I plan on putting it through in one go.

The current re-factoring work is regrettably still not finished, as my other day-to-day production tasks at DNeg have become more pressing of late. I have some time for dev work booked out in the coming weeks though, so hopefully I will have something more to show soon. My greater goal is to have everything out, feedback gathered, and tested before the SIGGRAPH 2016 deadline in order to make the changes available in the VFX platform for 2017.

In short, the ACES 1.0.1 configs will go out as soon as the final cleanup is done, and the library changes will be out for feedback hopefully not long after.

Cheers,
Mark

On Tue, Mar 8, 2016 at 8:26 PM, Haarm-Pieter Duiker <li...@...> wrote:
Hey Andy,

Here's an update from my side on the issue. After a bit of delay, Mark and the OCIO leadership have agreed to accept the pull request to integrate the ACES 1.0.1 config into the main OCIO configs repo. They have asked me to combine the commit history into a single commit before doing so, so the commit history for the general repo doesn't suddenly have a huge list of commits that won't mean much to most people. It's on my to do list. I'm also on a project that is barreling head-long towards a deadline this week, so that's taking precedence right now. I'm hoping to have the commits squashed this weekend so the pull request can be accepted.

Mark, correct me if that's not in line with your understanding.

HP




On Tue, Mar 8, 2016 at 2:37 PM, Andy Jones <andy....@...> wrote:
Bumping this, specifically WRT ACES 1.0 in the configs.  It would be great to get some kind of (hopefully short) timeline on that.  The configs in Nuke seem to be some ancient checkout of the examples, and we'd like to pressure them to bring them up to date for their next release.  We'd really like to see ACES 1.0 included in that update.  It seems like there's a chance Nuke might end up pulling from HP's github if the update doesn't happen soon, but I would imagine it's in everyone's best interest to keep everything pointed at the original repo.

If there's a big refactor of the configs going on for the major release mentioned above, perhaps it's worth making a branch and merging HP's ACES 1.0 config into master until that's ready?  Even if the configs are likely to need to change with the updates, it seems like places may need a legacy ACES 1.0 config for a while, until the future library makes its way into the apps.

--
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+u...@....
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+u...@....
For more options, visit https://groups.google.com/d/optout.


Re: OpenColorIO stewardship

Haarm-Pieter Duiker <li...@...>
 

Hey Andy,

Here's an update from my side on the issue. After a bit of delay, Mark and the OCIO leadership have agreed to accept the pull request to integrate the ACES 1.0.1 config into the main OCIO configs repo. They have asked me to combine the commit history into a single commit before doing so, so the commit history for the general repo doesn't suddenly have a huge list of commits that won't mean much to most people. It's on my to do list. I'm also on a project that is barreling head-long towards a deadline this week, so that's taking precedence right now. I'm hoping to have the commits squashed this weekend so the pull request can be accepted.

Mark, correct me if that's not in line with your understanding.

HP




On Tue, Mar 8, 2016 at 2:37 PM, Andy Jones <andy....@...> wrote:
Bumping this, specifically WRT ACES 1.0 in the configs.  It would be great to get some kind of (hopefully short) timeline on that.  The configs in Nuke seem to be some ancient checkout of the examples, and we'd like to pressure them to bring them up to date for their next release.  We'd really like to see ACES 1.0 included in that update.  It seems like there's a chance Nuke might end up pulling from HP's github if the update doesn't happen soon, but I would imagine it's in everyone's best interest to keep everything pointed at the original repo.

If there's a big refactor of the configs going on for the major release mentioned above, perhaps it's worth making a branch and merging HP's ACES 1.0 config into master until that's ready?  Even if the configs are likely to need to change with the updates, it seems like places may need a legacy ACES 1.0 config for a while, until the future library makes its way into the apps.

--
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+u...@....
For more options, visit https://groups.google.com/d/optout.


Re: OpenColorIO stewardship

Andy Jones <andy....@...>
 

Bumping this, specifically WRT ACES 1.0 in the configs.  It would be great to get some kind of (hopefully short) timeline on that.  The configs in Nuke seem to be some ancient checkout of the examples, and we'd like to pressure them to bring them up to date for their next release.  We'd really like to see ACES 1.0 included in that update.  It seems like there's a chance Nuke might end up pulling from HP's github if the update doesn't happen soon, but I would imagine it's in everyone's best interest to keep everything pointed at the original repo.

If there's a big refactor of the configs going on for the major release mentioned above, perhaps it's worth making a branch and merging HP's ACES 1.0 config into master until that's ready?  Even if the configs are likely to need to change with the updates, it seems like places may need a legacy ACES 1.0 config for a while, until the future library makes its way into the apps.

761 - 780 of 2226