Skip to content

Conversation

@omenos
Copy link

@omenos omenos commented Apr 14, 2020

The imageworks/OpenColorIO-Configs repository does not see
any new development or releases. Thomas Mansencal has been
maintaining the configs with newer standards such as
ACES 1.1 and 1.2 for the community.

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Apr 14, 2020

CLA Check
The committers are authorized under a signed CLA.

The imageworks/OpenColorIO-Configs repository does not see
any new development or releases. Thomas Mansencal has been
maintaining the configs with newer standards such as
ACES 1.1 and 1.2 for the community.

Signed-off-by: Michael Rochefort <[email protected]>
@michdolan
Copy link
Collaborator

michdolan commented Apr 18, 2020

Thanks @omenos . The reason for OpenColorIO-Configs being without the new ACES configs is related to a license & repo structure discussion we have been having with the ACES team. The solution is sort of in a holding pattern, but you can find more information about it here: imageworks/OpenColorIO-Configs#17

I think it's a good idea to link to @KelSolaar 's configs from the OCIO website for visibility (especially since these are shipping with DCCs like Nuke), but I think the link should be added in addition to the OpenColorIO-Configs repo, rather than replacing it, with a note that Thomas's fork is where to find these specific ACES configs.

My other comment is that if you want this to appear on the current website, you'll need to submit a PR against the RB-1.1 branch, which is what currently sources the website. master will eventually source the site, but closer to the OCIO v2 release later in the summer. Thanks!

@KelSolaar
Copy link
Contributor

Ahhhh, the Config Repo Location story! ;)

Related: I will tag the 1.2 as final given nobody complained during the past weeks :)

@omenos
Copy link
Author

omenos commented Apr 18, 2020

The reason for OpenColorIO-Configs being without the new ACES configs is related to a license & repo structure discussion we have been having with the ACES team.

Ah, I was not aware of this! Thanks for bringing it to my attention. I always did find it strange that the configs repository hadn't found its way over to the ASWF domain.

I think it's a good idea to link to @KelSolaar 's configs from the OCIO website for visibility (especially since these are shipping with DCCs like Nuke), but I think the link should be added in addition to the OpenColorIO-Configs repo, rather than replacing it, with a note that Thomas's fork is where to find these specific ACES configs.

My other comment is that if you want this to appear on the current website, you'll need to submit a PR against the RB-1.1 branch, which is what currently sources the website.

I will make that change, and thanks for the clarification on how the repository is structured. I'm very much looking forward to OCIO v2, a huge shoutout to the everyone working on it for the hard work they've done. It's been amazing for this industry.

@KelSolaar: I've been using it seemingly without issues, but I wonder if anybody with more knowledge/experience has been able to test it in a more thorough fashion across their pipeline. Have you gotten any feedback on it since you initially tagged it?

@omenos omenos closed this Apr 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants