Skip to main content
brunop95489334
Inspiring
November 10, 2021
Answered

Aerender no Exit Code

  • November 10, 2021
  • 4 replies
  • 865 views

Hi there.

Been trying to use Aerender on backburner. Made a tool for AE to send jobs, everything works fine except when there is an error.

 

No matter what, aerender always return exit code 0, even when there are errors, so if there is a problem on a node, like, not finding a file, even though the verbose shows "aerender Error..." the exit code is 0 and backburner thinks it successfully rendered the task.

 

Is there a solution to this?

Thanks!

This topic has been closed for replies.
Correct answer brunop95489334

The batch did not solve it entirelly in the end...

In case anyone stumbles on a similar problem, I've solved it like so:

"c:\Program Files\Adobe\Adobe After Effects 2021\Support Files\aerender.exe" %1 %2 %3 %4 %5 %6 %7 %8 %9 > temp.txt
find /I "ERROR" temp.txt
if %errorlevel% equ 0 (exit 32) else (exit 0)

 

It writes the output to a temp file, then searches that temp file for the word ERROR, if it finds it exits with an error code.

There is probably a better way, but this worked for me Cheers

4 replies

brunop95489334
brunop95489334AuthorCorrect answer
Inspiring
November 17, 2021

The batch did not solve it entirelly in the end...

In case anyone stumbles on a similar problem, I've solved it like so:

"c:\Program Files\Adobe\Adobe After Effects 2021\Support Files\aerender.exe" %1 %2 %3 %4 %5 %6 %7 %8 %9 > temp.txt
find /I "ERROR" temp.txt
if %errorlevel% equ 0 (exit 32) else (exit 0)

 

It writes the output to a temp file, then searches that temp file for the word ERROR, if it finds it exits with an error code.

There is probably a better way, but this worked for me Cheers

brunop95489334
Inspiring
November 12, 2021

I was trying to solve this using the find and exit windows commands, like so:

"aerender <options> | find "ERROR" && exit 1"

So if there is an ERROR string in the aerender process, it exits with code 1.

 

It works in cmd, but I cant seem to make it work in cmdjob.

Maybe someone at autodesk will be able to help, or is there any hope for adobe to fix aerender?

Mylenium
Legend
November 11, 2021

Ah, I see. I think that's a known bug/ issue. If my failing memory isn't betraying me, I believe you can solve this by creating a batch file instead of calling up the command directly. Something with how the command strings are handed over by the system. Sorry to be so vague, there's just so many issues with AE lately and my brain all too often forgets stuff even if I read it just two days ago...

 

Mylenium

brunop95489334
Inspiring
November 11, 2021

Not at all! Thank you so much for the assistance!

Mylenium
Legend
November 11, 2021

You have to be much, much more specific like providing actual info about the render nodes, your network setup, the watch folders, render settings and whatnot. Of course some info from the various logs would help as well.

 

Mylenium

brunop95489334
Inspiring
November 11, 2021

Hi there, thanks.

I dont see why that matters.

Just running aerender through the windows cmd with a wrong path for example, or a wrong flag like "aerender \n", it will show a message like "aerender SYNTAX ERROR: Illegal argument flag: \n"
Still, after that, if you run "echo %ERRORLEVEL%" it returns 0, meaning that aerender returns a sucessful run even though there were errors. This has nothing to do with the nodes or the farm itself, just that aerender does not return an error code when it encounters errors and dont render anything.