Attendees

• Pierre Jasmin (RE:Vision), JP Smith (Boris FX, Mocha), Guido Veldkamp (Assimilate), Mikki Wells (BorisFX), Gary Oberbrunner (Dark Star Systems, arrived late), Dennis Adams (Sony), Joshua Minor (OpenTimelineIO), Rohit Gupta (Blackmagic Design), Vivek Vedagiri (Blackmagic Design), Fu Qian (Blackmagic Design), KimHuat (Blackmagic Design), Peter Pakulski (Blackmagic Design), Qiu Ya (Blackmagic Design), Alexandre Bizeau

Agenda

• Website update progress report 

• CI and Conancenter

• Ticket triage and code review

• SIGGRAPH Virtual Town Hall speakers & content

• Pierre update on spatial issues

• Discuss PR #48 - optional functions in a suite

• Color updates

• GPU updates

• Effects metadata scheme: Resolve/OTIO as basis for OpenFX-compatible schema - Josh Minor

Future Agenda Items:

Minutes

Meeting called to order at 9am EDT

Organizational Matters

• Website update: design drafts complete; working on news section and "how to contribute"

Technical Matters

• Discussion of color, led by J-P

  • Rohit & Vivek will look at what J-P did (PR #103 on github, press borisfx branch on top), maybe look at:
    https://github.com/AcademySoftwareFoundation/OpenColorIO-Config-ACES/releases/tag/v0.2.0

  • Possibly add a custom mode which assumes linear and passes the colorspace triangle in CIE 1931 observer map primaries and white point location.

  • It was suggested by the Blackmagic folks not to use ACES only; its penetration is very low at the moment

  • How to give users basic color management support?

  • OCIO isn't designed for performance, says BlackMagic folks

  • They prefer a well-defined fixed list (AP0, SRGB, common color spaces, ACEScc, ACEScg)

    • camera space list will keep changing, so how can it be future proof?

    • What about ARRI LogC for instance -- people will want to work in camera spaces, but those are not standardized

  • We should version the color-space list, says J-P

  • Q from J-P: would the existing list in the PR cover most common cases?

  • Would custom with primaries & WP be better than using OCIO?

  • Prev version of this proposal used a basic OCIO "CG Config" -- as long as things are versioned this should be OK

  • J-P talked about the importance of "color space roles" e.g. "linear" to cover basic cases

• Website

  • Where should we put a newbie page? github, wiki, website? "Get Involved" button on site should link there, wherever it is

  • Are there ways to present tutorials, like slides?

  • Could be https://github.com/AcademySoftwareFoundation/openfx/wiki/Developer-FAQ

• BlackMagic folks are attending - thanks!

• OpenTimelineIO effect definition update from Joshua Minor

  • Ongoing conversation, but no progress on actual definition

  • Animation/keyframes specifically are worth discussing

  • Josh showed OTIO export from Resolve with effects with keyframes

  • Reviewed existing discussion

  • Q from J-P: how to use OTIO to help convert between other effects formats (AE, AVX) and OpenFX?

  • OTIO will start with basic effects and basics like coord spaces, keyframes, simple params

    • Then work on custom params, inputs, etc.

  • Next steps? Continue discussion. BMD folks can help with an initial implementation. Note that some companies use OTIO internally as well. Joshua will loop OpenRV folks in too.

  • https://github.com/AcademySoftwareFoundation/OpenTimelineIO/discussions/921

• Quick discussion of cmake & conan -- please review so we can merge it in

Misc

Meeting adjourned at 10:15am EDT

Meeting Recording is at here but it seems it failed to record properly.