Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aerender fails on Mac OS 11.4 with error -1701 "AEGetParamPt failed at line 918" #607

Closed
hdngr opened this issue May 28, 2021 · 10 comments
Closed

Comments

@hdngr
Copy link

hdngr commented May 28, 2021

EDITED

For all who come next. To be clear, this is a problem with AE Render and the newest OS Security Updates, not nexrender. My best guess is it is how AE Render uses it's websockets interface to communicate across the machine - kind of squirly and open ended with AE Render sending/receiving requests from the After Effects process.

Describe the bug
After upgrading to newest MacOS patches aerender chokes.

Seems to be a permissions issue where aerender cannot open After Effects.

Solution:

  1. Open After Effects with any project, or no project at all - just make sure the process is open and running
  2. Pass -reuse flag to aerender:
# If using nexrender programatically: 
{
...
aeParams: ['reuse'],
...
}

#Or, if via command line:
>> nexrender [other params] --reuse
@hdngr hdngr added the type:bug label May 28, 2021
@stevenzielke
Copy link

For all who come next.

Describe the bug
After upgrading to newest MacOS patches aerender chokes.

Seems to be a permissions issue where aerender cannot open After Effects.

Solution:
Pass -reuse flag to aerender.

Using nexrender programatically:

{
...
aeParams: ['reuse'],
...
}

Via command line:
nexrender ... --reuse

unfortunately I cannot get the --reuse working as mentioned. You use it like this?
./nexrender-worker --reuse --host=***** --secret=*****

@torresf
Copy link

torresf commented Jun 16, 2021

@stevenzielke You need to open After Effects Render Engine before running your nexrender-worker.
Hope this helps !

@stevenzielke
Copy link

@stevenzielke You need to open After Effects Render Engine before running your nexrender-worker.
Hope this helps !

Thank you so much. That worked. Now I dont have to downgrade my MacOS

@limzykenneth
Copy link
Contributor

reuse here doesn't work for me as I'm getting aerender ERROR -1712: AESend failed to send apple event at line 909 instead when setting the reuse flag.

@hdngr
Copy link
Author

hdngr commented Jul 6, 2021

reuse here doesn't work for me as I'm getting aerender ERROR -1712: AESend failed to send apple event at line 909 instead when setting the reuse flag.

Do you already have AE Open and Running? Try it with AE Already open and running, and then AE Render will using the existing process and not throw an error. That is what I and other user's are having success with.

@limzykenneth
Copy link
Contributor

limzykenneth commented Jul 6, 2021

Yes, I'm sure I have. That's the error it is giving.

Not using the reuse flag give error -1701 "AEGetParamPt failed at line 918" you mentioned in the original issue, using the reuse flag with AE already open and running gives ERROR -1712: AESend failed to send apple event at line 909.

@kimown
Copy link

kimown commented Jul 19, 2021

@chrisapplegate
Copy link
Contributor

I got an update from Adobe in the support forum - the issue has been fixed in the latest version of After Effects Beta, v22.0.0x94 (note that this is different from the stable version). I've tested it with my own install of nexrender on Catalina, and it works fine as it did before the security update broke things.

So an alternative for now if reuse=true is inconvenient or not an option is to install the AE Beta separately. A couple of caveats: first the AE Beta uses its own distinct settings from the stable release so you will need to re-enable "Allow Scripts to Write Files and Access Network" in After Effects preferences if your scripts rely on that. Second, you will need to explicitly set binary to the path of the After Effects Beta in the options when initialising nexrender rather than relying on autofind to pick it up.

@JamesBotterill
Copy link
Contributor

Thanks for this, I've been running into this issue and racking my brains about how this has occurred.|

Now I know

@stale
Copy link

stale bot commented Dec 9, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Dec 9, 2021
@stale stale bot closed this as completed Dec 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants