I could pull them apart if absolutely necessary, but since they sort of depend on each other it's easier said than done. For example, I made some changes to the AE files so that the Photoshop plug-in

Wonderful, thanks for the effort Brendan! I'll have to look at this shortly. Before I go too far, do you think you could separate it into two pull requests? One for the AE plugin and another for the

OK, I have a new pull request that should have everything up to date. https://github.com/imageworks/OpenColorIO/pull/476

Sorry, that should have been: c.rgb = exp( tex3D(lut, c.rgb * scale + offset ).rgb );

I was able to match the output of ociodisplay with a NUM_STOPS of 8, a lattice of 64x64x64 and with the following change to the shader code: c.rgb = exp( scale * texture3D(lut, c.rgb).rgb +

I have a GL Lut that is not created with OCIO.  Instead an initial identity lut is created and this lut is passed on to the gfx card by my own code.  So long, so good.  However, this lut is

Currently, I am using OCIO with a mixed CPU/GPU pipeline. Luts are 4 float colors which get fed like: // // Compute lutMin, lutMax, and scale and offset // values, lutM and lutT, so that

Hi Sean, What is the status for 1.0.10? Thanks.

Thank you very much.

Wonderful, yes I will. Thank you.

https://sourceforge.net/projects/mrviewer/files/v3.8.4 This version of mrViewer is the first to add some support for OCIO. Please add this software to the compatible list. Thank you.

Hi all, Patrick Hodoul has just pushed a number of Windows build related fixes as PR #464 . If any of you have free time to look at his commits and perhaps more importantly to test the build process

What do you want to know? As Deke pointed out, I have a blog post where you can download it. Code is on GitHub. It was made for use in a studio, so it's been tested. It's designed similarly to the

I'll happily look at anything pushed our way. Curious, would you be able to give a quick rundown of the PS plugin functionality / implementation?

Yea, that's what I figured. You have a pull request never fulfilled from 2016 so why bother with future ones. Now that we have Sean actively accepting changes you can probably update with your

Au contraire! I've actually updated it as recently as January. See my ae_plugin_update branch: https://github.com/fnordware/OpenColorIO/tree/ae_plugin_update I also have a Photoshop plug-in now in my

He also has a nice one for Photoshop http://fnordware.blogspot.com/2017/02/opencolorio-for-photoshop.html He hasn't made a pull request yet but you can see the source for it

Ah great, that's good to know. I'd never get my hand on AE anytime soon so I think its fair to trust your opinion on the situation. @cam Maybe you could be an additional tester on #405 and we can pull

I've used the plugin a few times. Minus a few minor issues it works fairly well. There is an updated pull request from 2016 though which we should probably accept. I've used this version and not

The latter mostly, most VFX studios that maintain the project don't actively use After Effects so it's not usually on our minds. So its also a question of, if its broken who cares enough to do