You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a RPi zero as the client (version 1.0.0 EA 3) in desktop mode and windows 10 as the server (also version 1.0.0 EA 3). I'm able to successfully use F1 through F12 as hotkeys in OBS (along with the specific OBS functions), but F13 through F24 don't appear to be sent to OBS. I also tried using a browser-based keyboard tester and saw the same results. FYI, I have been setting (for example) F13 in the key combination field of the server's Hotkey definition with zero milli-seconds delay. In searching through Google, I thought this issue had been raised and addressed before, but I don't see it in either the current server or client issues.
The text was updated successfully, but these errors were encountered:
As I mentioned in my first message, I also tried using a browser-based keyboard tester. It detected keys F1 through F12, but not F13 through F24. I'm suspecting that the key codes for F13-F24 on Windows may not be the same as the key codes on Linux. The reason may be related to the scancode sets in use. See http://www.quadibloc.com/comp/scan.htm for a comprehensive discussion of scancode sets and how different keyboards alter the scancode of each key.
I'm using a RPi zero as the client (version 1.0.0 EA 3) in desktop mode and windows 10 as the server (also version 1.0.0 EA 3). I'm able to successfully use F1 through F12 as hotkeys in OBS (along with the specific OBS functions), but F13 through F24 don't appear to be sent to OBS. I also tried using a browser-based keyboard tester and saw the same results. FYI, I have been setting (for example) F13 in the key combination field of the server's Hotkey definition with zero milli-seconds delay. In searching through Google, I thought this issue had been raised and addressed before, but I don't see it in either the current server or client issues.
The text was updated successfully, but these errors were encountered: