Skip to main content
Inspiring
November 10, 2022
Answered

Error with --Console es.processFile

  • November 10, 2022
  • 1 reply
  • 970 views

Hi there,

I have bat file with below contents

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

 

When media encoder is closed and i run bat file, jsx script runs fine.

When media encoder is open and i run bat, jsx script doesn't run and error pops up in media encoder.

 

Any Solution for this?

This topic has been closed for replies.
Correct answer EckiAME

To trigger jobs on another machine, I would recommend creating a watch folder on a shared location and use that with a dedicated AME machine for encoding.

1 reply

EckiAME
Community Manager
Community Manager
November 11, 2022

Media Encoder needs to be launched with the script in order to work properly. You can also use an IDE like Visual Studio Code with ExtendScript debugger to send the script over to AME.

Inspiring
November 11, 2022

I know IDE way to run scripts. I need to run scripts in media encoder in another machine to keep queuing batch items using  app.frontEnd() using bat file or any other way if exists.? Is there anyway to do with vbs createObject() and run with wscript? There shud be someway or work around to do this simple task? Can we use csinterface() in some way to trigger jsx scripts using dos command > html > csinterface ()? Am banging my head around this from past 1 week ? Why there s no binary to achieve this easily from command line? Any possibility to use portable extendscript over network path and mention target app in jsx and run thru command line? 

EckiAME
Community Manager
EckiAMECommunity ManagerCorrect answer
Community Manager
November 23, 2022

To trigger jobs on another machine, I would recommend creating a watch folder on a shared location and use that with a dedicated AME machine for encoding.