October 3, 2022

Host: Carol Payne

Secretary: Carol Payne

Attendees:

  • Rémi Achard (TSC) - DNEG

  • Mark Boorer (TSC) - Industrial Light & Magic

  • Mei Chu (TSC) - Sony Pictures Imageworks

  • Sean Cooper (TSC ACES TAC Rep) - ARRI

  • Michael Dolan (TSC) - Epic Games

  • Patrick Hodoul (TSC) - Autodesk

  • John Mertic - Academy Software Foundation / Linux Foundation

  • Carol Payne (TSC Chair) - Netflix

  • Mark Titchener (TSC) - Foundry

  • Carl Rand (TSC) - Weta Digital

  • Doug Walker (TSC Chief Architect) - Autodesk

  • Kevin Wheatley (TSC) - Framestore

  • Thomas Mansencal - Organization

Apologies:

  • Michael Dolan
  • Doug Walker

OCIO TSC Meeting Notes

  • OCIOZ PR:
    • Would appreciate some eyes very quickly on the review, so we can get it into the 2.2 release end of October 
    • Kevin has taken a quick look, will slack Doug a few questions before commenting on the PR
  • Remi's PR for ICC parametric curves, and a few other small ones - please have a look!
  • Mei is working on the OpenFX Plugin - not working out of the box on resolve 18
    • Remi was testing on Resolve 17
    • Make sure to build the plugin in static mode
    • Remi will provide links to previous discussions in this area
  • Latest artefacts from the Studio Config PR that includes ARRI/Canon transforms:
  • Foundry has untied the OCIO nodes from Nuke, they're in the Examples now!! Big win!
    • Bit more work to do before pushing them back to the repo, but great first step! 
  • Remi - using look transforms for the baker (ociobakelut), which doesn't currently support NamedTransforms. It should. Looking into it. 
  • Kevin - would like to have a good discussion around a possible file format to represent a colorspace transform (helpful for cases where there are multiple grading spaces on a project, etc)
    • CTF files are suggested for v2
    • Kevin is going to put together a few examples to start the discussion for next time. 
  • Overall discussion around OCIO's role in context variables for per-shot etc workflows. Might be time for us to take a stance here, in order to help software applications support some standards.
  • No labels