Beenden
  • Globale Community
    • Sprache:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티

State of OCIO, v2.5 and ACES updates

Community Expert ,
Oct 18, 2025 Oct 18, 2025

The links added refer to my old discussion and ideas posts on those topics.

 

I'd like to see OCIO platform being updated to the latest version which includes built-in ACES 2.0 configs.

I also want to stress again that ACES 1.2 should really be removed. By the time OCIO support was released it was already superseeded by ACES 1.3 which uses formula based transforms and there is no reason to keep these dependencies (430Mb of LUT files) in the installation and the config exposed to the user.  If users for whatever reason still want to use a legacy config they can download it themselves. LINK

 

Especially with ACES 2.0 it would be quite stupid to have 3 configs of ACES 1 still in the software making it a list of 5 configs... LINK

 

Also the ACES 1.3 configs should be updated to from

config-v1.0.0_aces-v1.3_ocio-v2.1

to

config-v2.2.0_aces-v1.3_ocio-v2.4

 

It would be nice in general to see more love for OCIO support in AE. It feels like a one time obligatory implementation that never gets looked back at. There are many remaining hurdles for professional workflows. Here's a list of the biggest ones.

 

- Lumetri Scopes cannot be switched between scene/working space and display space. LINK

- Color picker does not provide switchable scene/display color picking.

- Color square representation in the picker is color managed, I highly urgue that this is not what you want ever. It holds zero context. It should remain unmanaged.

- Composition viewer settings (including the OCIO view transform and display) are defined per composition. This is incredibly impractical if you work with OCIO. AE needs a user switch to make ALL comp window settings remain exactly the same regardless of which comp you open in it so it functions as you'd expect from a compositing software.

- The view transform and display are still combined into a single menu. This is terrible to navigate and not in line with how it should be presented. They need to be separated dropdown menus. LINK

- The view/display output setting in the color management window serves absolutely no purpose because the view/display is dictated by the composition and not the project setting. It should be removed.

- Input color space tagging is stupidly cumbersome. It should be accessible directly from the project panel. What you want is select a bunch of files, then either be able to click a dropdown in the preview area where it also states the input space, or via right-click and directly access it there in the menu. Now it's a separate settings window's second tab.... this needs change.

- The OCIO tools cannot be used in Adobe Managed context but there are many usecases for this to function. Please allow this including a project defined path + per effect user defineable. LINK

 

It would be welcome to see at least some movement here. There are plenty of people that would like to work with OCIO in AE but everytime I discuss the use of it with friends, colleagues or randoms from the internet, my only reply is, 'yea it's kinda dogsh*t' and then have to explain everything wrong with it and how to work around it. And it always ends up in, F it I'll just use the old fnord plugin.

THEMEN
Vorschlag für neue Funktion , Feedback
143
Übersetzen
Melden
Community-Richtlinien
Seien Sie freundlich und respektvoll, geben Sie die ursprüngliche Quelle der Inhalte an und suchen Sie vor dem Absenden Ihres Beitrags nach Duplikaten. Weitere Informationen
community guidelines
Neu hier ,
Nov 03, 2025 Nov 03, 2025
AKTUELL

Its a shame as alot of feedback regarding certain "features" which is my eyes should be basic feature are falling on deaf ears at adobe.

but lets keep concentrating on AI feature instead.....

Übersetzen
Melden
Community-Richtlinien
Seien Sie freundlich und respektvoll, geben Sie die ursprüngliche Quelle der Inhalte an und suchen Sie vor dem Absenden Ihres Beitrags nach Duplikaten. Weitere Informationen
community guidelines
Ressourcen