CreateMacro no response to typing hotkey

True one of these:

By the way, when you want to add an action, I prefer Ctrl+Cmd+A, which equates to Edit->Insert Action->By Name. If you do this then type in "volume", you'll see a bunch of different options.

Hi,

I tried Increase System Sound Volume. It triggers both Brightness Up and
Volume Up just like the original mapping.

I tried Increase Current Movie Volume by 10%. It triggers only
Brightness Up.

When I get back to the Mac Pro I will try these again. They are quite
irrelevant on the Air because I rarely use it with an external keyboard.

Dan

Does it do that on both computers, or just the one?

Don’t know until I get home.

Did you try some other hotkeys? Maybe those have conflicts. Try something totally different, like Control+Option+Command+V, or something strange.

Try the application mentioned here:

Sounds like it might help diagnose the problem.

Hi,

I'm back on the Mac Pro with the Unicomp PC Keyboard. have remove all
remapping-related stuff except KM.

I have created the attached macros.

and I have run KeyCode:
Key Down
Characters: 
Unicode: 63273 / 0xf729
Keys: :arrow_upper_left:
Key Code: 115 / 0x73
Modifiers: 8388864 / 0x800100 ⓘ

Key Up
Characters: 
Unicode: 63273 / 0xf729
Keys: :arrow_upper_left:
Key Code: 115 / 0x73
Modifiers: 8388864 / 0x800100 ⓘ

Key Down
Characters: 
Unicode: 63275 / 0xf72b
Keys: :arrow_lower_right:
Key Code: 119 / 0x77
Modifiers: 8388864 / 0x800100 ⓘ

Key Up
Characters: 
Unicode: 63275 / 0xf72b
Keys: :arrow_lower_right:
Key Code: 119 / 0x77
Modifiers: 8388864 / 0x800100 ⓘ

KeyCode apparently cannot trap the F13, 14, or 15 keys on the Mac Pro.

Pressing home brings the beginning of the document into view but does
not reposition the cursor. Pressing End brings the end of the document
into view but does not reposition the cursor.

On the Air with an HP keyboard connected. the Home and End remappings
worked as expected but the F14 and F15 mappings triggered both
brightness Up/Volume up and brightness down/volume down.

Both sets of behavior are not what one would expect.

btw, the Mac Keyboard Identifier app that runs when I plug in these
keyboards is unable to identify either of them. It used to be able
recognize these keyboards when I was running on Yosemite.

Dan

__Keyboard Remapping Macros.kmmacros (20.9 KB)

Also, on the Mac Pro, remapping F13-15 to control the voluume works fine.

Does anyone have any additional thoughts on this?.
I’m dead in the water until a solution is available.

Thank you

In the System Preferences, Keyboard, Shortcuts, Display preferences, there are settings for Increase/Decrease Brightness.

On my Mac, they are disabled, however on my Mac, with them disabled, if I press Control-F14/Control-F15 with Sierra it does the brightness up/down regardless.

Maybe it is a Sierra bug, I have no idea.

Sierra certainly has its share of bugs. The frequent freezing that Macbook Pro has been experiencing is a bigger problem than erratic keyboard behavior. Do you have a maintenance release of KM planned any time soon?

Maybe, but not to resolve any kind of Sierra issue like you are describing.

. . . and lack of compatibility with some applications, or design changes that affect how it behaves with apps.

That's why I almost always wait at least several months (sometimes up to a year) after a release before I install major updates to any OS.

Using broken stuff keeps me attuned to what users really need and equips me to give advice like “wait a few months before upgrading”. I use the macs primarily because the way they render text on the screen is easier for me to read. When I need reliability I use windows. I have a variety of machines available (6 PCs, 5 Macs, 3 iPads and an Android tablet) and a bunch of VMs with linux and older versions of windows (going back to windows 98) so I’m rarely without a way to get something done.

Mac screens not withstanding, I considered Mac to be essentially unusable until they enabled resizing windows some place beside the right lower corner and the Mac laptops only when I was able to remap a key (like F12) to do forward deletes. My day ends up with iPad in the morning, windows in the afternoon and the Mac in the evening and, if I need access to an OS specific function I just remote to one of the other machines using VNC or RDC.

As you can see, getting any particular key remapped is only essential to prevent annoyance, so I can wait while Sierra gets sorted out.

We have been able to resize Mac windows from any corner for a long time now (years). I think maybe since Mt. Lion.

That's funny! :smile:

I have used both Windows and Macs for many years (decades) now, and find the Macs are far, far more stable than Windows. Like most Windows users, I have suffered many "blue screens of death".

But then I don't load up my Mac with a lot of apps/utilities/system changes that try to make the macOS do stuff it doesn't really support. I find that with tools like Keyboard Maestro, LaunchBar, AppleScript/JXA, Typinator, etc I can highly automate my Mac and still have a very stable OS.

I've been running Keyboard Maestro 7+ on macOS 10.11+ (El Capitan) for about a year now, and it works really great. macOS Sierra does not provide me with any compelling reasons to update, so, as usual, I'll wait a few months until all the kinks are worked out, and all of my essential apps are fully supported.

To each his own. There is always a price for being on the bleeding edge. :wink:

Of course, but that was after my Mac classic and my Mac II FX drove me nuts.

In reading though this thread I didn't see any mention of this setting in the System Keyboard Prefs:

It should be checked if you want to use bare Function-Keys for keyboard shortcuts.

-Chris

it’s checked

Have you tried to boot in Safe Mode? (Hold down Shift after the startup sound.)

Amongst other things Save Mode disables certain kernel extensions and all Login Items, and it deletes kernel and system caches.

While in Safe Mode you have to launch KM Engine manually: Open KM Editor > File > Launch Engine.
Then try if something has changed. Then reboot in normal mode and try again.

Thanks, I’ll give it a try