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
nexrender-cli-macos failing to render for "an unknown reason" #965
Comments
Could you share the aerender log related to that render job? (it should be in this folder: |
Hello,
After Effects is the latest (24.1).
Had a try with setting the export : NEXRENDER_ENABLE_AELOG_ Thanks for your help. |
It could be indeed related to macOS binaries being built for x64. Let me try uploading custom-built ARM binaries here later today to verify that this is the case. Would you be able to test that? |
Yes, I will test this and give you proper feedbacks. |
Hi again, |
Here is a testing file: https://github.com/inlife/nexrender/releases/download/v1.48.4/nexrender-cli-macos-arm-test |
Hello, |
I see. Another option is getting the Nodejs installed locally and installing nexrender via NPM. That way, you would have a natively running Node.js, which could solve the issue. |
I manage to find out a solution. |
Hi, I have been trying to solve this error for many days but have not been successful. I am using aerender also but it is working correctly This is the error:
|
@MuazAshraf could you please provide logs coming from that file: |
Just as a side note for anyone else running into this issue like I was earlier today, doing this solved it for me. |
I have the same issue and log file is totally missing. It's not been created. |
I'm seeing this issue as well. Tried your suggestion @wmwccdd but still getting the same error. The job was getting accepted, also passed to the worker from the server, but when the rendering process starts, it says some tmp/result.mp4 file is not found. Not sure what is causing this issue. JSON Request --> http://localhost:3000/api/v1/jobs |
@tommycotter please provide contents of this log file: |
Hey @inlife I think it got removed when I closed the server. Don't have anything here. But I remember the file being empty. |
Hey ! If I copy the aerender process command and add quotes around some parameters it runs fine. @inlife Do you have any idea to get more error logs from the spawned process ? |
@torresf could you share your aeprocess command line both before and after adding quotes? |
Of course, here is the log : [nYsEfcbNSwYgTfVgUsln-] spawning aerender process: /Applications/Adobe After Effects 2024/aerender -project /var/folders/7p/mqjfrnb967n28vzl_9p9j0_00000gp/T/nexrender/nYsEfcbNSwYgTfVgUsln-/hfqn6xk6z9h..aep -comp LANDSCAPE_COMP -output /var/folders/7p/mqjfrnb967n28vzl_9p9j0_00000gp/T/nexrender/nYsEfcbNSwYgTfVgUsln-/result.mp4 -RStemplate Auguste Preview -r /var/folders/7p/mqjfrnb967n28vzl_9p9j0_00000gp/T/nexrender/nYsEfcbNSwYgTfVgUsln-/nexrender-nYsEfcbNSwYgTfVgUsln--script.jsx And here is the working command line : "/Applications/Adobe After Effects 2024/aerender" -project /var/folders/7p/mqjfrnb967n28vzl_9p9j0_00000gp/T/nexrender/nYsEfcbNSwYgTfVgUsln-/hfqn6xk6z9h..aep -comp LANDSCAPE_COMP -output /var/folders/7p/mqjfrnb967n28vzl_9p9j0_00000gp/T/nexrender/nYsEfcbNSwYgTfVgUsln-/result.mp4 -RStemplate "Auguste Preview" -r /var/folders/7p/mqjfrnb967n28vzl_9p9j0_00000gp/T/nexrender/nYsEfcbNSwYgTfVgUsln-/nexrender-nYsEfcbNSwYgTfVgUsln--script.jsx Could it be a permission problem ? |
It could be -RStemplate problem, at least judging by the generated line |
I tried without the My guess is that it could come from node not having the right permission to run aerender as a child process on macOS or something like that. |
I fixed it 🎉 |
Oh, great. Glad to hear that! |
Describe the bug
I'm trying to do a test nexrender on a simple project with a text layer.
But am getting an error without a lot of information, even with the --debug flag:
If I copy the aerender command and add escapes for spaces and quotes for the options it works exactly how I was expecting with the desired output:
Information about environment
Expected behavior
I expected the nexrender CLI command to spawn the aerender command and run exactly how it did when I manually ran the command with the generated jsx temp folder assets.
The text was updated successfully, but these errors were encountered: