Skip to main content
Inspiring
November 10, 2022
Answered

Unable to run jsx from command line for Media Encoder

  • November 10, 2022
  • 1 reply
  • 3390 views

Hi there,
Using media encoder 2022.

 

I have test.jsx script contains alert("Hello");

I have batch script run.bat which contains below.

"C:\Program Files\Adobe\Adobe Premiere Pro 2022\Adobe Premiere Pro.exe" --console es.processFile "test.jsx"

 

When executed.

Media encoder shows error and doesn't execute.

 

But, tried the same from console of media encoder with below command.

es.processFile "test.jsx"

It works fine and alert pops up.

 

Tried other commands in bat file es.executeScript , es.process ,  --executescript.
None seems to work.

How to solve this? Did anyone solve this?

This topic has been closed for replies.
Correct answer eckiAMETeam

I thought of that... Same issue wherever the .Jsx is placed. May I ask about the platform and version that the verification was completed on?

Thank you

Alan

 


We are running all our daily automated tests using this on MacARM, MacIntel, Windows 10 and Windows 11. What are your system specs? And which version of AME are you using? Can you try newer versions such as Beta?

Please create a small sample that only contains one line:

alert("hello World!");

Put that on the desktop. And run it from the command line, like above.

If that doesn't work, send me the script and all detailed steps that you performed, including the command line command you executed.

1 reply

EckiAME
Community Manager
Community Manager
November 23, 2022

You need to provide the full absolute path to the script.

Alan_AEDScripts
Inspiring
February 21, 2023

For AME 2022 - this is not working below  ? (command line send script to AME)

 

"You can also launch scripts from the command line on Mac and Windows, like this"

<fullPathToAMEbinary> --console es.processFile <fullPathToScript>

 

Is this known? 

Adobe Employee
February 21, 2023

I verified. It is working. You need to make sure that the file at the provided (absolute) path exists and the script does not have syntactic errors.

See here for more details:
https://ame-scripting.docsforadobe.dev/