Open additional window when opening multiple projects from extendScript.

[runag19091910]

I'm running app.openDocument(premiere_project_path) to open a project. That is working well. But if I already have project open it will close that and open the new project in it's place. Is there a way to open projects in a new window if another premiere instance is already running?

[Bruce Bullis · Accepted solution]

You never, ever want multiple PPro instances running.

PPro supports multiple open projects; in what version are you testing?

[runag19091910]

Hm, ok. Probably misunderstood something.

Thank you

[Bruce Bullis]

No problem; let's figure it out! What version of PPro are you running? [Check the about box, not "CC 2017"...]

What's the entire workflow you'd like to support?

[runag19091910]

CC 2018. Though I tested opening the projects by hand and have them open in separate windows, but testing again I do not get that, so I must be mistaken. Since that does not seem possible I think I have all functionality that I need at the moment.

[runag19091910]

Actually I do need help with something. So I write a batch script which I then call to open premiere. But when one is already open the calling of that script is not working. If I open the file in extendScript Toolkit and then run it everything works and I get two project tabs or whatever they are called.

This is the error message I get when I already have a project open. Do I need to run it differently when I have that?

[Bruce Bullis]

Is that where the file tmp4ycue4.jsx actually lives?

Also, passing scripts on the command line is a terrible, not-at-all-recommended way to drive PPro. Panels are definitely the way to go.

[runag19091910]

Yes the file is there, with that path.

[Bruce Bullis]

"C:\Program Files\Adobe\Adobe Premiere Pro CC 2018\Adobe Premiere Pro.exe" /C es.processFile "C:\example\script.jsx"

[n.abola]

Bruce Bullis, how I can run this code on CC 2017?

It does not work.

"C:\Program Files\Adobe\Adobe Premiere Pro CC 2017\Adobe Premiere Pro.exe" /C es.processFile "C:\example\script.jsx"

It shows Open Project dialog in Premiere.

I think that Premiere 2017 does not understand  "/C" parameter.

I tried to place extendscriptprqe.txt  at C:\Program Files\Adobe\Adobe Premiere Pro CC 2017 folder but it did not help.

[Bruce Bullis]

Try changing PPro's preferences to open the most recent file, instead of showing the open project dialog. Your script should work.

[n.abola]

It works if there are no running instances of Adobe Premiere, but if I open a project and then run this code

"C:\Program Files\Adobe\Adobe Premiere Pro CC 2017\Adobe Premiere Pro.exe" /C es.process "alert('test');"

then Premiere shows Open Project dialog with content "This file path does not exist on disk at this location. /C es.process "alert('test');".

[Bruce Bullis]

That seems right, in that you're passing raw ExtendScript, not a path.

Passing scripts on the command line isn't a supported workflow, in the shipping version of Premiere Pro.

CEP Panels are the right place, from which to invoke scripts.

What workflow(s) are you trying to support? [Write me directly, if you'd like; b b b at adobe dot com]

[n.abola]

But the same situation is with sending path of script to opened project in Premiere.

if I open a project and then run this code

"C:\Program Files\Adobe\Adobe Premiere Pro CC 2017\Adobe Premiere Pro.exe" /C es.processFile "C:\example\script.jsx"

then Premiere shows Open Project dialog with content "This file path does not exist on disk at this location.  /C es.processFile C:\example\script.jsx.

I want to combine some autohotkey scripts with Premiere ExtendScripts.

For example run ExtendScript after showing Export settings window.

[Bruce Bullis]

Running scripts from the command line works...

"C:\Program Files\Adobe\Adobe Premiere Pro CC 2017\Adobe Premiere Pro.exe" /C es.processFile C:\test.jsx

...and is not officially supported.

> For example run ExtendScript after showing Export settings window.

Export settings, from what application?

Panels are the right approach, for such integration; invoking scripts from a command line, is not.

[n.abola]

I want automate changing scale of all footages on timeline before export.

Therefore I wait for creating Premiere export settings window, then close it and then run ExtendScript.

But I do not know why Running script from the command line do not work for me if Premiere is already running.

[Bruce Bullis]

You want to programmatically change the scale of footage on the timeline? What's your user's goal, in doing so?

[n.abola]

I have dv footages which are with black border.

And if I work in HD sequence I want to increase dv footages to 103% to remove that border.

As I understand I cannot monitor "placing new footage to timeline event" with API.

Therefore I decided to change motion of DV footages before exporting.

I can run ExtendScript through CMD like this:

"C:\Program Files (x86)\Adobe\Adobe ExtendScript Toolkit CC\ExtendScript Toolkit.exe" -run "C:\Users\macev\Documents\Adobe Scripts\test.jsx"

test.jsx

#target premierePro

alert("test");

But it will be good to run script without ExtendScript Toolkit.exe.

[Bruce Bullis]

Maybe the best script for your purpose, is no script...

Wouldn't you get correct results, without manually scaling, if you turned "Scale to Frame Size" ON, in the prefs?

[n.abola]

"Scale to Frame Size" is On.

But source DV footages are rendered with black border.

Therefore "Scale to frame size" does not help.

Can You please give me advice what should I test to make this code work:

"C:\Program Files\Adobe\Adobe Premiere Pro CC 2017\Adobe Premiere Pro.exe" /C es.processFile "C:\example\script.jsx"

May be there are some preferences?

It is strange that it works on Your system but does not on mine.

[Bruce Bullis]

Take the quotes off of the .jsx path.

"C:\Program Files\Adobe\Adobe Premiere Pro CC 2017\Adobe Premiere Pro.exe" /C es.processFile C:\test.jsx

[n.abola]

No. It does not work if there is running instance of Adobe Premiere..

[KathyRST]

Is there a way in Quark 2018 to open multiple projects as tabs across the top instead of individual windows? (Like InDesign)

[Jenna26538309v9zk]

I also have this question. Did you ever figure out a way to get tabs in Quark instead of individual windows?