Tips creating keyboard maestro macros - following on from my drum sampler question
6 views
Skip to first unread message
Brian Casey
Dec 31, 2020, 11:05:01 AM12/31/20
to ptac...@googlegroups.com
Hi all,
Last week I began searching for a solid drum sampler plugin for protools, and having now found what appears to be a good candidate, I hope to create a set of macros to access the buttons for loading samples and routing outputs.
The plugin I found is called Sitala, which is free to download, and it already has a lot of its useful functionality showing in the plugin window for its 16 sample pads, so I’m hoping to create a solid set of macros which may also be of use to others.
I’ve started reading through the keyboard documentation but its all quite new to me, so pointers or good habits for reliable voice over macros would be hugely appreciated.
Many thanks,
Brian
Sent from my smart-ish phone!
Last week I began searching for a solid drum sampler plugin for protools, and having now found what appears to be a good candidate, I hope to create a set of macros to access the buttons for loading samples and routing outputs.
The plugin I found is called Sitala, which is free to download, and it already has a lot of its useful functionality showing in the plugin window for its 16 sample pads, so I’m hoping to create a solid set of macros which may also be of use to others.
I’ve started reading through the keyboard documentation but its all quite new to me, so pointers or good habits for reliable voice over macros would be hugely appreciated.
Many thanks,
Brian
Sent from my smart-ish phone!
Slau Halatyn
Dec 31, 2020, 12:55:56 PM12/31/20
to PTAccess List
Hi Brian,
The key to creating reliable Keyboard Maestro macros is to learn, as completely and as accurately as possible, the exact behavior of the user interface you're trying to control. For example, if there are potentially several tabs that might be active, you'll probably need to account for that and ensure that any given tab is active when it needs to be and inactive when you don't want it to be. Image recognition can be used to some degree and, when it works, it's great but, when it doesn't work, it's really not great. The developer of Keyboard Maestro maintains that image recognition is the least reliable way to control a UI. That's why, with Flo Tools, the scripts are relying on system objects and the Pro Tools UI which is extremely reliable. All that said, perhaps all you need is to consistently be able to click certain parts of a window that might possibly bring up an accessible menu and submenu structure. If so, then Keyboard Maestro would probably do the trick. Again, (and I can't stress this enough) the more you know about the UI you're trying to control, the better. Feel free to drop a line off list and we can chat about it some more.
Cheers,
Slau
> --
> You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+u...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/B02A0C8B-D2DE-4A66-9D4B-6756E2245E03%40wavefieldrecordings.com.
The key to creating reliable Keyboard Maestro macros is to learn, as completely and as accurately as possible, the exact behavior of the user interface you're trying to control. For example, if there are potentially several tabs that might be active, you'll probably need to account for that and ensure that any given tab is active when it needs to be and inactive when you don't want it to be. Image recognition can be used to some degree and, when it works, it's great but, when it doesn't work, it's really not great. The developer of Keyboard Maestro maintains that image recognition is the least reliable way to control a UI. That's why, with Flo Tools, the scripts are relying on system objects and the Pro Tools UI which is extremely reliable. All that said, perhaps all you need is to consistently be able to click certain parts of a window that might possibly bring up an accessible menu and submenu structure. If so, then Keyboard Maestro would probably do the trick. Again, (and I can't stress this enough) the more you know about the UI you're trying to control, the better. Feel free to drop a line off list and we can chat about it some more.
Cheers,
Slau
> You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+u...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/B02A0C8B-D2DE-4A66-9D4B-6756E2245E03%40wavefieldrecordings.com.
Reply all
Reply to author
Forward
0 new messages