[PremierePro_2024] Run script from command line

[h1tman2]

Hi!

Can I Run script from command line?
I need to insert files into a sequence, i use vs code to execute jsx file and works fine, but Can I Run script from command line?

/C es.processFile doesn't work with 2024 Premiere Pro

thanx

[Bruce Bullis · Accepted solution]

> /C es.processFile doesn't work with 2024 Premiere Pro

I've confirmed that it does. 🙂

Command line scripting can work, but it is definitely NOT a recommended workflow, for a variety of reasons. CEP panels remain the recommended and supported way to invoke ExtendScript in PPro.

[Mathias Moehl]

In addition to what Bruce said - if you are looking for alternative ways to execute scripts via command line:

In my (paid) extension Automation Blocks I implemented a listener which allows to execute Automation Blocks scripts with HTTP Get requests.These requests can be created in all kinds of ways - also from the commandline using wget or curl, for example.

Automation Blocks can also execute jsx script files, so you could use this mechanism not only for Automation Blocks tools, but also to trigger execution of other scripts.

If you are looking for a free alternative, which does not rely on Automation Blocks, you can also use Premiere Remote, which offers a similar mechanism to trigger jsx scripts via http requests. It is a bit more complex to configure and install than Automation Blocks, but can be customized to execute any jsx code within Pr.

[h1tman2]

> /C es.processFile doesn't work with 2024 Premiere Pro

I've confirmed that it does. 🙂

Command line scripting can work, but it is definitely NOT a recommended workflow, for a variety of reasons. CEP panels remain the recommended and supported way to invoke ExtendScript in PPro.

By @Bruce Bullis

"C:\Program Files\Adobe\Adobe Premiere Pro 2024\Adobe Premiere Pro.exe" --console es.ProcessFile "C:\Users\gmosc\GitProjects\AdobeScripting\auto_import_sequence.jsx"

 Error: Path not found, but path is ok

I tied also with \C flag (on palce of --console) but nothing

[Bruce Bullis · Accepted solution]

"C:\Program Files\Adobe\Adobe Premiere Pro 2024\Adobe Premiere Pro.exe" /C es.processFile C:\Users\bbb\Desktop\test.jsx

[h1tman2]

It's ok now i wrote es.ProcessFile wirh P instead p , tnx so much

[laveda_9072]

Why do people write script?  To automate stuff that they don't have to sit and click buttons.  I get that its not recommended, but I don't care about your opinion as much as getting it to work how it did before.  Can you not just provide an answer to the question?

This no longer works when it did before:

"C:\Program Files\Adobe\Adobe Premiere Pro 2023\Adobe Premiere Pro.exe" es.processFile "C:\LavedaJones\VideoList\00.3 TestWorkspace\SplitPodcast.jsx"

[laveda_9072]

Then help out here.. sounds like your users are not getting the same results.  Explain how you got it to work instead of just providing a "write-off" answer.

[Bruce Bullis]

Are you still targeting PPro 23.x, for script execution?

 "C:\Program Files\Adobe\Adobe Premiere Pro 2023\Adobe Premiere Pro.exe"