Adobe Media Encoder Job Type failed

Deadline
1

2016-07-05 15:28:36: 0: INFO: Checking for an existing AME Web Service at 192.168.94.47:8080... 2016-07-05 15:28:37: 0: INFO: Failed to connect to an existing AME Web Service at 192.168.94.47:8080. 2016-07-05 15:28:37: 0: INFO: Starting AME Web Service... 2016-07-05 15:28:37: 0: INFO: Getting host and port name from ini file found at C:\Program Files\Adobe\Adobe Media Encoder CC 2015.3\ame_webservice_config.ini 2016-07-05 15:28:37: 0: INFO: Port Number is 8080 2016-07-05 15:28:37: 0: INFO: Host is 192.168.94.47 2016-07-05 15:28:37: 0: Launching web services. Use --help for options. 2016-07-05 15:28:37: 0: Starting HTTP service on ip 192.168.94.47, port 8080 2016-07-05 15:28:37: 0: History will be retained for the most recent 100 jobs. 2016-07-05 15:28:37: 0: Creating AMEServer 2016-07-05 15:28:46: 0: Creating AMEServer - Succeeded 2016-07-05 15:28:46: 0: INFO: AME Web Service started. 2016-07-05 15:28:46: 0: Done executing plugin command of type 'Start Job' 2016-07-05 15:28:46: 0: Plugin rendering frame(s): 0 2016-07-05 15:28:46: 0: Executing plugin command of type 'Render Task' 2016-07-05 15:28:47: 0: Job request received. 2016-07-05 15:28:47: 0: Source path: C:\Users\ggreenwalt\Desktop\##@#@@#@@#_v09TEST.aep 2016-07-05 15:28:47: 0: Output path: C:\Users\ggreenwalt\Desktop\##@@##@@#@##v09TEST.mp4 2016-07-05 15:28:47: 0: Preset path: C:\Users\ggreenwalt\AppData\Local\Thinkbox\Deadline8\slave\daedalus\jobsData\577c342bb5b7e2260c1ba652\######.epr 2016-07-05 15:28:47: 0: Creating encoder. 2016-07-05 15:28:47: 0: Creating Encoder - Create encoder group failed Success

Same script file. I’ll email it to support. Still 2015.3

It’ll just sit indefinitely “rendering”. AME opens but nothing happens.

2

Hey Gavin,

Is there a job report from this, or does it end up needing to be cancelled and thus no report is made? I am curious about that message about the encoder group failing.

3

It just sits there in the “rendering” state indefinitely and has to be cancelled.

4

I’ve currently got exactly the same problem here with Deadline 7.2 and AME 2015.3

Dave

5

Hello Gavin,

Sorry for missing this reply. Can you verify if AME works for you outside of Deadline? I just want to make sure that it is working when Deadline is not involved. Thanks.

6

Hello Gavin,

I wanted to check in and see how things are going.

7

Yes it does work outside of Deadline. I can’t test the web-socket interface thing that Deadline uses though. I’m not sure how that works or how to simulate it since it’s not a strict command line process.

8

Hey Gavin,

So I have tried this over and over, googled for different messages in the log you pasted, and found nothing of substance. Can you send over your .aep and .epr files, so I can try to replicate this here? Thanks.