Nexrender: aerender not exiting on windows

[bgirschig]

Hi!
I'm having trouble with aerender not closing properly: even when I run the command manually, the command prompt never gives control back to me. Using node, the 'on close' event is never called, and the program gets stuck.

Have yo had this problem before and how do you solve it ?
thanks!

[inlife]

Hello @bgirschig !

Never had similar problem. Does that issue apply specifically to the nexrender, or you can reproduce it on any nodejs script? Maybe it's somehow connected to the particular version you are using...

[bgirschig]

Hi!
No the problem does not only affect nexrender: I've been trying to make it
work with a more basic script (spawning the command with basic options),
but it does the same (even using the command prompt).
The command works but does not exit

When you talk about the "particular version", do you mean the particular
version of after effects ?

Le lun. 17 sept. 2018 à 16:20, Vladyslav Hrytsenko [e-mail]
a écrit :

Hello @bgirschig https://github.com/bgirschig !

Never had similar problem. Does that issue apply specifically to the
nexrender, or you can reproduce it on any nodejs script? Maybe it's somehow
connected to the particular version you are using...

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/inlife/nexrender/issues/73#issuecomment-422035907,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF9ZHs32iJsHv1Qlb-hb3VfRHRcthKh8ks5ub6-4gaJpZM4Wrch9
.

--
Bastien Girschig
[phone]
bastien.[email protected]
[email protected]

[inlife]

I was actually asking about nodejs version, have you tried creating a child spawning process and testing it like that?

[bgirschig]

Hi
sorry for the late reply...

I have been chatting with after effects support, and this is apparently a known bug with AE 15.1.2 Downgrading to version 15.1.1 did the trick.

Thanks for your help!

[ddcrobert]

Hi,
I don't think it should be closed yet. It's happening on AE 16.0 too, better adapt than being stuck.

I had a very similar issue, on macOS, w/ the error being:

aerender ERROR -1712: AESend failed to send apple event at line 771

Note: After command is spawn, there's a few minutes before this error pops.

As @bgirschig mentionned, it's occuring w/ 15.1.2. But also w/ 16.0 (16.0x235).
I noticed the command used, was perfectly running in a terminal, therefore, I started looking around the spawn, which led me to the following workaround:

let ae = spawn(process.env.AE_BINARY, params, {
    env: {
        PATH: path.dirname(process.env.AE_BINARY)
    }
});

Yep, simply specifing PATH within env option solved the issue.

[davidbonting]

Maybe a bit too specific to my situation, but I also received the ... AESend failed to send apple event at line ... error.

My setup is:

• A Node script (worker.js) using:

exec('nexrender-worker ...')

• A package.json

{
  ...
  "scripts": {
    "worker": "pm2 start ./components/worker.js"
  },
  ...
}

• The MacOS command

npm run worker

---

But to solve this error, I had to use:

sudo npm run worker

Which is a bit weird, because if I run the following it doesn't work:

sudo pm2 start ./components/worker.js

While this does:

pm2 start ./components/worker.js

So no clue why I sometimes have to use sudo and sometimes I don't. But all in all, if anyone experience this issue. You may have to play around with sudo