Inspiring

Answered

AERender Error -1701

Forum|Forum|4 years ago
May 18, 2021
19 replies
17257 views

Hi there, I'm getting an error that I can't seem to find any info on.

Specifially, when running aerender int he terminal, i'll get this:

aerender ERROR -1701: AEGetParamPt failed at line 918

The only clue I've come across is somethign to do with Adobe ExtendScript Toolkit, which is deprecated and no longer even downloadable.

Any help would be appreciated.

Thanks!

_

G

This topic has been closed for replies.

Correct answer Rameez_Khan

Hi all,

UPDATE: The After Effects team has put a fix for the aerender bug in the latest After Effects Beta, version 22.0.0 (Build 87).

Please note that the fix is applicable to macOS Catalina 10.15.7 and Big Sur only. It would be great if you can test the bug-fix and let us know if aerender works for you. Due to the complexity of the bug, you might run into issues here and there. If you do, please let us know.

Thank you all for your patience on this. 🙏

Best,

Rameez

After Effects Community Manager

nishu_kush

Community Manager

Hi all,

Good news here!

This issue has been fixed in the latest official release (22.0.0). Please try it out and let us know.

Thanks,

Nishu

M

Matt Silverman

Participating Frequently

Nishu... its great that you finally fixed your bug. But this is not helpful for my studio since you will not fix v18. My studio never updates software for at least 3-6 months after a major release, and never in the middle of a project. We will not be pushing out v22 until at least May when our current project wraps. I know most studios have the same policy. Please reconsider updating 18.x. Thanks.

juicybiscuit

Participating Frequently

The beta works for me on BigSur 11.5.2

Rameez_Khan

Legend

Great! Thanks for reporting, juicybiscuit.

Best,

Rameez

P

PMVic

Participant

Any update on a stable release? I'd love to use my new machines on the farm.

Can't aerender in Rush...

Executing: aerender -project "/Volumes/..<snip>.../projects/ae/B_MSS0930_v003.aep" -comp "B_MSS0930_v003" -s 1131 -e 1135 -mp
aerender version 18.4.1x4
PROGRESS: Launching After Effects...
aerender ERROR -1701: AEGetParamPt failed at line 918

O

obio773188

Participating Frequently

Awesome so latest versions 22.0x87 and 22.0x94 both seem to work!

If the process gets stuck on launch, then exits without nothing happening, make sure the Allow Scripts to Write Files and Access Network option in the AE Scripting & Expressions prefs is turned ON.

H

Hendrik5E8E

Participating Frequently

I can confirm this, for the Beta version those settings fixed the issue for me (Not in the release version though). Thanks for sharing :)!

Rameez_Khan

Legend

Awesome!! I'll add this information to the bug.

Thanks,

Rameez

Rameez_KhanCorrect answer

Legend

Hi all,

UPDATE: The After Effects team has put a fix for the aerender bug in the latest After Effects Beta, version 22.0.0 (Build 87).

Please note that the fix is applicable to macOS Catalina 10.15.7 and Big Sur only. It would be great if you can test the bug-fix and let us know if aerender works for you. Due to the complexity of the bug, you might run into issues here and there. If you do, please let us know.

Thank you all for your patience on this. 🙏

Best,

Rameez

After Effects Community Manager

D

defaultyyfcy26lg8tb

Participant

Thanks a lot for the update! If the bugfix is implemented into the non Beta Version, will it still be running in Mac OS Mojave? (10.14.6)

Rameez_Khan

Legend

defaultyyfcy26lg8tb, I'll have to check that with the After Effects team.

Thanks,

Rameez

J

James Paulley

Known Participant

Any updates? I can no longer use RenderGarden.

D

defaultyyfcy26lg8tb

Participant

Please give us again a little hint on how long it might take you to fix the issue. If it holds on i will need to get in running with downpatch somehow

O

obio773188

Participating Frequently

Here's what we know:
* The issue occurs on MacOS only, and on newer OS releases that have received recent security updates from Apple.
* The security update changes means we need to alter the structure of aerender and how it starts up aerendercore on Mac to render the frames.
* We have two possible solutions, both of which we are in development on. One may get aerender working sooner but it's got the potential to break again in the future, and so the other is a longer-term fix but may have implications about how aerender is executed which we are working through.

We hope to have at least one of those fixes in place in the next few weeks. We are working with Apple closely to understand their changes to make sure we get this right. More updates as soon as we have them. Thank you for your patience!

Thanks,
Sean

By @jenkmeister17177426

https://community.adobe.com/t5/after-effects-beta/multi-frame-rendering-is-here-aka-the-multithreading-you-ve-been-asking-for/m-p/12332911#M1208

D

default46od73cvn27x

Participant

This remains a crippling bug in my studio's workflow. Any updates or work-arounds would be a great help.

F

fnordware

Inspiring

Back up to Big Sur 11.3.1, or whatever version of Catalina/Mojave. We just got a bunch of new Mac Minis for our farm and I had to set back each one. It was a drag, but worth it.

Naturally, auto-update has been turned off on each one!