KB doens't respond the same on new mac with sequoia

Hello, I just upgraded to a new M4 Pro Mac Studio running 15.6.1 and KB is not acting right. I have a ton of macros that are dual action: press once = action 1 and press and hold for 0.2s= action 2. In my previous system everything was working flawlessly. In this system unless I hold it for EXACTLY 0.2 seconds every single time (which is near impossible) the second action doesn’t work at all. What might be causing this behavior and how can I fix it?

Have you restarted? I had different issues when I upgraded to a new Mac with Sequoia and migrated my macros, and the issues were fixed by restarting.

You mean the computer and the software? I had the computer for a couple of weeks now so it’s been off and on everyday. Just in case, I just quit KB and opened it again and it’s as bad as before.

I did mean the Mac, though I may have also quit the Keyboard Maestro Engine (not the Editor), and I did an Apple Menu -> Restart when I rebooted the Mac.

I’ll try this now even though I’d imagine the shut down and boot would work the same way as the restart. Another peculiar thing in this new system is that the KB icon on the top bar keeps spinning. It didn’t use to do that.

If it's spinning, try turning on the debugger and see what's running. Most likely you have a macro that's running. Macros don't always behave exactly the same when you get new hardware (because some macros can be hardware specific) so you may have to investigate what's going wrong with your macros. If your macros have actions that work faster on a faster Mac, then that could cause issues.

So to answer your question directly, what might be causing this issue is having a faster Mac, and the way to fix it is to examine the macros and see what the issues are.

That’s it! The debugger (which I never used before) showed me a specific macro was firing non-stop and the reason is by mistake the mouse was assigned as the trigger. I just assigned the appropriate key and there is no spinning and it all works like it did before. Thank you so much, and for introducing me to the debugger!

2 Likes