Sysem beeps at function key presses, why?

Questions & Suggestions
1

The title says it all…
I have looked through all of my system prefs to see if function keys are used anywhere but they are not to be found. They seem to work as macro triggers but the beep is annoying, to say the least. All f-keys behave the same.

It seems to happen in most apps, but strangely not in Safari.

Any help with this would appreciated.

2

Is this when a macro is triggering?

If it is related to Keyboard Maestro, select Help ➤ Interactive Help, Something unexpected is happening and see if that finds anything.

You can also look in the log files (Help ➤ Open Logs Folder). For some serious errors, Keyboard Maestro will been when it gets the error.

3

It seems as though I can use the function keys as shortcuts in KM but I have an accompanying beep. However if the function key is used as a system shortcut for something then it doesn't beep.

I don't think KM is at fault here. I was just hoping that one of the gurus might be able to solve this…

4

I have something similar plague me now and then but not with function keys (which is a clue, I suppose).

In my case, it was usually some hidden (behind some bigger window) dialog waiting to be addressed with some key other than what I was typing.

Not wanting to risk confirming something, I just restart and the beep does not return.

5

Mine happens even after a reboot.

It means that if I want to use F1 thru F12 as hotkeys I have to put up with the annoying beep.

I am using Catalina 10.15.6 but it even happens if I boot up into Mojave 10.14.6.

Frustrating!

6

Just to confirm, is the Keyboard System Preference for using F1, etc. as standard function keys enabled?

7

Screen Shot 2020-08-15 at 11.55.42 AM
Screen Shot 2020-08-15 at 11.55.42 AM1122×290 34.5 KB

Yes it is. F1 works as a trigger for KM macros but the beep is there.

8

It is most likely something unique to your system.
I've been using F1 as a KM Macro trigger for several years, and never heard a beep out of it.
I would start by quitting the KM Engine, and see if pressing F1 still produces a beep.
If not, then start the KM Engine and do this:

  1. Search KM for all macros that use F1 as a trigger, using this:
    h:F1 -h:⌘ -h:⌃ -h:⌥
    • That will show only macros with F1 and F11-F19
    • Inspect to see if there are any macros that are being triggered that you did not expect
  2. You can also just review the recent-run macros using the Used image button.

Good luck, and let us know how it goes.

9

I think I have it figured out now.

I had used "device key" instead of "Hotkey" as a trigger. That led the OS to believe that F1 was not in use and then so beeps at me. If I use F1 as a "Hotkey" no beep and the trigger still works fine. It seems like the OS is aware of what keys are used as Hotkeys by various apps but that does not include device keys when used as a trigger.

That's a real education for me to be a bit more careful in both my wording and trigger selections.

I sincerely apologize for wasting people's time on this issue.

1 Like
10

No problem. Good lesson learned for all of us.
I'm glad your problem is resolved, and that you posted the solution.

1 Like