1. ocio-dev@lists.aswf.io
  2. Messages
   Date   
learning materials

Yaira Lamela <yai...@...>
 


to whom it may concern,

I would like to receive learning materials for ocio

thank you,

Yaira Lamela
Re: Building from a source on Linux

Cat Jordan <cdaly...@...>
 

Hey, thanks for clearing that up. Unfortunately Cmake couldn't find the compiler, and neither could I. here was the error I got this time:

CMake Error at CMakeLists.txt:1 (project):
  No CMAKE_CXX_COMPILER could be found.

  Tell CMake where to find the compiler by setting either the environment
  variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.


On Fri, Feb 22, 2019 at 9:56 AM Patrick Hodoul <patric...@...> wrote:

Here is a concrete Linux example (i.e. easily adaptable to other platforms) on how to download and build OCIO:


On Friday, February 22, 2019 at 1:26:58 AM UTC-5, Michael Dolan wrote:
"source/ocio" in the example cmake command needs to be replaced with the path to the OCIO source directory on your machine ("/home/sigi/Downloads/imageworks-OpenColorIO-a4dc9cd" in your case, pictured in your screen grab).

So you should:
1. Create an empty build directory somewhere and cd to it
2. From this directory, run cmake with the command:

cmake -D CMAKE_INSTALL_PREFIX=<where OCIO should be installed> <where the OCIO source lives>
This will configure the project for building within your current directory when you later run "make", and install to the install directory when you then run "make install"

Hope that helps.

On Wed, Feb 20, 2019 at 1:56 PM Cat Jordan <cdal...@...> wrote:
Ok, please keep in mind I'm very bad at coding while reading this question.
I'm following the "building from a source" instructions on this page (http://opencolorio.org/installation.html). I made it to "run cmake..." before I got stuck. Here's what I got when i tried to put in the code as is.
"CMake Error: The source directory "/source/ocio" does not exist.
Specify --help for usage, or press the help button on the CMake GUI."
Using 'sudo' didn't help. when I added " .." o the end I  got this error;
"CMake Error: The source directory "/home/sigi/Downloads" does not appear to contain CMakeLists.txt."
I had navigated to the downloads folder at this point because that's where the file in question is.
image.png
Trying to move all these files to tmp/ociobuild didn't help either.
I don't know what I'm doing please help

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

--
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: Building from a source on Linux

Patrick Hodoul <patric...@...>
 


Here is a concrete Linux example (i.e. easily adaptable to other platforms) on how to download and build OCIO:
https://github.com/imageworks/OpenColorIO/blob/master/share/docker/dockerfile_ubuntu16_gcc54 (refer to lines 83 to 99)


On Friday, February 22, 2019 at 1:26:58 AM UTC-5, Michael Dolan wrote:
"source/ocio" in the example cmake command needs to be replaced with the path to the OCIO source directory on your machine ("/home/sigi/Downloads/imageworks-OpenColorIO-a4dc9cd" in your case, pictured in your screen grab).

So you should:
1. Create an empty build directory somewhere and cd to it
2. From this directory, run cmake with the command:

cmake -D CMAKE_INSTALL_PREFIX=<where OCIO should be installed> <where the OCIO source lives>
This will configure the project for building within your current directory when you later run "make", and install to the install directory when you then run "make install"

Hope that helps.

On Wed, Feb 20, 2019 at 1:56 PM Cat Jordan <cdal...@...> wrote:
Ok, please keep in mind I'm very bad at coding while reading this question.
I'm following the "building from a source" instructions on this page (http://opencolorio.org/installation.html). I made it to "run cmake..." before I got stuck. Here's what I got when i tried to put in the code as is.
"CMake Error: The source directory "/source/ocio" does not exist.
Specify --help for usage, or press the help button on the CMake GUI."
Using 'sudo' didn't help. when I added " .." o the end I  got this error;
"CMake Error: The source directory "/home/sigi/Downloads" does not appear to contain CMakeLists.txt."
I had navigated to the downloads folder at this point because that's where the file in question is.
image.png
Trying to move all these files to tmp/ociobuild didn't help either.
I don't know what I'm doing please help

--
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.
Re: Building from a source on Linux

Michael Dolan <mich...@...>
 

"source/ocio" in the example cmake command needs to be replaced with the path to the OCIO source directory on your machine ("/home/sigi/Downloads/imageworks-OpenColorIO-a4dc9cd" in your case, pictured in your screen grab).

So you should:
1. Create an empty build directory somewhere and cd to it
2. From this directory, run cmake with the command:

cmake -D CMAKE_INSTALL_PREFIX=<where OCIO should be installed> <where the OCIO source lives>
This will configure the project for building within your current directory when you later run "make", and install to the install directory when you then run "make install"

Hope that helps.


On Wed, Feb 20, 2019 at 1:56 PM Cat Jordan <cdaly...@...> wrote:
Ok, please keep in mind I'm very bad at coding while reading this question.
I'm following the "building from a source" instructions on this page (http://opencolorio.org/installation.html). I made it to "run cmake..." before I got stuck. Here's what I got when i tried to put in the code as is.
"CMake Error: The source directory "/source/ocio" does not exist.
Specify --help for usage, or press the help button on the CMake GUI."
Using 'sudo' didn't help. when I added " .." o the end I  got this error;
"CMake Error: The source directory "/home/sigi/Downloads" does not appear to contain CMakeLists.txt."
I had navigated to the downloads folder at this point because that's where the file in question is.
image.png
Trying to move all these files to tmp/ociobuild didn't help either.
I don't know what I'm doing please help

--
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.
New OCIO mail lists | PLEASE READ

Michael Dolan <mich...@...>
 

Hello OCIO community,

As recently announced in the official press release, OpenColorIO has been approved as the second hosted project of the Academy Software Foundation (ASWF). The OCIO technical steering committee (TSC) has been working with the Linux Foundation in recent weeks to transition the project's infrastructure from its Sony Pictures Imageworks roots to the ASWF. Part of that transition involves moving the ocio-dev and ocio-users mail lists from Google groups to their new home on the aswf.io domain.

The history of the Google groups will be migrated to the new lists, but all subscribers will be required to sign up at lists.aswf.io to continue receiving messages. The Google groups will remain online until the migration is complete. Notice will be sent to the current lists one week prior to their shutdown. Please sign up as soon as possible to avoid missing news and discussion on the much anticipated OCIO v2, being helmed by Autodesk's Doug Walker, Patrick Hodoul, and Bernard Lefebvre. There's lots of work to be done, and community contributions play a big part in this effort, so your involvement is encouraged.

To subscribe to the new ocio-user list, follow this link:
https://lists.aswf.io/g/ocio-user

To subscribe to the new ocio-dev list, follow this link:
https://lists.aswf.io/g/ocio-dev

Thank you for your continued support and interest in OpenColorIO.

Michael Dolan
OpenColorIO TSC Chair
building from a source, linux

Cat Jordan <cdaly...@...>
 

Ok, please keep in mind I'm very bad at coding while reading this question.
I'm following the "building from a source" instructions on this page (http://opencolorio.org/installation.html). I made it to "run cmake..." before I got stuck. Here's what I got when i tried to put in the code as is.
"CMake Error: The source directory "/source/ocio" does not exist.
Specify --help for usage, or press the help button on the CMake GUI."
Using 'sudo' didn't help. when I added " .." o the end I  got this error;
"CMake Error: The source directory "/home/sigi/Downloads" does not appear to contain CMakeLists.txt."
I had navigated to the downloads folder at this point because that's where the file in question is.
image.png

Trying to move all these files to tmp/ociobuild didn't help either.
I don't know what I'm doing please help
Building from a source on Linux

Cat Jordan <cdaly...@...>
 

Ok, please keep in mind I'm very bad at coding while reading this question.
I'm following the "building from a source" instructions on this page (http://opencolorio.org/installation.html). I made it to "run cmake..." before I got stuck. Here's what I got when i tried to put in the code as is.
"CMake Error: The source directory "/source/ocio" does not exist.
Specify --help for usage, or press the help button on the CMake GUI."
Using 'sudo' didn't help. when I added " .." o the end I  got this error;
"CMake Error: The source directory "/home/sigi/Downloads" does not appear to contain CMakeLists.txt."
I had navigated to the downloads folder at this point because that's where the file in question is.
image.png
Trying to move all these files to tmp/ociobuild didn't help either.
I don't know what I'm doing please help
Re: Next steps on communication tools migration and meeting cadence

Michael Dolan
 

Thanks for the update John.

The initial maillist heads up about ocio-dev and ocio-users moving to the aswf domain might be a good opportunity for a general project update regarding the ASWF transition. It's been discussed some in ocio-dev already, but not in ocio-users. We could relay a (very) brief overview of what was presented at the TAC meeting recently, to give some context for the change.

Michael


On Sun, Feb 17, 2019 at 7:02 AM John Mertic <jmertic@...> wrote:
Hi everyone!

Hope everyone is having a good weekend. Since our next meeting is cancelled due to the holiday, wanted to provide some updates via email

1) Mailing lists

As you probably saw, I have setup the new mailing lists for the project on groups.io. The lists are:

ocio-user@... - General user discussion list
ocio-dev@... - General dev and TSC discussion list
ocio-tsc-private@... - Private TSC discussion list for sensitive matters ( such legal concerns, committer approval, and conduct issues ).

I'd propose the following next steps ( open to your guidance on timing )

- Announce to the existing groups about the migration, driving users to signup to the new lists ( I'd suggest this versus migrating the users over to help pare down any dormant mailing lists subscriptions ). Group members can be redirected to https://lists.aswf.io/g/ocio-dev or https://lists.aswf.io/g/ocio-user to sign up to the new lists. 
- After a week, send another notice to the group announce a firm shutdown date of the old Google Groups  - suggest another week. 
- After the shutdown date - LF IT will migrate the previous Google Groups archives into the groups.io lists.

Let me know thoughts on the proposed.

2) Domain transfer

Larry is working with our team here - Larry let me know if there is anything I can do to help.

3) Code scan

Steve Winslow will be sharing the more detailed report in the coming days. I also wanted to check on where the discussion on moving the dependency artifacts to Nexus lies ( and for that matter what to do about dependencies that are no longer maintained ).

4) Meeting notices and cadence

As mentioned, tomorrow's meeting is CANCELLED. I'm working to get Micheal Dolan the credentials for a OpenColorIO community use account. Once that is setup, I'll work with Micheal to take over the meeting invites going forward. Look for a new meeting notice coming soon.

Let me know if anyone has questions or concerns, or if there is anything I'm missing.

Thank you,

John Mertic
Director of Program Management - Linux Foundation
ASWF, ODPi, R Consortium, and Open Mainframe Project
Schedule time with me at https://calendly.com/jmertic
Next steps on communication tools migration and meeting cadence

John Mertic
 

Hi everyone!

Hope everyone is having a good weekend. Since our next meeting is cancelled due to the holiday, wanted to provide some updates via email

1) Mailing lists

As you probably saw, I have setup the new mailing lists for the project on groups.io. The lists are:

ocio-user@... - General user discussion list
ocio-dev@... - General dev and TSC discussion list
ocio-tsc-private@... - Private TSC discussion list for sensitive matters ( such legal concerns, committer approval, and conduct issues ).

I'd propose the following next steps ( open to your guidance on timing )

- Announce to the existing groups about the migration, driving users to signup to the new lists ( I'd suggest this versus migrating the users over to help pare down any dormant mailing lists subscriptions ). Group members can be redirected to https://lists.aswf.io/g/ocio-dev or https://lists.aswf.io/g/ocio-user to sign up to the new lists. 
- After a week, send another notice to the group announce a firm shutdown date of the old Google Groups  - suggest another week. 
- After the shutdown date - LF IT will migrate the previous Google Groups archives into the groups.io lists.

Let me know thoughts on the proposed.

2) Domain transfer

Larry is working with our team here - Larry let me know if there is anything I can do to help.

3) Code scan

Steve Winslow will be sharing the more detailed report in the coming days. I also wanted to check on where the discussion on moving the dependency artifacts to Nexus lies ( and for that matter what to do about dependencies that are no longer maintained ).

4) Meeting notices and cadence

As mentioned, tomorrow's meeting is CANCELLED. I'm working to get Micheal Dolan the credentials for a OpenColorIO community use account. Once that is setup, I'll work with Micheal to take over the meeting invites going forward. Look for a new meeting notice coming soon.

Let me know if anyone has questions or concerns, or if there is anything I'm missing.

Thank you,

John Mertic
Director of Program Management - Linux Foundation
ASWF, ODPi, R Consortium, and Open Mainframe Project
Schedule time with me at https://calendly.com/jmertic
Re: AllocationVars with GPU path and 1d LUT

Bernard Lefebvre <bernard....@...>
 

The issue is now fixed. See https://github.com/imageworks/OpenColorIO/issues/622


Le lundi 29 octobre 2018 20:19:53 UTC-4, Simon Therriault a écrit :
Hi,

I've been playing around an integration of OCIO using the GPU path (latest code version build 50) and things are going relatively smoothly. There's one problem that I still have though and it's when I compare conversion result to a conversion made in Nuke. 

I'm using the Nuke-Default configuration and playing with Linear to SRGB conversion.

colorspaces:
  - !<ColorSpace>
    name: linear
    family: ""
    equalitygroup: ""
    bitdepth: 32f
    description: |
      Scene-linear, high dynamic range. Used for rendering and compositing.
    isdata: false
    allocation: lg2
    allocationvars: [-15, 6]

  - !<ColorSpace>
    name: sRGB
    family: ""
    equalitygroup: ""
    bitdepth: 32f
    description: |
      Standard RGB Display Space
    isdata: false
    allocation: uniform
    allocationvars: [-0.125, 1.125]
    to_reference: !<FileTransform> {src: srgb.spi1d, interpolation: linear}

My source image is Marci_512_linear.exr that comes from the reference images. I have applied a Linear to SRGB transform in Nuke and saved an EXR 32 bits uncompressed out of it.

On my side, I have applied the same transform but using the GPU path.

In the hair region, where pixels are well over 1.0, I don't have the same result. My output has clipped to 1.0 and the one from Nuke clipped to 1.25. Samething happens for pixels below 0.0. My result has clipped to 0.0 but in Nuke's output, I can see sub 0.0 values. It looks like the allocation vars aren't taken into account or something.

My shader output looks like this and the language used is HLSL_DX11 :

Texture2D ociolut1d_0;
SamplerState ociolut1d_0Sampler;

float2 ociolut1d_0_computePos(float f)
{
  float dep = min(f, 1.0) * 65535.;
  float2 retVal;
  retVal.y = float(int(dep / 4095.));
  retVal.x = dep - retVal.y * 4095.;
  retVal.x = (retVal.x + 0.5) / 4096.;
  retVal.y = (retVal.y + 0.5) / 17.;
  return retVal;
}



float4 OCIOConvert(in float4 inPixel)
{
  float4 outColor = inPixel;
  outColor.r = ociolut1d_0.Sample(ociolut1d_0Sampler, ociolut1d_0_computePos(outColor.r)).r;
  outColor.g = ociolut1d_0.Sample(ociolut1d_0Sampler, ociolut1d_0_computePos(outColor.g)).g;
  outColor.b = ociolut1d_0.Sample(ociolut1d_0Sampler, ociolut1d_0_computePos(outColor.b)).b;

  return outColor;
}

If anyone ever had that issue, I'll be happy to hear it out :)


Thanks!
Re: pyOCIO Windows compilation error against Python36

Renaud Talon <renau...@...>
 

Hi Richard,

 

Thank you for your suggestions, I did look into your diff files but I couldn’t find anything that’s not already added to the current versions of the files.

I got it to compile with Windows 10 / Python 3.6 – Visual Studio 2015, by changing the following line in “pyUtil.h” (line 65):

from :

  #define MOD_INIT(name) PyMODINIT_FUNC EXPORT_SYMBOL PyInit_##name(void)

 

to:

  #define MOD_INIT(name) EXPORT_SYMBOL PyMODINIT_FUNC PyInit_##name(void)

 

I did get a warning message though but the compilation process went through and the “.pyd” file was generated.

I’m honestly no C++ expert so I’m not sure if this makes sense but it seems to work. I need to run further testing next week to confirm but so far so good.

 

Thanks again,

Renaud

 

 

From: ocio...@... <oc...@...> on behalf of Richard Shaw <hob...@...>
Sent: Monday, February 4, 2019 8:45:08 AM
To: ocio...@...
Subject: Re: [ocio-dev] pyOCIO Windows compilation error against Python36
 
I had completely forgotten that I moved the Fedora package over to Python 3.7 and haven't had any build issues... Now that being said I don't know if there's any consumers of the python library in Fedora...


Feel free to poke around the build logs...

Here's the spec file for building... Some of it won't make sense to you but you can review the settings / cmake options I use.


Thanks,
Richard

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

Lu anh tuan <l.a....@...>
 

My name Tuan as a compositor for films, i want to learn in depth how OCIO their works in software. Please send for me the list or video online!

Best;
Tuan
Press release : Academy Scientific and Technical Award Winning OpenColorIO Joins Academy Software Foundation

"Sanjay Gangal" <Sanjay...@...>
 

You will be pleased to know that we published your press release.

https://www10.ShareCG.com/nbc/articles/view_article.php?articleid=1648104

Let me know if you are interested in making this a 'Premium News Release'.

Here are the benefits and features:
* Premium Press Releases typically receive 50% more hits than regular press releases.
* Your press release listing is displayed in bold text and placed near the top of the day's news to stand out on the ShareCG.com homepage.
* Your press release is also positioned near the top of the daily newsletter distribution.

The cost is $399 (and we do take Visa, Master Card, and American Express).

To publish this article as 'Premium Press Release' with credit card, please use the following:
https://www10.ShareCG.com/nbc/purchase/credit_card.php?articleid=1648104

If your company is not yet a member of ShareCG.com and reaching the professionals in this industry is important to you, please feel free to contact me to ensure future press releases are published and to learn more about additional promotional opportunities on ShareCG.

Best regards!

Sanjay Gangal
President,
Phone: +1 (408) 882-6554
Email: Sanjay...@...
https://www.ShareCG.com
Re: OCIO -> ASWF

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

He lives!


On Feb 8, 2019, at 12:08 PM, Jeremy Selan <jeremy...@...> wrote:

Congrats!

On Fri, Feb 8, 2019 at 12:05 PM Piotr Stanczyk <piotr.s...@...> wrote:
Congratulations on getting this through. Great work!



On Fri, Feb 8, 2019 at 10:57 AM Larry Gritz <l...@...> wrote:
Official announcement: https://www.aswf.io/ocio-joins-aswf/

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




--
Larry Gritz
Re: OCIO -> ASWF

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

Congrats!


On Fri, Feb 8, 2019 at 12:05 PM Piotr Stanczyk <piotr.s...@...> wrote:
Congratulations on getting this through. Great work!



On Fri, Feb 8, 2019 at 10:57 AM Larry Gritz <l...@...> wrote:
Official announcement: https://www.aswf.io/ocio-joins-aswf/

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

--
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: OCIO -> ASWF

Piotr Stanczyk <piotr.s...@...>
 

Congratulations on getting this through. Great work!



On Fri, Feb 8, 2019 at 10:57 AM Larry Gritz <l...@...> wrote:
Official announcement: https://www.aswf.io/ocio-joins-aswf/

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

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

Official announcement: https://www.aswf.io/ocio-joins-aswf/

--
Larry Gritz
l...@...
Re: pyOCIO Windows compilation error against Python36

Richard Shaw <hobbe...@...>
 

I had completely forgotten that I moved the Fedora package over to Python 3.7 and haven't had any build issues... Now that being said I don't know if there's any consumers of the python library in Fedora...


Feel free to poke around the build logs...

Here's the spec file for building... Some of it won't make sense to you but you can review the settings / cmake options I use.


Thanks,
Richard
Re: pyOCIO Windows compilation error against Python36

Patrick Hodoul <patric...@...>
 

Hi Guys,

 

Thanks for your investigations around Python 3. 

 

OCIO does not currently support Python 3. But it would be appreciated to have a pull request fixing the Python 3 support   :-)

 

Patrick.

 


On Sunday, January 27, 2019 at 1:04:35 PM UTC-5, Richard wrote:
On Sun, Jan 27, 2019 at 12:05 AM <rena...@...> wrote:
I downloaded the latest OCIO code from GitHub (1.1.0) and I was able to compile OCIO using "Visual Studio 2015" as-well as pyOpenColorIO against Python27.

I checked online to see if I could figure out what's causing the issue but I couldn't figure it out. Anybody would know why this is happening ?
Was anyone able to compile OCIO 1.1.0 | Win64 | Visual Studio 2015 | Python36 (official 64 bit build) ?

My guess is that it hasn't been updated for Python3 yet... There are some incompatible changes.

You can try a converter and see if it takes care of the errors but beware any unintended side effects...


Thanks,
Richard 
Metadata (WAS: OCIO v2 January working group meeting)

Troy Sobotka <troy.s...@...>
 

First, an apology for igniting the naming debate. Second, a huge congrats on reaching consensus on the naming of the ExponentTransform and its sibling.

Part of me wants a PowerToe T shirt though...

On Mon, Jan 28, 2019 at 6:44 PM Doug Walker <Doug....@...> wrote:

TOPIC:  NEW COLORSPACE "CATEGORY" ATTRIBUTE  PR #648  (PR 7 days, but API/tests for 64 days)

-- Thomas pointed out the risk of these features not being implemented the same way (similar to roles).  The group agreed it was a useful feature but the standard list and intended behavior of the categories needs to be clearly documented.

I completely agree with this. From a UI construction point of view, and in accordance with the ISO’s additive RGB colorspace definition, is it feasible to enforce a bare minimum set of tags that might include:

1. TransferFunction
2. Chromaticity
3. AchromaticChromaticity

I ask because it is deadly tricky trying to implement OCIO v1 as a UI colour management system without some degree of clarity on certain transform classes and their undisclosed colorimetry. Being able to, for example, deduce the underlying chromaticities and separate them from both technical and aesthetic transfer functions is required for displaying UI elements correctly according to need. Attempting to do so with only a blind view transform is virtually impossible currently. 

Great work,
TJS
481 - 500 of 2258