Mimicing Photoshop Actions in Premiere

New Here ,
Jul 11, 2022 Jul 11, 2022

Copy link to clipboard

Copied

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

 

TOPICS
SDK

Views

25

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Jul 12, 2022 Jul 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 exter

...

Likes

Translate

Translate
Adobe Employee ,
Jul 12, 2022 Jul 12, 2022

Copy link to clipboard

Copied

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


Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 12, 2022 Jul 12, 2022

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jul 12, 2022 Jul 12, 2022

Copy link to clipboard

Copied

LATEST

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. 

 

 

 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines