Re: OpenColorIO stewardship


Mark Boorer <mark...@...>
 

Hi All,

Apologies Mark, I missed your previous request for an update, it's been a bit busier this year than I expected!

Andy, et al; As Haarm-Pieter put it, I am currently awaiting his final changes before I can merge his ACES 1.0.1 config into the repo. At the moment, the OpenColorIO-Configs repository is not versioned in lock step with the library, so I see no reason why this cannot go out immediately. Initially I'd had some reservations about the sheer size of the commits, and that the addition of other, non OpenColorIO related data would have an adverse effect on the usability / maintainability of the repository, but people seem keen to use this repo as a central ACES reference implementation, rather than just a place for OCIO configs, so I plan on putting it through in one go.

The current re-factoring work is regrettably still not finished, as my other day-to-day production tasks at DNeg have become more pressing of late. I have some time for dev work booked out in the coming weeks though, so hopefully I will have something more to show soon. My greater goal is to have everything out, feedback gathered, and tested before the SIGGRAPH 2016 deadline in order to make the changes available in the VFX platform for 2017.

In short, the ACES 1.0.1 configs will go out as soon as the final cleanup is done, and the library changes will be out for feedback hopefully not long after.

Cheers,
Mark

On Tue, Mar 8, 2016 at 8:26 PM, Haarm-Pieter Duiker <li...@...> wrote:
Hey Andy,

Here's an update from my side on the issue. After a bit of delay, Mark and the OCIO leadership have agreed to accept the pull request to integrate the ACES 1.0.1 config into the main OCIO configs repo. They have asked me to combine the commit history into a single commit before doing so, so the commit history for the general repo doesn't suddenly have a huge list of commits that won't mean much to most people. It's on my to do list. I'm also on a project that is barreling head-long towards a deadline this week, so that's taking precedence right now. I'm hoping to have the commits squashed this weekend so the pull request can be accepted.

Mark, correct me if that's not in line with your understanding.

HP




On Tue, Mar 8, 2016 at 2:37 PM, Andy Jones <andy....@...> wrote:
Bumping this, specifically WRT ACES 1.0 in the configs.  It would be great to get some kind of (hopefully short) timeline on that.  The configs in Nuke seem to be some ancient checkout of the examples, and we'd like to pressure them to bring them up to date for their next release.  We'd really like to see ACES 1.0 included in that update.  It seems like there's a chance Nuke might end up pulling from HP's github if the update doesn't happen soon, but I would imagine it's in everyone's best interest to keep everything pointed at the original repo.

If there's a big refactor of the configs going on for the major release mentioned above, perhaps it's worth making a branch and merging HP's ACES 1.0 config into master until that's ready?  Even if the configs are likely to need to change with the updates, it seems like places may need a legacy ACES 1.0 config for a while, until the future library makes its way into the apps.

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

Join ocio-dev@lists.aswf.io to automatically receive all group messages.