Academy Software Foundation Technical Advisory Council (TAC) Meeting - November 11, 2026

Join the meeting at https://zoom-lfx.platform.linuxfoundation.org/meetings/aswf?view=list&projects=aswf

Voting Representative Attendees

Premier Member Representatives

  • Alejandro Arango - Epic Games, Inc
  • Andy Jones - Netflix, Inc.
  • Chris Hall - Advanced Micro Devices (AMD)
  • Christopher Moore - Skydance Animation, LLC
  • Eric Enderton - NVIDIA Corporation
  • Gordon Bradley - Autodesk
  • Greg Denton - Microsoft Corporation
  • Jonathan Gerber - LAIKA, LLC
  • Kimball Thurston - Wētā FX Limited
  • Larry Gritz - Sony Pictures Imageworks
  • Mark Wiebe - Amazon Web Services, Inc.
  • Matthew Low - DreamWorks Animation
  • Michael Min - Adobe Inc.
  • Michael B. Johnson - Apple Inc.
  • Rebecca Bever - Walt Disney Animation Studios
  • Scott Dyer - Academy of Motion Picture Arts and Sciences
  • Sean Mcduffee - Intel Corporation
  • Ted Waine - Double Negative Limited
  • Youngkwon Lim - Samsung Electronics Co. Ltd.

Project Representatives

  • Carol Payne - OpenColorIO Representative
  • Cary Phillips - OpenEXR Representative
  • Chris Kulla - Open Shading Language Representative
  • Daniel Greenstein - OpenImageIO Representative
  • Diego Tavares Da Silva - OpenCue Representative
  • Jonathan Stone - MaterialX Representative
  • Karen Ruggles - Diversity & Inclusion Working Group Representative
  • Ken Museth - OpenVDB Representative
  • Nick Porcino - Universal Scene Description Working Group Representative

Industry Representatives

  • Jean-Francois Panisset - Visual Effects Society

Non-Voting Attendees

Non-Voting Project and Working Group Representatives

  • Alexander Schwank - Universal Scene Description Working Group Representative
  • Anton Dukhovnikov - rawtoaces Representative
  • Daryll Strauss - Zero Trust Working Group Representative
  • Eric Reinecke - OpenTimelineIO Representative
  • Erik Strauss - Open Review Initiative Representative
  • Gary Oberbrunner - OpenFX Representative
  • Jean-Christophe Morin - Rez Representative
  • John Mccarten - Rongotai Model Train Club (RMTC) Representative
  • Jon Lanz - MoonRay Representative
  • Josh Bainbridge - OpenQMC Representative
  • Philip Grobler - OpenAssetIO Representative
  • Sebastian Herholz - Open Path Guiding Library (OpenPGL) Representative
  • Stephen Mackenzie - Rez Representative
  • Tommy Burnette - Dailies Notes Assistant Representative

LF Staff

  • David Morin - Individual - No Account
  • Emily Olin - Academy Software Foundation
  • John Mertic - The Linux Foundation
  • Yarille Ortiz - The Linux Foundation

Other Attendees

  • James Uren - Mo-Sys / OpenTrackIO
  • Randy Packer - Dreamworks / Moonray
  • Jim Helman - MovieLabs / OpenTrackIO
  • Andrew Pearce - Dreamworks
  • Doug Walker - Autodesk / OpenColorIO
  • JT Nelson - Pasadena Open Source consortium / SoCal Blender group
  • Lee Kerley - Apple
  • Sam Richards - Open Review Initiative
  • Victor Lu

Meeting Assets

Antitrust Policy Notice

Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

Agenda

  • General Updates
  • Add Guide #1105
  • TAC Vice Chair 2027 #1551
  • New Project/Working Group Proposal: New Project Proposal - OpenTrackIO #1184
  • Annual Review: OpenTimelineIO #477
  • AGENDA TOPIC ASWF Project Health & Resource Framework #1377

Notes

  • OpenTrackIO #1184
    • Jim Helman: CTO MovieLabs, SMPTE Virtual Set WG
    • James Uren: Mo-Sys
    • Jim Geduldick: SMPTE RIS
    • Presentation Slides
    • Previous version or presentation was given a while ago
    • Has been stuck in admin back and forth for 12 months
    • Meeting / working on project in the background
    • Refresher presentation
    • Agenda
      • Background
        • Development and current state of OpenTrackIO
      • Proposal
        • Transition of the software associated with OpenTrackIO to ASWF
      • SMPTE and ASWF
        • Responsibilities and migration considerations
    • Virtual Production
      • On-set Virtual Production (VP) is an umbrella term for real-time VFX spanning:
        • Augmented reality
        • Chroma Key (live broadcast and simul-cam for on-set VFX pre-viz)
        • In-camera visual effects (ICVFX) extended reality (xr for LED set extension), and other Mixed Reality (MR) combinations
      • VP requires live accurate camera tracking and lens modelling to align the real world with the virtual every frame
    • Problem
      • Knowledge about metadata formats was encoded in spreadsheets, turning it into a ‘standard’ / set of guidelines and tools that will allow modelling the camera and the lens and transmit it in a standardized way into a graphics system for VP
      • “Wild West” VP: Before OpenTrackIO, no open standard for VP metadata existed, resulting in many different communication protocols needing to be wrangled on-set and in post
      • Metadata Producers: in the absence of any standard, lens, camera and tracking system manufacturers develop and maintain their own bespoke protocols
      • Metadata Consumers: real-time render engines and post-production tools must support multiple protocols
      • Adoption: Software tools and reference implementation are required to encourage wide adoption by producers and consumers. Started to write tools, check into GitHub
    • Current Status
      • OpenTrackIO is an open standard for real-time on-set virtual production metadata
      • It was developed by the SMPTE RIS OSVP group and v1 published in January 2025
      • The specifications can be found at SMPTE RIS CamDKit Specification
      • (The spec and associated web page is generated by RIS’s CamDKit)
      • OpenTrackIO uses the OpenLensIO mathematical model, also developed by RIS members
      • OpenTrackIO support has been implemented in Unreal Engine since 5.6 (mid 2025)
      • Protocol is now supported by Canon, Sony, Mo-Sys, Pixotope, Stage Precision, Aximmetry, Disguise, Chaos Arena and maybe more
    • Create an Open Source Space
      • For libraries, tools and reference implementations
    • Initial Contributions (Confirmed)
      • SMPTE RIS will migrate their Python API, examples and generator tools to this space
        • Mo-Syc C++ API and data simulator
        • Pixotope OpenLensIO reference implementation for image generation
        • Epic Games “Live Sender” tool
    • Future Contributions
      • Improved OpenLensIO …
    • Relationship with SMPTE
      • Maintenance and extensions to specification require the involvement of a quorum of industry .
      • SMPTE RIS group continues …
    • SMPTE
      • Define the Standard
        • Industry experts define what is …
    • Summary
      • OpenTrackIO is a big step forward
    • Q&A
      • JF: license and spec? Spec is under MIT, not a SMPTE standard per se, RIS is more informal. As for as license for code, likely Apache 2.0. The files that are coming from SMPTE would be re-licensed under Apache 2. James: only a handful of files from that repo. James: Agreement from other partners to use that license.
      • Eric: a big fan of the effort! This designs the schema of the data and how it moves around, but there’s how it’s placed in container formats. At SIGGRAPH Open Source Days Sony presented ideas on how lens metadata can live in OpenEXR, but how can it be enriched. Have you thoughts about standalone container formats, just attaching to OpenEXR may not make sense if you have more than per-frame sampling rates. Also any thoughts on places to put extended metadata that doesn’t map into common schema, such as proprietary metadata. James: based on JSON, open to adding fields, would much prefer that there was a lot of proprietary fields in OpenTrackIO packets, but you can throw away components you don’t read / want in JSON. OpenTrackIO support multiple sync and timestamping, so can run at different frame rate than basic video frame rate. But you can’t have an irregular frequency, designed to be a streaming protocol. For containerizing, one of the ref implementations is raw UDP, very low level. But we also working on a RTP container, which leads to potential SMPTE 2110. This is not a file container, this is streaming data. For storing in a file, up for grabs. We’re very interested in what Sony is doing with OpenEXR, and could be a layer in a OTIO timeline since you have timecoded data. Also potentially want to cut this data into an edit, since you are rendering sequences of camera takes, makes sense in a camera container. Interested in exploring all these options. Eric: my perspective is colored by the editorial to VFX / conform propagation. James U: hopefully metadata lives through the production pipeline. Want the metadata to last as long as possible. Camera and lens information live is useful downstream. Eric: at some point “metadata is data”, and that seems to be the case here. James: OpenTrackIO schema is really “data about metadata”
      • Sam: were you involved with the Stem v3 effort, or a future Stem project might include some of this data, end up with a library of good test data. James: one of the contributions is going to have a community of lens files, to help with calibration of lens files. Sam: was thinking about example data from a test shoot with OpenTrackIO data matching the rest of the VP data. Seems to live naturally in DPEL, but perhaps wasn’t part of StemV3? James: at Mo-Sys we have a sample data bundle to demonstrate. We have a plugin for Nuke, we could contribute one that supports OpenTrackIO. Sam: we can chat with Jim G, he may have some of that data. David: Stem3 built a movie, but the movie was done as a reference, the camera moves are captured the unreal engine scenes, but not done on OpenTrackIO. They could be processed to save as OpenTrackIO.
    • John: is this something we want to take to LFX voting, or wait until. Any concerns? JF: I think it’s a good fit. John: we’ll take it to a vote and get back to you.
  • OpenTimelineIO Annual Review
    • Eric Reineke, TSC chair for OTIO
    • Presentation Slides
    • Overview
      • TSC & Committer Updates
      • 2026 Themes
      • Ecosystem Update
      • Scorecard & Looking Forward
    • TSC & Committer Updates
      • Darby Johnston : TSC member
        • Number 1 contributer for last 2 years
        • Helped bring OTIO to cinesync play and KDEnlive
        • Countless quality of life improvements in the C++ core
      • Tim Lehr: committer
        • Led Dev Days prep for last two years
        • Shepherded AAF adapter
        • …
    • 2026 Themes
      • Modernization and cleanup (0.18.0)
      • Schema enhancements
      • Interchange in practice
      • CI infrastructure more stable
    • Schema Enhancements
      • 0.18.0
        • per track / per clip color
        • enabled flag on Effects
      • On-deck in main branch
        • Marker RGB colors
        • Enabled flag on Transitions
        • C++ otioz/otiod bundle support
    • Schema Development
      • Color Management
        • An effort spearheaded by Sam Richards
        • Identifies colorspaces and transforms in context of timeline hierarchy and informs color for various deliverables
        • Not designed to replicate what OpenColorIO or ACES do
        • Part of Color Interop Forum
      • Stream/Channel Mapping
        • A MediaReference is an opaque file today
        • No standard way to pick streams or channels: stereo “eyes”, 5.1 and stems, alternate languages
        • Proposal in 3 layers
          • Addressing: locate a stream in the container
          • Describing: StreamInfo adds meaning (“left eye”, “center”)
          • Selecting / mixing : StreamSelector, StreamMapper, AudioMixMatrix on a Clip
        • PR 2015
    • Interchange in Practice
      • OTIO AAF Adapter v2.0.0
        • Major rewrite of the reader code
        • new write features
          • Media embedding, transcribe hooks
          • Clip Color
          • Marker and data track roundtrip
        • v2.1.0 coming soon
        • Thank you Tim Lehr and Mark Reid!
      • OTIOZ core support
        • Single file delivery of a timeline and its referenced media
        • Suitable for archival use cases
        • Moved from Python to C++ core so all integrations can take advantage of it
      • Export Evaluation (Netflix)
        • Goal: can OTIO replace EDL for pulling the correct camera original media and frames?
        • Tested across NLEs: 7 timelines, 109 clips
        • Works Well
          • Timing was communicated more reliably in OTIO than EDL, 100% of the time
        • Needs work
          • Reel / tape name and CDL need more consistent communication across implementations
          • Format-level work in progress to address both: logging/source media…
    • Vendor Adoption
      • Premiere Pro 2026
        • OTIO import / export
      • Now shipping with native OTIO support
        • FilmLight
        • Adobe: Premiere Pro
        • Autodesk: RV / OpenRV, Flame
        • AVID: Media Composer
        • Colorfront: Transkoder
        • DNEG: xStudio
        • Foundry: Nuke Studio and Hiero
        • ftrack: cineSync Play
        • RODE: RODECaster Video Core
        • KDEnlive
    • Contribution Health
      • 37 Active Contributors, up a bit
      • Number of contributions looks less health: within LFX dashboard we include all the repos, including adapters, Raven (OTIO viewer), Toucan (OTIO renderer). Compared 2025 to 2026 contributions, OTIO core is pretty steady, big peak last year was flurry of getting these other projects bootstraped. These other projects have reached steady state. But would be nice to see uptick.
      • Leaderboard
        • Darby Johnston is top, but not bootstraping Toucan this year
        • Top 2 contributors is 60%, would like to see better distribution
        • But we have other contributors
    • Dev Days Contributions
      • 9 issues and pull requests labelled DevDay2026
      • …
    • AI Assisted Contribution Policy
      • Based on OIIO policy
      • Loosened disclosure policies
        • We worried they might penalize good actors but not effective against bad actors
        • Advocate that people disclose in their PR descriptions
        • Avoid haveing to rewrite commit history
      • Already seeing some really good AI-assisted contributions
    • What we said we’d do
      • Scorecard against our 2025 review
      • In progress: Calling ourselves 1.0
      • In progress: More requirements for ASWF adoption
      • Identify where …
    • 2027 Focus
      • 1.0 and ASWF Graduation (hopefully in a couple of months)
      • Deliver in progress schema enhancement
        • Audio mixing / channel mapping (PR open)
        • Color management (in progress)
        • Logging metadata : tape / reel name, slate number (in progress)
        • Delivery targets (in progress)
      • Plugfest : OTIO interchange testing
      • Publish “golden” reference files and media
    • Questions:
      • JF: more recent release stamps would be good. Eric: we’ve discussed how to increase our release cadence, our release process is pretty heavy, but we’re trying to automate them.
      • Michael: does OTIO have to look at legality of materials / ingest, in California have to deal with provenance data for mix of AI vs non-AI data. Any thoughts of dealing with that? Eric: Buzz Hayes from Google at Open Source Days proposed a schema for carrying that data in OTIO. Would be great if Premiere in OTIO export could adopt that schema. Include prompts, models. There’s the disclosure aspect, but also as an editor, need access to the tools. And at Conform / VFX Pull stage, knowing that a clip was generated in HD / Rec 709 for instance, useful to know. Michael: hopefully have the whole provenance / history. Eric: if you know someone who is strong in that area and would like to take the lead in schema developement, we’d be very happy to collaborate.

Next Meeting Agenda

  • General Updates
    • AGENDA TOPIC: agent skills repo #1467
    • AGENDA TOPIC: GitHub Security Manager role #1434