Is there a way to launch one time use .Jsx script files like you can in After effects?

[Ralf31824961sf2k]

In After Effects, you can place .Jsx script files at C:\Program Files\Adobe\Adobe After Effects 2023\Support Files\Scripts
Then on the next time you load the program, you can find the scripts on the main menu bar, File > Scripts.

I am looking for Premier Pro's equivalent of this features. I have looked at its program files directories, there is a scripts folder there, with a similar structure to AE:

C:\Program Files\Adobe\Adobe Premiere Pro 2023\Scripts
C:\Program Files\Adobe\Adobe Premiere Pro 2023\Scripts\Startup
C:\Program Files\Adobe\Adobe Premiere Pro 2023\Scripts\Hello World.jsx

I have placed the Hello World.Jsx file, there but I am not been able to find a way to launch the script within Premier itself.

I have searching everywhere on how to do THIS specifically. I have comes across two solutions.

1. To use a hidden CEP panel to communicate with Premier Pro
2. To run .Jsx code from the command line with Premiere, PremPro /C es.processFile "C:\TEMP\Test.jsx"

For the first solution, the learning curve and time needed to set this up is simply too steep. The second, it will only work on Premier when its first about to open, not on a already running Premier instance.

I just want to run simple scripts from within Premier, like you can out of the box with

- Photoshop
- Illustrator
- After Effects

I don't mind granting any "script execution" security permissions.

Thank you for any help.

[Bruce Bullis · Accepted solution]

CEP panels are the correct and supported approach to executing ExtendScript, within PPro. We have no plans to change that. 

There are pitfalls to the command line approach that make it unattractive (and unsupported). What is it you're trying to accomplish, with your stand-alone scripts? 

Yes, there's a learning curve for panel development; we have hundreds of panel developers who've succeeded, so we're optimistic you can also be successful. We're happy to help with any specific questions.

[Ralf31824961sf2k]

@Bruce Bullis 

Well first of all thank you for the conclusive answer, now I know what end is futile.

I don't mind learning and figuring out these things, I have been at this for two days now and I just seem to be going back and forth with no progress.

I have been searching allot from Medium Articles/QnA forums/Articles by Adobe but it seems Adobe itself is in the middle of a transition from the old way of doing things to a new way. So allot of written material seems to be redundant and others I am not sure of them.

There are pitfalls to the command line approach that make it unattractive (and unsupported). What is it you're trying to accomplish, with your stand-alone scripts?

By @Bruce Bullis

I am looking for a means to perform standard Premier Pro operations as well as get real time information from Premier , for use in a external process.

This way I can use my existing interfaces with Premier. I already do these sorts of things with other packages. The external process itself is not so important, I am just looking for a known standard means to execute Premiere commands externally and to also request information from Premiere.

"I admit launch one time use .Jsx script files" is short of this, this was just what I settled for, because I was getting nowhere.

Allot of the answers I am coming across is to use a hidden panel as a medium between my software and Premier. But other than that I have not been able to find anything on where I can learn more about this method.

I was able to finally able get this panel PProPanel working. It does I want, only that its a graphical window whose buttons I have to press to get something to happen.

I would love to have an example, like the above project, but for "hidden panels" that can be used to communicate with Premiere.

Cheers.

[Bruce Bullis · Accepted solution]

Hidden PPro Panel = replace the lifecycle section of PProPanel's manifest, with this: 

        <Lifecycle>
          <AutoVisible>false</AutoVisible>
          <StartOn>
            <!-- PPro dispatches this event on startup -->
            <Event>com.adobe.csxs.events.ApplicationActivate</Event>
          </StartOn>
        </Lifecycle>

[laveda_9072]

Just like Adobe to deprecate something that worked well and replace it with something that doesn't.  Way to go Adobe (worst development company ever).