OCIO not loading in CMD - aerender

[cbialk]

Aerender isn't able to see the default ACES configurations when rendering. I am not sure if this behavior is specific to AE 24.5, but I am fairly positive I have been able to render like this before.

Windows 11, AE 24.5

[James353933142jx0]

This is still broken (even in v24.6.1)

24.3 apparently still works:
https://www.reddit.com/r/AfterEffects/comments/1efwh0p/afx_245_render_ocio_error/

[ericmlevy]

AERender.exe says

WARNING:After Effects warning: After Effects is unable to fetch an OCIO Configuration as the file is not recognized (ACES 1.3 Studio v1.0). This project will be switched to Adobe color management.

😞

[Földváry29780652rs5u]

I was just about to report a similar bug, but I see it has already been reported. We are experiencing exactly the same issue. I would like to add that it works with version 24.4.1 as well, but not beyond that. Where can this be reported at a higher level? 🙂

[Földváry29780652rs5u]

I was just about to report a similar bug, but I see it has already been reported. We are experiencing exactly the same issue. I would like to add that it works with version 24.4.1 as well, but not beyond that.

[Földváry29780652rs5u]

We are using After Effects. For large-scale rendering, we use Deadline as the render manager. A problem has arisen where, if we use the ACES 1.3 Studio color space, renders submitted to Deadline will only be rendered correctly on machines running After Effects version 24.4 (or lower). On machines with a higher version of After Effects, even the latest version (24.6.1), we receive the following message: (After Effects warning: After Effects is unable to fetch an OCIO Configuration as the file is not recognized (ACES 1.3 Studio v1.0). This project will be switched to Adobe color management.) Despite this, the render is completed, but incorrectly. We also tried using ACES 1.2 color space and Custom ACES config, but the same error occurs every time. The aerender is unable to recognize the color space, which is odd because if I open the project on these higher-version machines, it renders ACES 1.3 without any issues.

I'm not alone with this problem. I've seen many posts here on the forum dealing with the same issue. It would be great to resolve this as soon as possible, as we obviously want to use the latest version of After Effects in our daily work, and not randomly test different versions to see which one works already.

[Rick Gerard]

Render Garden was made in 2017. It was great for several years, but if you try to download it or click on the links, it has been discontinued.

A few years ago, when it was still working with one of the later versions of After Effects, I ran some tests, and there was little or no improvement because of the GPU acceleration that AE now has. Unless the developer rebuilds the product, I don't think it will work with the latest versions of After Effects.

[ericmlevy]

Yeah, I know, but it’s what I use to render in the background while I’m
working.

[Rick Gerard]

With the latest builds, you can render as fast or faster using the Adobe Media Encoder. 

There is little hope for an update on Render Garden. 

[ericmlevy]

Agreed, they're not going to update RG. Id still like AE to be compatible with aerender.exe. This isnt a RG bug, really.

Do you render in the BG with Media Encoder? Can you throttle down tbe amount of cores it uses?

[ericmlevy]

Same. Annoyed.

[JohnColombo]

Hi all,

Thank you for reporting this issue. We are also able to reproduce this failure when rendering through arender using the ACES 1.3 Studio v1.0 OCIO config. A ticket has been opened for our team to investigate a fix.

For now, rendering via 24.4 should be unaffected by this issue.

We are only seeing the failure occur on Windows—are all of you using Windows as well when you encounter this issue?

Thank you again for reporting this issue. We will update this post as soon as a fix becomes available for testing in the public Beta builds.

- John, After Effects Engineering Team 

[ericmlevy]

Windows here. Thanks for looking into it.

[ericmlevy]

If you figure out a hacky fix, like adding something to the commandline prompt or using a previous version of AE Render, that would helpful, because not being to background render on this job is a problem. Thanks!

[Adam24634998sedo]

Re: "aerender.exe  WARNING:After Effects warning: After Effects is unable to fetch an OCIO Configuration as the file is not recognized. This project will be switched to Adobe color management."

Summary of testing various recent versions, including latest betas as of 9/17/24:
(Note: OS Name: Microsoft Windows 10 Pro for Workstations, OS Version: 10.0.19045 N/A Build 19045)
aerender version 24.4.1x2 *works* (as @JohnColombo noted)
aerender version 24.5x52 (fails)
aerender version 24.6.1x2 (fails)
aerender version 24.6.2x2 (fails)
aerender version 25.0x29 beta (fails)
aerender version25.1x9 beta (fails)

Additional details and tests, including pointing to a custom config, just in case that was a workaround (didn't work):

This persists for me in aerender version 24.6.2x2, also. Looking forward to a fix. Will look to roll back on the render farm to 24.4.1x2 meanwhile.

aerender version 24.6.2x2
PROGRESS: Launching After Effects...
WARNING:After Effects warning: After Effects is unable to fetch an OCIO Configuration as the file is not recognized (ACES 1.3 Studio v1.0).
This project will be switched to Adobe color management.

I can also confirm 24.5x52 presents the bug:
aerender version 24.5x52
PROGRESS: Launching After Effects...
WARNING:After Effects warning: After Effects is unable to fetch an OCIO Configuration as the file is not recognized (ACES 1.3 Studio v1.0).
This project will be switched to Adobe color management.

I can also confirm 25.0x29 beta presents the bug:
aerender version 25.0x29
PROGRESS: Launching After Effects...
INFO:After Effects (Beta): this project must be converted from version 24.5 (Windows 64). The original file will be unchanged.
WARNING:After Effects (Beta) warning: After Effects is unable to fetch an OCIO Configuration as the file is not recognized (ACES 1.3 Studio v1.0).
This project will be switched to Adobe color management.

As @JohnColombo suggested, I can also confirm 24.4.1x2 works and does not have the OCIO config load bug:
aerender version 24.4.1x2
PROGRESS: Launching After Effects...
(No OCIO Error)

As a test, in case it was just an issue with the built in configs, I manually overrode the OCIO config path in Custom directly to:
C:\Program Files\Adobe\Adobe After Effects 2024\Support Files\OpenColorIO-Configs\ACES 1.3 Studio v1.0\\studio-config-v1.0.0_aces-v1.3_ocio-v2.1.ocio
But still receive the same error:
aerender version 24.6.2x2
WARNING:After Effects warning: After Effects is unable to fetch an OCIO Configuration as the file is not recognized (C:\Program Files\Adobe\Adobe After Effects 2024\Support Files\OpenColorIO-Configs\ACES 1.3 Studio v1.0\studio-config-v1.0.0_aces-v1.3_ocio-v2.1.ocio).
This project will be switched to Adobe color management.

Also, to rule out a .config file issue I pointed AFX to Nuke's config for ACES 1.3:
C:\Program Files\Nuke15.0v5\plugins\OCIOConfigs\configs\fn-nuke_studio-config-v1.0.0_aces-v1.3_ocio-v2.1.ocio
No change.
aerender version 24.6.2x2
WARNING:After Effects warning: After Effects is unable to fetch an OCIO Configuration as the file is not recognized (C:\Program Files\Nuke15.0v5\plugins\OCIOConfigs\configs\fn-nuke_studio-config-v1.0.0_aces-v1.3_ocio-v2.1.ocio).
This project will be switched to Adobe color management.

Also, in case it was a OCIO v1 vs v2 issue, I tried pointing it to ACES 1.2, same result:
aerender version 24.6.2x2
WARNING:After Effects warning: After Effects is unable to fetch an OCIO Configuration as the file is not recognized (ACES 1.2).
This project will be switched to Adobe color management.

[defaultjib4ubh3034w]

This is a major issue and needs a priority fix ASAP. This affects us greatly as a studio with countless adobe licenses.

[James353933142jx0]

Hi @JohnColombo  

Any update on this?  It's pretty fundamental to render pipelines that this is resolved ASAP.

Latest version is not working still. There have been a few version releases since 24.4, seems like ample opportunity to have merged in a fix?

Kind Regards,

James

[ericmlevy]

This was mission-critical for us, so I rolled back to the last working version. Pretty crazy this hasn't been patched yet.

[JohnColombo]

Hi all,

Thank you for your patience with this issue. A fix is now available in the latest Beta builds of After Effects 25.1—please download the Beta build and let us know if you continue to experience the OCIO error with aerender.

Thanks again,

- John, After Effects Engineering Team 

[cbialk]

I can confirm. It works in the latest beta. I tested it with an external OCIO profile, and the render was successful.

[Adam24634998sedo]

@JohnColombo, yes, I agree, the latest update to 25.1, 25.1x36 works, and does not present the error with aerender on OCIO config. I concur with @cbialk.
Note: the problem does exist in earlier 25.1 releases, like 25.1x9, that I'd tested on Sept. 17th. So be sure you're downloading the very latest 25.1x36+ (Adobe Packager for the Beta build won't necessarily recognize that a previous 25.1 package needs an update, so build a fresh one to be sure). 

Summary of testing various recent versions, including latest betas as of 9/17/24:
(Note: OS Name: Microsoft Windows 10 Pro for Workstations, OS Version: 10.0.19045 N/A Build 19045)
aerender version 24.4.1x2 *works* (as @JohnColombo noted)
aerender version 24.5x52 (fails)
aerender version 24.6.1x2 (fails)
aerender version 24.6.2x2 (fails)
aerender version 25.0x29 beta (fails)
aerender version 25.1x9 beta (fails)
aerender version 25.1x36 beta *works*(as @JohnColombo noted Oct 7th, and verified by @cbialk already)

[Adam24634998sedo]

@JohnColombo any chance we'll see a patch to 24.x, or will it only come with the release of 25.x at this stage? Thanks. 

[ericmlevy]

Glad to see you’re working on it, thank you. I can’t upgrade to beta
software in the middle of delivering shots, so I’ll stick with my downgrade.

[Adam24634998sedo]

@JohnColombo I may have spoken too soon on my verification of 25.1x36 on OCIO. While I didn't see the OCIO error immediately, which is positive, it is hanging for me at the command line now. And attempting to open the GUI I am getting an "After Effects (Beta) error: Crash in progress. Last logged message was: <26120> <IR.Initlpp> <5> ippInit warning: ippStsNonIntelCpu: The target CPU is not Genuine Intel". That error is a true statement, as my CPU is AMD Threadripper, but it's causing 25.1x36 to crash. So I suspect the OCIO is indeed fixed as reported, as I saw no error, but I neglected to notice AE crashed prior to the frame outputting in my haste to respond. 

[Adam24634998sedo]

25.1x40 beta works for me in AMD & Intel Windows 10 Pro systems, I'm *not* getting the OCIO failure in aerender.exe. And x40 doesn't present the crash I got in x36 on AMD. 

Summary of testing various recent versions, including latest betas as of 10/14/24:
(Note: OS Name: Microsoft Windows 10 Pro for Workstations, OS Version: 10.0.19045 N/A Build 19045)
aerender version 24.4.1x2 *works* (as @JohnColombo noted)
aerender version 24.5x52 (fails)
aerender version 24.6.1x2 (fails)
aerender version 24.6.2x2 (fails)
aerender version 25.0x29 beta (fails)
aerender version 25.1x9 beta (fails)
aerender version 25.1x36 beta Fatal crash for me on AMD, reports "Not genuine Intel". I'm unable to verify, but OCIO/aerender.exe works per @cbialk
aerender version 25.1x40 beta *OCIO works for me with aerender.exe*. This also seems to resolve the "Not genuine Intel" fatal crash I got on AMD Windows in x36, and it does not present the OCIO error in aerender.exe. 

[cbialk]

Yeah. FWIW, I've seen that "Genuine Intel" error mentioned before with Red Giant plugins. That's where I would first look.