It’s a big day for Beta. In today’s Beta build (23.1.0 build 44), you are getting not just one, but two new features to take out for a test drive. Introducing native OCIO/ACES support in After Effects! I’ve attached documentation for a deep dive into the feature, including a Quick Start guide which is copied below. We would love to hear your feedback, including what you think of the workflow, and whether you get the results you expect. As always, thank you so much for participating! Quick start File > Project Settings a. Create an After Effects project and select Color Engine as OCIO color managed. b. Select the appropriate OCIO configuration file. i. We are shipping the ACES configuration ACES 1.0.3 with the application bundle. ii. NOTE on ACES 1.3 Configurations In addition to the default ACES 1.0.3 configuration, there are now two beta configurations from OCIO which are compliant with ACES 1.3 (ACES CG v0.2.0 (Beta) and ACES Studio v0.1.0 (Beta)). These are still under development, but they do include new features and enhancements setting the stage for ACES 2.0, such as the ability to set the Rules in the config file to an assigned color space. We will update these to the release 1.3 versions once they are available. c. Select a Working Color Space d. Select a Display Color Space2. Add some media (EXR, etc.) to your project a. Media Color Space is automatically assigned a default color space (specified by the default role) b. Media Color Space can be overridden via the Interpret Footage dialog accessed by right-clicking the footage in your Project panel 3. Create a composition a. Composition window shows color converted content i. Color conversion - Media Color Space to Working Color Space ii. Color conversion - Working Color Space to Display Color Space b. Use the Display Color Space dropdown in the composition toolbar to change which display transform you are viewing 4. Export the composition a. Add the composition to render queue b. Select the Output Color Space in Output Module Settings > Color dialog 5. Use OCIO Color Space Transform effect to apply any color space transform to your layer, especially if you need to apply an effect or CDL/LUT that was created in a different color space. 6. Use OCIO File Transform effect to apply a LUT or CDL to your layer. Make sure to change the color space using the OCIO Color Space Transform if required for that LUT/CDL, and then apply another transform to bring it back to the working space you are using.

Known Participant

Question

Welcome to native OCIO/ACES support in After Effects!

Forum|Forum|3 years ago
October 18, 2022
25 replies
29348 views

It’s a big day for Beta. In today’s Beta build (23.1.0 build 44), you are getting not just one, but two new features to take out for a test drive. Introducing native OCIO/ACES support in After Effects!

I’ve attached documentation for a deep dive into the feature, including a Quick Start guide which is copied below.

We would love to hear your feedback, including what you think of the workflow, and whether you get the results you expect.

As always, thank you so much for participating!

Quick start

File > Project Settings
a. Create an After Effects project and select Color Engine as OCIO color managed.
b. Select the appropriate OCIO configuration file.
i. We are shipping the ACES configuration ACES 1.0.3 with the application bundle.
ii. NOTE on ACES 1.3 Configurations
In addition to the default ACES 1.0.3 configuration, there are now two beta configurations from OCIO which are compliant with ACES 1.3 (ACES CG v0.2.0 (Beta) and ACES Studio v0.1.0 (Beta)). These are still under development, but they do include new features and enhancements setting the stage for ACES 2.0, such as the ability to set the Rules in the config file to an assigned color space. We will update these to the release 1.3 versions once they are available.
c. Select a Working Color Space
d. Select a Display Color Space2. Add some media (EXR, etc.) to your project
a. Media Color Space is automatically assigned a default color space (specified by the default role)
b. Media Color Space can be overridden via the Interpret Footage dialog accessed by right-clicking the footage in your Project panel

3. Create a composition
a. Composition window shows color converted content
i. Color conversion - Media Color Space to Working Color Space
ii. Color conversion - Working Color Space to Display Color Space
b. Use the Display Color Space dropdown in the composition toolbar to change which display transform you are viewing

4. Export the composition
a. Add the composition to render queue

b. Select the Output Color Space in Output Module Settings > Color dialog

5. Use OCIO Color Space Transform effect to apply any color space transform to your layer, especially if you need to apply an effect or CDL/LUT that was created in a different color space.

6. Use OCIO File Transform effect to apply a LUT or CDL to your layer. Make sure to change the color space using the OCIO Color Space Transform if required for that LUT/CDL, and then apply another transform to bring it back to the working space you are using.

Work_natively_in_ACES_in_After_Effects.pdf

Feature request

Show previous replies

SimonBjörk

Known Participant

Curious if there is access to any of the new features via scripting? If so, is there any documentation?

C

Christine24511803xxz8

Participating Frequently

Not yet, but stay tuned.

jackthegiantkiller

Inspiring

So does this mean that the ongoing issue with ProRes footage flickering when using certain color correction tools (namely Lumetri Color) has been addressed? I would really love to have this bug locked down and be able to turn "Enable hardware accelerated decoding" back on so I can use all the power of this maxed out M1 Macbook Pro.

Christine GoldbyAuthor

Known Participant

Hi @jackthegiantkiller . Unfortunately this OCIO work does not include the ProRes issue you mention here.

jackthegiantkiller

Inspiring

Ah, was worth a shot! Thought perhaps it was contingent on this build given the nature of it, thanks for the info.

Lars HAGLUND

Participating Frequently

Dear all,

I am testing Build 34.

Likely has someone else already asked for this, but please:

Add all the ACES-based "Inverse Display Color Spaces" under "Interpret Footage";
Add all the ACES-based "Inverse Display Color Spaces" under "Input Color Space" in the OCIO Color Space Transform FX;
Add all the ACES-based "(Forward) Display Color Spaces" under "Output Color Space" in the OCIO Color Space Transform FX;
Add an "OCIO ACES 1.3 Reference Gamut Compression" FX;
Add an initially enabled "ACES 1.3 Reference Gamut Compression" under "Interpret Footage" with a manual disabling possibility;
Allow the Viewer to communicate with Apple's ColorSync, based on the chosen ACES-based Display Color Space, in order to give a MacBook Pro (year 2021 and later) the possibility to display calibrated >10-bit HDR (both P3-D65 gamut and Rec.2100 gamut must work) and calibrated SDR.

Thanks in advance,

Lars

Lars HAGLUND

Participating Frequently

In addition, please:

In Project Settings, add a separate "Default Media Color Space Interpretation" where the "aces_interchange: ACES2065-1" would be set up by the company I work for - while other companies (internally) may interchange "ACEScg" (although confusing/dangerous between external companies).

For the moment, Build 34, when having ACEScg chosen as Working Color Space, all incoming ACES2065-1 EXRs are wrongly interpreted as ACEScg. It is much too easy to forget to manually change that in "Interpret Footage" if being stressed, because the only, but important, difference is the AP0 versus AP1 gamut interpretation.

Kindly, Lars

Christine GoldbyAuthor

Known Participant

@Lars HAGLUND , thanks for your suggestions, we'll add your votes to the requests. A question for you, the drop-down lists you are referring to in Interpret Footage and Input or Output Color Spaces are all populated off the OCIO configuration file that you choose in the Project Settings. In your first few suggestions above, are you saying you would prefer to see all available spaces beyond what your chosen config includes?

D

Dino Muhic

Participant

Here is one problem I have:
I'm on 23.2.0 Build 34
Settings:

Now I go to a website and use Shift+Win+S to create a screenshot of something from the web.
Say this website: https://www.pexels.com/de-de/foto/brown-mountains-2559941/

I save this using the Windows Snipping Tool as a PNG file (attached)

I add this to my AE Project and put it into a comp.
I interpret it as Matte Paint RGB or color picking RGB Texture like this

And the result is way too dark compared to the actual image:

If I instead set the display to RAW and Preserve RGB the texture interpretation, I get the same result as my screenshot, but then of course everything else thats actually ACES looks wrong in the Viewport.

So thats a no-go.

What to do in this case?

J

justins29082732

Participating Frequently

Glad to see it's not just me with this issue. I posted about this a couple months ago and tagged as a bug. Don't know if Adobe is following other threads or just this main one for the beta. Seems like all their responses are only in this thread. Anyway, I'll link to my original bug report.

https://community.adobe.com/t5/after-effects-beta-bugs/ocio-aces-interpretting-a-png-image-with-utility-srgb-texture-yields-incorrect-results/idc-p/13283929#M265

C

Chetan Nanda

Adobe Employee

Hi @justins29082732 , @Dino Muhic ,

Thanks for reporting the issue with PNG rendering.

We are able to reproduce the issue and fix is available. We will be pushing the new Beta with the fix soon.

I will update here once the beta is available for testing.

Shebbe

Community Expert

Two months have passed since initial beta launch and the only update we've seen so far was the simple replacement of the ACES release candidate config file with the release config file. There have been plenty of suggestions made on improvements and notes of lacking features in efforts to make OCIO work as smoothy as possible. Can we expect anything on this front with more room for feedback whilst in beta? What is being considered, and what isn't (if so with which reasons)? I feel like there isn't much back and forth going on. Little response on a technical level and no views on the implementations from Adobe's side for us to better understand current states and plans. Will it drop out of the blue in a release version as is?... I hope we still have time to work this out together as that is what a beta is for. Maybe it's the holidays holding you back on activity but I would love to have this be more of an open conversation rather than the occasional "Thanks, I'll add your request to a list."

Christine GoldbyAuthor

Known Participant

Hi @Shebbe . There has been a lot of work happening behind the scenes. We have also had a number of holiday and time off breaks across the team, and even for beta we won't send work until we know it won't cause problems. That menas we have to make sure testing is completed before it is posted. But we do have a number of updates that will be coming out very soon. In fact I believe one of the team members responded to you earlier today with one he would love for you to have a look at.

I do want to note though that it is also not a guarantee that we will be addressing all feature requests before the first version of OCIO support ships. We will be doing our best working with the beta group here to make sure we are building the most functional tool for the most people to begin with, and then continuing to work on it after it is out in the wild. So thank you for continuing to send your feedback, it is all being listened to and looked at, even if it cannot all be addressed right away.

Shebbe

Community Expert

Thanks @Christine Goldby!

I see @Chetan Nanda's reply now. Must have gone completely under my radar. I'll have a look at it tomorrow! Thanks for also explaining a bit more about the current status and confirmation that all is being read and taken into consideration. Looking forward to more updates to try out.

Dan Sturm

Participant

This is super exciting, so thank you for this.

Do you have any plans for a setting to adjust clip/comp thumbnails in the project window? Currently, when using the OCIO workflow, the clip is linearized so the thumbnail is so dark it's basically unviewable (attached). I think other apps often include an option to use a lut on the thumbnails? Also, if this is already in the app somewhere, I apologize, I get lost settings easily.

Secondly, it looks like the Display Colorspace of "P3-DCI" matches Nuke and Resolve's "P3-DCI D60 simulation". I don't mind that you don't also have the D65 simulation as an option, but it might be worth noting which version we're using?

Dan Sturm

Participant

Also, this may be a lot to ask for an intial release / counter to the way AE wants to work, but I would personally love it if the media colorspace settings were in the project context menu, rather than inside of "interpret footage". I know I can "remember" and then "apply" the interpretation across multiple clips, but that affects more than just the colorspace settings and it feels like an antiquated way to set color on a bunch of things at once. It would be much easier if we could just select everything, right click and set colorspace from the context menu.

moebius90009

Known Participant

A good Tutorial about the whole stuff? I hope it's accurate 🙂

https://youtu.be/5nVbAJd1R_4

kudos to i_go_by_zak

NamrataAgrawal

Adobe Employee

Hi, We have replaced the beta config file (ACES CG v0.2.0 (Beta) and ACES Studio v0.1.0 (Beta)) with the release v1.0 (ACES CG v1.0 and ACES Studio v1.0).

New changes are available from Beta build (23.1.0 build 60).
Please give them a try and keep sharing all your feedbacks.
Thanks.

Shebbe

Community Expert

Thanks for the updated configs. I have a small point about the names. If the idea is to have multiple ACES configs in release all should have a clear naming convention. I know the studio/cg configs are versioned but the ACES version itself is now missing from the folders and thus in the list in the selection. Consider naming these too and if you think it is too confusing to have 2 times a version number I'd remove the package version not the ACES versions, because that is much more important to know the differences. Especially if ACES 2.0 will also sit alongside it when it releases.

I'd do it like this:

F

Filip26812379jdvc

Participating Frequently

So this happens.

After inspecting the file - those are pixels where one of the channels has a negative value.

During the normal workflow with the OCIO plugin - they just get converted to 0s, and that particular background is just black. But the new OCIO CM makes these pixels glow like a christmas tree 🙂

Shebbe

Community Expert

With which config is that happening? Did you test with the same config loaded on the fnord OCIO plugin?

F

Filip26812379jdvc

Participating Frequently

Both 1.03 and 1.2. It is not happening with the same config and fnord plugin.

J

justins29082732

Participating Frequently

@Christine Goldby In your attached documentation, you'll need to adjust the bit depth in your Project Settings screenshot from 8-bit to 32-bit in order for ACES to work properly.

Thanks team. Been waiting a long time for native OCIO and am excited to test this out thoroughly.

Christine GoldbyAuthor

Known Participant

Ack! Good catch @justins29082732 , totally right. We'll have to update that.

moebius90009

Known Participant

still not updated?

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded