2022-02-14

February 14, 2022

Host: Michael Dolan

Attendees: 

OCIO UX Working Group Meeting Notes

• UX Guidelines status:

  • Michael: In process of moving UX guidelines into wiki. Everyone involved has been busy, so not a ton of progress lately. I reached out for help in #docs channel in OCIO Slack after last meeting, but didn't get much response. Brian Cipriano, Chair of OpenCue, recently brought up the possibility of hiring a technical writer to work on ASWF project documentation. Could be an option to assist with this effort in the future. It's a challenge all projects face.

  • Evan: Could participate in Google Season of Docs: https://developers.google.com/season-of-docs

  • Joseph: Docs and problem on OpenEXR also. No normative docs of EXR compression algorithm prevented standardization.

  • Michael: For main OCIO docs we had a big push with a lot of help from community, and help from an Autodesk technical writer.

  • Doug: Grahame Fuller (Autodesk technical writer) helped with OCIO docs, and has provided feedback which we're still reviewing. I'm hoping to revisit OCIO docs in March.

  • Mark: Trying to take approach of documenting about UX problems we're encountering.

  • Doug: Also got good feedback from Christophe Brejon, who was working with app vendors implementing OCIO.

  • J: Worked with plugin vendors implementing OCIO, to help them understand things like menu families, to not have one large list of color spaces.

  • Michael: OCIO v2 provides a number of app helpers to ease UX integration, like ColorSpaceMenuHelper, which helps with color space menu management.

  • Doug: Requires work from config author, and once organized like that, menu helpers in API will simplify for app developer.

  • TODO: Talk to Brian Cipriano about technical writer topic.

• ocioview update:

  • Michael: Continuing work on ocioview POC, which will provide a tool to edit and analyze OCIO configs. Working on color space management currently, as a starting point.

  • Doug: Would be good to include menu helpers, for preview.

  • Mark: Good for validation too, to help show what it should look like.

  • J: Ever considered including configs in other configs?

    • Doug: Has been proposed, and would like to support it, but currently no support.

    • J: The process of applying color management to a full edit is daunting at the moment. Can we translate the standard for OCIO performance into DI and other real-time implementations? OpenFX plugins, etc.

    • Michael: We did look at faster float parsing implementations prior to the 2.1 release. Work initially intended to solve LUT localization issues, but resulted in better read performance too, which should postiively affect shot based look workflows.

    • Joseph: Wouldn't config include make version control more complicated? Would you generate a whole bunch of things consistently being included?

    • J: Want to avoid needing to bake configs for reviews. Configs are too complex to share. We could do scripting, but ability to merge and diff configs would be nice.

    • Doug: Would be great to have it.

    • Michael: OTIO deepcopy support is nice. would be cool to support that for config merging in OCIO Python bindings.

    • Joseph: For diff tool, would it make sense to incorporate into ocioview? Would be able to see and A/B wipe between renderings.

    • Michael: Yes, could explore that.

• OCIO build artifacts:
  
  

  • J: Interested in captured assets from builds. Ground truth implementation. Good to give to implementers.

  • Michael: Would just need to be limited in platform support.

  • J: Think that's ok. Having ground truth binaries would be nice.

  • Evan: Looked at doing that with vcpkg, but issue was still with OCIO and OIIO circular dependency.

  • ASWF has Artifactory account, but may be private, Can put artifacts in GitHub too, from CI builds, which include core lib, apps, and OpenFX plugins.