Macro works with "try" in editor, but not in target App

Questions & Suggestions
1

Hello all, I'm new to KM and happy to find this community.

I am trying to make some basic short cuts inside pro tools and I have successfully created a macro that works when I use the "try" option in the KM editor but does not work inside Pro Tools.

Any idea why this could be happening?

Happy to provide more info if that can help diagnose

30%20PM
Screen Shot 2019-08-05 at 7.27.30 PM.png966×654 74 KB

2

is the Charlie Pro Tools group set to only be active in certain situations? Can you provide a screenshot of the Charlie Pro Tools group details?

3

I can't really tell why the macro is not working, but I can tell you do not need Keyboard Maestro for this kind of shortcut. You can get the same result (selecting menu items) by creating a macOS custom shortcut.

  • Open System Preferences
  • Open Keyboard Preferences
  • Select "Shortcuts" tab
  • Select "App Shortcuts" at the bottom of the list
  • Click on the + Button
  • Select the Application you want for this Shortcut
  • Type the Menu title Exactly as it is
  • Click the Keyboard Shortcut field and do your combination to capture it
  • Click Add
4

13%20PM
Screen Shot 2019-08-06 at 4.35.13 PM.png957×647 51.7 KB

5

Thanks for the advice. I think the issue Isn't with KM or OS shortcuts but has to do with activating plug ins inside the AudioSuite Menu, because I am successfully making hot keys that work the same way on other nested menu items. Though I'm still not sure why is would work with the try button

Are you a PT user? Have you dealt with any issues like this before?

6

46%20PM

Ok I figured out a work around. Basically this makes it open the menu then look again for the next menu that drops until it gets all the way to the target. it might be a weird crazy work around but it works beautifully!

7

I have not experienced this issue before, but it is nice to see you figured out a way around it. I am guessing the sub-sub-menu is populated dynamically so it is not really available for the hotkeys system :man_shrugging:t2:.

8

Cross platform applications, including Finale and many Adobe applications, do not necessarily update or even build their menu bar until the menu is selected with the mouse. When asked for the menus via the accessibility subsystem, the menus are either not there, or not currently correctly built for the context (eg, menus may be disabled or invisible when they should not be).

One option, as you discovered, is to use the Show Menu variant (leave the item field blank) of the Select Menu Item action to show the menu item first, and then the Select Menu Item.

9

Me too i suspect that the group that this macro is in,Charlie ProTools, has some rules that forbids it to work.