nexrender: Error: Couldn't find a result file

I am getting this error when rendering. Any idea of the origin? I am on the newest version of both globally installed cli and node modules.

[qDuniGSE9KlcUlTEe09Gs] rendering job...
[qDuniGSE9KlcUlTEe09Gs] rendering took ~12.336 sec.
[qDuniGSE9KlcUlTEe09Gs] writing aerender job log to: /Users/finnfrotscher/code/cofenster/api.renderer/tmp/aerender-qDuniGSE9KlcUlTEe09Gs.log
[qDuniGSE9KlcUlTEe09Gs] dumping aerender log:
Running Script: /Users/finnfrotscher/code/cofenster/api.renderer/tmp/qDuniGSE9KlcUlTEe09Gs/nexrender-qDuniGSE9KlcUlTEe09Gs-script.jsx
WARNING:After Effects warning: timeSpanStart of -0,87 seconds will cause render to have frames outside of range defined by comp displayStartTime (0,87) and end of comp duration (26,63). Render will succeed, but may have blank frames.
aerender version 17.0.5x16
PROGRESS: Launching After Effects...
PROGRESS: ...After Effects successfully launched


[ERROR]

{}
lifecycle error Error: Couldn't find a result file
    at ChildProcess.<anonymous> (/Users/finnfrotscher/code/cofenster/api.renderer/node_modules/@nexrender/core/src/tasks/render.js:137:31)
    at ChildProcess.emit (events.js:223:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
tick 13:28:47

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 25 (17 by maintainers)

Most upvoted comments

The problem happened to me again when switching from Mac to PC. Fixed By removing everything from the render queue. Try that.

Hi, to make an addition, I found that something wrong with templates can also lead to this error.

At first, I ran into this error. I was quite sure nothing was wrong with my OM/aerender. After I reset the property “postion” of one of my layers(it had been accidentally changed), the error just gone.

I don’t know how, but you may also check the .aep template.

That sometimes happens, when the after effects returns exit code which is not 0. Could you try to check what is in the log, maybe even tho rendering finishes, there are some errors that cause aerender itself to fail?