January 8th, 2024
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
- Zach Lewis (TSC) - Method
- Thomas Mansencal (TSC) - Weta FX
Carol Payne (TSC Chair)
Mark Titchener (TSC) - Foundry
Carl Rand (TSC) - Weta Digital
Doug Walker (TSC Chief Architect) - Autodesk
Kevin Wheatley (TSC) - Framestore
- Mark Reid
- Francesco Giardiello - Netflix
OCIO TSC Meeting Notes
- MacARM runners on GitHub Actions
- Github Actions now has Mac ARM runners - Larry already has this working in OIIO
- Issue to do something similar has been picked up by a new contributor
- Not running currently - check in with CI / Larry etc on how to get it running for OCIO
- Converting ACES Metadata Files (AMF) to OCIO configs
- We have a new contributor interested in improving the AMF support in OCIO
- We've had for a bit a python script that takes an AMF and produces a CTF of the parts not yet applied to the clip as a prototype
- Doug went through updates to that to instead ouput an OCIO config based on the AMF file given instead
- Would land in OCIO and include additions to the public API
- PR coming soon - definitely looking for input and feedback
- Mark B - still not sure we need this added to OCIO core - why is this getting the add vs. not other things
- Carol - not everything is need based dev - would love to be doing more future thinking and prediction of needed functionality
- Frankie - there is a lot of AMF dev happening in Netflix infrastructure now - seeing this ability in OCIO is very exciting
- Kevin - should be a standalone tool - or maybe AppHelpers? Need for discussion and use cases to fully think this through
- Doug - one way to think about a config return is not like a config for an artist or a pipeline - but whatever next processing or step you want to do from the result etc.
- Mark B - is there a reason this couldn't live in ACES dev / AMF repo?
- Remi - no real issues with having it in core, we already have ACES transforms built-in so this is another addition. But no real strong feelings
- Kevin: do we have resourcing, capability and desire to create something that reads and amf with ocio?
- Kevin: want this because of the benefit of an open source implementation, separate from OCIO or not
- Carol: in my opinion, we're way past this - we have discussed this feature in previous TSCs and working group meetings, we have a developer willing to implement and work on it, we just need to decide the right place for it to live in OCIO
- Mark - I disagree, don't want to bloat the library with things we shouldn't need to support or need in VFX workflows
- TODO: create issue, document the update to Doug's script and use that issue to document use cases and discussions
- New Github Label Descriptions
- Let us know if you have feedback on the label descriptions
- Kevin - do we need a C++ label
- Would prefer to not add labels that would get added to everything
- Do we need a won't fix label? Group will think about best way to handle this
- Added "tools" label to indicate command-line etc tools related issues
- Decide what to move forward with at next TSC
- ocioarchive - user experiences
- Kevin - when you run ocioarchive and it's not archivable, it still adds an empty file
- Would have been nice if ocioarchive tells you why it can't archive - more of a user experience thing
- it archives in a relatively unoptimised way - have we considered optimizing for what the exact config is using only?
- Doug - one of the reasons we implemented it to pull in everything is to handle the env var case - no way to really know unless user input is provided to help resolve
- Michael - likes the ideal of allowing user optimization flags - put it in their control/risk
- Doug - could be two tools - like an optimizer and an archiver
Overview
Content Tools