Hotkeys Stop Working - OBS 28.xx

pakpenyo

New Member
Any news on this?
I only experienced it while streaming.

Input monitoring: ON.
Never disable hotkeys: ON.
Macmini M1, latest OBS, latest Sonoma.
 

jremitz

New Member
Thanks for replying. I didn’t notice it yet on 30.1.2 but I just installed it and only streamed twice since then.

General observation although it might have been coincidental: the last time I experienced this bug I was cleaning up replay files before going live. Probably coincidental but just calling it out. Since I last saw it I have been making a habit of restarting my laptop before streaming and thus far I haven’t experienced it. Again, probably coincidental but sharing.

Also, while I’ve tried restarting my replay buffer which has never helped, I did notice that if I go in and remap my save replay buffer hotkey, it’s good for exactly one instant replay save. It then stops working until I go into settings and remap the hotkey again. I can do that as many times as I want to try to save a few replays while I’m streaming but it’s very distracting and unmanageable.

Just wanted to share in case it helps hone in on the issue.
 

pakpenyo

New Member
Thanks for replying. I didn’t notice it yet on 30.1.2 but I just installed it and only streamed twice since then.

General observation although it might have been coincidental: the last time I experienced this bug I was cleaning up replay files before going live. Probably coincidental but just calling it out. Since I last saw it I have been making a habit of restarting my laptop before streaming and thus far I haven’t experienced it. Again, probably coincidental but sharing.

Also, while I’ve tried restarting my replay buffer which has never helped, I did notice that if I go in and remap my save replay buffer hotkey, it’s good for exactly one instant replay save. It then stops working until I go into settings and remap the hotkey again. I can do that as many times as I want to try to save a few replays while I’m streaming but it’s very distracting and unmanageable.

Just wanted to share in case it helps hone in on the issue.
I've ready testing with one hour streaming, there's no problem. But, we'll see for 4-6 hour streaming. And I change the key to switch scene with shift (shift+1, shift+2, etc) rather than 1,2, etc.
 

insomnia_io

New Member
Created an Account on this forum just to keep me updated on this issue. Switched to Mac OBS this week. Have the exact same issue. Hotkeys randomly stop working. When I notice that a Hotkey doesn't work anymore, every other hotkey I have stays usable ONCE. This is far beyond my comprehension.
Going to downgrade to v27.x and hope the rest of my streaming-setup stays fuctioning.

Hopefully it will be fixed, even 2 years after the bug was introduced.
 

AaronD

Active Member
When I notice that a Hotkey doesn't work anymore, every other hotkey I have stays usable ONCE.
Ooo! THAT'S a good detail to include! It's not a complete solution of course, or a direct pointer to the problem, but it starts to suggest what the problem might be under the hood. That's FAR better than just, "it doesn't work." Thank you!

To me, it suggests that there's supposed to be an "edge detector" somewhere that for some reason stops (accurately) recording the previous state. Something like:
C-like:
if (status && !status_prev)
{
    do_something();
}
status_prev = status;
That's supposed to do_something() only when status *becomes* true, and not constantly while it's true. And as-written here, it usually does. It might be tempting though, to write it like this, which *almost* works:
C-like:
if (status && !status_prev)
{
    status_prev = status;
    do_something();
}
See if you can figure out how it breaks, or how the first one might break. And how you might fix either one and how that fix might break. Also consider the addition of other logic into the same if(...), which is normally in a state that has no effect on the condition shown here, but sometimes it changes to the other state...

Based on just your description, I suspect that something along those lines is happening *somewhere*. It could be in OBS, or it could be in the OS somewhere, with the way it handles keystrokes.
 
Last edited:
Top