Current Media Encoder automation from command line information.

[pctechtv]

Hello, I have been trying to make a script for Adobe that I can run via automation via the command line. The script that I have made runs well in the Extend Script console. I have seen information on how Media Encoder could be used from the command line in this post. I am wondering if this is still valid and up-to-date information, and I’m also wondering if there are configuration changes that may need to happen to your system to allow this. What I mean by this is in Adobe Premiere Pro to use panels you have to update your registry to allow it use panels. I understand what I am doing is different than using panels. However, because I could not get the stuff found in the post I linked you to work, I wonder if similar changes need to be made in the registry for Media Encoder to allow these communications. Does anybody know the answer? Thanks for any help 😊

[Alan_AEDScripts]

me too! Zero information on this....around the web.

[eckiAMETeam · Accepted solution]

Most up-to-date information is the official scripting guide here:
https://ame-scripting.docsforadobe.dev/

[Lloyd28200878thlg]

So since this was marked as the correct answer. Has the domentation changer so we can know how to use this? To be clear, the properties and methods do not work the way that document states anymore. So, I am asking is there any updated information or documentation about this?

[Lloyd28200878thlg]

Yes, there seems to be a lot of information that does not work and lacks full explanations. I wonder if the people who are trying to help are understaffed. It is, like you say, not much information. When you follow the information, it does not work.

I hope Adobe sees this and know that the vital concept of automation, in this case via the command line, is not robust enough. Multiple posts asking what is going on with the functionality that are rediriected and not answered thoroughly.

Hey Adobe, we need a command line for Media Encoder. Hey Adobe, with that command line we need some decent documentation, specifically about the command line. This would be very helpful to automate renders. I have seen like 20 post asking about this command.

I have seen an answer to a post that suggests if you want to automate Media Encoder, use Premier Pro Panels. I know a bit about making Premier Pro Panels. I have made some. Look here. However, that seems like overkill. Because it seems like many users just want to send a command to Media Encoder like above. Their requests are only met with riddles.

I think I might sit down and try to figure this out. I have done it before with Acrobat. Meaning… I figured out a way to talk to the program that Adobe does not support. However, I don’t want to hack what Adobe needs to become aware that should exist.

Hey Adobe… we need a robust command line for Adobe Media Encoder (someone, please say dido!) !!!

P.S. and when you do help your support engineers answer questions.

[eckiAMETeam]

Please be specific and tell us first what exactly is not working. We are using script execution from the command line on a daily basis in our test automation on all major platforms.

[Lloyd28200878thlg]

The command, when using it from the command line does not do anything. It seems like it tries to do something or just the mention of the exe focuses Media Encoder. However, the script instructions are ignored. The queue remains blank. Also, reading in some responces I think you are saying that the program has to be closed,,, OK, I tested like that many times. It does the same thing opens with an empty queue. So that makes me think there will be no way to send another command (automation). That is why I am asking Adobe to give us a robust command line, and help you guys support it well. As it is it is way too vauge. Thanks for the reply.

[eckiAMETeam]

We tried again the full filePath with AME 2022 and AME 2023 and this works both for the debug console and the cmd line. Also we use this functionality heavily in our daily test automation as well.

Here are a couple of important notes:

• AME always requires the full file path with an absolute folder path which contains script files.
• If there are fundamental syntactic errors, the script won't be executed.
• In both cases AME will start and stay at the start screen.

Here are the detailed calls for a script with the path "C:\Users\eckiAME\Desktop\test.jsx":

debug console:

es.processFile "C:\Users\eckiAME\Desktop\test.jsx"

Windows 10 and 11 cmd line:
[ame executable path] --console es.processFile "C:\Users\eckiAME\Desktop\test.jsx"

Please verify and if this still does not work, send me the script, and the exact command with which you tried to execute it from the command line. We also need the version of AME you tried to use and your exact system spects.

[Lloyd28200878thlg]

OK! I figured something out this time around. When I use a C:\ based path it works (because yours said \Desktop\). Up to now I was trying to use the command from my D:\ drive. This does not work. I would like to see if this is some of the other users problem also? I will add this to why I am asking Adobe for a Robust Command Line for Media Encoder. So cool for now something can be done!!! Thank you for sticking with this. I just have to know there is a limitation on where I can run the scripts from. However, like I said and why I am asking for more, is this. You cannot continue to send commands from the command line to Media Encoder. You have to close it. This is not a good work flow. So could Adobe take a look at making the feature work better, please. Thank you for all the help.

[Alan_AEDScripts]

I have tried this, won't work no matter where I place the file. 2018, 22, 22.5, 23.x.

[eckiAMETeam]

Still not able to repro with external drives on Windows 11. Can you guys please share your exact system specs?

And also can you please post the full console log you see in the command window?

[Alan_AEDScripts]

So just to refer to this thread too for others, seems that special characters in the path to the .jsx were the problem. 

[eckiAMETeam]

I will file a bug for this issue. Thanks for helping us getting down to the core of this.

[Lloyd28200878thlg]

OK after figuring out what I said, that being the C:\ file path is working. Everything has stopped working since the update to version 23.2.1 (Build 2). Does anybody else notice this? The line I put in code throws error. Thanks.

app.getFrontend().addFileToBatch(file, format, preset, destination).setWorkArea(2,208,238);

[Lloyd28200878thlg]

Yes I am sure that is what it is. I just put back version 23.1 (Build 81) and everything is working as I said before. C'mon Adobe get it together... please our work is suffering!

[EckiAME]

Can you please provide more details so that we can help you? 

[SükriyeLudwig]

Hi Lloyd, do you mind giving me the script file, your selected format and preset? Btw have you tried to run your script like blow? 

var frontend = app.getFrontend();
if (frontend) {
  var encoderWrapper = frontend.addFileToBatch(...);
  if (encoderWrapper) {
     encoderWrapper.setWorkArea(2, ...);
  }
}

[SükriyeLudwig]

Hello again,

meanwhile I tried to reproduce this case with one of my scripts and media sources.

Unfortunately I could not reproduce this case in both ame versions ame23.1.0x81 and ame23.2.1x2
In both versions my file is rendered exactly in the specified work area. I have also tried calling the script via ExtendScripting and via the command line.
Until then, I would need your script file and media files and the exact call routine you chose to run the script.
Sincerely,
-Süky