State of OCIO development re: CPU/GPU mismatches


Dithermaster <dither...@...>
 

Dennis, is your fork containing the OpenCL code path available to browse currently?
Nathan, no, but I could put something together for you if you'd like to review it.

///d@



On Mon, Sep 12, 2016 at 8:15 PM, Nathan Rusch <natha...@...> wrote:
Thanks for the responses everyone.

I'm attempting to reach out to some of the people who may have a connection to or interest in the project's stewardship, and will be asking them to weigh in on this thread so we can get as much information as possible out in the open. Sean, I'm wondering if you might be able to track down any of your colleagues who might have some interest or involvement in order to potentially get their input here as well. I'm not entirely sure how many of the original team are still at Imageworks, or how involved they want to be, so I don't necessarily want to blanket every name I can find.

In general, I'm inclined to agree with Deke that an ideal way forward from our perspective would be for active development to be out in the open on a development branch, rather than only landing in the form of releases.

Dennis, is your fork containing the OpenCL code path available to browse currently?


-Nathan


On Friday, September 9, 2016 at 2:18:51 PM UTC+10, Sean Cooper wrote:
Hello fellow color wizards,

I'd just like to introduce myself to the community here. I've joined Sony Imageworks as our Color Scientist this past January, and have been working on our internal color pipeline and taking on more responsibility as I continue to learn.

I have interest in seeing OCIO continue it's open development, and would like to help where ever I can. Admittedly my background is in pure color/imaging science so I won't be able to immediately jump on the reins of it's core development. However, it seems like we have the opposite problem, and I would be happy to work with you to siphon through its present state and work towards a game plan to give OCIO a fresh breath of life.

Sean Cooper
Color Scientist
Sony Pictures Imageworks

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


Dithermaster <dither...@...>
 

Nathan and others interested,

I've attached a PDF describing our OpenCL extensions to OpenColorIO. An accurate OpenGL path would do something very similar with multiple shader parameters, and would return GLSL instead of an OpenCL kernel. I am happy to work closely with anyone who wants to create the accurate OpenGL path starting from these changes, but I'm not an OpenGL expert so you'd need to handle the OpenGL side of things.

Sincerely,

///d@
Dennis Adams


On Tue, Sep 13, 2016 at 10:45 AM, Dithermaster <dither...@...> wrote:
Dennis, is your fork containing the OpenCL code path available to browse currently?
Nathan, no, but I could put something together for you if you'd like to review it.

///d@



On Mon, Sep 12, 2016 at 8:15 PM, Nathan Rusch <natha...@...> wrote:
Thanks for the responses everyone.

I'm attempting to reach out to some of the people who may have a connection to or interest in the project's stewardship, and will be asking them to weigh in on this thread so we can get as much information as possible out in the open. Sean, I'm wondering if you might be able to track down any of your colleagues who might have some interest or involvement in order to potentially get their input here as well. I'm not entirely sure how many of the original team are still at Imageworks, or how involved they want to be, so I don't necessarily want to blanket every name I can find.

In general, I'm inclined to agree with Deke that an ideal way forward from our perspective would be for active development to be out in the open on a development branch, rather than only landing in the form of releases.

Dennis, is your fork containing the OpenCL code path available to browse currently?


-Nathan


On Friday, September 9, 2016 at 2:18:51 PM UTC+10, Sean Cooper wrote:
Hello fellow color wizards,

I'd just like to introduce myself to the community here. I've joined Sony Imageworks as our Color Scientist this past January, and have been working on our internal color pipeline and taking on more responsibility as I continue to learn.

I have interest in seeing OCIO continue it's open development, and would like to help where ever I can. Admittedly my background is in pure color/imaging science so I won't be able to immediately jump on the reins of it's core development. However, it seems like we have the opposite problem, and I would be happy to work with you to siphon through its present state and work towards a game plan to give OCIO a fresh breath of life.

Sean Cooper
Color Scientist
Sony Pictures Imageworks

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

I think it would be very interesting to take a look at an OpenCL OCIO implementation.

It seems like: #304, #396, + Kevin's CDL parse, would be easy first steps to get these creaky joints moving again.

I'll have more time next week to investigate the other pull requests, and catch up on the test suite.

@Malcolm: do know the status of the DNeg OCIO pull that has been referred to? And if there are still people there interested in pushing to the public repo? 

On Tue, Sep 13, 2016 at 9:37 AM, Dithermaster <dither...@...> wrote:
Nathan and others interested,

I've attached a PDF describing our OpenCL extensions to OpenColorIO. An accurate OpenGL path would do something very similar with multiple shader parameters, and would return GLSL instead of an OpenCL kernel. I am happy to work closely with anyone who wants to create the accurate OpenGL path starting from these changes, but I'm not an OpenGL expert so you'd need to handle the OpenGL side of things.

Sincerely,

///d@
Dennis Adams


On Tue, Sep 13, 2016 at 10:45 AM, Dithermaster <dither...@...> wrote:
Dennis, is your fork containing the OpenCL code path available to browse currently?
Nathan, no, but I could put something together for you if you'd like to review it.

///d@



On Mon, Sep 12, 2016 at 8:15 PM, Nathan Rusch <natha...@...> wrote:
Thanks for the responses everyone.

I'm attempting to reach out to some of the people who may have a connection to or interest in the project's stewardship, and will be asking them to weigh in on this thread so we can get as much information as possible out in the open. Sean, I'm wondering if you might be able to track down any of your colleagues who might have some interest or involvement in order to potentially get their input here as well. I'm not entirely sure how many of the original team are still at Imageworks, or how involved they want to be, so I don't necessarily want to blanket every name I can find.

In general, I'm inclined to agree with Deke that an ideal way forward from our perspective would be for active development to be out in the open on a development branch, rather than only landing in the form of releases.

Dennis, is your fork containing the OpenCL code path available to browse currently?


-Nathan


On Friday, September 9, 2016 at 2:18:51 PM UTC+10, Sean Cooper wrote:
Hello fellow color wizards,

I'd just like to introduce myself to the community here. I've joined Sony Imageworks as our Color Scientist this past January, and have been working on our internal color pipeline and taking on more responsibility as I continue to learn.

I have interest in seeing OCIO continue it's open development, and would like to help where ever I can. Admittedly my background is in pure color/imaging science so I won't be able to immediately jump on the reins of it's core development. However, it seems like we have the opposite problem, and I would be happy to work with you to siphon through its present state and work towards a game plan to give OCIO a fresh breath of life.

Sean Cooper
Color Scientist
Sony Pictures Imageworks

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