Skip to main content
J
Jonas Almeida - Jonas
Participant
July 11, 2022
Answered

Mimicing Photoshop Actions in Premiere

  • July 11, 2022
  • 1 reply
  • 707 views

I got tired of doing the same stuff over and over for every pack of videos I had to edit.

I then decided to live this to robots!

In this version, my script asks me what I want to do and it does in a flash. It's the same as recording an action and pressing play!

The recording bit is a bit more painful process thought as it's all done in text 😛

If only the SDK were a bit better, we could have this inside or PR

 

This topic has been closed for replies.
Correct answer Bruce Bullis

>  I believe the SDK misses documentation in general, examples etc.

 

Here's the PProPanel sample, which exercises all of PPro's ExtendScript API: 

https://github.com/Adobe-CEP/Samples/tree/master/PProPanel

Here's public documentation of those APIs: 

https://ppro-scripting.docsforadobe.dev

Here's public documentation about ExtendScript development: 

https://extendscript.docsforadobe.dev


> I've tried to use the SDK with the ExtedScript Toolkit in the past and the interface
> with the software is external, so I was always facing issues connecting it, lags and

> errors that I could not solve.


ExtendScript Toolkit was retired years ago; Adobe's ExtendScript debugger for Microsoft Visual Studio Code is the right approach. 

https://extendscript.docsforadobe.dev/vscode-debugger/getting-started-with-vscode-debugger.html

> I did manage to get a plugin running and performing some tasks, but it was taking so much

> effort to export/import the plugin files and make it work due to the components naming

> conventions that are non intuitive.

I'm not sure which naming conventions were problematic(?); we're always happy to help with specific questions.

> Doing it with Python took me a couple minutes to have it running as it's working visually.

While Python can be made to cooperate, PPro's API is in ExtendScript (JavaScript). I imagine you must be using keystrokes, which is a very fragile approach.

 

PPro's API already provides the effect and component names you mentioned. 

 

 

 

1 reply

Bruce Bullis
Bruce Bullis
Legend
July 12, 2022

Specifically, what do you think needs to be 'better', in the SDK? What's missing?


Both MamoWorld and Knights of the Editing Table already ship extensions, that parallel the functionality in your video. 

https://mamoworld.com/docs/automation-blocks/tools-pr/overviewToolsPr

https://knightsoftheeditingtable.com/excalibur


    J
    Jonas Almeida - JonasAuthor
    Participant
    July 12, 2022

    Hi Bruce, I believe the SDK misses documentation in general, examples etc.
    I'm not a programmer, but I do know my way around the code 🙂

    I've tried to use the SDK with the ExtedScript Toolkit in the past and the interface with the software is external, so I was always facing issues connecting it, lags and errors that I could not solve.
    I did manage to get a plugin running and performing some tasks, but it was taking so much effort to export/import the plugin files and make it work due to the components naming conventions that are non intuitive.

    Doing it with Python took me a couple minutes to have it running as it's working visually.
    If you look at Nuke for example, the fx and fields components names are easy to find and therefore easy to code.

    Bruce Bullis
    Bruce BullisCorrect answer
    Legend
    July 12, 2022

    >  I believe the SDK misses documentation in general, examples etc.

     

    Here's the PProPanel sample, which exercises all of PPro's ExtendScript API: 

    https://github.com/Adobe-CEP/Samples/tree/master/PProPanel

    Here's public documentation of those APIs: 

    https://ppro-scripting.docsforadobe.dev

    Here's public documentation about ExtendScript development: 

    https://extendscript.docsforadobe.dev


    > I've tried to use the SDK with the ExtedScript Toolkit in the past and the interface
    > with the software is external, so I was always facing issues connecting it, lags and

    > errors that I could not solve.


    ExtendScript Toolkit was retired years ago; Adobe's ExtendScript debugger for Microsoft Visual Studio Code is the right approach. 

    https://extendscript.docsforadobe.dev/vscode-debugger/getting-started-with-vscode-debugger.html

    > I did manage to get a plugin running and performing some tasks, but it was taking so much

    > effort to export/import the plugin files and make it work due to the components naming

    > conventions that are non intuitive.

    I'm not sure which naming conventions were problematic(?); we're always happy to help with specific questions.

    > Doing it with Python took me a couple minutes to have it running as it's working visually.

    While Python can be made to cooperate, PPro's API is in ExtendScript (JavaScript). I imagine you must be using keystrokes, which is a very fragile approach.

     

    PPro's API already provides the effect and component names you mentioned. 

     

     

     

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices