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.
@tordenver if you are just on catalina then the fix is easy. It's the latest security update that caused the issue for Catalina so you can just boot up in recovery mode and re-install macos Catalina again on your man drive and this will basically revert back to 10.15.7 without the security update... then just don't install that security update. That's how I had to do it for all our render nodes. (It doesn't erase any apps or user stuff).
@SequenceGroup hi does this work on aac with a T2 chip like an iMac pro? I accidentally installed the Catalina security update. Are you able to provide some instructions? I'd really appreciate it 🙂 do I hold down command -r on boot? I don't wanna restore from time machine ideally. Thank you
I took the plunge and did this. Held down cmd-R, reinstalled Catalina and everything is working. RenderGarden working again now.
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!
Any updates? I can no longer use RenderGarden.
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
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. 🙏🏻
After Effects Community Manager
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)
Hi again, defaultyyfcy26lg8tb.
UPDATE: I chatted with an engineering manager on the After Effects team about this. From what I understood, the bug-fix should theoratically work on Mojave but the AE version that will contain this fix won't be compatible with Mojave. Sorry about that!
we have just tried it on two machines. Without the latest Beta both throw the 1701 error, now after the update either
A: It starts with "PROGRESS: Launching After Effects..." and after a few seconds finishes without doing anything.
B: Just gets stuck in "PROGRESS: Launching After Effects..." (The comp should just take a second to render)
Kind regards Hendrik
Thanks for letting me know. I've shared this with the team.
Same here, Big Sur 11.5.2:
/Applications/Adobe\ After\ Effects\ \(Beta\)/aerender -v -project /Users/s/Temp/Gfx/Ae_default/Boxes-v01.aep aerender version 22.0x87 PROGRESS: Launching After Effects...
hangs a short while, then nothing...
Attempted with the -reuse flag also on an open instance of the project.
Btw are there any specific settings we need to ensure for ae/aerender in the Security & Privacy Prefs? (Accessibility, Full Disk Access, Files and Folders...?)
Ah good to know about that flag, thx.
The issue for me got solved once the Allow Scripts to Write Files and Access Network option was turned on.
Hey Rameez! Its working for me on latest Big Sur. Yeah!
For me too, multiframe rendering off. Works like usually, good job 🙂
Just to confirm this works for me on Catalina 10.15.7 (release 19H1323) and the latest AE beta (22.0.0 Build 94). I am using aerender triggered via the nexrender library for Node, and it works fine there.
Do you have an idea of when these fixes will be put into the latest stable version of After Effects?
As far as I know, the fix would go live in the next stable version of After Effects. Sorry, I don't know when that version is going to be released. All I know is that it's coming soon!
This is encouraging progress! I'm able to get renders working again on Big Sur 11.5.2 with this beta release, after making sure "Allow Scripts to Write Files and Access Network" is checked. Is there any way that we could pre-approve that from the command line, or with a plist or configuration profile from an enterprise management solution? We manage a growing After Effects renderfarm and having to manually open After Effects and check that checkbox on all of our render nodes is not a very admin-friendly workflow.
Senior Systems Engineer @ Pixar Animation Studios
Let me get in touch with someone on the After Effects team and see if this is possible. Give me some time and I'll get back to you.
AE (Beta) 22.1.0 (Build 46)
macOS Big Sur 11.6
Mac Pro (2019)
I've just tested the latest version of Mekajiki's RenderGarden with the lateset build of AE (Beta) and the most recently updated macOS Big Sur.
AERender fired up really quickly and render was super speedy. Worked like a charm.
I'm going to keep using it on a few projects I have that vary in complexity. Hopefully I don't get any errors!