New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add OCIO integration #193
Comments
Does this plan include dealing with texture lookups? Or does that come for free? (I'm thinking of reading texture maps from plain 8 bit jpgs for example where the pixels should be "linearized" as they are read in) |
This plan does not include that, but it's something we'd like to do as step 2 after the top list is done. We've been pinged on this workflow before so it's definitely good to consider. In terms of implementation, we'll want to choose whether the processing is done as the pixels are read into the tile cache, or on a per-pixel basis at query time. There would be tradeoffs for cpu vs memory vs correctness for both approaches. |
I've begun a basic implementation: You can see that the exposed public interface to the color processing doesn't expose anything about OpenColorIO, which will let us stay ABI compatible even if OCIO is not enabled at build time: https://github.com/jeremyselan/oiio/blob/ocio/src/include/colorprocessor.h maketx has been updated, and I've confirmed the processing works. TODO:
Eventually,
|
Closing, this has long since been done. |
Rough Plan...
The text was updated successfully, but these errors were encountered: