search

TaranVH / 2nd-keyboard

ALL of Taran's scripts - not just for the 2nd keyboard.
https://www.youtube.com/watch?v=O6ERELse_QY
1.66k stars 534 forks source link

Trying to find the Premiere Functions mentioned in the Lua Macros ahk #62

Closed noncompete closed 6 years ago

noncompete commented 6 years ago

I'm hopelessly new to this but learning slowly but surely so forgive me if I am misunderstanding something really basic

-- I went through the Intercept.exe setup and couldn't get it to work but I've got Lua Macros working.

Problem is, it seems like some files got deleted in the github that are being referenced in the Lua AHK script/readme?

Specifically it says in the readme:

"2nd keyboard if using luamacros.ahk only has bare functions for proof of concept. You can write your own functions, or copy/paste some from from All Premiere Functions.ahk, but you'll probably need to modify them to fit your own system, by changing coordinates, windowClasses, colors, shortcuts, and so on."

I found "Almost_All_Premiere_Functions.ahk" but none of the functions seem to line up with the functions mentioned in the Lua AHK file. For instance:

"preset("flip horizontal") " doesn't seem to be present anywhere in the Almost_All_Premiere_Functions.ahk file.

Am I thinking about this completely wrong or is there an older file I should be using if I'm trying to get it working with Lua?

TaranVH commented 6 years ago

Props to you for giving it a go even though you're in over your head a bit. It is indeed there. You're searching for the wrong thing. You ought to have searched for preset( And you'd have found this: https://github.com/TaranVH/2nd-keyboard/blob/5b49a23353d47a6896fbf7a8785de76306bffe7f/Almost_All_Premiere_Functions.ahk#L301

You see, what's inside of the parentheses is called a "parameter." It can be almost anything... a string, a number, a variable...

Anyway, just copy (currently) lines 296 to 404, and paste it into your own AHK script. Read through it carefully and ensure that you have all the shortcuts it needs properly assigned in Premiere.

You'll also have to insert message boxes to debug the exact pixel positioning that the script uses to grab the presets themselves.

definitely take this whole tutorial if you haven't already. https://autohotkey.com/docs/Tutorial.htm

You should probably also look up some tutorials on strings, functions, and parameters. The fundamentals of scripting, really.

TaranVH commented 6 years ago

I actually suggest that you don't add the complication of a second keyboard before you even know the basics of AHK and my scripts in particular. Just assign stuff to F1, F2, F3, etc, to start.

F1::preset("crop half left") F2::preset("lumetri brighter")

Add a 2nd keyboard once you run out of function keys.

Be wary not to also have stuff assigned to those same function keys in Premiere, though!

noncompete commented 6 years ago

If you know what you're doing then what's the fun? :D In all sincerity, though, I have to say that I'm blown away by all the work you do in helping your fellow editors to improve our workflow. Really, hats off, you're doing an amazing job. Can't help but think that if Adobe had half the care and attention to detail that you have then our lives would all be a lot less frustrating, I'd imagine. I'll follow your advice and start with the F keys. Thanks again! Excelsior!

TaranVH commented 6 years ago

Adobe is actually starting to get it together. I'm not sure yet how much I can say publicly, but there's been a recent and impressive push to fix bugs in Premiere. Thanks! Now go make something cool!