TSC Meeting Minutes 2025-10-07

TSC Meeting Minutes 2025-10-07

OpenFX TSC — Meeting Minutes

Date: Tue, Oct 7, 2025 (monthly)
Duration: ~1:04

Attendees:
Gary Oberbrunner (Dark Star Systems), John-Paul Smith “JP” (Boris FX), Pierre Jasmin (RE:Vision Effects), Guido Veldkamp (Assimilate), Phil Barrett (FilmLight, joined during discussion), Peter Kovář (NetCinema Technologies), Christopher Weinberg (Limn)

Regrets / Unknown:
Paul Miller (Boris FX – Silhouette), Resolve/Blackmagic team


Topics & Decisions

  1. Conform extension (AKA names + conform action)

  • JP presented a proposal to let plugins supply “AKA” names for effects/params so hosts can map foreign timeline data (AAF/OTIO/FCPXML/etc.) to OFX, then invoke a conform action for plugin-side fix-ups.

  • Deliberately out of scope: keyframe interpolation (host best handles mapping from source).

  • Discussion covered OTIO as an optional, parallel path (e.g., OTIO plugin maintained by a vendor), but proposal remains host↔plugin only, independent of interchange format.

  • Decision: proceed with the focused proposal; hosts to review feasibility.

  1. Per-dimension alternate names / 2-D property need

  • JP needs a way to associate per-dimension AKA lists (e.g., X/Y/Z each with multiple foreign names).

  • Consensus: avoid a new 2-D property type; instead encode as one 1-D list whose length is (num_dimensions × num_alternatives), or provide dimension-indexed properties (e.g., AKA0, AKA1, …).

  • Action: JP to update PR accordingly.

  1. Clip & image metadata suite

  • Status check deferred (driver absent). Clarified that this is property-set based (enumerable properties with types), not parameters. Goal: plugins can query metadata cleanly.

  1. Parameter interpolation types

  • Pierre: implementation done and slated for next build; still needs a test/confirm round. This will be useful alongside conform (plugin can set interpolation during conform).

  1. Windows on ARM (ARM64 / ARM64EC / ARM64X) & plugin folders

  • Adobe is using Classic ARM (ARM64); ARM64EC is more complex and poorly supported across deps.

  • Resolve currently loads from existing locations (ARM64EC host); willing to look elsewhere if the standard defines it.

  • Direction: define a Classic ARM plugin folder; note ARM64X can carry both ARM64 + EC in a single binary (nice-to-have, harder for vendors).

  • NVIDIA/MediaTek ARM boxes discussed—no immediate spec changes required; keep watching.

  1. Color-management extension in Resolve

  • JP: Blackmagic indicated they’ll implement the new color-management mode; they mainly use their internal pipeline with OCIO as a bridge. No dates shared.

  1. C++ property checker / client layer (type-safe access)

  • Gary’s YAML-backed property definitions driving a new pick-and-choose C++ layer (type-safe props, helper for param definitions). Incremental test plugin in progress.

  1. Guests & ecosystem

  • Peter Kovář aims to revive legacy plugins on OFX; discussed HDR/format agnosticism and why OFX deprecates native YUV.

  • Christopher (Limn) shared stop-motion context; observing standards work for niche workflow needs.


Action Items

John-Paul Smith (Boris FX)

  • Update conform PR to support per-dimension AKA (either packed 1-D or AKA0/1/… per dimension).

  • Continue Resolve engagement for the conform feature and color-management extension (share outcomes with TSC).

Pierre Jasmin (RE:Vision Effects)

  • Coordinate with Paul Miller to deliver a build exposing param interpolation types; report test confirmation for merge readiness.

Guido Veldkamp (Assimilate)

  • Review the conform proposal from a host perspective; evaluate AAF/foreign-param mapping path and share feedback on host workload/UX.

Gary Oberbrunner (Dark Star Systems)

  • Draft/update guidance for Windows Classic ARM plugin locations and related doc changes.

  • Prepare short demo/status of the C++ property checker / metadata client for next meeting.

Peter Kovář (NetCinema Tech)

  • Share links on Slack to RED/Nikon OpenImageIO work; follow up with any OFX file I/O plugin questions.

All

  • Review the conform proposal text and leave concrete comments (host feasibility, plugin migration strategies).

  • Keep an eye on ARM hardware/toolchain evolution; note any blockers for CI and dependency builds.


Next Meeting

  • Tue, Nov 4, 2025 (note: US/EU DST changes will have just occurred; schedules re-align).