November 15, 2021

Host: Doug Walker

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

  • Sergio Rojas

Apologies:

  • Michael Dolan, Mark Boorer, Mei Chu

OCIO TSC Meeting Notes

  • Review of PRs in progress:
    • Patrick summarized the progress on PRs #1496, #1515, #1516, and #1535 that are awaiting review.  #1535 fixes a bug related to LUT search path validation involving context variables.
  • Config Validation in the case of Context Variables:
    • Mark: We have recently encountered situations where customer configs which worked in OCIO v1 are failing validation in v2 if they involve context variables that are not set as expected during config validation.  The first reaction of users is that it must be a bug, since the config worked in v1.  Specifically, this often happens in the case of FileTransforms where the transform name uses a context variable.
    • Kevin: Yes, I've run into this too and needed to update our configs to make them forward compatible.  This often requires adding a no-op transform and filling in the environment section in the config to provide a default value to the context variable that selects the no-op.  An identity matrix transform is convenient to use for this purpose.
    • Several people made statements to the effect that OCIO v1 was arguably too lenient and the validation did not pick up some real errors.
    • Doug: The v2 validation is technically correct, but I agree it is a judgement call on some of the specific checks as to whether certain ones are more helpful than annoying.  If people find specific cases where they think the validation could be improved, please log an Issue and we'll discuss at a future meeting.
    • Mark: As more people start using OCIO v2 apps, we will probably hear this coming up as a fairly common experience.  Need to consider best approach to make it clear what the issue is.
    • Carol: There may be a rough period as people transition to v2, but hopefully the stricter validation will move us to a better place going forward.
    • Mark: It would be great to update the documentation to highlight this issue for config authors to be aware of.  I'll take a look at doing this.
  • Misc:
    • Doug: ACES is having their Architecture and Implementation TAC meetings this week on GoToMeeting.  These are open to the public, if anyone wants to attend, let me know if you need help finding the link.
  • No labels