Attendees: Gary Oberbrunner (Dark Star Systems), John-Paul Smith (Boris FX), Pierre Jasmin (RE:Vision Effects), Guido Veldkamp (Assimilate), Mikki Wells (Boris FX)
Regrets/Unknown: Paul Miller (Boris FX – Silhouette), Resolve/Blackmagic team (not present), Phil Barrett (FilmLight)

• ASWF TAC representation: OpenFX should have a rep at every TAC (bi-weekly).

• ASWF Dev Days (mid-September): Opportunity to attract new contributors.

1. ASWF TAC (tomorrow)

   • JP’s calendar is tight; Pierre will attend as OpenFX representative and introduce himself as such.

   • Purpose: stay visible, share updates, avoid missing deliverables (annual report was late previously).

2. ASWF Dev Days

   • Mark issues as “good first issue” to attract students/indies.

   • Full mentoring track is possible but no bandwidth now.

3. Incoming PRs / “typo” bots

   • AI/code-cleanup PRs are OK if limited to comments/docs.

   • Vigilance required: JP spotted a suspicious/syntax-breaking change (CodeSpell artifact in OFXS/ImageEffect.cpp around line ~1319). Needs flagging/fix.

4. Windows ARM (OFX examples/build)

   • Need cross-compilation support (x64 builders → ARM64 targets).

   • Demonstrate builds for ARM64 (native), ARM64EC, and ARM64X in examples/CI.

   • Gary has recent CMake cross-compile experience; JP notes Adobe and others using similar CI.

5. Issue #116 – Param interpolation types

   • Paul is working/testing; Pierre to sync with Paul, then update the issue with current status (Fusion behavior noted).

6. PR/Issue hygiene

   • Everyone should review open PRs and stale issues; merge what’s approved.

7. Security/deps

   • Automated PRs pinning Python requirements for docs/build to address a vuln. Gary to review/merge as appropriate.

8. Thumbnail render / property proposals

   • Discussion ongoing; Pierre to add concrete notes in the relevant ticket to move it forward.

9. DaVinci Resolve engagement

   • Action at IBC: JP to raise participation with Resolve team; goal is more than the usual 1–2 touchpoints per year. Consider proposing quarterly/biannual time-zone-friendly syncs.

10. 3D Suite for OpenFX (exploratory)

    • Many hosts with 3D (Nuke/Fusion/Flame) require deeper integration; JP considering an NDK plugin for a 3D-dependent product.

    • Keep a running list of 3D needs/gaps that might inform a future OpenFX 3D suite (multi-year effort; 2027–2028 horizon if pursued).

    • Hybrid approaches (OpenFX UI + host-native calls) discussed; prior Python bridge patterns exist.

11. Color-managed color parameter

    • Renewed interest now that color management extension is stable.

    • Likely model: color param carries an explicit color-space tag; host controls UI/space, plugin converts as needed (akin to clip color-space negotiation).

    • JP to lead next steps toward a concrete proposal (scope: read/write semantics, roles/strings vs. OCIO mapping, user/UI considerations).

    • Wide-gamut/HDR workflows reinforce need.

12. Closed during call

    • The long-standing basic color-space issue was agreed to be not useful anymore → close.

• Pierre Jasmin

  • Attend ASWF TAC tomorrow as OpenFX rep; state affiliation, take brief notes, and report back to TSC.

  • Follow up with Paul and update Issue #116 (param interpolation types status, Fusion specifics).

  • Add comments on thumbnail/property ticket to clarify host/plugin testing expectations.

• John-Paul Smith (JP)

  • Flag/comment on the typo/CodeSpell PR with the stray/syntax-error change (~line 1319 in ImageEffect.cpp).

  • Comment on Issue #202 (render-fail flag for unlicensed): propose plugin returns a specific “unlicensed” status and may still watermark; host decides to fail early and report. Note pre-render/BeginSequenceRender path.

  • At IBC, engage the Resolve team re: OpenFX participation and possible regular syncs.

  • While scoping Boris’s 3D-dependent plugin, capture concrete NDK capabilities/gaps that could inform a future OpenFX 3D suite write-up.

  • Collaborate on examples/CI to demonstrate ARM64/ARM64EC/ARM64X builds.

• Guido Veldkamp

  • Check host behavior around pre-render/BeginSequenceRender (and “continue on errors”) to see how an “unlicensed” status could abort before frame renders; comment findings on Issue #202.

• Gary Oberbrunner

  • Follow up with Pierre about TAC attendance and ensure Zoom/link/details are good.

  • Progress the Windows build scripts (cross-compile and ARM64 variants) and plugin locations changes.

  • Continue work on Property Checker / Metadata C++ client library; share status when ready.

  • Review/merge dependency-pinning/security PRs (docs/build pipeline).

  • Merge any already-approved PRs; encourage reviews on outstanding ones.

  • For Unique Identifier / property and related issues: propose next concrete steps or close if superseded.

• All

  • Before ASWF Dev Days (mid-September): tag approachable items as “good first issue”, add brief onboarding notes where helpful.

  • Review open PRs/issues without comments; leave at least a triage note.

• OpenFX 3D suite: start a requirements doc (camera, transforms, scene IO, host bridging), socialize with host vendors; expect a multi-year track.

• Color-managed color param: produce a strawman spec (roles/strings, OCIO alignment, host vs plugin control, conversion responsibilities).

• In ~1 month (standard TSC cadence).

• Optional: schedule a Resolve-friendly quarterly sync in their time zone.