Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Info: I made a thing! #147

Open
Hyyeve opened this issue Aug 28, 2021 · 3 comments
Open

Info: I made a thing! #147

Hyyeve opened this issue Aug 28, 2021 · 3 comments

Comments

@Hyyeve
Copy link

Hyyeve commented Aug 28, 2021

Hi! A while ago, I was inspired by this to make my own automation scripts for premiere
As a decent coder as well as a video editor, I also wanted to massively optimize and improve on the functionality I needed
I haven't actually made many scripts so far - to date, ApplyPreset has really been the only thing that I've found super useful -
but I decided to put my AHK code up on github too, incase it's useful to anyone.

Anyway, I just wanted to say a massive thanks for inspiring my to make my own automation scripts and macros for general use,
and if you - or anyone else - might find some VERY optimized (and a lot more organised!) functions useful, they're over in
this repo: https://github.com/Drakeyn/AdobeMacros :)

(I'm especially proud of my much simpler, near-instant ApplyPreset :>)

@TaranVH
Copy link
Owner

TaranVH commented Aug 30, 2021 via email

@Hyyeve
Copy link
Author

Hyyeve commented Aug 30, 2021

cCheck is defined in the line above - with ControlGetFocus, which returns the ClassNN of the currently focused control :D

And I remember you mentioning that before, but I haven't looked at it - I'll take a look, if there's a built in shortcut for it (or at least one that can partially replace the script) that'd be neat. ~ okay, just checked, yup, don't need that script anymore I guess

With regards to ApplyPreset, I'm not sure exactly what workflow you have with effects, so you might have to adjust the timings a bit - I have everything I use regularly in a custom presets bin, which I keep opened all the time, for easy access. With it open, premiere will update the list almost instantly when the script types in the name, and it will work with no sleep calls at all. HOWEVER, if it's not already open, or it's a default effect not in my custom bin, it takes premiere a lot longer to update the list properly, and I've been having occasional issues with it failing to open in time or the image search actually finding the WRONG preset, somehow. Right now I've re-added a sleep of about 130 just after sending the preset name, which seems to work pretty consistently for me, but it might vary for you.

@Hyyeve
Copy link
Author

Hyyeve commented Aug 30, 2021

~ I've just pushed my local changes, which include a bunch of fixes and other improvements

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants