Adobe Media Encoder errors?

Deadline
1

[code]=======================================================
Error

Error: error : [Errno 10061] No connection could be made because the target machine actively refused it (Python.Runtime.PythonException)
File “none”, line 124, in StartJob
File “none”, line 164, in StartWebService
File “C:\Program Files\Thinkbox\Deadline7\bin\lib\httplib.py”, line 995, in request
self._send_request(method, url, body, headers)
File “C:\Program Files\Thinkbox\Deadline7\bin\lib\httplib.py”, line 1029, in _send_request
self.endheaders(body)
File “C:\Program Files\Thinkbox\Deadline7\bin\lib\httplib.py”, line 991, in endheaders
self._send_output(message_body)
File “C:\Program Files\Thinkbox\Deadline7\bin\lib\httplib.py”, line 844, in _send_output
self.send(msg)
File “C:\Program Files\Thinkbox\Deadline7\bin\lib\httplib.py”, line 806, in send
self.connect()
File “C:\Program Files\Thinkbox\Deadline7\bin\lib\httplib.py”, line 787, in connect
self.timeout, self.source_address)
File “C:\Program Files\Thinkbox\Deadline7\bin\lib\socket.py”, line 571, in create_connection
raise err

at Deadline.Plugins.ScriptPlugin.StartJob(Job job, String& outMessage, AbortLevel& abortLevel)

=======================================================
Type

RenderPluginException

=======================================================
Stack Trace

at Deadline.Plugins.Plugin.StartJob(Job job)
at Deadline.Slaves.SlaveRenderThread.a(TaskLogWriter A_0)

=======================================================
Log

2015-08-16 05:32:26: BEGIN - HEX-I7\nixx
2015-08-16 05:32:26: 0: Start Job timeout is disabled.
2015-08-16 05:32:26: 0: Task timeout is disabled.
2015-08-16 05:32:26: 0: Loaded job: AME_DS_Screen_04 (55cfda7e1c5645061c9a1647)
2015-08-16 05:32:26: 0: Skipping drive mapping because they have already been mapped for this job
2015-08-16 05:32:26: 0: INFO: Executing plugin script C:\Users\nixx\AppData\Local\Thinkbox\Deadline7\slave\Hex-i7-03\plugins\55cfda7e1c5645061c9a1647\MediaEncoder.py
2015-08-16 05:32:26: 0: INFO: About: Adobe Media Encoder Plugin for Deadline
2015-08-16 05:32:26: 0: INFO: The job’s environment will be merged with the current environment before rendering
2015-08-16 05:32:26: 0: INFO: Checking for an existing AME Web Service at 127.0.0.1:8080…
2015-08-16 05:32:27: 0: INFO: Failed to connect to an existing AME Web Service at 127.0.0.1:8080.
2015-08-16 05:32:27: 0: INFO: Starting AME Web Service…
2015-08-16 05:32:27: 0: INFO: Getting host and port name from ini file found at C:\Software\Adobe\Adobe Media Encoder CC 2014\ame_webservice_config.ini
2015-08-16 05:32:27: 0: INFO: Port Number is 8080
2015-08-16 05:32:27: 0: INFO: Host is 127.0.0.1

=======================================================
Details

Date: 08/16/2015 05:32:32
Frames: 0
Elapsed Time: 00:00:00:07
Job Submit Date: 08/16/2015 02:34:01
Job User: nixx
Average RAM Usage: 3211774720 (10%)
Peak RAM Usage: 3218817024 (10%)
Average CPU Usage: 7%
Peak CPU Usage: 15%
Used CPU Clocks: 120998
Total CPU Clocks: 1728540

=======================================================
Slave Information

Slave Name: Hex-i7-03
Version: v7.1.2.1 R (53013d5bd)
Operating System: Windows 81 Pro
Running As Service: No
Machine User: nixx
IP Address: 192.168.0.2
MAC Address: 54:04:A6:3C:D7:BC
CPU Architecture: x64
CPUs: 12
CPU Usage: 12%
Memory Usage: 3.0 GB / 31.9 GB (9%)
Free Disk Space: 669.367 GB (67.429 GB on C:, 585.473 GB on D:, 16.464 GB on T:)
Video Card: NVIDIA GeForce GTX 580[/code]

This is what I get when I try to run a AME job.

Python and AME are both installed and working on the machine.
(both are not in their default directory though)

Basically the webservice starts, AME starts and then nothing happens…

2

Hey there!

Adobe broke the API we were using to support media encoder. That’s not Adobe’s fault as we were using a draft spec no one was supposed to have in the first place, but our support for it is broken in one of the upgrades to 2014. We’re really appreciative that they were kind enough to give us the specs regardless. We’ve now removed the plugin until things settle a bit and we’ll bring it back when we can.

Looking at the log here, it’s looking like AME isn’t starting on that machine. I can’t be sure if that problem is because of the API change or some configuration problem. I’ll ask around here for a bit.

3

Hi Edwin, thanks for the explanation, don’t worry, there’s no rush, just was curious

The AME is actually starting (as in, the program opens) but nothing is loaded into it.

I tried the QT submit, but this was running 5 hours without any result/progress.
For now I rendered it through an AE comp that was loaded into AME and build QT on a local drive from files that are on the LAN, which took about 1.5 hours each.
Using AME directly from the LAN resulted in corrupt exports, so that didn’t work either (1 out of 4 was succesfull)

After this project I want to look at Draft as I understood this could be used for automated compression too.

4

FYI. It’s recently been decided NOT to remove this plugin but continue to support it in the short term in Deadline.

5

ok, cool!

Just for my info, would draft be able to replace this? Or is it slower and more aimed at making ‘draft’ quality compression?

(or am I mixing things up ?!)

6

Draft can handle pretty much everything except for ProRes as it’s a wrapper around FFMPEG, and it’s reasonably quick about it.

Deadline 7.2 is going to come with what we call “Quick Draft” which will generate QuickTimes and other output formats automatically directly from the submitter.

What is the workflow you’re dealing with now? Is it just taking some completed frames and creating a quicktime out of it? Try using the “[repo]/draft/Samples/encode_to_MOV_H264_1080p_with_audio.py” script to generate a QuickTime from a list of images. Try right-clicking the job and creating a Draft job from there. It should pre-populate a bunch of stuff for you.

7

Haha, nice, that’s actually exactly what I was looking into today.
Have found that script and the python guy is now modifying it for more automated use.
(autoscale to custom width, custom fps, custom quality and auto-output location-generation)
We’ll look around a bit more and try to get some convenient automation going on.

I really wish that someone would invent a way to distributed-encode a QT… It now took longer then it’s original render :slight_smile:

In terms of workflow it’s just very useful to have automated QT’s to review the renders overnight instead of having to do it manually (and waiting for it)
They can be crappy quality as long as it’s visible how the animation is actually going.
Besides that I’ll use it for pre-final previews and perhaps later on with a nice Slate in the start and framenumbers for feedback.

I’m using since GUI for FFMPEG now to encode h265 .ts files… will have a look if that’s possible with draft too

8

ok, I’m running into some interesting stuff with the Draft system.
Will go and post it on that sub-forum