2021-06-14

Owned by Michael Dolan
Jun 14, 2021
3 min read

June 6, 2021

Host: Michael Dolan

Attendees:

Mark Boorer (TSC) - Industrial Light & Magic
Mei Chu (TSC) - Sony Pictures Imageworks
Sean Cooper (TSC ACES TAC Rep) - ARRI
Michael Dolan (TSC Chair) - Epic Games
Patrick Hodoul (TSC) - Autodesk
John Mertic - Academy Software Foundation / Linux Foundation
Carol Payne (TSC) - Netflix
Mark Titchener (TSC) - Foundry
Carl Rand (TSC) - Weta Digital
Doug Walker (TSC Chief Architect) - Autodesk
Kevin Wheatley (TSC) - Framestore
Simran Spiller
Rémi Achard - DNEG
Thomas Mansencal - Weta Digital
Sergio Rojas

OCIO TSC Working Group Meeting Notes

  • Summer (pre-SIGGRAPH, 2.1.0 release) goals:

    • TODO: Michael will setup GH project to track planned work for 2.1.0 release, targeting SIGGRAPH release.

    • Doug: Are some other items beyond current PRs, but not clear what's feasible. 

    • Michael: Planning on completing OFX nodes, and Imath 3 support. Imath support may be higher priority.

    • Patrick: OFX nodes won't impact ABI compatibility so can be updated later as well, but would be good to have in package.

  • Open source days coverage:

    • Michael: Should we give a smaller presentation than normal since we have a SIGGRAPH course? Focus on new features in 2.1.0 release?

    • Patrick: Good to discuss working groups and the work being done there. We've completed the v2 library. Next step is configs and UX. Not source code, but as important as library. Having right config for average user is almost as important as having library.

    • Carol: Also can give update on app integrations, and where we go from here.

    • Michael: Good points. Configs aren't tied to VFX ref platform so we can continue to work on the studio config after 2.1.0.

    • Carol: Since we have the ACES reference config and Doug's awesome example config, we have time to get it right.

  • PRs ready for review

    • OCIO PyPI support

    • Visibility flag improvements

    • GPU renderer improvements

    • ACES 1.3 support

    • Patrick: Most of these are good candidate for 2.0.2 if we want to have one. Visibility issues and DX11 bugs are a problem. Good to get those in.

  • GPU CI: 

    • Patrick: Having problem with certain PRs trying to complete GPU CI. Mechanism has started to have issue. Need. investigation.

    • Michael: Odd that this is happening, and only for some users, who I think all have admin rights. Issue is that GH secrets aren't available to forks, so GPU CI will fail. I have heard there may be support for that in the future, but we'll have to be careful if there is, to not overuse AWS. The workflow has conditions that it is only triggered on push, and when current repo is the main ASWF OCIO repo, and since these forks aren't within that, not sure what's happening. We could perhaps make the workflow conditions more strict. In the meantime, GPU CI is not a required check, so does not need to block merges.

    • Doug/Patrick: We can do local GPU testing where needed too.

  • Gamut compress PR:

    • Carol: Gamut compression meeting decided on naming. Keeping ACES in naming. Using parametric in name, and reference. Hoping to move on from naming to unblock OCIO PR. Will comment decisions on PR. In summary: FixedFunction → parametric, Builtin → reference.

    • Remi: Regarding discussion around range of parameter. Any decision on that?

    • Carol: No. Parametric transform will be a bit hidden from general user, so we can make our own decisions for now. A lot of decisions need to be made elsewhere for the long term. Trying to get reference implementation done first. Lots of discussion around what to call parameters, and how they should be presented to users and APIs. What should the ranges be, and should the parameterized transform start at no-op or default values. Might change per implementation, so we can talk about a sensible range for the near term in this PR. 

    • Kevin: Since it's hidden, suggest not imposing any ranges or arbitrary limits.

    • Carol: Will likely have change to handle the zero division case.

    • Remi: Maybe OFX plugin is a good opportunity to implement the parametric version of that.

    • Carol: Would be cool, once it's in config. Can look at parametric implementation in OFX. A couple other apps may hit that sooner (Resolve for example).

  • Items for next meeting agenda:

    • Finalize scope of 2.1.0 and make sure features are on track.