You'll need to ask the developer to update the app. Adobe has nothing to do with it. I don't use AERenderer, I use Render Garden and so far it is 100% compatible with all of my machines.
AE Renderer does not use the After Effects you are using to render, it opens a background copy. If it is only crashing on one version of AE and the Output Module, which also uses a background copy, and Dynamic Link through Premiere Pro work, then it is a problem with AE Renderer.
Let me clarify, as "crashing" is not the exact behaviour.
When After-Effects is opened in the background, and we set "-reuse" in the command, then aerender exits immediately while the application GUI starts the rendering. The behaviour is different than the previous version, in which -reuse also caused aerender to wait until the render is complete.
I hope the explanation is better now. Please let us know if that's a known behaviour/issue as we would like to upgrade as soon as it will be solved.
aerender.exe submits the job and exits immediately when using the "-reuse" flag. Previous behavior (e.g. AE 16.1.3) was to wait until the submitted job had finished rendering.
The submitted job does eventually render succesfully, but has to be tracked independently. This is an issue for automated pipeline workflows.
Hey Shani, any chance you also experiencing unexpected slow render times when job is being processed?
Put it in other words - with CC2020 version of aerender (17.x.x), it takes ages for project target comp to beging being added into the render queue, as well as frame render times is 10-15times more than in aerender 14.x.x
It seems that something has changed fundamentally in the logic of how aerender.exe works. In case you are experiencing anything similar - please get in touch thus we might be able to track it down together, as I am doing some testings to narrow down the issue, not yet successfully.
8
Replies
AdChoices