I'm using my Stream Deck with KMlink to control macros in Keyboard Maestro. KM is sending actions with an ID to Reaper (a DAW). Everything is working fine until at random moments Keyboard Maestro stops sending messages. Other The things that work to get KM working again are:
A. Waiting for like 10 mins.
B. Rebooting Reaper.
Anyone had this behavior before? And how to solve it?
The first thing you should do is check the Engine.log file, which likely contains an error message when everything stops.
Another thing you can do is open the debugger and validate that you don't have extra macros running. You see, there's a 50-macro limit. If you have more than 50 running at the same time, every macro stops immediately.
P.S.. What's "Reaper"?
P.S. What does this mean: "It not only stops sending messages to Reaper"?
P.S. Does "The thing that works are" mean that that's how you fix the problem?
Thanks! I've edited my post to be a bit more clear. This is what I'm getting back.
curl: (56) Recv failure: Connection reset by peer. Macro “Reaper - Hide Empty tracks under selection” cancelled (while executing Execute Shell Script).
2025-05-30 12:15:40 Execute macro “Reaper - Hide Empty tracks under selection” from trigger Do Script
2025-05-30 12:15:40 Action 4001 failed: Execute a Shell Script failed with script error: % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 8080 after 0 ms: Couldn't connect to server
Trying to find a solution within Reaper with the help of ChatGPT
That's probably helpful information, but I don't think I can do much with it. It sounds like your web server isn't responding. That's not really a Keyboard Maestro issue. But I'm not sure. It might help if you share your macro.
It's not the KM is failing to send the message -- Reaper isn't listening for it.
So it looks like a problem with Reaper's internal web server -- see also this Forum post.
One for the Reaper team, I guess -- although you could use KM to quit/relaunch Reaper whenever this happens or, if Reaper does recover after some time, pop up a "Stop and Wait!" notification and keep resending the message until it goes through then carry on as normal...