| |
|---|
Old OCIO V1 website | |
Multi-platform Python wheels | Zach PR to fix linux ARM wheels, noticed it was happening on OIIO Switching to ARM native runners seems to fix things Should we be testing linux ARM in the normal CI? On MAC, we’re making separate x86 & ARM wheels instead of universal, can cause limitations specifically with PIP - Autodesk found a workaround, but is anyone else experiencing this? Remi - we should be able to control the versions, can’t quite remember why we switched. Building universal in addition to specific won’t solve, as you can’t force it to download universal
|
Color Interop Forum update | Proposed: EXR Color metadata revamp / standardization |
ACES 2 Optimization Update | Kevin has almost finished getting his work to a stable, matching state between CPU & GPU to be able to create a PR Then the question becomes do we use Remi’s texture lookup fix for metal or for everything or not at all?
|
ACES 2 Configs | Small issue with views assigned to the displays Also in a bit of a random order, is that because of the spreadsheet order? PR: ACES 2.0 by KelSolaar · Pull Request #130 · AcademySoftwareFoundation/OpenColorIO-Config-ACES Let’s aim for having the configs ready by next TSC meeting In apps not using hierarchical menus, color space order is a bit random - if people have opinions on this, lets us know. Mostly driven by spreadsheet order. Blender is an example of this if folks want to test.
|