Hi
I am trying to submit after effect file to render in encoder via deadline, but deadline monitor and
submitter crashes, we use deadline version 10.1.21.4
can anybody help with this problem ?
Any more info than that?
Deadline version, AE version ? assuming encode is MediaEncoder?
any crash logs from the submitter? do you have the network access option checked?
deadline version 10.1.21.4, media encoder version 2022
ok Adobe Media Encoder 2022 isn’t on the supported list for Deadline, you’ll have to modify the scripts.
Assuming you’re not submitting directly from AE but using Deadline Monitor to submit the file?
We tested with AME 2021 and it was hanging indefinitely - no progress and no completion. Then I read somewhere else that it does not work, but I do not have the link.
I updated to 10.1.22.4, the ME option is there in the plugin but doesn’t have an entry assigned, so I added the latest ME
"C:\Program Files\Adobe\Adobe Media Encoder 2022\ame_webservice_console.exe"
I also enabled DEBUG mode in the plugin for any extra output.
With a really simple job I got this error
DEBUG: Exception in StartJob: ConnectionRefusedError : [WinError 10061] No connection could be made because the target machine actively refused it (Python.Runtime.PythonException)
So I tried running the command in cmd.exe, what I got was it running from a random network address from one of the VPN services I’m running
STDOUT: Starting HTTP service on ip 123.45.67.89, port 8080
I disabled all other network adaptors, and now the jobs seems to run but hangs Creating the AMEServer
STDOUT: Launching web services. Use --help for options.
STDOUT: Starting HTTP service on ip 192.168.1.666, port 8080
STDOUT: History will be retained for the most recent 100 jobs.
STDOUT: Creating AMEServer
STDOUT: Creating AMEServer - Timeout
STDOUT: AMEServer OFFLINE!
I tried to launch the application via CMD again, but this time using Admin and it worked
C:\Program Files\Adobe\Adobe Media Encoder 2022>ame_webservice_console.exe
Launching web services. Use --help for options.
Starting HTTP service on ip 192.168.1.666, port 8080
History will be retained for the most recent 100 jobs.
Creating AMEServer
Creating AMEServer - Succeeded
AMEServer OFFLINE!
I modified the file to try and launch as admin (I’m on Win11) and this works when launching the app, but not via Deadline
Error: Exception : Error starting "C:\Program Files\Adobe\Adobe Media Encoder 2022\ame_webservice_console.exe" in "C:\Program Files\Adobe\Adobe Media Encoder 2022" : The requested operation requires elevation.
If I launch Deadline with Admin rights it starts the job but gives me other errors (this maybe as I don’t really know AME well)
Error in EndJob: Error: ConnectionRefusedError : [WinError 10061] No connection could be made because the target machine actively refused it
and
RenderPluginException -- Error: FailRenderException : Render failed because the AME job status is "Not Found". Please check the AME logs located in the Adobe documents folder.
The logs in this folder
C:\Users\antg\Documents\Adobe\Adobe Media Encoder\22.0\logs\Adobe Media Encoder Log.txt
Look like it’s trying to connect outside
Ticks = 6672 <3776> <AMEApp> <0> Time taken to load MediaCore plugins: 1893.58 milliseconds.
Ticks = 7500 <3776> <AMEApp> <1> Entering RunEventLoop
Ticks = 7515 <3776 (main)> <hang> <5> Potentially Hung Thread
...
Ticks = 8578 <15604> <EACL> <5> Connecting local hub to remote hub, requestID: "*******", server: "https://cc-api-teamprojects.adobe.io:443", serverType: 2, user: "antg@*******.com", machineID: "*******"
Ticks = 9547 <7744> <EACL.CloudProjectsLogin> <5> Finished sending new access token to LocalHub, result: 0, requestID: "dvanet-******", duration: 0.38, httpStatusCode: 200, httpLibCode: 0, payload: "[{\"authorized\":true,\"connected\":true,\"forbidden\":{\"error_code\":\"\",\"message\":\"\"},\"lastAuthorizationStatusCode\":200,\"serverURL\":\"https://cc-api-teamprojects.adobe.io:443\",\"serverVersion\":\"2016.*******\"}]"
EDIT: I actually looked at the application and may have been doing it wrong! I added a MOV and set it to export as a MP4, using a Preset. I then closed it, jump onto Deadline Monitor and submitted via the menu only adding the input, output and preset, it seemed to work… so maybe just the permissions is the issue
2022-07-04 22:56:10: 0: INFO: Process is now running
2022-07-04 22:56:22: 0: STDOUT: Launching web services. Use --help for options.
2022-07-04 22:56:22: 0: STDOUT: Starting HTTP service on ip 192.168.1.666, port 8080
2022-07-04 22:56:22: 0: STDOUT: History will be retained for the most recent 100 jobs.
2022-07-04 22:56:22: 0: STDOUT: Creating AMEServer
2022-07-04 22:56:22: 0: STDOUT: Creating AMEServer - Succeeded
2022-07-04 22:56:23: 0: INFO: AME Web Service started.
2022-07-04 22:56:23: 0: DEBUG: StartJob: returning
2022-07-04 22:56:23: 0: Done executing plugin command of type 'Start Job'
2022-07-04 22:56:23: 0: Plugin rendering frame(s): 0
2022-07-04 22:56:23: 0: Executing plugin command of type 'Render Task'
2022-07-04 22:56:23: 0: DEBUG: RenderTasks: called
2022-07-04 22:56:23: 0: DEBUG: RenderTasks: rendering frames 0 to 0
2022-07-04 22:56:26: 0: STDOUT: Job request received.
2022-07-04 22:56:26: 0: STDOUT: Source path: C:\share\jobs\bottlecap\bottlecaps.mov
2022-07-04 22:56:26: 0: STDOUT: Output path: C:\share\jobs\bottlecap\bottlecaps.mp4
2022-07-04 22:56:26: 0: STDOUT: Preset path: C:\ProgramData\Thinkbox\Deadline10\workers\***\jobsData\***\TestPreset.epr
2022-07-04 22:56:26: 0: STDOUT: Creating encoder.
2022-07-04 22:56:26: 0: STDOUT: Creating Encoder - Succeeded
2022-07-04 22:56:26: 0: STDOUT: AME now encoding: C:\share\jobs\bottlecap\bottlecaps.mov encoder ID: ****
2022-07-04 22:56:35: 0: STDOUT: AME signaled status change to Encoding, encoder ID: ***
2022-07-04 22:56:35: 0: STDOUT: Current job progress: 0% complete
2022-07-04 22:56:37: 0: STDOUT: Current job progress: 37.3% complete
2022-07-04 22:56:38: 0: STDOUT: Current job progress: 72.41% complete
2022-07-04 22:56:39: 0: STDOUT: Current job progress: 100% complete
2022-07-04 22:56:39: 0: STDOUT: AME signaled job completion, encoder ID: ***
Good dive, Anthony!
So this network service… does it try to connect to Adobe? Is it for authentication purposes?
The webservice program probably has a command line option to specify which network interface to listen on - Use --help for options.
probably just the auth yeah, I left that part in the post even though it’s irrelevant as the job is actually being processed.
I’ve not used AME, usually it’s AE for comps and FFmpeg for conversion etc.
I ran the --help switch to see if there was an option to specify the network interface, but it doesn’t seem to dump out the help options, just launches the console (that’s why I just disabled the other interfaces to get it running)
C:\Program Files\Adobe\Adobe Media Encoder 2022>ame_webservice_console.exe --help
Launching web services. Use --help for options.
Starting HTTP service on ip 192.168.1.666, port 8080
History will be retained for the most recent 100 jobs.
Creating AMEServer
Creating AMEServer - Timeout
Creating AMEServer - Succeeded